ABB ACS560

The drive displays a single dash '-', indicating a critical initialization error, possibly due to improper memory module insertion or the drive being stuck in recovery mode. This prevents the drive from starting up correctly and becoming operational.

The encoder has detected an internal error related to its position counter. This indicates a problem with the encoder's ability to accurately track position, which can lead to inaccurate motor control or positioning if unresolved.

The encoder has detected an unspecified internal error. This signifies a general malfunction within the encoder hardware or firmware, compromising its functionality. Without resolution, motor control and feedback will be unreliable.

This event code is reserved and not actively used by the system for application events. Its appearance suggests that an unassigned event ID was triggered or a placeholder is being used inadvertently. Encountering this indicates a potential misconfiguration within the event generation logic.

The application event function block attempted to trigger an event ID that is not defined as a user-defined event. This typically means the event ID is outside the designated user-definable range (0xE100-0xE2FF) or has not been configured in the ApplicationParametersAndEvents tool.

The 'EventType' input for the application event function block has been set to an unsupported value. Valid types include Fault (1), Warning (2), and Pure (8). This error indicates an attempt to use an unrecognized event classification, preventing proper logging or processing.

The format or data type of the 'ID' input provided to the event function block is incorrect or incompatible with the expected event ID structure. This can occur if the ID is not a WORD data type or falls outside the expected hexadecimal range, leading to a failure in event registration.

Similar to 0x0001, this event code is reserved and currently not utilized by the system for specific application events. Its presence points to an event ID being triggered that is a placeholder or has no active definition. This could indicate a misconfigured event source.

The event system received a request to handle an event with an 'EventType' that it does not recognize. This is similar to 0x0003 but specifically indicates the system cannot categorize the event based on the provided type, leading to an unregistered event.

This is a synchronous programming error where a line of Mint code attempts to assign a value that falls outside the permissible range for a specific parameter, such as setting a negative scalefactor. This indicates a logical flaw in the program that must be corrected to prevent immediate program termination.

The system attempted to write a value to a parameter that is currently configured as write-protected. This prevents accidental or unauthorized changes to critical configuration settings. If left unresolved, the desired parameter change will not be applied.

The system attempted to access a parameter that is currently configured as hidden. This means the parameter is not visible through standard interfaces, potentially to simplify the user experience or restrict access. This prevents direct interaction with the parameter.

An operation was attempted on a parameter that is invalid for its type or current state, such as trying to assign a string value to a numeric parameter, or an incorrect parameter type is being used. This prevents data corruption or unexpected behavior within the drive.

The drive is stuck in its default configuration state during boot-up, rather than progressing to an operational state. While a normal temporary boot state, persisting in this state indicates an underlying hardware or configuration problem, potentially preventing the drive from enabling or communicating.

The drive is stuck in its default communication profile configuration state during boot-up, preventing it from initializing correctly. This can be caused by mismatched encoder configurations or corrupted drive parameters. If unresolved, the drive will not enter an operational state or establish proper communication.

An attempt was made to set a parameter's value above its defined maximum limit. This prevents system operation outside safe or intended bounds, crucial for equipment longevity and safety. If the new value is critical, the parameter limits must be expanded.

The system attempted to select a value for a list-type parameter that is not available in its predefined list of options. This typically occurs when a discrete parameter is assigned an undefined enumeration value, leading to an invalid configuration.

The system attempted to access or modify a parameter using an invalid group or index. This means the specified parameter does not exist in the drive's parameter database, likely due to a typo or incorrect reference in the application code. This will prevent any operation on the intended parameter.

The drive's internal IGBT temperature has exceeded its safe operating limit, indicating potential overheating. This can lead to reduced lifespan or premature failure of the IGBTs if the root cause is not identified and resolved promptly.

An internal file read error has occurred within the drive. This means the drive cannot access critical internal files required for its operation, leading to a non-resettable fault. This could indicate corrupted internal storage or a hardware issue.

An internal error occurred while loading a data record within the drive. This suggests issues with internal data storage integrity or access, which is crucial for drive configuration and operational data. This fault can impact the drive's ability to maintain its settings or proper functionality.

The drive's application file is either incompatible with the current hardware/firmware or has become corrupted during storage or transfer. This critical fault prevents the application from loading and operating the drive, rendering it inoperable.

Loading of a user-defined parameter set failed. This can happen if the requested set does not exist, is incompatible with the control program's version, or if the drive lost power during the loading process. This prevents the drive from operating with the desired configuration, potentially defaulting to an unsafe or incorrect state.

An operating system error indicating that the drive's internal kernel (core operating system) is experiencing an overload. This is a severe internal fault preventing normal drive operation and cannot be reset by the user. It points to a critical issue with the drive's core processing capabilities.

The drive has encountered a conflict where a functionality requested by the PLC via Fieldbus Adapter A is either not available on the drive or has not been activated in its configuration. This prevents proper fieldbus control and data exchange, leading to communication errors or incorrect drive behavior.

A reference source is simultaneously connected to multiple parameters with different units, causing a configuration conflict. This inconsistency prevents correct signal processing and can lead to incorrect drive operation. Refer to warning A6DA for detailed information.

A mechanical brake control fault has occurred because the brake acknowledgment signal was not as expected during the brake closing sequence. This implies either the brake did not close, its feedback mechanism failed, or an obstruction is present, leaving the motor potentially unsecured or unable to hold position.

A mechanical brake control fault has occurred because the brake acknowledgment signal was not as expected during the brake opening sequence. This implies either the brake did not open, its feedback mechanism failed, or it is stuck, potentially preventing motor rotation or causing excessive load.

The conditions required for opening the mechanical brake cannot be met, often because the brake is being intentionally kept closed by a parameter setting (e.g., 44.11 Keep brake closed) or due to a safety interlock. This prevents motor operation and is usually a configuration or interlock issue.

The motor has not stopped within the maximum allowed time after an emergency stop command (Off1 or Off3 mode) was issued. This indicates a failure in the emergency braking sequence, which could lead to unsafe operation if the system cannot stop as expected. The drive trips and coasts to a stop.

An analog input signal is outside the limits specified for that input (under minimum or above maximum). This indicates a problem with the sensor, wiring, or the signal source itself. Incorrect analog input can lead to incorrect process control or drive operation.

A fault generated by the signal supervision 1 function, indicating that a monitored signal has violated its defined limits or conditions. This signifies an abnormal condition in a specific process signal that the drive is supervising. Unresolved, it can lead to incorrect operation or safety issues.

This programmable fault is triggered by the signal supervision function 2, indicating that a monitored signal (defined in parameter 32.17) has violated its configured supervision criteria (defined in parameter 32.16). This helps in detecting abnormal conditions of critical internal or external signals, preventing unintended operation or damage.

A fault generated by the signal supervision 3 function, indicating that a monitored signal has violated its defined limits or conditions. This signifies an abnormal condition in a specific process signal that the drive is supervising. Unresolved, it can lead to incorrect operation or safety issues.

This programmable fault is triggered by the signal supervision function 4, indicating that a monitored signal (defined in parameter 32.37) has violated its configured supervision criteria (defined in parameter 32.36). This helps in detecting abnormal conditions of critical internal or external signals, preventing unintended operation or damage.

This programmable fault is triggered by the signal supervision function 5, indicating that a monitored signal (defined in parameter 32.47) has violated its configured supervision criteria (defined in parameter 32.46). This helps in detecting abnormal conditions of critical internal or external signals, preventing unintended operation or damage.

This programmable fault is triggered by the signal supervision function 6, indicating that a monitored signal (defined in parameter 32.57) has violated its configured supervision criteria (defined in parameter 32.56). This helps in detecting abnormal conditions of critical internal or external signals, preventing unintended operation or damage.

This fault occurs when the amount of data being sent by the system exceeds the maximum capacity of an ICM (Industrial Communication Module) telegram. This typically happens in host applications using doMultipleCommands with too many encapsulated calls, preventing proper data transmission and potentially causing communication timeouts.

This is a warning during parameter application to an e100 drive, often due to an unsupported parameter, an incorrect number of arguments/values, wrong value types, or attempting to download a parameter table from a different product configuration (e.g., a resolver option table to a non-resolver drive). While a warning, it means parameters may not be correctly applied, leading to suboptimal or incorrect drive operation.

This error indicates an incorrect configuration when assigning POWERREADYINPUT or POWERREADYOUTPUT to an I/O. This can be caused by incompatible INPUTMODE/INPUTACTIVELEVEL/OUTPUTACTIVELEVEL settings, or by attempting to reconfigure an I/O that is already designated as POWERREADY. This prevents the drive from correctly signalling or detecting its power-ready status, potentially impacting system safety or startup sequences.

This error occurs when a new move command is issued to an axis that is currently in the process of stopping. This can happen if CANCEL or STOP commands are sent while the axis is already stopping or handling another CANCEL. Issuing commands prematurely can lead to unpredictable axis behavior and potentially unsafe conditions.

This error indicates that an event referenced in the Mint program is either not present or not installed in the drive's system. This can disrupt program flow or prevent expected actions from occurring, leading to incorrect system behavior.

This error occurs when the Mint program attempts to use an event that is not supported by the drive's firmware or hardware. This prevents the intended event-driven logic from executing, potentially causing program failures or unexpected machine behavior.

An attempt was made to access a parameter index that falls outside the permissible range for its group. This often happens with array-like parameters where indices are restricted to a specific count (e.g., Motor 1, Motor 2, but attempting to access Motor 3 if only 2 are supported).

An operation was attempted that would create an overlapping condition between parameter groups, which is not allowed by the system architecture. This can happen when configuring resources that are allocated in blocks, and a new allocation attempts to use an already occupied segment, leading to resource conflict.

This is a generic 'UFF error,' indicating an unspecified or internal error related to the User Function Flag system or a similar internal drive component. This often points to a software or firmware issue, or a complex interaction that is not explicitly covered by other error codes, potentially affecting drive functionality.

A failure has occurred in a current transformer within the output current measurement circuit. This will lead to inaccurate or no current feedback for the drive, severely impacting motor control, protection functions, and overall drive performance.

The drive has detected an excessive current flow to the motor, exceeding its operational limits. This typically indicates an overload condition, mechanical binding, or a short circuit in the motor or cabling, potentially leading to motor or drive damage if left unaddressed.

The drive has detected excessive output current unbalance, typically due to an earth fault in the motor or motor cable. For systems with parallel inverter modules (xx refers to module number 1-12), this may indicate an unbalance across units or an internal fault. This condition poses a risk of electrical shock and equipment damage.

A fatal synchronous programming error indicating that the program's call stack has exceeded its allocated memory limit. This typically results from deep or infinite recursion, or excessive local variable usage, leading to an immediate program crash without standard error handling mechanisms.

A fatal synchronous programming error that occurs when the program attempts to access an element of an array or data structure using an index that is outside its defined boundaries. This is a critical programming flaw that bypasses standard error recovery, leading to program termination.

A fatal synchronous programming error indicating that the program tried to perform a 'pop' operation on an empty stack. This typically points to an imbalance in stack operations, where more items are being removed than were added, leading to program termination.

The drive has detected a loss of one or more phases in the incoming supply power and has tripped. This fault prevents operation on an unbalanced supply which can cause severe damage to the drive's input rectifier stage and other internal components. It indicates a problem in the electrical supply chain.

The drive has detected an incorrect input power or motor cable connection, or an earth fault. This includes scenarios where an input power cable is inadvertently connected to the drive's motor connection terminals, posing a significant electrical safety risk and potential damage to the drive or motor.

An excessive DC voltage has been detected in the intermediate circuit of the drive. The DC overvoltage trip limit is calculated as 1.3 × 1.35 × U1max, which corresponds to 728 VDC for 400 V units, 877 VDC for 500 V units, and 1210 VDC for 690 V units. This fault is associated with bit 2 of Fault Word 1 (3.05 FW 1).

The drive is limiting torque due to an intermediate circuit DC voltage that is either too high or too low. This is an informative alarm (programmable Fault Function 30.23, bit 1: DC_VOLT_LIM_IND) indicating the drive is actively compensating to protect internal components from over or undervoltage conditions.

The intermediate circuit DC voltage is insufficient, typically due to a missing supply voltage phase, a blown input fuse, or an internal rectifier bridge fault. This condition prevents the drive from powering the motor correctly, leading to a shutdown or inability to start.

The drive has detected a loss of one or more phases between its output terminals and the connected motor. This typically results from a broken cable, loose connection, or open circuit protection, which can lead to motor instability, overheating, or failure if ignored.

A general fault has been detected within the encoder system, which could be related to its configuration, wiring, or physical operation. This fault can lead to incorrect position feedback, affecting motor control accuracy and stability.

The calculated duration for a test move is excessively long, indicating potential misconfiguration of test move settings or incorrect scaling parameters. This can prevent tuning procedures from completing efficiently or accurately, and may indicate an issue with motion profiles.

During velocity autotuning, the calculated test move velocity exceeds the configured `DriveSpeedMax` parameter. This indicates a mismatch between the desired tuning speed and the drive's maximum allowed operating speed, which can cause unsafe operation, tuning failures, or unexpected drive trips.

The motor's rated current is configured to be less than 0.2A, which is too small for the drive to effectively control. This indicates incorrect motor data entry or an incompatibility between the connected motor and the drive's operating range, preventing proper motor control.

The current control loop, which is essential for stable motor operation, has not been tuned prior to attempting rotor parameter autotuning (applicable specifically to asynchronous motors). This prevents successful autotuning and proper motor control, potentially leading to unstable operation.

The selected autotuning procedure is not compatible with the motor type currently configured in the drive. This indicates a mismatch between the motor data and the desired autotuning function, preventing the tuning process from completing.

The drive is unable to set the proportional gain for the flux control loop. This issue typically stems from incorrect motor data or internal drive parameter conflicts, which can prevent the drive from achieving stable and efficient flux control, impacting motor performance.

The drive is encountering an issue when attempting to set the integral gain for the flux control loop, even though the API may not report a direct error. This suggests an underlying problem with the motor data or internal drive settings, hindering proper and stable flux control.

The drive is unable to set the motor's magnetizing inductance (Lm) parameter. This usually points to incorrect or incomplete motor data, which is crucial for the drive's internal motor model and control algorithms. Incorrect Lm can lead to suboptimal motor performance or control instability.

The control board temperature has exceeded 88°C, indicating a critical overheating condition. Sustained high temperatures can lead to unreliable drive operation, component damage, or premature failure of the control board, ultimately causing system shutdown.

The motor temperature is excessively high, or appears high, due to factors such as excessive load, insufficient motor power for the application, inadequate motor cooling, or incorrect drive start-up data. Sustained overtemperature operation risks motor winding damage and premature failure.

The measured temperature of motor 1 has exceeded the alarm limit defined by parameter 35.02. This indicates a potential overheating situation specific to this motor, which can lead to insulation degradation and reduced motor lifespan if not addressed.

The measured temperature of motor 2 has exceeded the alarm limit set by parameter 35.05. This indicates a potential overheating condition specific to motor 2, requiring attention to prevent damage.

An external temperature sensor (sensor 1) has detected that the monitored equipment (e.g., motor winding) has exceeded its programmed temperature limit. This fault protects external components from overheating and potential damage, which could lead to critical system failure.

An external temperature sensor (sensor 2) has detected that the monitored equipment (e.g., motor bearing) has exceeded its programmed temperature limit. This fault protects external components from overheating and potential damage, which could lead to critical system failure.

A main cooling fan fault has been detected in the inverter unit. This indicates a failure in the drive's primary cooling system. While other fans may compensate and switching frequency might be reduced, prolonged operation with a main fan fault risks overheating and damage to the drive.

An auxiliary fan fault has been detected; the auxiliary fan is not running. This compromises secondary cooling. The drive trips after a 2-minute suppression period during power-up, during which it only issues a warning. Continued operation without auxiliary cooling can lead to overheating.

A critical hardware failure has occurred within the Safe Torque Off (STO) circuit of the drive, compromising safety functionality. This means the drive cannot guarantee safe disconnection of motor torque, requiring specialist intervention to ensure safety integrity.

The Safe Torque Off (STO) function is active, meaning both STO signals (IN1 and IN2) are switched off or lost, causing the drive to trip. This is a critical safety function that stops the motor for safety. The drive will not start until both STO signals are restored and all faults are reset.

The memory within the drive's Power Unit has been cleared, indicating a loss of configuration or operational data. This internal fault requires expert diagnosis to restore functionality and prevent reoccurrence, as it affects the core logic of the power unit.

There is a discrepancy between the drive's physical hardware identification and the information stored in its memory unit. This often occurs after maintenance such as a firmware update or memory unit replacement, potentially preventing the drive from operating correctly or safely.

The control panel, which was selected as the active control location for the drive, has ceased communicating. This prevents local control, monitoring, and parameter adjustment via the panel, potentially disrupting operator interface.

The feedback signal from the charging system is missing or not detected. This typically indicates a problem with the charging circuit or its monitoring, which could prevent the drive's DC bus from charging correctly, leading to operational failure or preventing the drive from starting.

An unidentified logical fault has occurred within the power unit. This suggests a deep internal problem with the power unit's control or processing, possibly due to corrupted firmware, a hardware malfunction, or an unexpected state. Unresolved, this prevents the drive from operating reliably and requires expert attention.

An internal software error has occurred within the drive's operating system or application. This is a critical fault indicating a software anomaly that prevents normal operation and usually requires expert intervention to resolve. This can be caused by corrupted memory or an unexpected program state.

The firmware installed on the control board is incompatible with the FPGA logic version on the power unit. This mismatch can occur after updates where one component was updated but the other was not, preventing proper communication and control between the two main drive components. This issue prevents the drive from operating.

A read error occurred with the mapping file for fieldbus adapter A. This file is essential for establishing proper data exchange between the drive and the PLC or control system via the fieldbus. Without a valid mapping file, fieldbus communication will fail, preventing remote control or monitoring.

An internal fault where the drive's processor is experiencing an overload of its internal tasks. This indicates a critical condition where the drive cannot maintain its real-time operations and cannot be reset normally. Continued operation is impossible and typically points to a fundamental software or hardware issue.

An internal fault indicating that the drive's program stack has overflowed its allocated memory. This is a severe internal software issue that prevents the drive from executing code correctly and cannot be reset by the user. It signifies a critical programming error or memory corruption.

An attempt to load or save drive parameters has failed. This could indicate an issue with internal memory, configuration storage, or a transient software problem during the parameter operation. This can lead to loss of configuration settings or prevent proper drive setup.

Communication has been lost on the embedded fieldbus (EFB). This means the drive is no longer receiving or sending data to the fieldbus master, leading to loss of control or monitoring via the fieldbus. Critical control functions may be disrupted.

The embedded fieldbus (EFB) configuration file could not be read by the drive. This indicates a potential issue with the EFB's internal software or memory where its settings are stored, preventing it from initializing or operating correctly.

The parameter settings for the embedded fieldbus (EFB) are inconsistent or incompatible with the selected protocol. This prevents the EFB from establishing a stable connection or communicating effectively, leading to operational errors.

The embedded fieldbus (EFB) protocol firmware could not be loaded, or there's a version mismatch between the EFB protocol firmware and the drive firmware. This means the EFB functionality is completely disabled. The drive cannot communicate via EFB.

This is a generic fault reserved for the embedded fieldbus (EFB) protocol application, indicating an unspecified error within the EFB communication stack or protocol execution. The precise cause and resolution are dependent on the specific fieldbus protocol implemented.

This is another generic fault reserved for the embedded fieldbus (EFB) protocol application, indicating an unspecified error within the EFB communication stack or protocol execution. Like EFB fault 2, its exact meaning is dependent on the specific fieldbus protocol in use.

An internal fault indicating an overflow in the text data buffer. This is an internal software or memory issue within the drive. If persistent, it suggests a deeper problem that could affect drive stability and operation.

An internal fault indicating an overflow in a 32-bit text table within the drive's memory. This typically points to an internal software anomaly or a memory management issue. If unaddressed, it could lead to unpredictable drive behavior or further system faults.

An internal fault indicating an overflow in a 64-bit text table. This is an internal software or memory issue within the drive. If persistent, it suggests a deeper problem that could affect drive stability and operation.

An internal fault indicating an overflow related to an internal text file within the drive's memory. This is usually indicative of a software bug or a transient memory allocation issue. Continued occurrence can compromise drive stability.

A communication error has occurred on the control board, specifically on channel CH1. This issue is often caused by electromagnetic interference. The fault is indicated by bit 6 of Fault Word 2 (3.06 FW 2).

Communication between the drive and an option module has been lost. This means the functionality provided by that specific option module is unavailable. The drive may continue to operate but without the features of the affected module.

The control panel or PC tool, configured as the active control location, has ceased communication with the drive. This results in a loss of local control and monitoring capabilities, potentially stopping the drive or preventing startup.

Communication between an I/O module and the drive's control unit is not working properly. This fault can lead to unreliable or non-functional digital/analog inputs and outputs, affecting connected sensors, actuators, and overall process control.

An attempt was made to use a saved control panel reference in multiple control modes simultaneously, which is not permitted. The control panel reference can only be saved for one reference type at a time. This prevents correct reference assignment.

A fieldbus or other option module installed in the drive's option slot is not supported by the drive's firmware or hardware. This module will not function, and its presence might cause conflicts or prevent proper drive operation.

An overvoltage condition has been detected on an Analog Input (AI) of an I/O module. The AI automatically switches to voltage mode from mA mode as a protective measure. If the high signal level persists, it could damage the input circuit or lead to inaccurate process feedback.

The configuration of an I/O module is either not supported or contains illegal settings. This prevents the I/O module from operating as intended, leading to incorrect I/O behavior or non-functionality of connected devices.

The brake resistor is incorrectly wired. This can lead to improper braking operation, potential damage to the resistor or drive, and ineffective energy dissipation during deceleration, creating unsafe operating conditions and poor speed control.

The brake resistor is overloaded, leading to excessive temperature. This can occur if the braking cycle is too demanding, if the supply AC voltage to the drive is excessive, or if the resistor overload protection is misconfigured, risking damage to the resistor.

The motor is operating in a stall region, indicating an excessive mechanical load or insufficient motor power for the applied task. Sustained stalling leads to rapid motor overheating, potential winding damage, and reduced motor lifespan.

The drive detects an issue with the brake resistor, indicating it might be disconnected, physically damaged, or improperly sized. This prevents proper dissipation of regenerative energy, potentially leading to DC bus overvoltage and drive trips during deceleration.

The brake resistor has overheated beyond its fault limit, indicating it's dissipating too much energy. This can be caused by continuous heavy braking cycles, improper resistor sizing, or inadequate cooling, posing a risk of resistor damage or fire.

A short circuit has been detected in the brake resistor wiring, or there's an issue with the brake chopper control circuit. This prevents the brake resistor from functioning correctly, leading to potential DC bus overvoltage and can damage the chopper or drive components.

A short circuit has occurred within the brake chopper's IGBT, indicating a component failure that disables the regenerative braking function. This prevents the dissipation of excess energy, potentially leading to DC bus overvoltage and further drive damage if not addressed.

The IGBT within the brake chopper has overheated beyond its internal fault limit, often due to high ambient temperatures, cooling fan failure, or excessive braking cycles. This fault protects the IGBT from permanent damage but requires investigation into the cooling system or operational demands.

A communication fault exists between the pulse encoder and its interface module, or between the module and the drive. This indicates a failure in the feedback loop crucial for precise motor control, potentially leading to uncontrolled motor movement, poor speed regulation, or system shutdown.

The pulse encoder phasing is incorrect, specifically Phase A is connected to the terminal for Phase B and vice versa. This will result in incorrect speed or position feedback, potentially causing motor rotation direction issues or control instability.

A pulse encoder phase signal is missing, indicating a problem with the encoder connection or the encoder itself. This will result in a loss of accurate motor speed and position feedback, causing erratic motor control or complete shutdown of the motor.

An internal fault has occurred within the encoder system itself, indicating a problem with the encoder's electronics or processing. This is a critical fault preventing accurate speed/position feedback, rendering closed-loop control impossible. This typically requires specialized assistance.

A feedback fault has occurred with Encoder 1. This can manifest during initial setup due to incorrect wiring, or after sustained operation due to damage, electromagnetic interference, or module failure. It results in a loss of accurate motor position/speed data, which is critical for precise motor control.

A feedback fault has occurred with Encoder 2. This is identical in nature to the Encoder 1 fault but pertains to the second encoder feedback channel, leading to similar loss of accurate motor position/speed data. This can affect dual-feedback systems or applications requiring redundant speed/position control.

Cyclical communication between the drive and the master control system has been lost. This indicates a breakdown in fieldbus communication, which can lead to loss of control over the drive and the machinery it operates. Unresolved, this will prevent proper drive operation and could impact process stability.

The supply unit (LSU) did not become ready (e.g., main contactor/breaker closing) within the expected timeframe. This indicates a problem with the LSU's pre-charging or readiness sequence. The drive cannot operate without a ready supply unit.

This is a general EtherCAT Application Layer (AL) status code, indicating that the EtherCAT master received an error code from the drive. The specific fault is detailed by an associated Profile Code in the Mint WorkBench Error Log, which needs to be converted to hexadecimal for interpretation. Without resolving the underlying EtherCAT error, the drive will not communicate correctly, preventing coordinated motion.

This error signifies a CIP (Common Industrial Protocol) configuration issue, where the EtherCAT master received a CIP error code from the drive. The specific problem is detailed by a Profile Code in the Mint WorkBench Error Log, which needs hexadecimal conversion. Improper CIP configuration can lead to communication failures and prevent the drive from operating correctly on the network.

This is a general POWERLINK error code, meaning the POWERLINK master received an error from the drive. The specific fault is represented by a Profile Code in the Mint WorkBench Error Log, which requires hexadecimal conversion for proper identification. Unresolved POWERLINK errors disrupt real-time communication, making the drive unresponsive or causing system halts.

This PROFInet error occurs when the PROFINET master fails to configure the device ID, specifically due to a multicast MAC filter configuration failure. This prevents the drive from being properly identified and communicated with on the PROFINET network, leading to a complete loss of control.

An analogue input signal has fallen below its set minimum limit, which can cause the drive to react by either tripping or setting the speed to a predefined value. This warning indicates a potential loss of critical feedback or reference signal, which could lead to unsafe or unintended operation if not addressed.

A fault signal has been received from an external device, which is configured through one of the drive's programmable digital inputs. This indicates a problem in an external system or process that the drive is integrated with, often a safety interlock or monitoring system, requiring the drive to stop.

An external device configured as External Event 1 (parameters 31.01 and 31.02) has generated a fault. This indicates a problem with equipment or sensors outside the drive's direct control, potentially impacting the entire system's operation and requiring immediate attention.

An external device configured as External Event 2 (parameters 31.03 and 31.04) has generated a fault. This indicates a problem with equipment or sensors outside the drive's direct control, potentially impacting the entire system's operation and requiring immediate attention.

An external device configured as External Event 3 (parameters 31.05 and 31.06) has generated a fault. This indicates a problem with equipment or sensors outside the drive's direct control, potentially impacting the entire system's operation and requiring immediate attention.

The drive has detected an over-temperature condition in the motor. This can be due to a hardwired thermistor input (X10) detecting overheating from a PTC sensor, or from a serial encoder (e.g., Hiperface DSP) reporting excessive motor thermistor resistance. Failure to address this can lead to motor damage and shutdown.

The required phase search process, essential for controlling 'encoder only' type motors, did not complete successfully. This indicates an issue with the motor's initial setup or feedback configuration. The motor cannot be properly controlled until this is resolved, potentially leading to incorrect or no motor movement.

This error occurs when a feedback type of 'halls only' or 'Encoder + Halls' is used, and the drive detects an illegal Hall sensor state (0 or 7). This typically points to a faulty encoder, especially if it includes simulated hall signals, or issues with its wiring. Unresolved, this prevents accurate motor commutation and control.

This fault indicates the drive's serial encoder is not providing position data, either because it's still initializing, or its configured resolution doesn't match the drive. This will prevent axis operation, leading to a crash stop and disabling of the axis, posing a risk of uncontrolled motion if not addressed.

This fault occurs when the drive, designed for a three-phase AC supply, detects a loss in one of its input phases. MotiFlex e100 uses dedicated hardware, while e180 monitors DC bus ripple. Operating with missing phases can lead to motor damage, uneven torque, or drive instability.

This fault indicates a loss of Process Data Object (PDO) communication between a remote axis (Client Node, CN) and the manager (Master Node, MN), specifically when at least two consecutive PDO packets are not received. For a NextMove e100, it means a drive has disappeared from the network. Unresolved, this can lead to loss of control over the remote axis and system instability.

The drive's heatsink has exceeded its safe operating temperature, preventing the system from performing a phase search function. This indicates inadequate cooling, which if ignored, can lead to permanent damage to the drive's power electronics.

This error occurs during Real-time Ethernet control when a Process Data Object (PDO) value sent to the drive exceeds its valid range, often seen with velocity reference PDOs. This typically happens when an axis geared to a master reference has its master position/encoder value changed programmatically, leading to an excessive velocity demand. An out-of-range PDO can cause erratic or uncontrolled motion and system instability.

This fault indicates that one or both of the Safe Torque Off (STO) inputs on the drive are not powered, occurring only when the drive is enabled. This means the safety function is active, preventing motor torque generation, which can halt machine operation for safety reasons.

This fault signals an internal hardware malfunction within the Safe Torque Off (STO) circuits, indicated by the assertion of one or both internal fault circuit outputs. This is a critical safety-related fault, occurring regardless of whether the drive is enabled or disabled, and means the STO function cannot be relied upon, risking uncontrolled torque.

The drive has detected an inconsistency in its internal Safe Torque Off (STO) registers, meaning the two redundant STO inputs are not in the same state. This is a safety fault that can occur whether the drive is enabled or disabled, indicating a potential failure in the safety circuit or a timing issue, which compromises the STO function.

This error indicates a significant discrepancy (at least 70 degrees) between the measured Hall transition angle and the electrical angle used for motor control, suggesting either an encoder reading issue or a Hall sensor fault. This will lead to improper motor commutation, poor control performance, and potentially motor damage.

This is an informational message appearing in the error log, simply indicating that all previously active axis errors have been successfully cleared from the system. It does not signify a new fault.

This information message indicates that the battery backup supply for a Smart Absolute (Smart Abs) encoder has failed. This typically appears during startup or when the drive is enabled. A dead encoder battery means the absolute position information will be lost during power cycles, requiring re-homing or potentially causing incorrect startup positions.

An error has occurred when using the Resolver Adapter (OPT-MF-201 or FB-03) due to a loss of resolver signals. This typically indicates an issue with the wiring to the motor's feedback device, the integrity of the motor connector, or the connections inside the adapter itself, preventing accurate position feedback and control.

An error has occurred while attempting to read position data over the Hiperface DSL interface. This suggests a problem with the feedback device wiring, the motor connector, or connections inside the adapter, which can lead to inaccurate or lost position information, affecting motor control and synchronization.

The drive has detected that the output frequency has exceeded 550 Hz. This restriction is required to meet relevant European Export Control Regulations. Operating above this frequency can violate regulatory requirements and indicates an issue with the control system's commanded speed, potentially leading to shutdown.

The motor's commanded velocity has exceeded the value set in the `DRIVESPEEDMAX(0)` parameter. This indicates that the drive is attempting to operate the motor beyond its configured maximum speed limit, potentially causing instability, fault trips, or premature wear on mechanical components.

The drive's internal temperature sensor has detected a dangerously high temperature, exceeding the model-dependent TEMPERATURELIMITFATAL threshold (e.g., 80°C for e190 3A/e180, 75°C for e190 6A/9A). Sustained over-temperature operation can severely reduce the lifespan of electronic components and lead to drive failure.

The Field-Programmable Gate Array (FPGA) within the drive's controller failed to initialize correctly. This indicates a critical internal hardware issue. If unresolved, the drive will be inoperable, preventing any control functions.

The drive is unable to access its non-volatile memory, where critical parameters and configurations are stored. This suggests a hardware fault within the memory system. Without access to this memory, the drive cannot retain settings or operate correctly.

This error indicates that during a parameter table download or startup, some parameters could not be correctly applied, often due to an issue with the parameter file (.ptx). This commonly occurs when using a parameter file generated with an older firmware version that has incompatible parameters or limits. The drive will not operate correctly with incorrect parameters, potentially leading to unexpected behavior or damage.

A generic internal error has occurred within the controller, specifically indicating a failure to read a parameter. This points to an underlying hardware or firmware issue. The drive cannot operate reliably with internal errors, risking unpredictable behavior.

The drive has detected a failure of its internal cooling fan. This means the drive is not being adequately cooled, and continued operation risks severe over-temperature conditions, leading to damage to internal components.

The drive has detected a communication error with the Mint option card, specifically related to transmit (Tx) operations. This indicates a problem with the data exchange between the main drive and its optional Mint module. If persistent, this can render the Mint functionality unusable, affecting specialized control or communication tasks.

The controller has detected that the ambient temperature around the drive has fallen below its minimum operating threshold of -5°C. Operating below the specified temperature range can lead to unreliable performance or damage to electronic components. The drive will prevent enablement until conditions are suitable.

This is an informational message in the error log, indicating that all previous controller-related errors have been cleared. It's a status notification, not an active fault.

This error indicates that the drive's hardware revision does not support Ethernet POWERLINK (EPL). Specifically, earlier e180 drives with GCU-01 control cards before Revision A lack EPL support. If the EPL address switches are not set to '0' on such hardware, this error will be generated. While the drive may function in other modes, EPL functionality will be unavailable, requiring a hardware upgrade if EPL is essential.

The drive has detected an earth (ground) fault or current unbalance in the motor or motor cable, but it is configured to issue a warning rather than trip. While allowing continued operation, this indicates a potentially developing safety issue or insulation degradation that requires immediate attention before it escalates to a full fault.

The Safe Torque Off (STO) function is active, meaning the safety circuit signal(s) connected to the STO connector have been lost or removed. Depending on parameter 31.22, this can be a warning when STO is intentionally activated, or an indication of an unintended safety circuit issue. The drive will prevent motor rotation for safety.

A problem has been detected with the internal temperature measurement circuit of the drive. This means the drive may be unable to accurately monitor the temperatures of critical components (e.g., IGBTs, power supply board), which could lead to undetected overheating and damage if left unresolved. The auxiliary code provides specific location details of the issue.

The drive's built-in or extension I/O module is not detected or improperly connected. This configuration failure can lead to loss of control, inability to read inputs, or activate outputs, rendering the drive's control functions inoperable.

The control panel (or connected PC tool) has lost communication with the drive. This prevents operator interaction and monitoring through the panel. If communication is not restored, local control and diagnostics are unavailable.

This warning is generated by a signal supervision function, indicating an abnormality or unexpected condition in a monitored signal, potentially due to out-of-range values, signal loss, or noise. This can affect the drive's control accuracy or lead to unexpected behavior.

The Insulated Gate Bipolar Transistor (IGBT) within the brake chopper has exceeded its internal temperature warning limit. This indicates excessive heat generation due to sustained braking, inadequate cooling, or an overdriven chopper, risking damage to the power components and potentially causing drive failure.

Warning generated by value counter 1, indicating a predefined count threshold has been reached for a monitored value. This is often used for tracking production cycles, material usage, or other process-related counts. Overlooking this could lead to process deviations or component wear.

Warning generated by value counter 2, indicating a predefined count threshold has been reached for a monitored value. This is often used for tracking production cycles, material usage, or other process-related counts. Overlooking this could lead to process deviations or component wear.

This warning is generated by an on-time timer, signaling that a specific device requires cleaning based on its operational duration. An auxiliary code in the event log indicates which timer is responsible for triggering this warning. Ignoring this warning can lead to reduced efficiency, overheating, or premature failure of the device.

A main cooling fan fault has been detected in the inverter unit. This indicates a failure in the drive's primary cooling system. While other fans may compensate and switching frequency might be reduced, prolonged operation with a main fan fault risks overheating and damage to the drive. The drive generates a warning and attempts to continue operation.

An auxiliary cooling fan, typically connected to the control board, is either stuck, disconnected, or has failed. This compromises the supplemental cooling for the drive's internal components, potentially leading to overheating warnings or faults if the thermal conditions worsen, especially in high ambient temperatures or loads.

The drive's hardware setup is in the process of initializing. This is a normal startup phase; however, if this warning persists, it might indicate a hang in the initialization sequence. This can prevent the drive from entering a ready state for operation.

The drive's hardware is undergoing its initialization process. While typically a brief startup event, persistent initialization can signal a deeper issue with the drive's hardware or firmware. The auxiliary code might provide more context on the specific stage of initialization.

This is a programmable warning indicating a motor stall condition. The motor current has exceeded the defined stall current limit, while the output frequency or speed is below its respective limit for a set duration. This suggests the motor is overloaded or mechanically constrained, potentially leading to overheating if not addressed.

No feedback has been received from the external motor fan. This indicates that the fan may not be operating, leading to potential motor overheating if cooling is insufficient. The drive may continue operation, but motor thermal protection could eventually trip it.

An error in temperature measurement from a KTY or PTC sensor connected to encoder interface FEN-xx has occurred. This could be due to incorrect parameter settings or using an unsupported sensor type (e.g., KTY on FEN-01). Inaccurate temperature feedback risks motor overheating or improper thermal protection.

The motor current is too high, indicating an overload condition on the motor. This can lead to motor overheating, winding damage, and reduced motor lifespan if sustained. The drive will eventually trip to protect the motor.

The drive has detected that all three output phases are disconnected from the motor. This can occur due to an open motor circuit, open switches, or faulty cabling, preventing the drive from controlling the motor and potentially causing damage to the drive if it attempts to operate into an open circuit.

A general fault has been detected within the brake resistor circuit. This may indicate an open circuit, incorrect resistance, or an inability to dissipate regenerative energy, which could lead to DC link overvoltage and a drive trip.

A short circuit has been detected in the brake resistor or a fault within the brake chopper itself. This condition prevents the safe dissipation of regenerative energy and can lead to damage to the brake chopper components, potentially causing further drive faults.

The brake resistor temperature has exceeded the warning limit defined by parameter 43.12. This indicates the resistor is overheating, potentially due to excessive braking duty or improper dimensioning. Continued operation risks damage to the resistor or associated components.

One or more critical parameters related to the brake resistor's data (such as resistance value, thermal time constant, or maximum continuous power) are either incorrect or not properly configured. This prevents the drive from accurately managing and protecting the brake resistor, risking damage during braking operations.

The speed feedback configuration has changed or is inconsistent. The auxiliary code provides details on the specific encoder interface module and encoder affected, and the nature of the problem. This can lead to incorrect speed control or motor operation.

The drive generates a warning when communication to an I/O extension module fails. This indicates a disruption in the control signal flow between the drive and its peripheral I/O, potentially affecting system operation and control accuracy.

This warning is generated by an on-time timer or a value counter, likely indicating a scheduled maintenance alert for the motor bearings. It signals that a predefined operating threshold has been met, suggesting a need for inspection or service. Ignoring this could lead to bearing failure and motor damage.

This warning is triggered by an edge counter, implying a monitoring function for an output relay has reached a programmed limit or detected an unexpected edge transition. It likely indicates an issue with the relay's operation or a need for inspection. Unresolved, this could affect controlled equipment.

Warning generated by on-time timer 1, indicating that a predefined operational time limit has been reached or exceeded. This often serves as a maintenance reminder or an alert for extended operation. Failure to address could lead to component wear or overdue service.

Warning generated by on-time timer 2, indicating that a predefined operational time limit has been reached or exceeded. This often serves as a maintenance reminder or an alert for extended operation. Failure to address could lead to component wear or overdue service.

Warning generated by edge counter 1, indicating that a specific number of events (edges) has been detected or a threshold has been crossed. This is typically used for monitoring operations, component life, or sequence integrity. Ignoring this could lead to unexpected behavior or component failure if a limit is exceeded.

Warning generated by edge counter 2, indicating that a specific number of events (edges) has been detected or a threshold has been crossed. This is typically used for monitoring operations, component life, or sequence integrity. Ignoring this could lead to unexpected behavior or component failure if a limit is exceeded.

An external device configured as External Event 1 (parameters 31.01 and 31.02) has generated a warning. This indicates a potential issue with external equipment or sensors that should be investigated, though it may not cause an immediate drive trip. Addressing warnings proactively prevents escalation to faults.

A fault has occurred in an external device connected to the drive's external event input 2. This general warning indicates an issue with peripheral equipment that the drive is monitoring. The drive continues to operate, but the external device needs attention.

A fault has occurred in an external device connected to the drive's external event input 3. This general warning indicates an issue with peripheral equipment that the drive is monitoring. The drive continues to operate, but the external device needs attention.

A fault has occurred in an external device connected to the drive's external event input 4. This general warning indicates an issue with peripheral equipment that the drive is monitoring. The drive continues to operate, but the external device needs attention.

A fault has occurred in an external device connected to the drive's external event input 5. This general warning indicates an issue with peripheral equipment that the drive is monitoring. The drive continues to operate, but the external device needs attention.

The supply unit generates a warning when an earth fault or current unbalance is detected. This indicates a potential insulation issue within the supply unit's power circuit or its input cabling, requiring attention to prevent a full fault trip or damage.

The drive is entering sleep mode as part of its process PID control function. This is an informative warning, indicating normal operation when conditions allow for energy saving. It does not signify a fault requiring intervention.

DDCS (fiber optic) communication between converters (e.g., inverter unit and supply unit) has been lost. The inverter unit will continue operating based on the last received status, but synchronized operation and full diagnostics are compromised. Loss of communication can lead to system instability or incorrect power flow.

The supply unit (or another converter) has generated a warning. The auxiliary code specifies the original warning code from the supply unit's control program. This indicates a problem on the line-side of the system, which could affect the entire drive operation.

The drive's season configuration for scheduled operations contains an error where a season is set to start before a previous one. This logical inconsistency will prevent proper execution of time-based functions, potentially causing the system to operate outside of desired schedules.

The speed controller autotune routine did not complete successfully. The auxiliary code provides details, such as the drive being stopped prematurely. This means the speed controller may not be optimally tuned, leading to suboptimal motor performance.

This alarm signal from the ground fault monitor (option +Q954) is explicitly recommended to be connected for immediate drive tripping upon detection of a ground fault in IT (ungrounded) systems. The contact is normally closed when no ground fault is present and has a load capacity of 250 V AC, 2 A. Be aware that the ground fault monitor performs self-testing, which might momentarily activate this signal, necessitating careful distinction between actual faults and test sequences.

This alarm signal from the ground fault monitor (option +Q954) is intended for general alarm indication purposes, rather than directly tripping the drive. The contact is normally closed when no ground fault is present and has a higher load capacity of 250 V AC, 8 A. It is crucial to understand that the monitor's internal self-testing might briefly activate this signal, requiring careful interpretation by any receiving alarm or monitoring system.

A fatal error occurred during the drive's boot-up sequence, indicated by a 'b' followed by a five-digit code on the seven-segment display. This suggests a critical issue with the memory module, firmware, or connected external hardware that prevents the drive from initializing and becoming operational.

This error typically occurs after a firmware upgrade when parameters are being re-instated. It indicates that the new firmware version includes parameters not present in the old parameter file, preventing proper configuration. The drive may not become operational without intervention.

A fatal error occurred during the drive's boot-up sequence, displayed as a 'b' followed by a five-digit code on the seven-segment display. This indicates a critical issue with the memory module, firmware, or connected external hardware, preventing the drive from initializing and becoming operational.

A resource failure has occurred on the I/O bus module. This means a critical component or allocated resource within the module (e.g., memory, processing units, communication channels) has become unavailable or corrupted, leading to operational issues and potential loss of I/O control.

A timeout occurred during an operation on the I/O bus module. This indicates that a communication or processing step did not complete within its expected timeframe, possibly due to bus congestion, a slow response from a connected device, or a module malfunction. This can lead to unresponsive I/O.

The type scaling process failed during PLC startup. This is a critical error that prevents the PLC from correctly interpreting data types and ranges for I/O and internal variables. It can halt the startup process, lead to incorrect calculations, and compromise process control.

The flash memory, specifically for the flash disk, has entered a temporary protected (read-only) 'panic mode'. This critical state is typically triggered to prevent further data corruption when severe integrity issues are detected, rendering the system unable to write data and potentially causing instability.

An error occurred while attempting to set a parameter for the I/O bus master. This indicates a problem with configuring the communication master, potentially preventing it from correctly initiating or controlling connected I/O devices. This can lead to a complete loss of I/O communication.

The display unit has an incompatible or incorrect firmware version installed. This mismatch can lead to the display not functioning, showing corrupted graphics, failing to communicate with the main processor, or displaying incorrect information. This hinders effective user interaction and diagnosis.

The CPU failed to set the 'Reboot at powerfail' parameter, which controls the system's behavior during power interruptions. This means the system might not restart correctly or automatically after a power failure, potentially requiring manual intervention to resume operation. This impacts system resilience.

The CPU has detected an unsupported or invalid combination of plugged option boards. This hardware configuration error can prevent the CPU from starting or operating correctly, as the system does not recognize the installed modules. This requires physical verification of the setup.

A restore operation on the CPU, likely involving configuration or application data, has failed. This can lead to the CPU operating with incorrect settings, an older configuration, or failing to start completely, compromising the intended system functionality. Data integrity is at risk.

An I/O bus module timed out during its initialization sequence. This critical error suggests a problem preventing the module from becoming ready for operation, possibly due to a hardware fault, firmware issue, or communication problem. The module will not be functional.

An I/O bus module failed to complete its reset sequence within the allotted time. This indicates a severe issue with the module's internal processing or its ability to respond to control signals, halting its operation and preventing it from becoming ready for use.

Communication has been completely lost with an I/O bus module, indicating a breakdown in the communication link. This critical failure means the module is no longer accessible or functional within the system, leading to a complete loss of I/O control for that module.

A severe error has occurred on the I/O bus module, significantly impacting its operation. More detailed information regarding the specific cause and context of this error is available in the system log files, which should be consulted for proper diagnosis and troubleshooting.

A severe, fatal error has occurred on the I/O bus module, leading to a critical system failure. This likely halts operation and requires immediate investigation into the system logs for specific details on the cause. Unresolved, this error will prevent the system from functioning.

A fatal error has occurred on the I/O bus module, causing the entire system to stop running. This indicates a critical fault that has rendered the system inoperable. Immediate intervention is required to identify and rectify the issue and restore system operation.

For an I/O bus module, the configured discrepancy time for a specific channel has expired. This typically occurs in safety applications where redundant signals do not match within the allowed time frame, indicating a potential sensor malfunction, wiring issue, or incorrect time setting. This can lead to safety shutdowns.

The flash disk medium has almost used its complete spare capacity or is already dead. This is a severe warning indicating imminent or actual storage failure, which can lead to irreversible data loss, system operational halts, and inability to store critical data. Immediate action is required.

A test pulse error has been detected on an I/O bus module channel. This indicates a problem during the module's self-diagnosis, where the generated test pulse or its response was unexpected, potentially due to wiring faults or sensor malfunctions. It can compromise the reliability of the I/O channel.

A test pulse cross-talk error has occurred on an I/O bus module channel. This suggests unwanted interference between adjacent channels or an issue where a test pulse is being incorrectly detected on another channel. This can lead to unreliable I/O operation, incorrect data, and system instability.

A general test error has been reported by an I/O bus module. This indicates a failure during an internal diagnostic test, implying an issue with the module's hardware or firmware functionality. This can lead to unreliable I/O behavior or a complete module failure.

An error occurred during the initialization process of the system's display unit. This means the display may not be functioning correctly, showing no output, or displaying garbled information, hindering user interaction, diagnosis, and overall system usability.

A 'stuck-at' error has been detected on an I/O bus module, indicating that a signal line or a logic gate within the module is permanently fixed at a high or low state. This prevents proper signal transmission or processing, leading to incorrect I/O values and unreliable control.

A cross-talk error has been detected on an I/O bus module. This means unwanted signal coupling is occurring between adjacent channels, leading to incorrect readings or control actions, and potentially compromising system integrity. This interference affects signal reliability.

The CPU failed to load the boot project because of an issue with loading retain data. This indicates that critical persistent data, necessary for the project's operation, could not be retrieved, potentially leading to an incomplete or incorrect system startup. This can cause the PLC to run with default or corrupted settings.

The CPU failed to load the boot project because the retain data detected does not match the project's requirements. This mismatch can occur after firmware updates or project changes, causing the CPU to reject the current configuration and potentially halting operation. Data consistency is crucial.

The CPU was unable to load the boot project because it detected insufficient licensing for the application. This prevents the application from starting and running, indicating a licensing issue rather than a hardware fault. The PLC may enter demo or stop mode, rendering it inoperable for licensed features.

The CPU failed to load the boot project for an unspecified reason. This general error indicates a problem during the loading process that could stem from various issues, including corrupted project files, transient hardware issues, or firmware problems. Further investigation is needed to pinpoint the cause.

A backup operation on the CPU, such as saving configuration or application data, has failed. This means recent changes may not be properly archived, putting critical data at risk in case of a system failure, power loss, or accidental deletion. Regular backups are crucial for system recovery.

The root partition of the flash disk has 1% or less free space remaining. This is a critical error indicating imminent disk space exhaustion, which can lead to system instability, crashes, inability to write logs, or update firmware. Urgent action is required to prevent system failure.

A general test error has been reported by an I/O bus module on a specific channel. This indicates a failure during an internal diagnostic test, implying an issue with the module's hardware or firmware functionality related to that particular channel. This can compromise the reliability of the affected I/O.

The measured value on an I/O bus module channel exceeds the configured tolerance window compared to an expected or redundant value. This indicates a potential sensor malfunction, wiring issue, or an incorrectly set tolerance. It can lead to false alarms or inaccurate process control.

A 'stuck-at' error has been detected on an I/O bus module for a specific channel. This indicates that a signal line or a logic gate within that channel is permanently fixed at a high or low state, preventing proper signal transmission or processing. This leads to incorrect I/O values.

A readback error has occurred on an I/O bus module. This means the value read back from an output or an internal register does not match the value that was commanded or expected. This indicates a potential hardware fault, wiring issue, or corrupted internal state, compromising output verification.

A cross-talk error has been detected on a specific channel of an I/O bus module. This means unwanted signal coupling is occurring between adjacent channels, leading to incorrect readings or control actions, and potentially compromising system integrity. This interference affects signal reliability.

A general test error has been reported by an I/O bus module on a specific channel. This indicates a failure during an internal diagnostic test, implying an issue with the module's hardware or firmware functionality related to that particular channel. This can compromise the reliability of the affected I/O.

A general internal error has occurred within a specific channel of the I/O bus module. This signifies an unspecified hardware or software fault within that particular channel, potentially halting its functionality or causing unreliable operation. This indicates a localized critical internal issue.

A general test error has been reported by an I/O bus module on a specific channel. This indicates a failure during an internal diagnostic test, implying an issue with the module's hardware or firmware functionality related to that particular channel. This can compromise the reliability of the affected I/O.

The I/O bus module has detected a communication protocol variant that is not supported. This indicates an incompatibility in communication standards between the module and other devices, preventing proper data exchange and potentially halting the module's operation. This is a configuration or firmware mismatch.

The I/O bus module failed to complete its maximum allowed wait run time. This indicates a significant delay in processing or a communication deadlock, potentially causing I/O operations to time out and impacting system responsiveness or control. It suggests a performance or communication bottleneck.

The F-Parameter configuration for the I/O bus module does not match the module's physical address switch value. This discrepancy indicates an incorrect setup, potentially leading to improper I/O operation, communication failures, and system instability. Incorrect configuration can halt module functionality.

An internal data interchange failure has occurred within the I/O bus module. This suggests a critical hardware malfunction or corruption within the module's internal communication pathways, preventing proper data exchange and rendering the module inoperable. It is a severe internal fault.

The I/O bus module has incompatible hardware and/or firmware versions. This mismatch can lead to unexpected behavior, functional limitations, or complete operational failure as components are not designed to work together, potentially causing system instability.

A general internal error has occurred within the I/O bus module. This signifies an unspecified hardware or software fault within the module itself, potentially halting its functionality, causing unreliable operation, or leading to system downtime. It indicates a critical internal issue.

The sensor voltage detected on the I/O bus module is below the acceptable threshold. This indicates a potential issue with the power supply to the connected sensors or a fault within the sensors themselves, leading to inaccurate readings or complete sensor malfunction and unreliable process control.

The system's battery is either empty or entirely missing. This warning indicates that non-volatile data, such as configuration parameters, retained variables, or real-time clock settings, may be lost during power cycles if the issue is not resolved. This can lead to system re-configuration needs on every restart.

The flash disk medium has utilized 80% of its total spare capacity. This is a warning that the flash storage is approaching its wear limit, which can lead to reduced performance, slower write operations, and eventual component failure if not addressed. Proactive measures are recommended.

The root partition of the flash disk has 15% or less free space remaining. This warning indicates that critical system operations may be impacted, potentially leading to instability, inability to store new logs, updates, or temporary files. Continued operation with low space can cause system crashes.

The I/O bus module's compensation channel is providing incorrect measurements or a false temperature reading. This can lead to inaccurate process control, improper compensation for sensor errors, or system instability, especially in temperature-sensitive applications. Untrustworthy data poses operational risks.

For analog input AI531, the measurement is incorrect due to an excessively high potential difference. For PWM output CD522, the duty cycle is operating outside its acceptable range. Both issues can lead to inaccurate control, component damage, or system instability, requiring immediate attention to prevent operational errors.

An I/O module has been removed from a hot swap terminal unit while the system was operational. This is typically a warning indicating a change in the I/O configuration. If unintentional, this can lead to incomplete I/O functionality or system errors related to the missing module.

An incorrect I/O module type has been plugged into a hot swap terminal unit, replacing the module that was originally expected. This module type mismatch can lead to configuration errors, prevent the system from operating correctly, and potentially damage the module or terminal unit.

Communication has been lost with an I/O module installed on a hot swap terminal unit. This indicates a failure in the communication link or a fault within the module itself, preventing data exchange and rendering the I/O module inoperable. This affects all connected sensors/actuators.

An I/O module that does not support hot swap functionality has been detected on a hot swap terminal unit. This configuration mismatch can lead to improper operation, module damage if removed/inserted while powered, or general system errors. Modules not designed for hot swap require specific handling.

The system requires a hot swap terminal unit for proper operation, but it was not detected or is missing. This configuration error can prevent the system from recognizing or communicating with I/O modules, leading to incomplete system functionality or a halt.

The hot swap terminal unit itself has been identified as defective. This hardware fault can prevent proper communication with any I/O modules connected to it, potentially leading to widespread I/O errors and system instability. All modules on this unit will be affected.

Communication with the hot swap terminal unit has been lost. This can be due to a temporary glitch or a hardware failure in the terminal unit or its communication path, affecting all I/O modules connected to it. This can lead to loss of I/O control.

An I/O bus module has been identified as not having passed its factory tests. This indicates a manufacturing defect or pre-existing hardware fault, which could lead to unreliable operation, premature failure, or incorrect functionality. This module is likely faulty out of the box.

The required process voltage (UP or UP3) for the I/O bus module is not present. This critical power supply issue will prevent the I/O module and any connected field devices from operating correctly, resulting in a complete loss of I/O functionality.

The CPU was unable to locate at least one required parameter during operation. This parameter error can prevent proper configuration or execution of CPU functions, potentially leading to system misbehavior, incomplete startup, or a halt in processing. It indicates a configuration or memory issue.

The CPU encountered an error while attempting to read the value of at least one parameter. This can signify data corruption, an inaccessible memory location, or a configuration issue, affecting the CPU's ability to operate as intended and potentially leading to incorrect processing or system failures.

This fault indicates a discrepancy in the status of the two Safe Torque Off (STO) channels. The drive's diagnostics have detected that the STO channels are not in the same state, or that STO was attempted to be activated in a non-redundant manner (e.g., only one channel activated). This prevents the STO safety function from operating correctly and will cause the drive to trip, leading to an uncontrolled stop or inability to start, posing a safety risk if machine motion is not reliably prevented.

This fault indicates a discrepancy in the status of the two Safe Torque Off (STO) channels. The drive's diagnostics have detected that the STO channels are not in the same state, or that STO was attempted to be activated in a non-redundant manner (e.g., only one channel activated). This prevents the STO safety function from operating correctly and will cause the drive to trip, leading to an uncontrolled stop or inability to start, posing a safety risk if machine motion is not reliably prevented.

The inverter type (e.g., sr0025_3) has been changed, a process typically performed at the factory or during initial drive implementation. This alarm signals that the new hardware configuration needs validation by cycling the control board power.

The inverter type (e.g., sr0025_3) has been changed, typically at the factory or during drive implementation, and a power cycle is required to validate this change. This alarm prompts the user to switch off the control board power to finalize the hardware reconfiguration and allow the drive to operate with the new settings.

A fault has occurred on the line-side converter of the drive system. This indicates a problem with the input power stage that converts AC supply to DC bus voltage, potentially affecting the drive's ability to operate or drawing excessive current.

Motor data required by the drive is either missing or the configured motor data does not match the inverter's requirements. This fault is linked to bit 1 of Fault Word 2 (3.06 FW 2).

One of the motor phases is lost, caused by a fault in the motor, motor cable, thermal relay (if used), or an internal drive fault. This condition leads to unbalanced motor currents, potentially causing motor overheating, vibration, and damage to the motor or drive.

The drive's supply voltage is excessive, exceeding 124% of the unit's voltage rating. When this occurs, the motor speed can rapidly accelerate (rush) to a trip level (40% of nominal speed), indicating a potentially damaging overvoltage condition for the drive and potentially the motor.

The drive output filter (choke) has an excessive temperature. This supervision function is typically used in step-up drives and indicates potential overheating due to restricted airflow, a faulty filter fan, or high ambient temperatures, risking damage to the filter components.

The drive output filter fan has an excessive temperature. This supervision is active in step-up drives and indicates potential overheating if airflow is restricted, the fan is faulty, or ambient temperatures are too high, risking damage to the filter or drive.

The drive is limiting motor torque based on calculated motor pull-out torque and the minimum/maximum torque limits defined by parameters 20.13 and 20.14. This informative alarm indicates the drive is operating at its torque limits, potentially due to high load, incorrect motor parameters, or insufficient motor identification. Sustained operation at torque limits can hinder performance and prevent achieving desired output.

The drive is actively limiting motor power according to the boundaries defined by parameter 20.11 (P MOTORING LIM) for motoring and 20.12 (P GENERATING LIM) for generating. This is an informative alarm (programmable Fault Function 30.23, bit 4: MOT_POW_LIM_IND) indicating the drive is operating at its configured power limits.

An overtemperature condition has been detected on the AINT board of an inverter module. Prolonged operation at elevated temperatures can lead to accelerated degradation and eventual failure of critical electronic components on the board.

An overtemperature condition has been detected in the choke of a liquid-cooled R8i inverter module. This indicates that the choke's temperature has surpassed its safe operating threshold.

A source selection (pointer) parameter within the drive's configuration is pointing to a non-existent parameter index. This indicates an invalid parameter configuration, which can lead to unexpected drive behavior or incorrect signal routing.