Rexroth IndraDrive Error Codes

F2026: Undervoltage in power section

What it means: The DC bus voltage dropped below the undervoltage threshold (P-0-0114), or the supply reported the DC bus as not ready, while the drive was in control. P-0-0118 decides whether low DC bus voltage trips as this error, as fatal warning E8026 or only as warning E2026.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: error reaction set in P-0-0119 (best possible deceleration), then torque-free

Likely causes

• Power switched off while drive enable (AF) was still on
• Supply unit failure or supply overload
• Mains failure or dip
• Short supply overload during a heavy machine cycle
• HCS02: loose or wrong mains wiring at connector X3

First checks, in this order

1. Check the control logic: drive enable must be removed before power is switched off.
2. Measure the mains supply and check the supply unit; on HCS02 check the mains wiring at X3.
3. Find the cause of any mains failure, then switch mains on again.
4. If the supply is overloaded for short moments, reduce the demand of the machine cycle.
5. Clear with Esc on the panel or S-0-0099 (C0500), then set drive enable again.

F2028: Excessive deviation

What it means: In position control the gap between the drive's model position and the actual position grew larger than S-0-0159 Monitoring window, so the axis could not follow the position command (following error).^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: error reaction set in P-0-0119 (best possible deceleration), then torque-free

Likely causes

• Monitoring window S-0-0159 set too small
• Acceleration demanded by the control is too high
• Torque limit S-0-0092 too low
• Axis blocked, jammed or running stiff
• Control loop settings wrong or not tuned
• Drive or motor too small for the required acceleration

First checks, in this order

1. Read P-0-0098 Max. model deviation to see how far the axis lagged.
2. Check S-0-0159 Monitoring window and S-0-0092 Bipolar torque/force limit value.
3. Look for mechanical binding, a crash, a dragging brake or a seized ballscrew.
4. Check controller settings such as S-0-0104 (position Kv-factor) and S-0-0100 (velocity P gain).
5. Reduce the acceleration programmed in the control.

E8260: Torque/force command value limit active

What it means: At least one torque or force command limit was reached (a set limit or the speed dependent voltage limit), so the drive cannot give the torque the controller asks for. It often shows just before F2028. It can be switched off with P-0-0556 bit 4.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Likely causes

• Acceleration demand beyond what the drive can deliver, so following error builds up
• Speed command above what the motor voltage allows (P-0-0535, P-0-0536)
• Torque limits set too low (S-0-0082, S-0-0083, S-0-0092, P-0-0109)
• Current controller set wrong for a kit or third-party motor (S-0-0106, S-0-0107)
• U/f operation: speed ramp too steep for the motor (P-0-0569)

First checks, in this order

1. Reduce the acceleration or the maximum speed in the control.
2. Check the torque limit parameters S-0-0082, S-0-0083, S-0-0092 and P-0-0109.
3. For motors without encoder data memory, check current loop settings S-0-0106 and S-0-0107.
4. With an uncontrolled supply, check that the mains voltage is not low; a regulated supply (HMV-R) helps.
5. Asynchronous motor at standstill: lower P-0-0532 Premagnetization factor or use a larger drive.

F2031: Encoder 1 error: Signal amplitude incorrect

What it means: The sine and cosine signals of encoder 1 left the monitored amplitude range or were disturbed enough to corrupt the position. The encoder has to be reinitialized, so the error clears only in parameter mode (PM).^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: error reaction set in P-0-0119 (best possible deceleration), then torque-free

Likely causes

• Damaged encoder cable or poor cable shield
• Electrical noise from the motor power cable
• Defective or dirty encoder
• Linear scale: read head mounted wrong
• Hardware fault on the drive control section

First checks, in this order

1. Check the encoder cable and connectors; replace the cable if in doubt.
2. Check the shield connection of the motor power cable and keep it away from the encoder cable.
3. Check, clean or replace the encoder or scale.
4. As of MPx17 this case can be set to warning E2031 instead (P-0-0173, list element 0).
5. If the error stays with a good encoder and cable, have the control section replaced by trained staff.

F2042: Encoder 2: Encoder signals incorrect

What it means: The signals of encoder 2 (the optional or external encoder) left the allowed range or were disturbed, or a digital encoder sent a checksum (CRC) error. The position is no longer reliable and the encoder must be reinitialized.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: error reaction set in P-0-0119 (best possible deceleration), then torque-free

Likely causes

• Damaged encoder 2 cable or poor shield
• Electrical noise from the power cable
• Defective encoder
• Linear scale: read head mounted wrong, or scale dirty
• Hardware fault on the control section

First checks, in this order

1. Check the encoder 2 cable, connectors and shield.
2. Check the power cable shielding and routing.
3. Check, clean or replace the encoder or scale; check the read head mounting.
4. Clear the error once the signals are back in range, or in parameter mode.
5. As of MPx17 this case can be set to warning E2042 (P-0-0173, list element 2).

F8060: Overcurrent in power section

What it means: The current in the power transistors went above the device peak current (S-0-0110 Amplifier peak current). If the internal 15 V signal supply of the power section fails, it can also show right at switch-on, before power is applied.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: drive enable removed at once (torque-free), holding brake applied

Likely causes

• Short circuit in the motor or motor cable
• Power section of the drive defective
• External 24 V supply not able to handle the load
• Current loop parameters wrong for the motor
• Large DC bus voltage swings from a weak supply (high system impedance)

First checks, in this order

1. With power off and discharged, disconnect the motor cable and check motor and cable for shorts between phases and to ground.
2. Check that the external 24 V supply can handle the load.
3. Compare the current loop parameters with the motor data sheet; talk to Rexroth service before changing them.
4. Check supply wire sizes; increase the cross section if the supply is weak.
5. Before switching power on again, read the error memories of all drives and remove any DC bus short; replace the drive if it repeats.

F2174: Loss of encoder 1 reference

What it means: During position initialization the drive found that the absolute position reference of encoder 1 is no longer valid, so the position status (S-0-0403) switches to relative. Up to firmware 19VRS it was called Loss of motor encoder reference.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (older name: Loss of motor encoder reference)

Drive response: error reaction set in P-0-0119 (best possible deceleration), then torque-free

Likely causes

• First commissioning, or parameters that describe the mechanics or scaling were changed
• Motor or encoder replaced
• 24 V DC relays or contactors switched without a suppressor on the coil
• Encoder backup battery low or a break in its supply line (F2048 also in the error memory)
• Drive replaced and loaded with axis parameters
• Defective encoder

First checks, in this order

1. Clear the error and set the position reference again: homing with S-0-0148 (C0600) or set absolute position with S-0-0447 (C0300).
2. Check P-0-0192 Error memory for F2048; if present, replace the encoder battery or repair the cable.
3. Fit suppressor circuits on 24 V DC relay and contactor coils.
4. After a drive swap, load P-0-0195 retain data if it was saved, then check the restored position.
5. If the reference keeps getting lost, replace the motor or encoder.

F2074: Actual pos. value 1 outside absolute encoder window

What it means: At power up the absolute motor encoder position differs from the position stored at the last power down by more than P-0-0095 Absolute encoder monitoring window for motor encoder.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: error reaction set in P-0-0119 (best possible deceleration), then torque-free

Likely causes

• Axis moved while the drive was off (brake slip, gravity, moved by hand)
• P-0-0095 too small for the encoder resolution, so normal jitter trips it
• Drive replaced without updating parameters
• Mechanical parameters changed (gear ratio, feed constant)
• Motor encoder defective

First checks, in this order

1. Before moving, confirm the displayed position matches the real position relative to machine zero (risk of unexpected motion).
2. Clear the error and set the position reference again if needed (S-0-0447, C0300).
3. Check P-0-0095 and increase it if jitter trips the monitor; 0 switches the monitor off.
4. If the position reference is wrong, the encoder is defective: replace the motor.

E2050: Device overtemp. prewarning

What it means: The drive heat sink is close to its shutdown temperature. If it keeps rising, the drive trips with F2018 Device overtemperature shutdown. Use the time to stop the axis in a controlled way or reduce the load.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: warning only, the drive keeps running

Likely causes

• Drive overloaded
• Cabinet ambient above 40 °C
• Dirty heat sink
• Airflow blocked by other parts or wrong mounting
• Internal fan failed, or cabinet air conditioning failed

First checks, in this order

1. Check the load: average working power must stay under the drive's continuous power.
2. Clean the heat sink and check the drive fan.
3. Check cabinet cooling and air conditioning.
4. Check that the drive is mounted vertically with enough free space for airflow.

E2051: Motor overtemp. prewarning

What it means: The motor temperature reached S-0-0201 Motor warning temperature (as of MPx17 also when the motor thermal model passes its prewarning threshold P-0-0468). The drive shuts down with F2019 when S-0-0204 Motor shutdown temperature is reached.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: warning only, the drive keeps running

Likely causes

• Motor overloaded for too long
• S-0-0201 or P-0-0468 set wrong
• Break, ground fault or short in the motor temperature sensor line
• Unstable speed control loop
• Motor fan or cooler defective

First checks, in this order

1. Read the motor temperature in S-0-0383.
2. Check S-0-0201 against the motor or sensor data sheet.
3. Check motor sizing and look for new friction, dirt or extra load.
4. Check the temperature sensor wiring and the motor fan or cooler.

F2086: Error supply module

What it means: The supply unit reported an error to the drives over the module bus. Drives in operation run their error reaction, and the supply switches power off (or opens the Bb contact of converters).^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: error reaction set in P-0-0119 (best possible deceleration), then torque-free; supply power switched off

Likely causes

• Supply unit failure or overload
• Another drive in the group reported its error to the supply (set in P-0-0118)

First checks, in this order

1. Read the display of the supply unit for its own error code.
2. Find the drive in the group that shows an error and fix that cause first.
3. Check the supply sizing and P-0-0118 Power supply, configuration.

F2100: Incorrect access to command value memory

What it means: An error happened while the drive accessed its command value memory (flash or internal memory).^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: error reaction set in P-0-0119 (best possible deceleration), then torque-free

Likely causes

• One-off firmware error
• Control section hardware defective
• Programming module defective

First checks, in this order

1. Clear the error and note how often it returns.
2. Ask Rexroth service whether a firmware update is available.
3. If it repeats, replace the programming module, then the control section or drive.

F2820: Braking resistor overload

What it means: The braking resistor load (P-0-0844) reached 110 %, so power was switched off to protect it. The same error shows when the braking resistor is missing or broken.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: power switched off

Likely causes

• Deceleration of the connected drives too high
• Too much regenerated energy per machine cycle
• Power cut at E-stop or drive off on a regenerative supply, so the resistor takes all the energy
• Continuous regenerative power or rotating energy too high for the resistor
• Braking resistor defective or not connected

First checks, in this order

1. Reduce deceleration rates or maximum speed, or lengthen the cycle.
2. Check the wiring and resistance of an external braking resistor.
3. Check the sizing of the braking resistor; add capacity if needed.
4. After fixing the cause, test that the braking resistor works; the threshold is in P-0-0833.
5. If the internal resistor is defective, replace the device.

F2834: Contactor control error

What it means: The mains contactor could not be switched on or dropped out during operation (supply unit or converter with mains contactor control).^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 and HMV01 supply units (same code and name)

Likely causes

• Contactor coil supply voltage missing
• Feedback from the contactor auxiliary contacts missing
• Contactor control output (XG34) does not switch
• HMV supply: DC bus short circuit (ZKS) or mains OFF contact opened while mains ON was still closed

First checks, in this order

1. Check the wiring and the supply voltage of the mains contactor control.
2. Check the wiring of the contactor acknowledgement contacts (XG40).
3. HMV supply: check the X32 contact sequence and the voltages at X32 and X14 or L1, L2, L3.
4. Do not let the contactor switch while voltage is on the power wiring before the DC bus is charged through the HNA module.
5. If all wiring is correct, the device is faulty: replace it.

F2833: Ground fault in motor line

What it means: While charging the DC bus, the HMV supply unit detected a ground fault in the motor line of one of the connected drives.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name); listed under HMV01 supply unit diagnostics

Likely causes

• Ground fault in a motor cable or motor
• Ground fault inside one drive of the group

First checks, in this order

1. With power off and discharged, measure the insulation of the motor cables and motors with an insulation tester.
2. Take the drives out of the group one at a time (control voltage and power side) until the error stops, to find the faulty axis.
3. If the motor cable is good, suspect the drive or its connections.

F8022: Encoder 1: Incorrect enc. signals (can be cleared in PM)

What it means: The motor encoder (encoder 1) signals left the allowed range, were disturbed, or a digital encoder sent checksum (CRC) errors. This is a fatal error; the encoder must be reinitialized, so it clears only in parameter mode (PM).^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (older name: Enc. 1: Enc. signals incorr. (can be cleared in ph. 2))

Drive response: drive enable removed at once (torque-free), holding brake applied

Likely causes

• Damaged encoder cable or poor shield
• Electrical noise from the motor power cable
• Defective or dirty encoder; linear read head mounted wrong
• MSM motors: encoder telegram failed twice, for example after static discharge to the shaft
• Hardware fault on the control section

First checks, in this order

1. Check the encoder cable, connectors and shield; replace the cable if in doubt.
2. Check the shield of the motor power cable.
3. Check, clean or replace the encoder.
4. Switch to parameter mode (PM) to clear, then back to operating mode.
5. If it persists with a good encoder and cable, replace the control section or drive.

F8064: Interruption of motor phase

What it means: In voltage controlled (U/f) operation of an asynchronous motor, the drive measured zero current in at least one motor phase. The axis goes torque-free and can coast.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: drive enable removed at once (torque-free), holding brake applied

Likely causes

• A motor phase not connected, or a broken wire
• Double-axis drive: the two motor connections swapped
• Burnt motor winding
• Voltage boost too low, or motor data wrong (P-0-4004 Magnetizing current too high)
• Power section defective

First checks, in this order

1. Check each motor phase from the drive terminal for a break or high resistance.
2. Check that each motor is wired to the correct axis.
3. Check the windings with an ohmmeter.
4. Adjust P-0-0568 voltage boost until magnetizing current flows at standstill, and compare motor data with the nameplate.
5. Monitoring is only reliable above about 10 rpm command; replace the drive if all else checks out.

F8069: Error in device-internal power supply

What it means: The internal power supply of the device failed. Older firmware calls it +/-15Volt DC error. It cannot be cleared with S-0-0099 (C0500).^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (older name: +/-15Volt DC error)

Drive response: drive enable removed at once (torque-free), holding brake applied

Likely causes

• Problem with the external 24 V DC supply
• Power section defective

First checks, in this order

1. Measure the external 24 V DC supply under load and check its wiring.
2. Switch the control voltage fully off and on.
3. If the error returns, replace the device.

F8091: Power section defective

What it means: At start-up the drive could not read valid power section data: a checksum error or an invalid value in parameters such as S-0-0140, P-0-1510 or P-0-4058.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: fatal error; drive must be restarted

Likely causes

• Invalid power section parameter data
• Control section or power section defective

First checks, in this order

1. Read S-0-0021 IDN list of invalid operating data and note the parameters listed.
2. Send that list to Rexroth service.
3. Replace the drive controller if service confirms a hardware fault.

F4001: Sync telegram failure

What it means: The drive missed the master synchronization telegram: on sercos for several cycles in a row (allowed count in S-0-1003), on CANopen for two cycles in a row.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: error reaction set in P-0-0119, then torque-free

Likely causes

• sercos cycle time set differently in master and drive
• Disturbance on the bus or loose fiber or cable
• CANopen: no node set as sync master, or bus interrupted
• Interface hardware defective

First checks, in this order

1. Compare the sercos cycle times in the master and the drive.
2. Check bus cables, fibers and connectors.
3. CANopen: check that a sync master is configured and is not in an error state.
4. If it persists, replace the control section or drive.

F4002: RTD telegram failure

What it means: Cyclic command telegrams from the master were missed: on sercos the connection failures passed S-0-1050.x.11 Allowed data losses; on CANopen and EtherCAT two cycles in a row were lost.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: error reaction set in P-0-0119, then torque-free

Likely causes

• Bad bus cable or connector, or line topology without redundancy
• Electrical disturbance on the bus
• Master stopped cyclic telegrams while the drive was still enabled
• EtherCAT: timing or distributed clock settings wrong

First checks, in this order

1. Check bus cables and connectors; on sercos use ring topology.
2. Remove drive enable before the master stops cyclic communication.
3. Check the master timing and distributed clock settings.
4. If short dropouts are acceptable, review S-0-1050.x.11.

F2025: Drive not ready for control

What it means: Drive enable was set while the drive only reported bb (ready for operation) instead of Ab (control and power section ready).^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: error reaction set in P-0-0119 (best possible deceleration), then torque-free

Likely causes

• Drive enable set before power was switched on
• Drive enable set while the drive was still in parameter mode
• Safe torque off (STO) still active
• E-Stop function active
• Module bus reaction E8058: another drive in the group has an error

First checks, in this order

1. Fix the control sequence: power on, wait for Ab (P-0-0115 bit 15 = 1, bit 14 = 0), then enable.
2. Deselect STO before setting drive enable.
3. Release the E-Stop before setting drive enable.
4. Clear the errors on the other drives in the group first.

F2018: Device overtemperature shutdown

What it means: The drive heat sink reached its maximum temperature and the drive switched off to protect itself. Warning E2050 shows for 30 seconds before this trip.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: error reaction set in P-0-0119 (best possible deceleration), then torque-free

Likely causes

• Drive overloaded
• Cabinet ambient above 40 °C
• Dirty heat sink or blocked airflow
• Drive fan failed, or cabinet air conditioning failed
• Liquid cooled drives: coolant missing, pump failed, filter clogged or inlet too hot

First checks, in this order

1. Switch off and let the drive cool down.
2. Check that average working power stays under the drive's continuous power.
3. Clean the heat sink and check the drive fan.
4. Check cabinet cooling, vertical mounting and free space around the drive.
5. Liquid cooled drives: check coolant flow and inlet temperature.

F2019: Motor overtemperature shutdown

What it means: The motor temperature sensor reached S-0-0204 Motor shutdown temperature. The drive stops with its error reaction and shuts down.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: error reaction set in P-0-0119 (best possible deceleration), then torque-free

Likely causes

• S-0-0204 set wrong (it is fixed for MHD, MKD, MKE and LSF motors)
• Motor overloaded: torque above continuous rating for too long
• Break, ground fault or short in the temperature sensor line
• Unstable speed control loop
• Liquid cooled motors: cooling missing or failed

First checks, in this order

1. Let the motor cool down.
2. Check S-0-0204 against the motor or sensor data sheet.
3. Check motor sizing and look for new friction, dirt or added mass.
4. Check the sensor wiring in the motor cable and connector.
5. Check the speed loop settings and any motor cooling.

E2026: Undervoltage in power section

What it means: The DC bus voltage is low, and P-0-0118 is set so that undervoltage is only reported as a warning instead of error F2026 or fatal warning E8026.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: warning; any drive reaction depends on P-0-0118

Likely causes

• Power switched off without removing drive enable first
• Supply fault or supply overload
• Mains failure
• Short supply overload during the machine cycle

First checks, in this order

1. Check the control logic: remove drive enable before switching power off.
2. Check the supply unit and the mains voltage.
3. Find the cause of any mains failure and restore mains.
4. Reduce the peak demand of the machine cycle.

E2056: Torque limit = 0

What it means: One of the torque or force limit parameters is 0, so the motor cannot produce torque.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: warning only

Likely causes

• S-0-0082, S-0-0083, S-0-0092 or P-0-0109 set to 0
• Torque limit taken from an analog input that reads 0 V
• Potentiometer in the control set to 0, or the analog cable or input defective
• Motor without encoder data memory whose current limits (S-0-0109, S-0-0111) are still 0

First checks, in this order

1. Check S-0-0082, S-0-0083, S-0-0092 and P-0-0109 and enter a real limit.
2. If a limit comes from an analog input, measure the voltage and check the cable.
3. For a motor without encoder memory, load the motor data from the motor database in the commissioning software.

E2061: Device overload prewarning

What it means: The drive's thermal load (temperature model, P-0-0141) passed P-0-0441 Drive load warning threshold. Near 100 % the drive starts limiting current and shows E8057.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: warning only, the drive keeps running

Likely causes

• P-0-0441 set too low
• Drive overloaded by heavy cuts or high acceleration to high speed
• Mechanics changed: more friction or more moving mass

First checks, in this order

1. Check P-0-0441; 80 to 90 % gives a useful margin.
2. Read P-0-0141 Thermal drive load during the cycle.
3. Check drive sizing and the command profile.
4. On older machines, check the mechanics for new friction.

F8025: Overvoltage in power section

What it means: The DC bus voltage reached its maximum (E8025 shows first), the axes were disabled, and the voltage still did not drop below the switch-off threshold. The device is disconnected from the mains.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: drive enable removed at once (torque-free), holding brake applied

Likely causes

• Too much energy fed back while braking for the supply to absorb
• Braking resistor missing, badly connected or cable faulty
• Synchronous motor at high speed in field weakening
• Fault in the DC bus voltage measurement of the supply unit

First checks, in this order

1. Lower the deceleration rates.
2. Check the braking resistor and its connection.
3. Check the supply and braking resistor sizing; add a resistor if needed.
4. Check that the braking resistor value suits the motor.
5. If it repeats with no clear cause, replace the supply power section and contact service.

F8027: STO/SBC while drive enabled

What it means: Safe standstill (safe torque off, with or without safe brake control) was selected while the drive was enabled, or drive enable was set while safe standstill was active. The drive goes torque-free at once.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (older name: Safe torque off while drive enabled)

Drive response: torque-free at once

Likely causes

• STO selected by the safety circuit while the drive was enabled
• Drive enable set while STO was still active
• P-0-0119 set to use motor phase short circuit as the F8 reaction on an axis with STO
• Motor phase short circuit switched during safe standstill

First checks, in this order

1. Fix the sequence: remove drive enable before STO is selected, and leave STO before enabling.
2. Check that the drive is ready for enable (P-0-0110 bit 7, or S-0-0135 bit 7 on sercos).
3. Check the safety relay and STO input wiring.
4. Check the F8 error reaction setting in P-0-0119.

F8028: Overcurrent in power section

What it means: The current through the power transistors (motor side on a drive, mains side on a supply) went above their allowed value, so they were switched off for protection.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: drive enable removed at once (torque-free), holding brake applied

Likely causes

• Short circuit at the motor or mains connection
• Supply unit: wiring error in the mains connection components
• Parallel connected drives: error in the motor output wiring or balancing choke
• Device defective

First checks, in this order

1. With power off and discharged, check motor and mains connections for shorts.
2. Check the wiring of the mains components (choke, filter, contactor).
3. Parallel drives: check output wiring and balancing choke.
4. Replace the device if wiring is good.

F8000: Fatal hardware error

What it means: A collective fatal hardware error. It is usually replaced on the display a moment later by F8060 or F8069, which names the real cause.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: drive enable removed at once (torque-free), holding brake applied

Likely causes

• Overcurrent in the power section (follow-up code F8060)
• Internal power supply error (follow-up code F8069)

First checks, in this order

1. Read S-0-0390 and S-0-0095 again, or the error memory, to find the follow-up code.
2. Then work through F8060 or F8069.

F2008: RL The motor type has changed.

What it means: At start-up the connected motor does not match S-0-0141 Motor type. The panel shows RL and the drive asks to load the motor specific control loop values from the motor encoder memory.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Likely causes

• Motor replaced with a different motor type
• A parameter file for a different motor type was loaded
• First switch-on of a new drive with a motor

First checks, in this order

1. Confirm the correct motor is fitted.
2. Back up the parameters, then clear with Esc on the panel or S-0-0099 (C0500).
3. Clearing runs S-0-0262 load defaults (C07_x), which overwrites the control loop settings, unless this is turned off in P-0-0556.

F2009: PL Load parameter default values

What it means: After a firmware change the drive found a problem in its non-volatile parameter memory. The panel shows PL and the drive wants to load default values.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Likely causes

• First start with new firmware, or an update that changed the number of stored parameters
• Parameter memory (programming module or internal memory) defective, so PL keeps coming back

First checks, in this order

1. Save the current parameter set before clearing.
2. Clearing at the control panel resets all parameters to defaults.
3. Clearing with S-0-0099 (C0500) keeps readable values and sets only new parameters to defaults, marked invalid.
4. If PL keeps returning, replace the programming module or control section.

F2021: Motor temperature monitor defective

What it means: The drive found the motor temperature sensor circuit faulty: open line, short circuit, or a reading below -40 °C.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: error reaction set in P-0-0119, or drive enable refused

Likely causes

• Break in the sensor line
• Short circuit in the sensor line
• Sensor defective
• NTC sensor: motor colder than its allowed ambient range
• Drive defective

First checks, in this order

1. Check the motor connector and the sensor wires in the motor cable.
2. Check that P-0-0512 matches the sensor type fitted.
3. Use a spare sensor if the motor has one, or replace the motor.
4. Replace the drive or power section if the circuit is good.

F2036: Excessive position feedback difference

What it means: With both encoders homed, the difference between encoder 1 and encoder 2 positions (P-0-0391) went beyond S-0-0391 Monitoring window feedback 2. Both reference bits are cleared.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: error reaction set in P-0-0119 (best possible deceleration), then torque-free

Likely causes

• Encoder 2 type or resolution set wrong (S-0-0115, S-0-0117)
• Gear or feed constant set wrong (S-0-0121, S-0-0122, S-0-0123)
• Backlash or slip between motor and encoder 2, with a tight window
• Encoder cable defective, or encoder input frequency exceeded
• Absolute encoder reference wrong

First checks, in this order

1. Check the encoder 2 and gear parameters listed above.
2. Check for backlash or belt slip; widen S-0-0391 if needed (0 switches the monitor off).
3. Replace a suspect encoder cable; reduce speed if the input frequency is exceeded.
4. Set the absolute position again with S-0-0447 (C0300).

F2037: Excessive position command difference

What it means: In position control with cyclic command values, two position commands in a row differed by more than S-0-0091 Bipolar velocity limit value allows.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: error reaction set in P-0-0119 (best possible deceleration), then torque-free

Likely causes

• S-0-0091 set too low
• Control sends commands before the drive follows them (P-0-0115 bit 3 = 0)
• Switch from drive-controlled to NC-controlled position without matching the position
• Drive-controlled homing (C0600) started while NC position control was active
• Wrong command values from the control

First checks, in this order

1. Read P-0-0010 (excessive command) and P-0-0011 (last valid command).
2. Check S-0-0091.
3. After homing, set the position command equal to the actual position (S-0-0047 = S-0-0051) before switching modes.
4. Ask the control programmer to check the command values.

F2048: Low battery voltage (encoder)

What it means: The battery in the encoder cable that keeps the absolute position of MSM motors while the drive is off is below its allowed voltage. It is checked when switching to operating mode; the absolute position can no longer be trusted.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (listed as F2048 Low battery voltage)

Drive response: error reaction set in P-0-0119 (best possible deceleration), then torque-free

Likely causes

• Battery used up (designed for about 10 years in three-shift use)
• Warning E2048 ignored and 24 V switched off before the battery was changed

First checks, in this order

1. Clear the error and replace the battery right away (see the IndraDrive Cs project planning manual).
2. Set the position reference again after the change.
3. The error cannot be cleared while the drive is locked with a customer password.

F2057: Target position out of travel range

What it means: Before a drive-controlled move, the target position was found outside the allowed travel range set by S-0-0049, S-0-0050 and S-0-0278.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: error reaction set in P-0-0119 (best possible deceleration), then torque-free

Likely causes

• Position limits set wrong
• Limit monitoring active where it is not needed, for example a modulo axis
• Relative moves adding up past the limits
• Absolute target position wrong in the control program
• Wrong positioning block target, or wrong block selected

First checks, in this order

1. Check S-0-0049 (must be greater than S-0-0050) and S-0-0050.
2. Switch the limit monitor off in S-0-0055 if it is not needed.
3. Check the target in S-0-0258 or S-0-0282, or P-0-4006 and the block selection P-0-4026.
4. The reaction to a travel range error is set in P-0-0090.

F2067: Synchronization to master communication incorrect

What it means: The phase locked loops that keep the drive in step with the fieldbus cycle (sercos, PROFIBUS and others) went beyond their allowed deviation.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: error reaction set in P-0-0119 (best possible deceleration), then torque-free

Likely causes

• Faulty bus connection or shield causing interference
• Master cycle jitters because of a software or hardware problem in the master
• Master communication hardware in the drive defective

First checks, in this order

1. Check the bus connections, including shields.
2. Check that the master delivers a clean, steady cycle.
3. If it persists, replace the control section or drive.

F2068: Brake error

What it means: The holding brake current was out of range when the brake was switched. On IndraDrive Cs a broken brake wire also triggers it.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: error reaction set in P-0-0119 (best possible deceleration), then torque-free

Likely causes

• Brake supply not connected right or outside 24 V +/-5 %
• Motor cable not fully connected
• Motor holding brake defective
• Drive defective

First checks, in this order

1. Measure the 24 V brake supply.
2. Check the motor cable, the brake wires and the cable shield connection at the drive.
3. Wire break monitoring can be set in P-0-0525 if it causes false trips.
4. IndraDrive Cs: clear by switching off the brake supply voltage.
5. Replace the motor or drive if the wiring is good.

F2104: Commutation offset invalid

What it means: The commutation offset stored in the motor encoder memory is invalid. The motor must not run without a valid offset.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: error reaction set in P-0-0119 (best possible deceleration), then torque-free

Likely causes

• One-off firmware error
• Encoder memory or encoder electronics defective

First checks, in this order

1. Clear the error and run P-0-0524 C1200 Commutation offset setting command.
2. If it comes back, contact Rexroth service about firmware.
3. If the encoder is at fault, replace the encoder or motor, then run C1200.

F2190: Incorrect Ethernet configuration

What it means: At start-up the drive found invalid Ethernet (TCP/IP) settings.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: error reaction set in P-0-0119 (best possible deceleration), then torque-free

Likely causes

• IP address and gateway in different networks, or set to the same value
• IP address set to the network broadcast address
• Automatic IP not possible: network mask not class C, or device address outside 1 to 254
• Internal IP stack setup failed (hardware problem)

First checks, in this order

1. Check engineering IP settings P-0-1531, P-0-1532, P-0-1533.
2. Check master communication IP settings P-0-4089.0.13, P-0-4089.0.14, P-0-4089.0.15 (sercos: S-0-1020 to S-0-1022).
3. Keep S-0-1040 or P-0-4089.0.3 between 1 and 254.
4. If the settings are valid and it persists, replace the drive.

F2814: Undervoltage in mains

What it means: Supply unit or converter: the mains voltage fell below the allowed minimum, or, with extended supply monitoring on (S-0-1712.0.150 bit 0), a phase voltage fell under the thresholds S-0-1712.0.160 or S-0-1712.0.161.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 and HMV01 supply units (same code and name)

Likely causes

• Mains voltage too low
• Supply transformer not matched to the unit
• Thresholds set too tight

First checks, in this order

1. Measure all mains phases at the supply input under load.
2. Use a matching transformer if the mains is out of range.
3. Check the extended monitoring thresholds.

F2815: Overvoltage in mains

What it means: Supply unit or converter: the mains crest voltage rose above the allowed maximum, or, with extended supply monitoring on, a phase voltage passed S-0-1712.0.162 or S-0-1712.0.163.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 and HMV01 supply units (same code and name)

Likely causes

• Mains voltage too high
• Transformer tap set wrong
• Thresholds set too tight

First checks, in this order

1. Measure the mains voltage.
2. Use an impedance matching transformer where needed.
3. Check the extended monitoring thresholds.

F2818: Phase failure

What it means: The supply detected one missing mains phase for longer than the tolerated time (about 2 seconds on HMV01 and HMV02).^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 and HMV01 supply units (same code and name)

Likely causes

• Mains phase missing
• Mains circuit breaker or fuse defective
• Wiring error

First checks, in this order

1. Measure all three phases at the supply input.
2. Check breakers and fuses.
3. Check and correct the wiring.
4. On some devices phase monitoring can be switched off with P-0-0860 bit 13 (see the parameter description first).

F2819: Mains failure

What it means: An HMV supply or an HCS, HCT or HCQ converter detected a mains failure longer than the tolerated time. A regenerative supply switches off at once if this happens while feeding back.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Likely causes

• Permanent or short mains failure
• Mains circuit breakers defective

First checks, in this order

1. Find and remove the cause of the mains failure.
2. Check and replace defective mains breakers.

F2860: Overcurrent in mains-side power section

What it means: The current in the mains-side power section went above its maximum, so the power supply was switched off.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 and HMV01 supply units (same code and name)

Drive response: power supply switched off

Likely causes

• Mains choke connected wrong, missing or undersized
• Mains filter missing or undersized
• Too much capacitance connected to the DC bus
• Device defective

First checks, in this order

1. Check the mains choke wiring and rating.
2. Check the mains filter.
3. Reduce DC bus capacitance to the project planning limits.
4. Replace the device if all of the above is correct.

F3115: Brake check time interval exceeded

What it means: The holding brake check (enabled in P-0-0525) was not run within the interval set in P-0-0550. The brake check status in P-0-0539 is reset.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: error reaction set in P-0-0119, then torque-free

Likely causes

• Brake check not run within 15 minutes after commissioning and drive enable
• Time in P-0-0550 passed since the last brake check

First checks, in this order

1. Clear the error; the drive is ready again.
2. Run P-0-0541 C2100 Holding system check command within 15 minutes with drive enable on.
3. Make the brake check part of the regular machine routine.

F3134: Dynamization time interval incorrect

What it means: The two safety selection channels are tested with short test (dynamization) pulses at least once per hour. The safety diagnostics found the pulses missing or wrong. About 30 minutes later a safety reaction locks the output stage on two channels and applies the brake.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: set error reaction; safety reaction after 30 minutes locks the output stage and applies the brake

Likely causes

• Loose connections in the safety selection wiring
• Inputs or outputs wired wrong
• Short between the two channels, or a channel shorted to 24 V
• Hardware defect

First checks, in this order

1. Check the wiring of the safety selection inputs and of the device that sends the test pulses.
2. Look for shorts between channels and to 24 V.
3. After fixing, clear by a selection and deselection sequence.
4. Replace the drive if the wiring is good.

F4009: Bus failure

What it means: Cyclic communication with the master failed after it had been running: no telegram within the monitoring time P-0-4075, the control was set to stop, or the drive was removed from the bus group while under torque.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: error reaction set in P-0-0119, then torque-free

Likely causes

• Bus or Ethernet cable broken or unplugged, or a switch failed
• Electrical noise on the bus
• Master stopped or in an error state
• Network load too high, or missing bus terminating resistors (PROFIBUS, CANopen)
• EtherCAT or sercos: phase 0 commanded while drive enable was on

First checks, in this order

1. Check the state of the master.
2. Check cables, connectors, switches, shields and routing.
3. PROFIBUS and CANopen: check terminating resistors at the two end nodes only.
4. Make the control reset Drive Halt, drive enable and drive ON on a bus failure so the axis cannot restart by itself.
5. P-0-4088 can turn this into warning E4005, which needs a reaction in the control.

F4034: Emergency-Stop activated

What it means: The E-Stop input monitored by the drive went to 0 V and the axis stopped as set in P-0-0119. The E-Stop function is switched on and set up in P-0-0008.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: error reaction set in P-0-0119, then torque-free

Likely causes

• E-Stop pressed or the E-Stop circuit opened
• Digital inputs set up wrong
• E-Stop switch or cable defective or wired wrong
• Digital inputs on the control section defective

First checks, in this order

1. Find out why the E-Stop opened and fix it.
2. Check which input is assigned in P-0-0223 and the digital input setup.
3. Check the switch and its wiring.
4. Clear with the reset key or C0500, then switch power on again.

F6024: Maximum braking time exceeded

What it means: After drive enable was removed or an error occurred, the motor did not slow below 10 rpm (or the standstill window S-0-0124) within S-0-0273 Maximum drive off delay time.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: fastest possible stop set in P-0-0119, then torque-free; behavior depends on brake type in P-0-0525

Likely causes

• S-0-0273 or S-0-0372 Drive Halt acceleration set wrong
• Torque limit too low, or current limited by thermal overload
• Motor connected wrong
• Power section hardware fault

First checks, in this order

1. Match S-0-0273 and S-0-0372 to what the axis can really do.
2. Check torque and current limits and the thermal load.
3. Check the motor connection.
4. Replace the drive if the cause is a hardware fault.

F6029: Positive position limit exceeded

What it means: The axis was commanded past the positive software limit S-0-0049. P-0-0090 decides whether this is an error or a fatal warning (E8029).^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: fastest possible stop set in P-0-0119 (bits 4 to 7), then torque-free

Likely causes

• Command from the control leads beyond the positive limit
• S-0-0049 set wrong

First checks, in this order

1. Clear the error, switch power on, enable, and command a move back into the allowed range.
2. Ask the machine builder why the command went past the limit.
3. Check S-0-0049 and S-0-0055; S-0-0057 sets the hysteresis.

F6030: Negative position limit exceeded

What it means: The axis was commanded past the negative software limit S-0-0050. P-0-0090 decides whether this is an error or a fatal warning (E8030).^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: fastest possible stop set in P-0-0119 (bits 4 to 7), then torque-free

Likely causes

• Command from the control leads beyond the negative limit
• S-0-0050 set wrong

First checks, in this order

1. Clear the error, switch power on, enable, and command a move back into the allowed range.
2. Ask the machine builder why the command went past the limit.
3. Check S-0-0050 and S-0-0055; S-0-0057 sets the hysteresis.

F6034: Emergency-Stop activated

What it means: The E-Stop input monitored by the drive (set up in P-0-0008) went to 0 V; in this F6 class the axis is stopped as fast as possible. It can only be cleared once the E-Stop is released or its evaluation is off.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: fastest possible stop set in P-0-0119 (bits 4 to 7), then torque-free

Likely causes

• E-Stop pressed or the E-Stop circuit opened
• Digital inputs set up wrong
• E-Stop switch or cable defective or wired wrong
• Digital inputs on the control section defective

First checks, in this order

1. Find out why the E-Stop opened and fix it.
2. Check the input assignment (P-0-0223) and the digital input setup.
3. Check the switch and its wiring.
4. Release the E-Stop, clear the error, switch power on and enable again.

F6043: Positive travel range limit switch activated

What it means: The positive hardware limit switch (monitoring set in P-0-0090) was hit and the axis was stopped with a velocity command reset.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: fastest possible stop (velocity command reset), then torque-free

Likely causes

• Axis ran past the travel range onto the limit switch
• Digital inputs set up wrong
• Limit switch or cable defective or wired wrong
• Control section inputs defective

First checks, in this order

1. Clear the error (reset key or C0500) and switch power on.
2. Enable and command a move back into the allowed range.
3. Check the limit switch, its wiring and the digital input setup.
4. If set as a fatal warning instead, the code is E8043.

F6044: Negative travel range limit switch activated

What it means: The negative hardware limit switch (monitoring set in P-0-0090) was hit and the axis was stopped with a velocity command reset.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: fastest possible stop (velocity command reset), then torque-free

Likely causes

• Axis ran past the travel range onto the limit switch
• Digital inputs set up wrong
• Limit switch or cable defective or wired wrong
• Control section inputs defective

First checks, in this order

1. Clear the error (reset key or C0500) and switch power on.
2. Enable and command a move back into the allowed range.
3. Check the limit switch, its wiring and the digital input setup.
4. If set as a fatal warning instead, the code is E8044.

F7020: Safe maximum speed exceeded

What it means: Integrated safety (Safe Motion) saw the actual speed go above the safe maximum speed set in P-0-3270.0.2, in normal operation or in a special mode.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: safety stop set in P-0-3263.0.1, then torque-free with output stage locked

Likely causes

• Safe speed threshold set too low
• Speed command too high (control program, S-0-0259 or P-0-4007 positioning data)

First checks, in this order

1. Check the command speed in the control or the positioning data.
2. Check P-0-3270.0.2; changes to safety settings need authorized staff and a new safety validation.
3. The stop behavior is set in P-0-3263.0.1.

F8042: Encoder 2 error: Signal amplitude incorrect

What it means: Only with the redundant motor encoder function: the encoder 2 signals left the allowed range, were disturbed, or a digital encoder sent checksum errors. Fatal error; the encoder must be reinitialized.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: drive enable removed at once (torque-free), holding brake applied

Likely causes

• Damaged encoder cable or poor shield
• Electrical noise from the power cable
• Defective or dirty encoder; linear read head mounted wrong
• Hardware fault on the control section

First checks, in this order

1. Check the encoder 2 cable, connectors and shield.
2. Check the power cable shield.
3. Check, clean or replace the encoder and its mounting.
4. Replace the control section or drive if the encoder side is good.

F8070: Control voltage failure

What it means: The external 24 V control voltage left its allowed tolerance. All motors go torque-free at once and holding brakes apply. It cannot be cleared with C0500: the drive must be switched off completely. Up to MPx16 it was called +24Volt DC error.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (older name: +24Volt DC error)

Drive response: all motors torque-free at once, holding brakes apply

Likely causes

• 24 V supply cable or connector defective
• 24 V power supply overloaded
• 24 V power supply defective
• Short circuit in the 24 V wiring

First checks, in this order

1. Measure the 24 V at the drive while the machine runs.
2. Check the 24 V cable and connectors.
3. Check the load and condition of the 24 V power supply; replace it if needed.
4. Look for shorts in the 24 V wiring.

F8078: Speed loop error

What it means: The velocity loop monitor tripped: torque at its limit while torque and speed have opposite signs above 20 rpm, so the motor moves away from the command instead of following it.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: drive enable removed at once (torque-free), holding brake applied

Likely causes

• Motor phases U, V, W swapped, so commutation is wrong
• Encoder mounted or counting in the wrong direction
• Velocity loop settings wrong
• Commutation offset wrong
• Motor encoder defective; or U/f operation where this monitor makes little sense

First checks, in this order

1. Check the motor phase order at the drive and the motor.
2. Check the encoder arrangement and counting direction.
3. Check the velocity loop settings.
4. Kit motors: set commutation again (C1200); MHD, MKD, MKE motors: replace the motor.
5. In U/f operation the monitor can be switched off in P-0-0556.

F8079: Velocity limit value exceeded

What it means: The actual speed (S-0-0040) went above 1.125 times one of the velocity limits S-0-0091, S-0-0038 or S-0-0039.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: drive enable removed at once (torque-free), holding brake applied

Likely causes

• Velocity limits set wrong
• Unstable or strongly oscillating velocity loop
• Export-free firmware: inverter output frequency above 600 Hz
• Open loop: slip compensation too high
• Another motor on the same load drives this one faster

First checks, in this order

1. Check S-0-0091, S-0-0038 and S-0-0039.
2. Check the velocity controller settings.
3. Check that the output frequency in P-0-0580 stays under 600 Hz.
4. Open loop: check slip compensation (P-0-0600).

F8100: Error when initializing the parameter handling

What it means: The control section check at start-up failed.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: fatal initialization error; restart needed

Likely causes

• MPx16: shows once at the first start after a firmware upgrade
• An optional module on the control section is not supported by the firmware
• Firmware does not match the hardware
• Control section hardware defect

First checks, in this order

1. Switch the 24 V control voltage off and on.
2. Check the firmware against the control section type code and the release notes.
3. If it persists, contact Rexroth service and replace the control section or drive.

F8118: Invalid power section/firmware combination

What it means: The firmware does not support the power section fitted.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: fatal initialization error; restart needed

Likely causes

• Firmware version does not support this power section type
• MPx-18 and later on IndraDrive C and M: power section hardware too old (built before week 30 of 2007)

First checks, in this order

1. Use a firmware release that supports the power section, or a supported power section.
2. Check the production date (FD field) on the power section type plate.
3. Contact Rexroth service if unsure.

F8120: Invalid control section/firmware combination

What it means: The control section does not match the firmware in use.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: fatal initialization error; restart needed

Likely causes

• Wrong firmware loaded during a firmware replacement
• Control section not suited to the application
• Safety technology set up wrong on a double-axis device

First checks, in this order

1. Load firmware that matches the control section, or fit a matching control section.
2. Check the control section configuration and type code.

F8122: Control section defective

What it means: An error occurred while the control section initialized; its hardware is defective.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: fatal initialization error; restart needed

Likely causes

• Control section hardware defective

First checks, in this order

1. Switch the control voltage off and on once to confirm.
2. Replace the control section or the whole drive with the same hardware configuration.

F9001: Error internal function call

What it means: The firmware switched the device off after an internal software error. As a fatal system error, digital outputs go to 0, the ready relay opens and the holding brake applies.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 and HMV supply units (same code and name)

Drive response: output stage locked, ready relay opens, brake applied; 24 V restart needed

Likely causes

• Undefined cause
• General firmware error

First checks, in this order

1. Switch the 24 V control voltage completely off and on.
2. If it happens again, replace the device and contact Rexroth service.

F9003: Watchdog

What it means: The firmware watchdog timer tripped (general firmware error) and the drive was switched off.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 and HMV supply units (same code and name)

Drive response: output stage locked, ready relay opens, brake applied; 24 V restart needed

Likely causes

• Firmware error
• Device hardware fault

First checks, in this order

1. Switch the 24 V control voltage completely off and on.
2. If it repeats, replace the device and contact Rexroth service.

E8026: Undervoltage in power section

What it means: The DC bus voltage fell below P-0-0114 Undervoltage threshold, or the module bus reports DC bus not OK, and P-0-0118 is set to fatal warning for undervoltage. Motor torque for driving is locked: the control can still brake the axis but cannot accelerate it.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: fatal warning: driving torque locked, braking still possible

Likely causes

• Power switched off without removing drive enable first
• Supply fault or overload
• Mains failure

First checks, in this order

1. Check the control logic: remove drive enable before switching power off.
2. Check the supply unit and mains voltage.
3. Find and fix the cause of any mains failure.

E8025: Overvoltage in power section

What it means: The DC bus voltage went above its maximum. The drive switches motor torque off until the voltage falls back, then switches it on again. If the voltage stays high, F8025 follows.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: fatal warning: motor torque off while the voltage is too high

Likely causes

• Too much energy fed back while braking
• Mains voltage too high
• Braking resistor missing, badly connected or cable faulty
• Motor not rated for the DC bus voltage (P-0-0853 lower than S-0-0380)

First checks, in this order

1. Lower the deceleration rates or review drive sizing.
2. Check the braking resistor and its wiring.
3. Check the mains voltage; adapt it with a transformer if it is too high.
4. Compare P-0-0853 with the actual DC bus voltage in S-0-0380.

E8027: STO/SBC while drive enabled

What it means: Safe standstill was selected while the drive was enabled, or drive enable was set while safe standstill was active. The drive goes torque-free at once.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (older name: Safe torque off while drive enabled)

Drive response: torque-free at once

Likely causes

• STO selected while the drive was enabled
• Drive enable set while STO was active

First checks, in this order

1. Remove drive enable before selecting STO.
2. Return to normal operation before setting drive enable.
3. Check the safety circuit wiring and the control sequence.

E8055: Motor overload, current limit active

What it means: The motor thermal model has reduced the available current below S-0-0109 Motor peak current, so the drive may no longer follow the commands from the control.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: fatal warning: current limited

Likely causes

• Acceleration torque demanded too high
• Continuous load too high
• Process force too high (for example infeed)
• Mechanics changed: friction or load

First checks, in this order

1. Reduce acceleration in the command profile.
2. Reduce load during long machining phases or the process force.
3. Check the mechanics for friction and binding.

E8057: Device overload, current limit active

What it means: The drive's thermal load (P-0-0141) reached about 97 % on HCS, HMS and HMD units, so continuous current limiting is active and the drive may no longer follow commands.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: fatal warning: current limited

Likely causes

• Drive too small for the application or motor
• Acceleration torque demanded too high
• Continuous load or process force too high
• Mechanics changed: friction or load

First checks, in this order

1. Check drive sizing; use a larger drive if needed.
2. Reduce acceleration and process force.
3. Check the mechanics for friction and binding.
4. Watch P-0-0141 and the earlier warning E2061.

E8058: Drive system not ready for operation

What it means: Another drive on the shared module bus reported an error, and this drive shut down as part of a group reaction. The supply unit shows E2810.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: fatal warning: drive shut down with the group

Likely causes

• An error on one or more other drives in the drive system

First checks, in this order

1. Check the displays of all drives in the group and find the one with the real error.
2. Fix that error first.
3. Group reactions are set in P-0-0118.

E2054: Not homed

What it means: An absolute positioning move was requested (S-0-0258, S-0-0282 or P-0-4006) but the encoder used is not homed (S-0-0403). The drive stops or rejects the target.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: warning: the move is not carried out

Likely causes

• Position reference not set yet
• Reference lost, for example after encoder or drive replacement

First checks, in this order

1. Home the axis with S-0-0148 C0600 Drive-controlled homing procedure command.
2. Or set the absolute position with S-0-0447 C0300.

E2055: Feedrate override S-0-0108 = 0

What it means: The feedrate override is 0 %, so drive-controlled moves stop or do not start even with a speed command present.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: warning: axis stays stopped

Likely causes

• S-0-0108 set to 0
• Override taken from an analog input that reads 0 V
• Override potentiometer of the control at 0 or read wrong
• Analog input or its cable defective

First checks, in this order

1. Set the override above 0; 100 % gives full speed and switches the effect off.
2. Measure the analog input voltage (10 V equals 100 %).
3. Check the potentiometer, cable and analog input.

E2053: Target position out of travel range

What it means: The requested target position lies outside the travel range set by S-0-0049 and S-0-0050. From MPx05 the positioning move is not started.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: warning: the move is not started

Likely causes

• Position limits set wrong
• Limit monitoring active where it is not needed (modulo axis)
• Relative moves adding up past the limits
• Wrong absolute target or wrong positioning block

First checks, in this order

1. Check S-0-0049, S-0-0050 and S-0-0055.
2. Check the target in S-0-0258 or S-0-0282, or P-0-4006 and block selection P-0-4026.
3. The reaction is set in P-0-0090.

E2059: Velocity command value limit active

What it means: The total velocity command at the controller input is above the allowed limit and is being clipped.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: warning only

Likely causes

• Cyclic command from the control wrong or too high
• S-0-0091 Bipolar velocity limit value set too low
• Export-free firmware in open loop: command equal to more than 600 Hz output frequency

First checks, in this order

1. Check the cyclic command values from the control.
2. Check S-0-0091.
3. Keep the command below the 600 Hz output frequency limit.

E2063: Velocity command value > limit value

What it means: The velocity command (S-0-0036 or another source) is above the smallest velocity limit, so following error can grow during positioning.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: warning only

Likely causes

• Cyclic command from the control wrong or too high
• Velocity limits set too low (S-0-0091, S-0-0038, S-0-0039)
• Export-free firmware in open loop: command equal to more than 600 Hz output frequency

First checks, in this order

1. Check the command values from the control.
2. Check S-0-0091, S-0-0038 and S-0-0039.

E2074: Encoder 1: Encoder signals disturbed

What it means: On absolute encoders the drive compares the incremental sine and cosine track with the absolute position. A mismatch means the analog encoder signals are disturbed. It clears only when the encoder is reinitialized (switch to parameter mode PM).^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: warning only

Likely causes

• Damaged encoder cable or poor shield
• Electrical noise from the power cable
• Defective or dirty encoder; linear read head mounted wrong
• Firmware 18V30 and later: low encoder battery
• Firmware 20 and later: the encoder reports its own diagnostic (read S-0-0603.x.5)

First checks, in this order

1. Check the encoder cable and shield, and the power cable shield.
2. Check, clean or replace the encoder.
3. Replace the encoder battery if fitted.
4. Read S-0-0603.x.5 and look up the code in the encoder documentation.

E2077: Absolute encoder monitoring, encoder 1 (encoder alarm)

What it means: The absolute encoder (EnDat 2.x) set its own error bit for the absolute position. It clears only when the encoder is reinitialized (switch to communication phase 2 or parameter mode).^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (older name: Absolute encoder monitoring, motor encoder (encoder alarm))

Drive response: warning only

Likely causes

• Encoder defective
• Linear scale: read head mounted wrong
• Encoder or scale dirty

First checks, in this order

1. Check the encoder and replace it if needed.
2. Check the read head mounting.
3. Clean or replace the scale.

E2048: Low battery voltage (encoder)

What it means: MPx-18 and later: the encoder backup battery of MSM motors is below its allowed voltage during operation. If 24 V is switched off before the battery is replaced, F2048 follows at the next start and the position reference is lost.^[1][2]

Also on: Different meaning on firmware MPx-02 to MPx-08, where E2048 is Interpolation acceleration = 0

Drive response: warning only

Likely causes

• Encoder battery near end of life (designed for about 10 years)

First checks, in this order

1. Replace the battery while the 24 V control voltage is still on (see the IndraDrive Cs project planning manual).
2. Do not switch off 24 V until the battery is replaced.

E2086: Prewarning supply module overload

What it means: The supply unit warns over the module bus that it is close to overload. If the load does not drop, F2086 and power off can follow.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: warning only

Likely causes

• Power demand close to the supply rating
• Braking resistor close to its energy limit

First checks, in this order

1. Reduce the power demand, for example lower infeed rates.
2. Check the sizing of the supply unit.
3. Check the sizing of the braking resistor.

E2820: Braking resistor overload prewarning

What it means: The thermal model of the braking resistor reached its warning threshold (fixed at 90 % in MPx16, set in P-0-0469 from MPx17). F2820 follows if the load keeps rising.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: warning only

Likely causes

• Deceleration of the connected drives too high
• Too much regenerated energy per cycle
• Braking resistor connection interrupted
• Continuous regenerative power too high for the resistor
• P-0-0469 set wrong

First checks, in this order

1. Reduce deceleration, or lengthen the cycle or lower maximum speed.
2. Check the external braking resistor wiring.
3. Check the braking resistor sizing.
4. Check P-0-0469.

E4005: No command value input via master communication

What it means: The drive is not receiving command values from the master. P-0-4088 is set so that a bus failure only gives this warning instead of a drive error such as F4009.^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: warning only; the control must react

Likely causes

• Bus failure: cable, connector or switch problem
• Master stopped, or the drive removed from the bus group
• No telegram within the monitoring time P-0-4075
• EtherCAT: cables in the wrong ports (incoming to X25 P1, outgoing to X24 P2)

First checks, in this order

1. Treat it like F4009: check master state, cables and timing.
2. On EtherCAT check the port wiring and bus timing.
3. Make sure the control resets Drive Halt, drive enable and drive ON on a bus failure so the axis cannot restart by itself.

E8034: Emergency-Stop activated

What it means: The E-Stop input monitored by the drive (set up in P-0-0008) went to 0 V. The axis decelerates as set for removing drive enable (P-0-0119 bits 0 to 3).^[1][2]

Also on: IndraDrive firmware MPx-02 to MPx-08 (same code and name)

Drive response: fatal warning: drive decelerates as for drive enable off

Likely causes

• E-Stop pressed or the E-Stop circuit opened
• Digital inputs set up wrong
• E-Stop switch or cable defective or wired wrong
• Control section inputs defective

First checks, in this order

1. Find out why the E-Stop opened and fix it.
2. Check the digital input setup and P-0-0223.
3. Check the switch and its wiring.