SEW Eurodrive MOVIDRIVE

No fault is currently active within the drive system. The MOVIDRIVE® unit is operating normally without any detected issues. This status indicates a healthy system state, requiring no immediate intervention.

This PROFIBUS-DP additional code (Error Class 8, 'Other Error') indicates successful parameter setting with no error detected. This is a confirmation of correct communication in the parameter channel.

Immediate shut-off due to a short circuit at the inverter output, an oversized motor connected, or a faulty output stage within the inverter. This condition can lead to component stress and potential damage to the drive.

This PROFIBUS-DP additional code (Error Class 8, 'Other Error') means parameter access was attempted via an incorrect communication interface. This specific parameter requires access through the RS-485 diagnostic interface, and the current access method is not permitted.

This PROFIBUS-DP additional code (Error Class 8, 'Other Error') indicates a parameter setting was attempted for a parameter that is currently protected from modification. This protection mechanism prevents unauthorized or accidental changes to critical operational parameters.

This PROFIBUS-DP additional code (Error Class 8, 'Other Error') means an attempted parameter change requires the drive inverter to be in a 'controller inhibit' state before modification can be applied. The inverter is currently enabled, preventing the parameter change.

This PROFIBUS-DP additional code (Error Class 8, 'Other Error') indicates the value supplied for a parameter setting is logically invalid, even if it numerically falls within the acceptable range. This suggests a mismatch with the parameter's expected states or enumerations.

This PROFIBUS-DP additional code (Error Class 8, 'Other Error') is an informative message indicating a command or condition triggered the activation of the drive inverter's factory settings. This signifies a system reset to default configurations.

Immediate shut-off caused by a ground fault detected in the incoming power cable, within the inverter's internal circuitry, or in the motor windings. This poses an electrical safety hazard and can damage equipment.

Immediate switch-off indicating an issue with the braking system, such as excessive regenerative power, an interrupted braking resistor circuit, a short circuit in the braking resistor circuit, a braking resistor with too high resistance, or a defective brake chopper. A ground fault could also be a contributing factor.

A communication error has occurred within the inverter system, specifically between the fieldbus interface and the inverter system itself. This may prevent the requested parameter service from being executed and often indicates a temporary internal data exchange issue. The error class is 'Access' and error code is 'Hardware fault'.

During a write service via the parameter channel, an incorrect data length was specified (other than 4 data bytes). This error is generated by the fieldbus card's communication software and indicates a mismatch between the expected data size and the actual data provided for a parameter. This prevents correct parameter configuration.

Immediate switch-off triggered when the DC link voltage exceeds its maximum permissible limit. This is often caused by excessive regenerative energy from the motor during deceleration or potentially a ground fault, risking damage to inverter components.

Immediate switch-off because the speed controller or current controller is operating at its setting limit. This can be due to mechanical overload, a phase failure in the power supply or motor, an incorrectly connected encoder, or exceeding the maximum speed (nmax) during torque control.

The parameter being accessed is restricted to modification or reading solely through the RS-485 diagnostics interface. Attempts to access this parameter from any other communication interface will be rejected. This limitation is typically for parameters related to diagnostics or maintenance.

The parameter is currently protected by an access mechanism, such as a password, a specific user level, or an operational state. This protection prevents unauthorized or accidental modification of the parameter's value. Any attempt to write to it without proper authorization will be rejected.

The requested parameter change or action cannot be performed while the inverter's controller is active (enabled). For safety or operational integrity, this parameter requires the controller to be inhibited (disabled) before modification. Attempts to change it during active control will result in this error.

The value provided for the parameter is invalid, not necessarily because it's outside the numerical range, but due to an incorrect format, data type, or unsupported option. This means the input does not conform to the parameter's expected structure or choices. The inverter rejects the invalid value.

The parameter index specified in the communication request is invalid or not recognized by the inverter. This implies an attempt to access a non-existent parameter or a typo in the parameter address. This error is returned under error class 8 (other error) and prevents the requested parameter operation.

The specific function or parameter being requested is not implemented in the current inverter's firmware or hardware configuration. This can occur if the inverter unit does not support a particular feature, or if a required optional module is missing. The requested operation cannot be performed.

An attempt was made to write data to a parameter that is configured for read-only access. This parameter's value cannot be altered via communication, either by design or due to its current operational state. The write operation is rejected.

The parameter being accessed is currently locked, preventing any modification. This lock can be activated by the system's operational state, security settings, or a specific user program. Any attempt to change the parameter will be rejected until the lock is released.

This indicates that the inverter is currently operating with its default factory settings. While not an error in itself, it confirms that custom parameterization may not be active or an attempt to write a specific parameter has been rejected because factory settings are overriding it. The system is in a default state.

The value provided for the parameter exceeds its defined maximum permissible limit. This means the requested setting is outside the operational or hardware capabilities for that specific parameter. The parameter value is rejected and not applied.

The value provided for the parameter is below its defined minimum permissible limit. This means the requested setting is less than the smallest allowed value for that specific parameter, often due to physical limitations or control stability requirements. The parameter value is rejected.

The function or parameter being accessed requires a specific option card to be installed in the inverter, which is currently absent. This hardware dependency prevents the requested operation from being executed. The feature associated with the missing option card cannot be utilized.

An internal error has occurred within the inverter's system software. This could be caused by temporary disruptions, corrupted firmware, or a fault in the hardware components supporting the software. This critical error affects the inverter's operational integrity.

The parameter being accessed is restricted to modification or reading solely through the RS-485 process interface (X13). Attempts to access this parameter from any other communication interface will be rejected. This is often a design choice for critical process parameters.

Immediate switch-off indicating that the inverter has not been properly commissioned or 'taken into operation' for the currently selected operating mode. This prevents the drive from starting or functioning as intended.

This PROFIBUS-DP additional code (Error Class 8, 'Other Error') signifies the drive inverter received a parameter setting request with an invalid or non-existent parameter index. This suggests a misconfiguration in the parameter channel, potentially preventing proper drive operation.

Emergency stop caused by an incorrect command detected during the execution of the IPOS plus® program, incorrect conditions for command execution, or an attempt to use a function not supported by the inverter. This points to a logical error in the PLC program.

This PROFIBUS-DP additional code (Error Class 8, 'Other Error') indicates a function or parameter requested via the parameter channel is not supported by the drive inverter's current configuration or hardware. This highlights a mismatch between the requested functionality and the inverter's capabilities.

Emergency stop due to thermal overload of the inverter. This indicates that the internal temperature of the drive has exceeded safe operating limits, posing a risk of damage to the power electronics.

This PROFIBUS-DP additional code (Error Class 8, 'Other Error') occurs when an attempt was made to write to a parameter via PROFIBUS-DP that is designated as read-only. The inverter rejects the write request for parameters that cannot be modified.

Emergency stop occurs because 14-bit resolver evaluation is active, and the actual motor speed exceeds 3600 1/min. The resolver feedback system is not designed for accurate operation above this speed.

This fault indicates issues with the brake output, such as no brake connected, a disconnected brake cable when the brake is commanded 'ON', or an overload condition due to excessive current or frequent operation. This can lead to uncontrolled loads, mechanical damage, or safety hazards if the brake fails to engage or disengage correctly.

The 24V supply voltage for the brake is not within the permitted tolerance of ±10%. This can prevent the brake from operating reliably, potentially causing it to fail to engage or disengage, leading to uncontrolled loads or safety risks. This monitoring is active only when the brake is parameterized as 'installed' and 'applied'.

This PROFIBUS-DP additional code (Error Class 8, 'Other Error') indicates a parameter setting was attempted while the parameter lock function was active on the drive inverter. This lock prevents unintended modifications to critical settings.

Immediate switch-off because the selected control signal source (e.g., analog input, fieldbus) is either not defined or incorrectly configured. The inverter cannot properly receive its operational commands.

There is a discrepancy between the raw position data and the track counter of absolute Encoder 1, suggesting an internal inconsistency in position tracking. This can lead to incorrect position readings and unstable drive operation. Unresolved, it can cause erratic movements or positioning errors.

The connected Encoder 1 type is not recognized or supported by the inverter's firmware. This prevents the drive from correctly interpreting encoder signals, leading to non-functional position or speed feedback. Continued operation without proper encoder recognition is impossible.

Encoder 1's nameplate data, such as measuring steps, pulses per revolution, or multi-turn counts, is invalid or incorrectly configured. This means the drive cannot accurately calculate position or speed, leading to severe control errors. Persistent invalid data will prevent proper drive function.

A fault has been detected during the track measurement process of Encoder 1, indicating issues with the encoder's ability to accurately track movement. This can result in inaccurate position feedback and unreliable drive operation. Continued use with this fault can lead to positioning inaccuracies or uncontrolled movements.

The drive's current position mode does not allow for movement beyond the configured travel range, indicating a limit has been reached. This prevents further machine movement, potentially causing operational halts if the system attempts to exceed its boundaries. If ignored, it can lead to repeated stops or inability to complete movements.

This PROFIBUS-DP additional code (Error Class 8, 'Other Error') means the drive inverter is currently operating with factory default settings, and a parameter change request was rejected. Parameters may be unwritable or require explicit action to exit factory setting mode.

Immediate switch-off due to an issue with the encoder feedback, such as an incorrectly connected encoder cable or shield, a short circuit or broken wire within the cable, or a defective encoder unit itself. This prevents accurate speed and position feedback.

This PROFIBUS-DP additional code (Error Class 8, 'Other Error') indicates a value provided for a parameter setting exceeded its maximum allowable range. This signifies an attempt to configure the inverter with an out-of-bounds value.

Immediate switch-off due to the absence of the internal DC 24V supply voltage. This indicates a failure in the inverter's internal control power supply circuitry.

This PROFIBUS-DP additional code (Error Class 8, 'Other Error') indicates a value provided for a parameter setting was below its minimum allowable range. This signifies an attempt to configure the inverter with an out-of-bounds value.

This PROFIBUS-DP additional code (Error Class 8, 'Other Error') means an attempt was made to access or configure a function or parameter that requires a specific hardware option card, which is not currently installed in the drive inverter.

Immediate switch-off indicating a malfunction of the inverter's internal electronics. This could be caused by electromagnetic compatibility (EMC) influences or an internal hardware defect.

This PROFIBUS-DP additional code (Error Class 8, 'Other Error') indicates an internal error occurred within the drive inverter's system software during a parameter setting operation. This points to a potential internal malfunction or corruption within the inverter's firmware.

This PROFIBUS-DP additional code (Error Class 8, 'Other Error') means parameter access was attempted via an incorrect communication interface. This specific parameter requires access through the RS-485 process interface on terminal X13, and the current access method is not permitted.

Rapid stop due to an error encountered while accessing the Electrically Erasable Programmable Read-Only Memory (EEPROM). This suggests potential corruption or a problem with storing/retrieving configuration parameters.

Emergency stop triggered by an external error signal received via a programmable input terminal. This indicates a fault condition originating outside the inverter, as defined by the application's logic.

Emergency stop because both hardware limit switches are either missing/open circuit, or they are incorrectly wired in relation to the motor's direction of rotation. This prevents the drive from accurately detecting its travel limits.

Rapid stop caused by a loss of communication between the master and slave devices within the configured response monitoring time on the fieldbus. This signifies a disruption in fieldbus data exchange.

Emergency stop indicating that a physical limit switch was reached while the drive was operating in IPOS mode. This suggests the programmed movement exceeded the defined mechanical travel range.

Immediate switch-off because the drive is overloaded or the emergency stop ramp is configured too short. The drive is unable to decelerate to a stop within the programmed emergency stop time.

No immediate drive response, but a fault is indicated, because the motor has become too hot and its TF (thermal feedback) sensor has tripped. This can also occur if the TF sensor is incorrectly connected or if the connection between the MOVIDRIVE and the motor's TF is interrupted.

Emergency stop caused by a violation of programming principles within the IPOS program, leading to an internal system stack overflow. This indicates a complex logic or resource management issue within the user program.

Immediate switch-off because the setpoint source (e.g., analog input, fieldbus, internal parameter) is either not defined or incorrectly configured. The inverter cannot determine how to receive its target values for speed, position, or torque.

Immediate switch-off because the inverter's operating mode (e.g., VFC, Servo, Positioning) is either not defined or incorrectly configured. The inverter cannot determine its fundamental control strategy.

Immediate switch-off due to an error encountered during the execution of system software. This typically indicates a critical internal software malfunction or an unhandled exception.

Immediate switch-off due to a general system error related to the inverter's core system software. This points to a fundamental and critical internal fault within the drive's operating system.

Immediate switch-off during reference travel because the reference cam is missing or not switching correctly, limit switches are connected incorrectly, or the reference travel type was changed while the process was active. This prevents the drive from accurately establishing its home position.

Immediate switch-off caused by an error in communication between system software and option software, a watchdog event within the IPOS program, an application module being loaded into a unit without the application version, or an incorrect technology function set with an application module. This indicates an incompatibility or logical error with advanced control functions.

Immediate switch-off because the actual position or speed of the motor is lagging too far behind its setpoint. Possible causes include an incorrectly connected encoder, overly short acceleration ramps, a P component of the positioning controller that is too small, incorrectly set speed controller parameters, a lag fault tolerance value that is too small, or mechanical binding in the system.

Rapid stop because the RS485 communication connection between the inverter and the PC has been interrupted, leading to a communication timeout. The drive loses its control link to the PC.

Immediate switch-off because the inverter's utilization (IxT value), representing its thermal load, has exceeded 125%. This means the inverter is operating beyond its continuous thermal capacity, risking overheating and damage.

Immediate switch-off because parameters for the EEPROM in the power section are either not set or incorrectly set. This prevents the inverter from properly initializing its core operational settings.

Rapid stop due to an error during communication via the internal system bus. This indicates a disruption in the high-speed data exchange between internal modules of the inverter.

No immediate drive response, but a fault is indicated, in IPOS operating mode if an invalid automatic mode was attempted to be set via an external controller, or if parameter P916 is set incorrectly. The IPOS program cannot interpret the received control command.

No immediate drive response, but a fault is indicated, in IPOS operating mode if the programmed target position falls outside the travel range defined by software limit switches. This signifies a position command that attempts to move beyond the safety boundaries.

Immediate switch-off, specific to 'VFC hoist' operating mode, occurring when the motor cannot be supplied with the correct current during pre-magnetizing time. This typically happens if the rated motor power is too small relative to the inverter, or if the motor cable cross-section is insufficient.

Immediate switch-off, specific to 'VFC hoist' operating mode, indicating that two or all output phases to the motor are interrupted, or that the rated motor power is too small compared to the inverter's rated power. This results in an inability to power the motor correctly.

Emergency stop because the motor utilization is too high, indicating that the motor is experiencing prolonged overload conditions. This trip protects the motor from thermal damage.

Immediate switch-off due to an error encountered while copying parameters, typically between the inverter and a connected PC or other device. This indicates a problem with the data transfer integrity or connection.

Immediate switch-off caused by an attempt to load a parameter set intended for an application version unit with an activated technology function into a standard version unit. This signifies an incompatibility between the loaded configuration and the inverter's hardware/firmware capabilities.

Immediate switch-off, specific to VFC n-CTRL operating mode, if the actual motor speed is detected to be greater than 5000 1/min when the inverter is enabled. The flying start function cannot engage at such high initial speeds.

Immediate switch-off due to disrupted inverter electronics, possibly caused by strong EMC effects or an internal defect. This indicates a data integrity issue within the EEPROM where critical configuration parameters are stored.

Immediate switch-off in IPOS operating mode if the positioning ramp is configured as sinusoidal or square, and an attempt is made to change ramp times or traveling velocities while the inverter is already enabled. These parameters cannot be modified dynamically with these specific ramp types during active operation.

The safety option failed to synchronize with a subcomponent, indicating a communication or hardware recognition issue. This prevents the safety functions from operating correctly and will inhibit the output stage, rendering the system inoperable.

The installed safety option variant is incompatible with the inverter type, or an incorrect variant (e.g., with an encoder interface on a double axis system) has been plugged in. This prevents the safety functions from operating and inhibits the output stage, requiring immediate correction for functionality.

Communication between the inverter and the safety option has been interrupted, potentially due to a loose connection or a subcomponent fault within the safety option. This prevents proper safety function and inhibits the output stage, compromising system safety.

The safety option is signaling a subcomponent fault of a warning type. This indicates a non-critical issue within the safety circuit that could affect safety integrity or system reliability if not addressed, potentially escalating to a more severe fault.

The safety option is reporting a standard subcomponent fault, leading to an emergency stop and output stage inhibit. This indicates a significant problem within the safety circuit that requires immediate resolution to restore safe and operational status.

The safety option has signaled a critical subcomponent fault, leading to output stage inhibit. This is a severe safety integrity issue, indicating a major failure within the safety circuit that prevents safe operation and demands immediate, thorough investigation.

This return code, structured as Error class 6 (Access Error) and Error code 2 (Hardware fault), signifies an internal communication error within the system, specifically a hardware fault. The requested parameter service may not have been performed.

This return code, structured as Error class 6 (Access Error) and Error code 8 (Type conflict), indicates that a write service during configuration via the parameter channel specified a data length other than the expected 4 data bytes. This causes a conflict in data type interpretation.

The inverter has detected that the output current exceeded 185% of the rated output current for more than 60 milliseconds. This indicates a significant overload on the motor or a short circuit in the output wiring. This will cause an immediate switch-off of the inverter to prevent damage to the motor or the drive.

An overcurrent or faulty output stage control has been detected, causing the output stage to be inhibited by hardware. This often indicates a short circuit at the motor output, excessive motor current, or a defective power output stage. Failure to resolve risks severe damage to the drive and connected motor.

The motor current flowing through the output stage is excessively high, potentially due to an undersized motor, issues with the current supply or transformer, incorrect ramp times, a defective phase module, or an unstable 24 V supply. This condition can lead to severe damage to both the drive and the motor if not corrected.

A ground fault has been detected, which could be located in the motor leads, the inverter itself, or within the motor windings. This fault presents a significant electrical safety hazard and can cause extensive damage to equipment if not immediately addressed.

An overcurrent condition has been detected in the brake chopper circuit. This is typically caused by excessive regenerative power during deceleration, a short circuit in the braking resistor circuit, or an incorrectly sized braking resistor. Failure to resolve risks damage to the brake chopper or resistor.

The output stage of the brake chopper component is defective. This critical failure prevents the drive from effectively dissipating regenerative energy during deceleration, potentially leading to DC bus overvoltage faults and irreversible damage to the drive.

A missing line phase, periodically low DC link voltage, or inadequate line voltage quality has been detected in the incoming AC supply. This can lead to imbalanced motor operation, reduced torque, and potential damage to the inverter's input rectifier section if not addressed.

Encoder 1 is signaling an internal warning status, indicating a non-critical issue within the encoder. This could be related to wiring, external interference, or sensor cleanliness, and may degrade performance or escalate to a fault if not addressed.

The signal level from Encoder 1 is too low, falling below the permitted limit during monitoring. This indicates a problem with the wiring, external electromagnetic interference (EMC), or a faulty encoder, leading to unreliable position feedback.

The signal level from Encoder 1 is excessively high, exceeding the permitted limit during monitoring. This often points to an incorrect gear ratio configured for the resolver or a wiring issue, potentially leading to inaccurate position readings.

An error occurred while monitoring the signal level from Encoder 1, where the signal vector exceeded its permitted limit. This could indicate an issue with the encoder's physical mounting position affecting its signal output or data integrity.

An error was detected during the quadrant check for the sine encoder (Encoder 1), indicating a problem with signal integrity or phase relationship. This can be caused by wiring issues, EMC interference, or a defective encoder, leading to incorrect position feedback.

The actual position detected by Encoder 1 has moved outside the configured position tolerance band. This could be due to incorrect startup parameters, faulty wiring, external interference, or a defective encoder, potentially leading to inaccurate positioning or unexpected movements.

Encoder 1 has failed to provide process data within the expected timeframe, resulting in a data timeout. This typically points to communication issues caused by electromagnetic interference (EMC) or incorrect startup parameters.

Encoder 1 has transmitted an emergency error message, indicating a critical internal or communication issue requiring immediate attention. This is often triggered by severe interference or incorrect communication parameters, leading to loss of position control.

A communication error occurred during the initialization phase of Encoder 1. This can be caused by incorrect parameterization, mismatched baud rates, an improperly configured CANopen node ID at the encoder, or faulty wiring. This prevents the encoder from being properly recognized and providing feedback.

There is faulty communication with Encoder 1, preventing the drive from receiving reliable data. This can be caused by issues with the encoder's voltage supply, electromagnetic interference (EMC), or damaged/incorrect wiring, leading to loss of position feedback and control.

The encoder evaluation system is signaling a critical system error for Encoder 1, possibly due to a multi-turn encoder being outside its configured track area, incorrect limits, or faulty numerator/denominator factors. This indicates a severe issue with position calculation or encoder setup, risking incorrect positioning and drive instability.

Encoder 1's data signal line is permanently stuck at a high level, indicating a critical communication issue. This suggests a wiring problem (e.g., short to supply voltage) or a defective encoder, preventing reliable position feedback and risking uncontrolled drive behavior.

The data signal from Encoder 1 is persistently at a high level. This typically points to a wiring problem (e.g., short to supply voltage) or a defect within the encoder unit, resulting in lost or incorrect position feedback and impacting precise drive control.

Encoder 1's data signal line is permanently stuck at a low level, indicating a critical communication issue. This suggests a wiring problem (e.g., short to ground) or a defective encoder, preventing reliable position feedback and risking uncontrolled drive behavior.

The data signal from Encoder 1 is persistently at a low level. This typically points to a wiring issue or a defect within the encoder unit, resulting in lost or incorrect position feedback and impacting precise drive control.

A critical error bit has been set within the SSI protocol from Encoder 1, indicating a severe communication or data integrity issue. This can be due to incorrect parameters, encoder settings, wiring faults, or external interference, leading to unreliable or lost position data.

An error bit has been set in the SSI protocol by Encoder 1, indicating a data or communication problem. This can result from incorrect startup parameters, encoder settings, wiring issues, or external interference, affecting position feedback reliability.

Encoder 1 is signaling a critical internal fault, meaning the encoder itself has detected a severe malfunction. This prevents the drive from receiving reliable position feedback and could lead to unsafe or uncontrolled operation.

Encoder 1 is reporting an internal fault status, indicating a malfunction within the encoder hardware or software. This compromises the accuracy and reliability of position feedback, potentially causing drive control issues.

The encoder or its cable is either not connected correctly, has a short circuit or broken wire, or the encoder unit itself is defective. It may also occur if 2 inverters are connected via X14 and P505 is set to YES, causing SubC 27.

A communication fault on the RS485 channel at X14 indicates issues such as incorrect encoder cable/shield connection, short circuits, broken wires, or a defective encoder. It may also occur if 2 inverters are connected via X14 and P505 is set to YES, causing SubC 27.

The signal level from Encoder 2 is too low, falling below the permitted limit during monitoring. This indicates a problem with the wiring, external electromagnetic interference (EMC), or a faulty encoder, leading to unreliable position feedback.

The signal level from Encoder 2 is excessively high, exceeding the permitted limit during monitoring. This often points to an incorrect gear ratio configured for the resolver or a wiring issue, potentially leading to inaccurate position readings.

An error occurred while monitoring the signal level from Encoder 2, where the signal vector exceeded its permitted limit. This could indicate an issue with the encoder's physical mounting position affecting its signal output or data integrity.

An error was detected during the quadrant check for the sine encoder (Encoder 2), indicating a problem with signal integrity or phase relationship. This can be caused by wiring issues, EMC interference, or a defective encoder, leading to incorrect position feedback.

The actual position detected by Encoder 2 has moved outside the configured position tolerance band. This could be due to incorrect startup parameters, faulty wiring, external interference, or a defective encoder, potentially leading to inaccurate positioning or unexpected movements.

Encoder 2 has failed to provide process data within the expected timeframe, resulting in a data timeout. This typically points to communication issues caused by electromagnetic interference (EMC) or incorrect startup parameters.

Encoder 2 has transmitted an emergency error message, indicating a critical internal or communication issue requiring immediate attention. This is often triggered by severe interference or incorrect communication parameters, leading to loss of position control.

The data signal from Encoder 2 is persistently at a low level, suggesting a problem with the encoder's wiring or a defect within the encoder unit itself. This will result in lost or incorrect position feedback, impacting precise drive control.

A critical error bit has been set within the SSI protocol from Encoder 2, indicating a severe communication or data integrity issue. This can be due to incorrect parameters, encoder settings, wiring faults, or external interference, leading to unreliable or lost position data.

An error bit has been set in the SSI protocol by Encoder 2, indicating a data or communication problem. This can result from incorrect startup parameters, encoder settings, wiring issues, or external interference, affecting position feedback reliability.

Encoder 2 is signaling a critical internal fault, meaning the encoder itself has detected a severe malfunction. This prevents the drive from receiving reliable position feedback and could lead to unsafe or uncontrolled operation.

Encoder 2 is reporting an internal fault status, indicating a malfunction within the encoder hardware or software. This compromises the accuracy and reliability of position feedback, potentially causing drive control issues.

The drive's position for Encoder 2 has exceeded the maximum allowable travel range defined by the current position mode (8382.10). This indicates a configuration error or unexpected machine movement, which can lead to mechanical limits being hit or incorrect positioning.

A 'Stack overflow' fault indicates that the inverter electronics have been disrupted, possibly due to external EMC influences. This suggests an internal software or memory management issue triggered by environmental factors.

The current load on the 24 V standby supply voltage in the MOVIDRIVE® system is too high. This overcurrent causes the device's internal signal output to de-energize. Leaving this unresolved can lead to system instability, unexpected shutdowns, and potential damage to internal components from sustained overload.

An unspecified error has occurred within the device's internal hardware. This indicates a critical malfunction that can lead to unpredictable operation and eventual complete system failure. If not resolved, the device cannot guarantee reliable control or safety functions.

The cooling fan's function is impaired, indicating a potential issue with its operation. While currently a warning, prolonged impairment can lead to inadequate cooling, causing internal components to overheat and potentially suffer damage over time.

The cooling fan is defective, indicating a critical failure in the device's thermal management system. Continuing operation with a defective fan will lead to rapid overheating of internal components, risking permanent damage to the drive.

The supply voltage required for the cooling fan is missing, preventing it from operating. This critical fault will lead to rapid overheating of internal components, potentially causing permanent damage to the drive if left unaddressed.

A switching delay has been detected between the two Safe Torque Off (STO) channels. This indicates a potential malfunction within the safety circuit, which compromises the safety integrity of the drive and risks uncontrolled motor movement if not resolved.

A fault with a 'warning' response has occurred within the power section of the device. This indicates an underlying issue that could degrade drive performance, reduce reliability, and potentially escalate to a full operational fault if ignored.

A standard fault has been detected in the power section, resulting in an emergency stop and output stage inhibit. This signifies a critical problem preventing safe operation and demands immediate attention to prevent further damage to the drive components.

Access to the EEPROM of the memory card has failed, leading to a read or write fault on the EEPROM power section. This indicates an issue with the drive's non-volatile memory.

An external fault signal has been read via a programmable input. The specific cause depends on the connected external device or condition triggering this input.

The fieldbus interface option card is reporting a warning-level subcomponent fault. While not immediately critical, this indicates a potential issue with the fieldbus communication or hardware that could degrade performance or escalate to a full fault if not addressed.

A fault occurred during internal data transmission within the DCS..B option. This indicates a communication issue between internal components of the option.

A fault occurred during internal data transmission within the DCS..B option. This indicates a communication issue between internal components of the option.

An internal program fault has occurred within the DCS..B option. The specific nature of the program fault is not detailed.

The watchdog test within the DCS..B option failed, indicating faulty feedback from the internal shutdown channel of the digital outputs. This implies a safety-critical monitoring failure.

Faulty process data has been detected within the DCS..B option. This indicates an issue with the integrity or handling of operational data.

An internal processing fault occurred within the user program on the DCS..B option. This indicates a problem with the custom logic or application running on the option.

An internal processing fault occurred within the user program on the DCS..B option. This indicates a problem with the custom logic or application running on the option.

An internal processing fault occurred within the user program on the DCS..B option. This indicates a problem with the custom logic or application running on the option.

An internal processing fault occurred related to an input element on the DCS..B option. This suggests an issue with processing signals from connected inputs.

An internal processing fault occurred related to an input element on the DCS..B option. This suggests an issue with processing signals from connected inputs.

An internal processing fault occurred within the user program on the DCS..B option. This indicates a problem with the custom logic or application running on the option.

This fault indicates a general runtime issue within the DCS..B option. The root cause is not specified, suggesting an internal operational error.

This fault indicates a general runtime issue within the DCS..B option. The root cause is not specified, suggesting an internal operational error.

An interrupt fault occurred during time monitoring within the DCS..B option. This suggests an internal timing or process scheduling issue.

This fault indicates a general runtime issue within the DCS..B option. The root cause is not specified, suggesting an internal operational error.

An internal program fault has occurred within the DCS..B option. The specific nature of the program fault is not detailed.

An internal fault has been detected within the CPU of the DCS..B option. This indicates a critical hardware or firmware issue with the processing unit.

An internal fault has been detected within the CPU of the DCS..B option. This indicates a critical hardware or firmware issue with the processing unit.

An internal fault has been detected within the CPU of the DCS..B option. This indicates a critical hardware or firmware issue with the processing unit.

An internal fault has been detected in the RAM of the DCS..B option. This suggests an issue with the memory component crucial for operation.

An internal fault has been detected in the flash memory of the DCS..B option. This indicates an issue with the non-volatile memory storing firmware or configuration.

An internal fault has been detected within the CPU of the DCS..B option. This indicates a critical hardware or firmware issue with the processing unit.

An internal processing fault occurred related to the PROFIsafe functionality within the DCS..B option. This indicates a problem with the safety communication protocol or its implementation.

An internal processing fault occurred related to the PROFIsafe functionality within the DCS..B option. This indicates a problem with the safety communication protocol or its implementation.

An internal processing fault occurred related to the PROFIsafe functionality within the DCS..B option. This indicates a problem with the safety communication protocol or its implementation.

A fault occurred during internal data transmission within the DCS..B option. This indicates a communication issue between internal components of the option.

A fault occurred during internal data transmission within the DCS..B option. This indicates a communication issue between internal components of the option.

A fault occurred during internal data transmission within the DCS..B option. This indicates a communication issue between internal components of the option.

A fault occurred during internal data transmission within the DCS..B option. This indicates a communication issue between internal components of the option.

A fault occurred during internal data transmission within the DCS..B option. This indicates a communication issue between internal components of the option.

A fault occurred during internal data transmission within the DCS..B option. This indicates a communication issue between internal components of the option.

The core voltage (DMP1) of the DCS..B option is incorrect, or a component on the DCS..B option is faulty. This affects the internal power supply to critical components.

The core voltage (DMPM) of the DCS..B option is incorrect, or a component on the DCS..B option is faulty. This affects the internal power supply to critical components.

A fault was detected during the internal RAM test of the DCS..B option. This indicates an issue with the memory component crucial for operation.

A fault was detected during the test of static registers within the DCS..B option. This indicates an issue with internal control logic or memory elements.

The current acceleration has exceeded the configured maximum acceleration limit. This indicates a discrepancy between actual motor dynamics and the set parameters, potentially due to incorrect configuration or mechanical issues.

The encoder interface (A3401 or A3402) does not match the configured data. This suggests a mismatch between the physical encoder type/connection and the drive's settings.

The encoder voltage supply (A3403 or A3404) is outside the defined range (min. DC 20 V / max. DC 29 V). This can be caused by an overload in the supply voltage, potentially tripping an internal polyswitch fuse on the DCS..B option.

The reference voltage input of the encoder system is outside of its defined operational range. This can impact the accuracy or functionality of the encoder.

A fault is detected in the RS485 driver 1, specifically with the 'B' or 'Cycle' signal. This is usually caused by no encoder connection or an incorrect encoder type being connected.

The encoder interface (A3401 or A3402) does not match the configured data. This suggests a mismatch between the physical encoder type/connection and the drive's settings.

An incorrect encoder type is connected for a SIN/COS encoder. This results in a plausibility fault in the connection.

A phase fault has occurred in the incremental or SIN/COS encoder connection. This indicates an issue with the signal integrity from the encoder.

The connected encoder type does not correspond to the configuration for an SSI encoder operating in master mode. This indicates a mismatch in setup.

The connected encoder type does not correspond to the configuration for an SSI encoder operating in slave mode. This indicates a mismatch in setup.

A DC 24 V short circuit has been detected at the digital output DO0_P (X82:1) from the high-side driver. This indicates an electrical fault on the output channel.

A DC 0 V short circuit has been detected at the digital output DO0_M (X82:2) from the low-side driver. This indicates an electrical fault on the output channel.

A DC 24 V short circuit has been detected at the digital output DO1_P (X82:3) from the high-side driver. This indicates an electrical fault on the output channel.

The voltage supply of the encoder (E3405 or E3406) is not within the defined range (min. DC 20 V / max. DC 29 V). This may be due to an overload, causing the internal polyswitch fuse to trip.

A fault is detected in the RS485 driver, specifically with the 'B' or 'Cycle' signal. This is usually caused by no encoder connection or an incorrect encoder type being connected.

A fault is detected in the RS485 driver, specifically with the 'A' or 'DATA' signal. This is usually caused by no encoder connection or an incorrect encoder type being connected.

An incorrect encoder type is connected for a SIN/COS encoder, causing a plausibility fault in the connection.

The connected encoder type does not correspond to the configuration for an SSI encoder operating in master mode. This indicates a mismatch in setup.

The connected encoder type does not correspond to the configuration for an SSI encoder operating in slave mode. This indicates a mismatch in setup.

Faulty monitoring of the external shutdown channel EMU1. This may be due to incorrect hardware connections or an inappropriately short pick-up or release time for the channel.