ABB ACS850

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.

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 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.

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.

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.

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.

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.

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.

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.