SEW Eurodrive MOVIMOT Field Distributor

An overcurrent condition has been detected in the inverter output stage. This fault is typically triggered by a short circuit in the motor cabling or within the motor itself, leading to excessive current draw.

A phase fault has been detected in the supply system. This error specifically occurs when the drive is operating under load, indicating an imbalance or loss of one or more phases in the power input.

The DC link voltage has exceeded its permissible upper limit. This typically occurs due to regenerative energy during deceleration, or issues with the braking circuit components, which fail to dissipate excess energy.

The speed monitoring function has detected an anomaly, indicating that the drive is operating under an overloaded condition. This fault prevents the drive from maintaining its commanded speed or torque.

The IPOS (Intelligent Positioning System) program has stopped due to an error, indicated by a process output data value of DO=0. Further details about the specific error may be available in IPOS variable H469.

The output stage of the inverter or an internal unit component has experienced a thermal overload. This could be due to inadequate cooling, high ambient temperatures, or excessive load, potentially indicating an internal fault.

Communication with the MOVIMOT has stopped, indicated by DO=0, due to an interruption in the electrical connection to the proximity encoder NV26. This prevents accurate position or speed feedback.

The inverter electronics has experienced a stack overflow, typically caused by a corrupted program stack or excessive data processing. This issue can sometimes be influenced by electromagnetic compatibility (EMC) disturbances.

A CPU-related fault indicating a critical internal software issue, likely related to improper memory stack management. This condition causes communication to the MOVIMOT to stop (DO=0).

A CPU-related fault indicating a critical internal error that cannot be ignored by the processor. This type of fault typically signifies a severe hardware or software malfunction within the inverter, causing communication to stop (DO=0).

A CPU-related fault indicating that the processor attempted to execute an invalid or unrecognized instruction code. This usually points to a corruption in the program memory or a hardware malfunction, causing communication to stop (DO=0).

A CPU-related fault indicating that a protection mechanism within the inverter electronics has been triggered. This could be due to an internal hardware error or an attempt to perform an operation outside defined safety limits, causing communication to stop (DO=0).

A CPU-related fault indicating an attempt to access memory or data in an unauthorized or incorrect manner, specifically concerning word-sized operands. This typically points to a software bug or memory corruption, causing communication to stop (DO=0).

A CPU-related fault indicating an attempt to fetch or execute an instruction from an unauthorized or incorrect memory location. This typically suggests a program counter error or memory corruption, causing communication to stop (DO=0).

A CPU-related fault indicating an invalid attempt to access an external bus or peripheral device. This could be due to incorrect addressing, faulty hardware, or a software error in bus communication, causing communication to stop (DO=0).

An error occurred while accessing the EEPROM (Electrically Erasable Programmable Read-Only Memory), resulting in data inconsistency. This can lead to incorrect parameter settings or loss of configuration.

No master-slave communication took place within the configured response monitoring period on the fieldbus. This results in process output data being set to 0 (DO=0) and the fault is disengageable.

The IPOS program has stopped (DO=0) because basic programming rules were violated, leading to a stack overflow within the system. This indicates an issue with the structure or complexity of the user program.

An error occurred during the execution of the system software, triggering the internal watchdog timer. This critical fault causes communication to the MOVIMOT to stop (DO=0), indicating a fundamental issue with the unit's operating system.

The IPOS Watchdog has tripped because the IPOS program's execution time exceeded the adjusted watchdog time. This indicates that a part of the program is taking too long to execute, potentially due to an infinite loop or heavy processing.

An error occurred after the self-test during the unit's reset sequence. This indicates a problem with the internal initialization process, preventing the MOVIMOT from starting up correctly.

An attempt was made by an external controller to set an invalid automatic mode within the IPOS program. This action caused the IPOS program to stop (DO=0), indicating that the command sent was outside the permissible range or format.

A short circuit has been detected on either the digital outputs DO0, DO1, or on the voltage supply lines for the VO24 sensors. This can lead to incorrect switching signals or power loss to connected devices.

The motor has experienced a thermal overload, or its internal winding thermostat (TH) has tripped. This can be caused by excessive load, high ambient temperatures, or incorrect drive configuration settings for motor protection.

The brake coil has either experienced a thermal overload or is internally defective. This can result from short ramp times, excessive braking cycles, or an incompatibility between the drive and inverter, impacting braking performance.

One or more MOVIMOT stations could not be addressed by the MQ.. unit within the configured timeout interval. This indicates a system-level communication issue where stations are not responding or are incorrectly configured.

An error occurred during EEPROM access, indicating potential data inconsistency or corruption within the unit's non-volatile memory. This can affect stored parameters and configurations.

A fault occurred while a data record was being copied, resulting in inconsistent data within the system. This issue causes communication to the MOVIMOT to stop (DO=0), indicating a critical data integrity problem.

The MOVIMOT unit detected a low DC link voltage or a complete loss of supply voltage, causing the motor to stop without generating a specific error code. The motor is designed to restart automatically once the supply voltage returns to its normal operating range.

Communication timeout occurred between the MOVIMOT unit and the RS-485 master, causing the motor to stop without generating a specific error code. This indicates a disruption in the data link.