SEW Eurodrive MOVIFIT SC

This fault signifies that the output current to either drive 1 (monitored by P300/P301) or drive 2 (monitored by P310/P311) has exceeded its configured cut-off limit for the parameterized delay time. This protective shutdown is often caused by excessive mechanical load on the motor, a short circuit in the motor windings or cables, or improperly set overcurrent parameters. Persistent overcurrent can lead to motor winding damage, thermal stress on cables, and potential failure of the MOVIFIT unit's output stage. If left unaddressed, this could result in costly motor replacement or unit downtime.

This fault indicates either the unit's heatsink temperature has exceeded its permitted limit (sub-error 1-2) or the total utilization of both drives in dual-motor operation is excessively high (sub-error 4-5). Causes include high ambient temperatures, insufficient ventilation, or excessive mechanical load on the drives. Overheating and overutilization can lead to component degradation, reduced lifespan of the MOVIFIT unit, and potential permanent damage to power electronics if not resolved promptly.

This fault indicates a general error within the unit's Central Processing Unit, signaling an internal malfunction of the control electronics. While it can sometimes be a transient issue, it may also point to a deeper hardware defect within the unit's core processing components. Repeated occurrences of this error can lead to unpredictable unit behavior, loss of control, or complete operational failure, potentially causing process interruptions.

This fault indicates a general error within the unit's Central Processing Unit, signaling an internal malfunction of the control electronics. While it can sometimes be a transient issue, it may also point to a deeper hardware defect within the unit's core processing components. Repeated occurrences of this error can lead to unpredictable unit behavior, loss of control, or complete operational failure, potentially causing process interruptions.

This fault indicates an issue with reading from or writing to the unit's EEPROM (Electrically Erasable Programmable Read-Only Memory), which stores configuration parameters and operational data. This can lead to lost settings, incorrect unit operation, or an inability to store new parameters or changes. If left unresolved, corrupted EEPROM data could prevent the unit from functioning correctly and require complete re-configuration.

This fault is triggered when a low signal is detected on a specific terminal that has been configured for the '/External fault' function, primarily when the MOVIFIT unit operates as an SBUS slave. This indicates an issue with an external device connected to this terminal, signaling a fault condition from that external source. The low signal could be due to wiring issues, a faulty sensor, or an active fault in the connected external equipment, causing the MOVIFIT unit to stop operation.

This fault occurs when the temperature sensor (TF) in either drive 1 or drive 2 is triggered, indicating an overtemperature condition in the respective motor. Common causes include excessive motor load, high ambient temperatures, inadequate motor cooling, or a faulty sensor itself providing an incorrect reading. Operating a motor above its rated temperature severely shortens its lifespan, degrades winding insulation, and risks permanent motor damage, necessitating immediate attention.

This fault indicates a general error within the unit's Central Processing Unit, signaling an internal malfunction of the control electronics. While it can sometimes be a transient issue, it may also point to a deeper hardware defect within the unit's core processing components. Repeated occurrences of this error can lead to unpredictable unit behavior, loss of control, or complete operational failure, potentially causing process interruptions.

This fault indicates that the combined output current from both drive 1 and drive 2 has exceeded 180% of the unit's nominal current (IN,unit). This represents a severe overload condition, potentially leading to immediate shutdown to protect the power electronics and prevent damage to the MOVIFIT unit. It can be caused by excessive mechanical load or by simultaneously enabling both drives when their combined current draw exceeds the unit's capacity. Unresolved, this can lead to premature failure of the drive unit.

This fault indicates that the MOVIFIT unit was unable to automatically detect or recognize the sequence of the incoming three-phase power supply during its initialization phase. This prevents the unit from starting correctly and is typically due to incorrect wiring of the grid connection (L1, L2, L3). An unrecognized phase sequence can lead to motors rotating in the wrong direction, damage to mechanical components, or unit malfunction, requiring immediate correction before operation.

This fault indicates a timeout in the cyclical communication over the CAN bus, meaning the unit is not receiving expected data from, or sending data to, another device on the CAN network within the specified time window. This can interrupt critical control and data exchange, leading to system halts, unpredictable behavior, or loss of synchronized operation. It's often related to wiring, termination, baud rate, or configuration issues on the bus, and can cause significant process downtime.

This fault indicates a loss of one line phase (L1, L2, or L3) either during initial network detection or after the network has been successfully established. Note that the failure of two line phases does not trigger this error, but rather a 'Not ready, 24V' state without an explicit error message. Prolonged operation with a missing phase can lead to motor damage, unit malfunction, and potential safety hazards due to unbalanced loads. It is crucial to resolve this promptly to prevent further component stress.

This fault signifies that the measured output current for either drive 1 or drive 2 is less than 2% of the unit's nominal current (IN,unit/device) when the respective drive is enabled. This strongly suggests an open circuit in the motor circuit, such as a disconnected or broken motor cable, a faulty motor winding, or an issue with the drive's output stage itself. This condition prevents motor operation and could indicate significant wiring or motor damage, posing a risk of component failure if the unit attempts to drive into an open circuit.

This fault indicates various forms of motor overload or overtemperature protection. It can be triggered by cyclical monitoring exceeding limits (due to frequent starts/stops or high load), by UL protection functions detecting time violations of current limits (e.g., 750% IN,unit), or by the internal motor temperature simulation reaching 110% utilization. These protections safeguard the motor and drive from damage due to excessive mechanical load, demanding duty cycles, or insufficient cooling. Unresolved overload conditions lead to reduced motor lifespan and potential drive unit failure.

This fault indicates that the cycle monitoring for either brake 1 or brake 2 has triggered during brake release operations when the drive is not actively enabled. This typically means the brake is being released too frequently or held open for extended periods without motor operation, which can lead to excessive wear, overheating, or premature failure of the brake mechanism. The protection is in place to preserve brake integrity and prevent unintended brake degradation, which could compromise safety.

This fault encompasses two distinct startup issues. In 'dual-motor operation', it signifies an incorrect line phase sequence, preventing motors from running in the intended clockwise direction. In 'single-motor operation', it means an unexpected current (over 10% IN,unit) is detected on drive 2, usually due to incorrect wiring, such as a drive connected to X9 or two drives being present when only one is allowed. Both scenarios prevent proper unit startup and operation, risking mechanical stress to connected equipment or uncontrolled motor movement.

This fault indicates a permanent hardware defect in the unit's EEPROM (Electrically Erasable Programmable Read-Only Memory), suggesting the memory chip itself is faulty and likely beyond a simple reset or re-parameterization. A defective EEPROM will prevent the unit from reliably storing or retrieving critical configuration data, making consistent and reliable operation impossible. This is a severe hardware failure that typically requires unit replacement.

This fault indicates an error occurred during a data transmission or copying process within the unit, possibly when transferring parameters, firmware, or application-specific data. This could lead to incomplete or corrupted data, potentially affecting the unit's functionality, causing it to operate with incorrect settings, or failing to load a new configuration. It might be due to transient memory issues or an interrupted copy procedure, and can result in unreliable operation.