Indramat Indradrive

This fault indicates an unhandled software exception or a severe firmware error within the IndraDrive controller's main processor. It typically points to an internal system inconsistency or a critical programming issue, causing the drive to halt operation to prevent damage or unsafe conditions.

The drive detected a simultaneous failure of two Master Status Telegrams (MST). This is a critical communication error indicating a severe disruption in the primary communication link between the master controller and the IndraDrive, leading to a shutdown to ensure safety.

The drive detected a simultaneous failure of two Master Data Telegrams (MDT). This is a critical communication error indicating a severe disruption in the primary communication link where the master controller fails to receive expected data from the IndraDrive, leading to a shutdown.

The IndraDrive detected an invalid communication phase in its bus communication. This means the communication process is not progressing through the expected states (e.g., initialization, pre-operational, operational) in the correct order, often due to an unexpected command or communication failure.

The communication between the IndraDrive and its master controller failed to progress to the next expected communication phase. This indicates a stall or failure in advancing through the required communication states (e.g., from phase 0 to 1, or 1 to 2), preventing operational mode.

The drive has exceeded the maximum allowable braking time during a deceleration sequence. This means the motor or load took too long to come to a stop or reduce its speed, often indicating an issue with the braking system or excessive inertia.

The motor's actual position has exceeded the configured positive software travel limit. This fault indicates that the axis has moved beyond its allowed maximum position, potentially entering an unsafe area or causing mechanical damage.

The motor's actual position has exceeded the configured negative software travel limit. This fault indicates that the axis has moved below its allowed minimum position, similar to F6029 but in the opposite direction.

The external emergency stop circuit connected to the IndraDrive has been activated, commanding an immediate and controlled stop of the motor. This is a safety feature designed to bring the machine to a safe state in an emergency.

Both the positive and negative hardware travel limit switches have been simultaneously activated. This is an illogical state, as the axis cannot physically be at both ends of its travel range at the same time, indicating a wiring error or sensor malfunction.

The hardware limit switch for the positive travel range has been activated, indicating that the axis has reached or exceeded its positive mechanical limit. This causes the drive to stop further movement in the positive direction to prevent damage.

The hardware limit switch for the negative travel range has been activated, indicating that the axis has reached or exceeded its negative mechanical limit. This stops further movement in the negative direction to prevent damage.

This safety fault indicates that a safety-related monitored increment of position has been exceeded. This is part of safe motion monitoring functions (e.g., Safe Incremental Position) which ensure that the axis does not move more than a defined distance within a specific timeframe or under certain conditions.

The motor's actual position has exceeded a defined safety-related position limit in the positive direction. This fault is triggered by safety monitoring functions (e.g., Safely Limited Position) to prevent the axis from moving beyond a safe physical boundary.

The motor's actual position has exceeded a defined safety-related position limit in the negative direction. This fault, part of safe motion monitoring, prevents the axis from moving beyond a safe physical boundary in the reverse direction.

The motor's actual velocity has exceeded a safety-related velocity threshold. This fault is part of safe motion monitoring (e.g., Safely Limited Speed) and is triggered when the axis moves faster than permitted under certain safety conditions, potentially leading to a hazardous situation.

The motor's actual acceleration has exceeded a safety-related acceleration threshold. This fault is triggered by safety monitoring functions (e.g., Safe Acceleration Monitoring) to ensure that the axis does not accelerate faster than what is considered safe for the application, preventing sudden, uncontrolled movements.

The motor's actual velocity has exceeded a safety-related maximum velocity limit. This is a critical safety function (e.g., Safe Maximum Speed) designed to prevent the axis from ever exceeding an absolute safe operating speed, regardless of commanded values, to avert machinery damage or injury.

The motor's actual position has exceeded a safety-related end position limit. This is a critical safety function similar to F7011/F7012 but often refers to an absolute physical stop or a final safety limit, indicating that the axis has moved into an unsafe zone.

The motor's actual position has moved outside the defined safety-related operational stop position window. This fault occurs when a safe operational stop function is active, meaning the motor should be held within a very narrow position tolerance, but has drifted or moved excessively.

The motor attempted to move in a direction opposite to the allowed or commanded direction during a safety-monitored operation. This fault indicates a serious discrepancy between the expected and actual motion, usually triggered by a safety function like Safe Direction.

This safety fault indicates an inconsistency or implausibility between a configured safety-related threshold parameter and the actual effective threshold being applied by the drive's safety logic. This typically means the drive cannot confirm that the safety setting is correctly implemented or active.

The actual position value reported by the encoder or derived by the safety technology is deemed implausible or inconsistent. This often occurs when there's a significant and unexpected discrepancy between redundant position sensors or internal estimations, indicating a potential loss of reliable position feedback.

An inconsistency or implausibility was detected in the active safety-related operating mode. This means the drive's safety system cannot confirm that the commanded or actual operating mode (e.g., Safe Limited Speed, Safe Operating Stop) is being correctly and safely implemented.

This safety fault indicates a problem with the interlock circuit that controls the output stage (power section) of the drive. The interlock is a critical safety mechanism that prevents the drive from applying power to the motor unless all safety conditions are met, and an error means it's not functioning correctly.

The axis failed to come to a complete stop within the allocated time after a safety-related stop command was issued. This indicates that the machine's deceleration was insufficient, or there was an uncontrolled movement during the stop, violating a safety stopping time requirement.

During automatic commutation determination, the motor exceeded its maximum allowed motion range while attempting to move backward. This error indicates that the drive could not find the correct commutation offset within the expected mechanical limits during an automatic setup procedure.

The IndraDrive failed to determine the commutation offset necessary for proper motor control during an automatic setup routine. This offset is crucial for aligning the rotor position with the stator field, and its absence prevents the drive from starting the motor correctly.

During automatic commutation, the motor exceeded its maximum allowed motion range (either positive or negative direction). This indicates that the drive could not complete the commutation determination within the configured or inherent mechanical movement limits.

During the automatic commutation procedure, the current measured by the IndraDrive was too low to effectively determine the motor's commutation offset. This typically means the drive cannot apply enough current to rotate the motor or detect its response reliably.

An overcurrent condition occurred in the power section during the automatic commutation procedure. This indicates that the drive commanded or experienced current levels exceeding safe limits while attempting to determine the motor's commutation offset.

The automatic commutation procedure failed to complete within the allotted time. This indicates that the IndraDrive could not successfully determine the motor's commutation offset within the expected duration, leading to a timeout error.

The automatic commutation routine repeatedly failed to converge on a valid commutation offset, indicating that the iteration process did not yield a stable or conclusive result. This suggests inconsistent feedback or an inability to consistently influence motor position.

Encoder 1, which is typically the primary motor feedback encoder, is providing incorrect or invalid signals. This could mean signal loss, noise, inverted signals, or a general malfunction preventing accurate position or velocity feedback to the IndraDrive.

This error indicates a problem with the mechanical coupling between the encoder and the motor shaft, or a general issue with the motor's mechanical connection. This can lead to a discrepancy between the motor's actual rotation and the encoder's reported position, causing control instability.

The IndraDrive is in an enabled state but cannot start the motor due to an active starting lockout condition. This lockout typically occurs for safety reasons or to prevent unintended motor movement until specific conditions are met, even if the enable signal is present.

The IndraDrive has detected an overload condition within its internal power components and has shut down to protect itself. This typically happens when the drive is commanded to supply current beyond its continuous rating for an extended period, leading to excessive internal heat generation.

A sudden surge of current exceeding the instantaneous rating was detected in the IndraDrive's power section, leading to an immediate shutdown to prevent damage. This is often caused by a short circuit in the motor or cabling, or a rapid acceleration of a high inertia load.

This error indicates an issue with the internal ±15V DC power supply rails within the IndraDrive. These voltages are typically used for sensitive analog circuitry, such as encoder interfaces, current measurement, and control section components. A failure here affects internal signal integrity.

This error signifies a problem with the internal +24V DC power supply of the IndraDrive. This voltage rail typically powers control logic, digital I/O, and possibly external sensors or actuators. A failure here can lead to loss of control, I/O functionality, or sensor readings.

The IndraDrive detected an excessive deviation or instability in the motor's actual speed compared to the commanded speed, indicating a problem with the speed control loop. This can result in poor motor performance, oscillations, or inability to maintain target velocity.

The motor's actual velocity has exceeded the limit defined by parameter S-0-0091 (Maximum Velocity). This fault occurs when the drive detects the motor spinning faster than permitted, potentially due to external forces, incorrect control, or an encoder misread.

This fatal error indicates a failure within the IndraDrive's power section, which is responsible for converting and supplying power to the motor. This could involve issues with IGBTs, power capacitors, or other high-power components, making the drive unable to control the motor.

The IndraDrive's control section encountered an error during its power-up or reset initialization sequence. This indicates a fundamental problem preventing the control electronics from starting up correctly, which could be due to hardware failure, firmware issues, or memory corruption.

The IndraDrive failed to successfully initialize its power section during power-up or after a reset. This suggests an issue with the power components, current sensing, or voltage monitoring circuits that prevent the drive from preparing to deliver power to the motor.

The firmware loaded on the IndraDrive is not compatible with the detected power section hardware. This mismatch can occur after firmware updates, hardware changes, or if an incorrect firmware package was installed, preventing the drive from operating safely or correctly.

The firmware loaded on the IndraDrive is not compatible with the detected control section hardware. This mismatch prevents the control unit from operating correctly, potentially due to incorrect firmware installation or a control section replacement with an incompatible model.

This fatal error indicates a general hardware malfunction within the IndraDrive's control section. This can encompass issues with the processor, memory, communication interfaces, or other core components, rendering the drive inoperable.

The firmware for the safety technology option module 1 is detected as defective or corrupted. This prevents the safety functions from operating correctly and will typically disable the drive for safety reasons.

The firmware for the safety technology option module 2 is detected as defective or corrupted. Similar to F8129, this prevents safety functions from operating and results in drive shutdown for safety compliance.

This fault indicates a problem during the internal diagnostic check of safety-related interrupting circuits, often associated with Safe Torque Off (STO) or Safe Stop functions. The drive detected an inconsistency or malfunction in the circuitry designed to safely cut off power to the motor.

The safety command issued for basic initialization of the safety technology was incorrect or arrived in an invalid sequence. This indicates a programming or configuration issue with the safety control logic that prevents the safety system from correctly starting up.

One or more configuration parameters for the safety technology within the IndraDrive are found to be invalid or inconsistent. This prevents the safety functions from operating reliably and will typically prevent the drive from enabling or will trigger a shutdown.

The IndraDrive experienced a timeout during a loading process, typically when trying to load parameters, firmware, or other data to/from its memory or an external storage medium like an MMC card. This suggests a communication issue or a problem with the storage itself.

The IndraDrive detected an issue with the connection or functionality of the external mains choke. The mains choke is used for suppressing harmonics and limiting inrush current, and a connection error can lead to power quality issues or prevent safe operation.

An excessive current was detected flowing through the external braking resistor, indicating that the resistor is dissipating more power than its rated capacity. This can lead to resistor overheating, damage, or even fire hazards.

This fatal error signifies an issue where an internal software function call within the IndraDrive's operating system or application layer has failed or returned an unexpected result. This can indicate a software bug, memory corruption, or an internal logic error, leading to a system shutdown.

This fatal error indicates a failure within the Real-Time Operating System (RTOS) kernel of the IndraDrive. An RTOS function call returning an error points to a critical issue in task scheduling, memory management, or inter-process communication, which is essential for the drive's real-time performance and control.

The watchdog error indicates that the IndraDrive's internal watchdog timer has not been reset within its expected interval, causing the system to trigger a fault. This typically signifies that the main processor or a critical software task has become unresponsive or stuck, preventing proper system operation.

This fault indicates a critical hardware error detected by the IndraDrive's processor, such as an invalid memory access, division by zero, or other unrecoverable CPU exception at the hardware level. It suggests a fundamental problem with the drive's internal electronics or firmware's interaction with the hardware.