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.

This warning occurs when an attempt is made to switch to encoder 2 for position control, but a second encoder has not been properly defined or configured as the control encoder in the IndraDrive MPx02. This typically happens in operating modes that utilize parameter S-0-0520 (Control word of axis controller) for encoder selection.

This is a user-generated warning (one of E2011 to E2014) originating from the drive-integrated PLC program within the IndraDrive MPx02, typically in conjunction with Rexroth technology functions. The specific cause and remedy depend entirely on the logic programmed into the user's PLC project or the active technology function.

Similar to E2011, this is a user-generated warning (one of E2011 to E2014) produced by the drive-integrated PLC program in the IndraDrive MPx02, typically when using Rexroth technology functions. The meaning and resolution are specific to the customer's PLC project and the configured technology function.

The IndraDrive MPx02 has detected an undervoltage condition within its internal power section (DC bus voltage has dropped below a critical threshold). This is a warning state that precedes a fault if the condition persists, impacting drive performance and potentially leading to a controlled shutdown to protect the drive.

The actual positioning velocity of the motor in the IndraDrive MPx02 has reached or exceeded the configured velocity limit. This is a warning indicating that the motor is operating at its maximum allowed speed, potentially due to an aggressive command, incorrect scaling, or an unexpected external condition.

The commanded target position for the IndraDrive MPx02 is outside the defined mechanical or software travel limits of the axis. This warning prevents the drive from moving the axis to a potentially damaging or undesired physical location, ensuring machine safety and integrity.

This warning indicates that the feedrate override parameter S-0-0108 is currently set to zero. A zero feedrate override means that any motion commands will be scaled down to zero velocity, effectively preventing the axis from moving or continuing motion despite active commands.

The IndraDrive MPx02 detects that the active torque limit has been set to zero. This effectively prevents the motor from generating any torque, causing the axis to stop or be unable to start motion, thereby protecting the mechanical system from unintended force.

The IndraDrive MPx02 attempted to execute a process block (e.g., a motion task, sequence step, or program segment) that has not been programmed or does not exist in its memory. This typically occurs in systems using internal motion control capabilities where sequences of operations are defined in blocks.

The current velocity command value for the IndraDrive MPx02 is being limited by a configured maximum velocity parameter. This is a warning indicating that the requested velocity exceeds the allowed limit, and the drive is automatically capping it to prevent overspeed or mechanical stress.

The IndraDrive MPx02 has detected that its internal thermal load or output current is approaching its maximum permissible limit. This is a prewarning, indicating that continued operation under current conditions could lead to an overload fault, subsequent shutdown, and potential damage to the drive.

The velocity command received by the IndraDrive MPx02 from the master controller (e.g., PLC, CNC) is currently higher than the configured maximum velocity limit. The drive may cap the velocity at this limit or signal an impending error if the commanded value is not corrected, to prevent overspeed.

The commanded target position for the IndraDrive MPx02 is outside the permissible numerical range of the drive's internal position calculation or a defined travel range. This prevents the drive from executing the positioning command correctly, indicating an invalid position request.

The IndraDrive MPx02 has detected that the holding brake is unable to generate sufficient torque to hold the load, possibly during a brake test or when monitoring brake engagement. This can indicate a potential safety hazard if the load is not securely held, especially in vertical applications.

The IndraDrive MPx02 is currently limiting the acceleration of the motor because the commanded acceleration value from the master controller or the motion profile exceeds a configured maximum limit. The drive automatically caps the acceleration to protect the mechanical system and maintain smooth operation.

The IndraDrive MPx02 has detected disturbances or errors in the feedback signals from Encoder 1. These disturbances can include signal loss, noise, intermittent faults, or incorrect signal levels, leading to unstable or inaccurate position and velocity control for the motor.

The IndraDrive MPx02 has detected disturbances or errors in the feedback signals from Encoder 2. These disturbances can include signal loss, noise, intermittent faults, or incorrect signal levels, potentially leading to unstable or inaccurate position and velocity control, especially in dual-encoder systems.

The IndraDrive MPx02 has detected disturbances or errors in the feedback signals from the measuring encoder. These disturbances can include signal loss, noise, intermittent faults, or incorrect signal levels, impacting position and velocity accuracy, especially in applications with direct machine feedback or closed-loop position control.

The IndraDrive MPx02's internal monitoring has detected an alarm condition from the motor's absolute encoder. This indicates a problem with the absolute position feedback from the motor encoder, which is critical for accurate homing and position tracking without a reference run, affecting both control and safety functions.

The IndraDrive MPx02's monitoring system has detected an alarm condition from the optional absolute encoder (e.g., a second motor encoder or an external absolute encoder). This signifies an issue with the absolute position feedback from this auxiliary encoder, which could affect dual-encoder or master-slave configurations, or safety functions.

An alarm condition has been detected by the IndraDrive MPx02 from the absolute measuring encoder (often a linear scale or external rotary encoder directly monitoring the load). This indicates a problem with the primary absolute position feedback for the machine's actual position, impacting precision, homing, and safety functions.

The IndraDrive MPx02 has detected that the associated supply module is operating close to its maximum continuous load capacity, indicating a potential for overload if current conditions persist or increase. This is a prewarning to allow corrective action before an actual overload fault occurs and shuts down the system.

The IndraDrive MPx02 has detected an issue with its internal synchronization. This internal synchronization is crucial for coordinating various drive functions, especially in multi-axis systems or when precise timing is required. A defective synchronization can lead to erratic behavior, loss of control, or inability to operate.

The IndraDrive MPx02 has detected that the commanded positioning velocity from the master axis generator (e.g., in a gearing or camming application) is exceeding its permissible limit for the slave axis. This can lead to following errors, instability in the slave axis, or a failure to accurately track the master.

The IndraDrive MPx02 has detected that the acceleration commanded by the master axis generator is zero. In some motion control scenarios, especially those involving dynamic following, a zero acceleration from the master can indicate an unexpected or incorrect master motion profile, potentially leading to issues for slave axes.

This error indicates a Communication Control Device (CCD) error at a specific node on a network, likely a fieldbus such as SERCOS. A CCD error implies a problem with the communication interface or the underlying communication protocol, preventing reliable data exchange and proper control of the IndraDrive MPx02.

The IndraDrive MPx02 has detected an open circuit or wire break on either analog input 1 or analog input 2. This means the drive is not receiving a valid signal from the connected analog sensor or command source, potentially leading to incorrect control, erratic behavior, or machine safety issues.

This warning indicates an issue related to the hardware control of the external braking resistor connected to the IndraDrive MPx02. This could imply a fault in the braking resistor circuit, the drive's internal brake chopper, or its control, preventing effective dissipation of regenerative energy.

The IndraDrive MPx02 has not reached the "ready for operation" state, meaning it cannot accept motion commands or enable its power section. This typically occurs because certain prerequisite conditions have not been met, or other active warnings/errors are preventing full readiness.

The IndraDrive MPx02 has detected that the incoming mains (AC line) voltage is below the minimum permissible operating threshold. This can lead to insufficient power delivery to the drive and potentially to the DC bus, impacting performance and potentially causing a shutdown to prevent damage.

The IndraDrive MPx02 has detected an undervoltage condition within its internal power section, specifically on the DC bus. This means the DC link voltage has fallen below a safe operating threshold, which can occur due to insufficient incoming AC power or excessive current demand, impacting drive stability.

The IndraDrive MPx02 has detected the loss of one or more phases of the incoming three-phase AC mains supply. This condition prevents proper operation, leading to unbalanced currents and insufficient power, and can damage the drive and motor if not addressed promptly.

The IndraDrive MPx02 has detected a complete loss of the incoming AC mains power supply. This means the drive is no longer receiving power from the grid and will initiate a controlled shutdown or ride-through sequence based on its configuration, as it cannot sustain operation.

The IndraDrive MPx02 has detected that the external braking resistor is approaching its maximum thermal capacity. This prewarning indicates that excessive regenerative energy is being dissipated, and continued operation under these conditions could lead to resistor overheating and potential damage or fault.

The IndraDrive MPx02 is in a state where it cannot be powered on, meaning its internal power section cannot be enabled. This typically implies that a critical prerequisite or safety condition required before activating the power output stages has not been met, preventing motor control.

The IndraDrive MPx02's integrated safety technology has detected an inconsistency or error during the validation of safety-related parameters. This indicates a potential breach or misconfiguration in the safety system, preventing safe operation and requiring immediate attention.

The IndraDrive MPx02's integrated safety function has detected an invalid or inconsistent configuration for a safety-related operating mode (e.g., Safely Limited Speed, Safe Operating Stop). This prevents the drive from entering a verified safe mode, indicating a potential safety risk and requiring re-configuration.

A general system error has occurred within the IndraDrive MPx02's integrated safety technology. This indicates a fundamental issue with the safety module's operation, its internal diagnostics, or its communication, leading to a critical safety shutdown and inability to operate safely.

The IndraDrive MPx02's integrated safety technology is missing a required safety-related reference. This reference could be a specific position, velocity, or direction, which is crucial for safety functions like Safe Operating Stop or Safe Position monitoring. Without it, the safety system cannot guarantee safe operation.

The IndraDrive MPx02 has detected that the starting lockout has not been activated within the specified time interval defined by parameter P-0-0103 (Time interval of forced dynamization). This indicates a potential safety-related issue if the lockout is not engaged as required, possibly allowing unintended startup.

This prewarning is generated by the IndraDrive MPx02 when the time since the last holding brake check approaches the parameterized interval (P-0-0550 or P-0-3302) by 15 minutes or less, or if 5 minutes have passed since drive enablement without a brake check. It serves as a reminder that a brake check is due to ensure the holding brake's functionality and safety.

Command value input from the master communication interface (fieldbus) is not possible for the IndraDrive MPx02. In firmware version 04VRS, this warning is named "No data exchange possible via the field bus." The drive may continue running with the last valid command value. This warning can lead to an automatic restart if not handled by the control unit.

An error occurred during the index check in the multiplex channel of the IndraDrive MPx02. During cyclic data exchange, the index used to access "Data container A: configuration list command value-x" points to a non-initialized position in the list, causing data access issues.

An error occurred during the index check in the multiplex channel of the IndraDrive MPx02. During cyclic data exchange, the index used to access "Data container A: configuration list actual value-x" points to a non-initialized position in the list, leading to issues with reading actual values.

The IndraDrive MPx02 (acting as a slave device on a fieldbus network) has not been successfully scanned by the master controller, or its configured address is detected as 0, which is typically an invalid or unassigned address. This prevents communication and control via the fieldbus, rendering the axis inoperable.

This warning signifies that the DC bus voltage within the IndraDrive MPx02's power section has dropped below a specified undervoltage threshold. This can lead to reduced motor performance and, if prolonged, can trigger a fault condition to protect the drive from improper operation.

The IndraDrive MPx02's integrated safety technology has detected that the drive is enabled, but the motor is at a safety-related standstill. This condition is a warning indicating that the safety standstill function is active while the drive's power section is still enabled, which may not be the intended safe state or might indicate an issue with the safety circuit's command.

The IndraDrive MPx02 has detected that the actual position of the axis has moved beyond the configured positive software travel limit (P-0-0045). This warning indicates that the axis has entered a restricted zone, and further movement in the positive direction may be prevented or cause a fault, protecting the machine from overtravel.

The IndraDrive MPx02 is currently executing a quick stop sequence, and during this process, a probe input (e.g., for homing, precise position capture, or a limit switch) has become active. This warning ensures the technician is aware of the concurrent events, which might be normal or indicate an unexpected interaction in the control logic.

The actual torque or force produced by the motor is being limited by a configured parameter in the IndraDrive MPx02. This warning indicates that the motor is operating at its maximum allowed torque/force, potentially due to excessive load or a low-set limit, preventing further increase in output.

The IndraDrive MPx02 has detected that the physical positive travel range limit switch (hardware limit switch) has been activated. This is a critical warning indicating that the axis has reached or exceeded its absolute positive mechanical limit, preventing further movement in that direction to protect the machine.

The torque or force command value issued to the IndraDrive MPx02 is being limited by a configured maximum value. This indicates that the requested torque/force from the master controller exceeds the drive's or application's set limit, and the drive is capping the output.

The IndraDrive MPx02's integrated safety technology has encountered a fatal error during the validation of safety-related parameters. This indicates a severe inconsistency or corruption in the safety configuration, making safe operation impossible and requiring a complete safety system re-commissioning before the drive can operate.

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.

"F8000" is a collective diagnostic message for underlying fatal hardware errors within the IndraDrive MPx02, specifically F8060 (Overcurrent in power section) and F8069 (+/-15Volt DC error). This code is typically not displayed directly, as the more specific fault is shown. The occurrence of this error leads to an immediate torque-free shutdown of the drive, making operation impossible.

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.

An excessive current flow has been detected in the power section of the IndraDrive MPx02, exceeding the drive's internal limits. This is a fatal error, leading to an immediate torque-free shutdown to protect the drive and motor from damage.

An error has been detected in the internal +/-15VDC power supply of the IndraDrive MPx02. This internal supply is critical for sensitive control electronics, and its failure results in a fatal error, causing the drive to shut down immediately to prevent further damage.

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.