Omron MX2 Fault Codes

E01: Over-current event while at constant speed

What it means: Output current jumped above the trip level while the motor was running at a steady speed, so the drive shut off its output. Omron puts the trip point at about 200% (MX2 V2) or 220% (RX) of the drive's rated output current.^[1][2][3]

Also on: RX manual: Overcurrent trip, constant speed (E01). MX2 V2 manual: Overcurrent protection, during constant speed.

Likely causes

• Sudden load change or a jam while running
• Short circuit in the output wiring or the motor
• Ground fault in the motor cable or motor
• Dual-voltage motor wired for the wrong voltage

First checks, in this order

1. Look for a jam, a binding mechanism or a sudden load swing on the machine.
2. After the 10 minute wait, check the output cables and the motor for shorts and ground faults.
3. Confirm the motor connection matches the supply voltage.
4. Open d081 to see the output current and frequency at the moment of the trip.

E02: Over-current event during deceleration

What it means: Output current went over the trip level while the drive was slowing the motor down.^[1][2][3]

Also on: RX manual: Overcurrent trip, deceleration (E02). MX2 V2 manual: Overcurrent protection, during deceleration.

Likely causes

• Deceleration time too short for the load inertia
• Short circuit or ground fault on the output side

First checks, in this order

1. Increase the deceleration time (F003, F203, A093, A293).
2. Check the output cables and the motor for shorts and ground faults.

E03: Over-current event during acceleration

What it means: Output current went over the trip level while the drive was speeding the motor up. This is the overcurrent trip Omron covers in most detail in the troubleshooting tips.^[1][2][3]

Also on: RX manual: Overcurrent trip, acceleration (E03). MX2 V2 manual: Overcurrent protection, during acceleration.

Likely causes

• Acceleration time too short
• Load too heavy or motor shaft locked
• Torque boost set wrong for the load
• Overload limit (current limit) disabled or set too high

First checks, in this order

1. Increase the acceleration time (F002, A092, A292), or use the acceleration stop function (A069, A070).
2. Check that the motor shaft turns freely and the load is not jammed.
3. Check the torque boost: the RX manual says lower it if it is too high; for a heavy load the MX2 manual suggests torque boost or free V/f (A044/A244 = 02).
4. Enable the overload limit (b021 = 01, 02 or 03). If it still trips, set the level b022/b025 lower and the time b023/b026 longer.

E04: Over-current event during other conditions

What it means: Output current went over the trip level when the drive was not accelerating, decelerating or running at constant speed, for example during DC braking or at stop.^[1][2][3]

Also on: RX manual: Overcurrent trip, others (E04). MX2 V2 manual: Overcurrent protection, others.

Likely causes

• DC injection braking force set too high
• Current detector (CT) problem (RX manual)
• PM motor not set up or tuned correctly (MX2 V2 manual)

First checks, in this order

1. Lower the DC injection braking power (A054).
2. If a PM motor is used, check the motor settings and tuning.
3. If it repeats with no load reason, have the drive's current detection checked or repaired.

E05: Motor overload protection

What it means: The drive's electronic thermal model calculated that the motor is overloaded, so it tripped. Monitor d104 shows the thermal load and the trip happens at 100%.^[1][2][3]

Also on: RX manual: Overload trip (E05). MX2 V2 manual: Overload protection.

Likely causes

• Load too heavy for the motor
• Electronic thermal level (b012/b212) set below the real motor current
• Frequent hard accelerations with high peak current
• Wrong motor parameters forcing too much current
• DC injection braking too strong (MX2 V2 manual)

First checks, in this order

1. Set the electronic thermal level b012 (b212 for motor 2) to the motor nameplate full load amps, and check b013 and b910 to b912.
2. Watch d104 while running to see how fast the thermal load climbs.
3. Lengthen the acceleration time (F002, F202, A092, A292) to cut peak current.
4. Check the motor parameters (H020 to H034, or H005) for the control method set in A044/A244.
5. If the drive truly cannot deliver the current, use a larger inverter. Reset is refused for about 10 seconds after this trip.

E06: Braking resistor overload protection

What it means: The braking resistor circuit was used more than the allowed rate set in b090, so the drive tripped to protect the resistor.^[1][2][3]

Also on: RX manual: Braking resistor overload trip (E06).

Likely causes

• Deceleration too fast, putting too much energy into the resistor
• Stop and start cycle too frequent
• b090 usage rate set too low for the application

First checks, in this order

1. Increase the deceleration time.
2. Reduce how often the machine stops and starts, or lengthen the cycle time.
3. Set b090 to match the resistor's allowed duty, and check the resistor value in b097.
4. Watch d103 (regenerative braking load rate) during a cycle.

E07: Over-voltage protection

What it means: The DC bus voltage went too high, usually from energy the motor sends back while slowing a heavy load. The RX and MX2 V2 manuals put the trip at about 400 V DC (200 V class) or 800 V DC (400 V class).^[1][2][3]

Also on: RX manual: Overvoltage trip (E07). MX2 V2 manual: Overvoltage protection.

Likely causes

• Deceleration time too short
• Load driving the motor (overhauling or high inertia load)
• Overvoltage suppression (b130) disabled
• Supply voltage too high
• Ground fault on the output side

First checks, in this order

1. Increase the deceleration time (F003, F203, A093, A293).
2. Enable overvoltage suppression during deceleration (b130 = 01 or 02).
3. If it still trips with b130 on, set the level b131 lower and check the integral time b134.
4. Check the output wiring and motor for ground faults.
5. For regular heavy braking, add a braking resistor or regenerative braking unit. If the incoming voltage is high, fit an AC reactor.

E08: EEPROM error

What it means: The drive's built-in memory reported a problem, usually caused by electrical noise or too much heat inside the drive.^[1][2][3]

Also on: RX manual: EEPROM error (E08).

Likely causes

• Electrical noise near the drive
• High internal temperature (clogged fins or failed fan)
• Memory damaged or parameters not stored correctly

First checks, in this order

1. The STOP/RESET key and RS input will not clear this trip: switch the power off and on.
2. If E08 returns at power up, initialize the parameters and set them again.
3. Check for noise sources nearby and for proper grounding and cable separation.
4. Clean the cooling fins and check the fan.
5. If it keeps coming back, the drive needs repair.

E09: Under-voltage error

What it means: The DC bus voltage dropped below the level the control circuit needs, so the drive shut off its output. The MX2 V2 manual puts this at about 173 V DC (200 V class) or 345 V DC (400 V class).^[1][2][3]

Also on: RX manual: Undervoltage trip (E09). MX2 V2 manual: Undervoltage.

Likely causes

• Supply voltage dip or brief power loss
• Supply capacity too small, or a poor contact in the breaker or contactor
• Lost input phase (the MX2 manual warns this can cause undervoltage trips)
• Smoothing capacitors worn out (MX2 V2 manual)

First checks, in this order

1. Measure the supply voltage at the drive terminals while the machine runs.
2. Check the breaker, contactor and fuses on the input side.
3. If the drive should ride through or restart after short dips, check the retry settings b001 to b004.
4. If the supply is fine, check capacitor life (see the capacitor life curve in the manual).

E10: Current detection error

What it means: The drive's internal current measurement (current detector, CT) has failed its self-check.^[1][2][3]

Also on: RX manual: CT error (E10). MX2 V2 manual: Current detector error.

Likely causes

• Faulty current detector inside the drive

First checks, in this order

1. Switch the power off and on once.
2. If E10 comes back, the drive needs repair or replacement.

E11: CPU error

What it means: The drive's built-in CPU malfunctioned, so the drive stopped its output.^[1][2][3]

Also on: RX manual: CPU error (E11).

Likely causes

• Strong electrical noise
• Internal fault in the drive

First checks, in this order

1. Switch the power off and on (the RX and MX2 V2 manuals say the reset key is not accepted for this trip).
2. Look for noise sources and check grounding and cable routing.
3. If it repeats, the drive needs repair.

E12: External trip

What it means: An input set as EXT (code 12) was turned on by outside equipment, so the drive tripped. The trip stays latched even after the input turns off.^[1][2][3]

Also on: RX manual: External trip (E12).

Likely causes

• An external device wired to the EXT input signalled a fault (for example a protection relay or interlock)
• Wiring fault or noise on the EXT input

First checks, in this order

1. Find which device drives the EXT input (C001 to C007 set to 12) and fix its fault.
2. Check the input wiring and look for noise.
3. Reset with STOP/RESET or the RS input. If the RUN command is still on, the motor starts again after the reset.

E13: USP

What it means: Unattended start protection: power was switched on while a RUN command was already present, so the drive refused to start the motor.^[1][2][3]

Also on: RX manual: USP trip (E13). MX2 V2 manual: USP error.

Likely causes

• RUN command left on when power came back
• PLC or switch sequence gives RUN before the drive is powered

First checks, in this order

1. Turn the RUN command off, then reset with STOP/RESET or the RS input.
2. Check the start sequence so RUN comes only after power up.
3. The function is active when an input is set to 13 (USP) in C001 to C007.

E14: Ground fault

What it means: During its power-up test the drive found a ground fault between its output and the motor. This check protects the drive, not people, and does not work while the motor still has residual voltage.^[1][2][3]

Also on: RX manual: Ground fault trip (E14). MX2 V2 manual: Grounding protection.

Likely causes

• Damaged insulation in the motor cable or motor
• Fault in the drive's output or main circuit

First checks, in this order

1. Power off, wait 10 minutes, then disconnect the motor cable at U, V and W and test the cable and motor insulation.
2. If it trips with the output wiring disconnected, the drive itself is faulty.
3. Only a power cycle clears this trip.
4. On the MX2 V2, b098 switches this detection on or off (default on).

E15: Input over-voltage

What it means: The incoming supply stayed too high for 100 seconds while the drive was stopped. The RX and MX2 V2 manuals give about 390 V DC (200 V class) or 780 V DC (400 V class) on the DC bus. After the cause is cleared the drive can run again.^[1][2][3]

Also on: RX manual: Incoming overvoltage trip (E15). MX2 V2 manual: Incoming overvoltage protection.

Likely causes

• Supply voltage too high, often at light plant load
• Supply voltage swings

First checks, in this order

1. Measure the supply voltage while the drive is stopped.
2. Lower the incoming voltage or steady the supply.
3. Fit an AC reactor on the input.

E16: Momentary power interruption trip

What it means: RX only: the supply was lost for 15 ms or more, so the drive shut off its output. If restart is selected, the drive can restart at power return while the RUN command is still on.^[3]

Also on: E16 appears only in the RX manual. On the MX2, a supply dip shows as undervoltage (E09) or undervoltage standby.

Likely causes

• Brief supply dip or loss
• Poor contact in the input breaker or contactor

First checks, in this order

1. Check the supply for dips and restore power.
2. Check and replace the breaker or contactor if its contacts are worn.
3. Review the restart settings b001 to b004.

E21: Inverter thermal trip

What it means: The temperature of the drive's power devices went over the limit, so the drive tripped.^[1][2][3]

Also on: RX manual: Temperature error (E21). MX2 V2 manual: Abnormal temperature.

Likely causes

• Cooling fins clogged with dust
• High ambient temperature or poor ventilation
• Cooling fan stopped or not powered
• Drive not mounted vertically or without enough clearance

First checks, in this order

1. Clean the heat sink fins.
2. Check the cabinet temperature and air flow.
3. Check that the cooling fan runs. The MX2 V2 manual suggests setting b092 to always on.
4. Check that the drive is mounted vertically.
5. Use the fin overheat warning level C064 with the OHF output to get a warning before the trip.

E20: Temperature error when the rotation speed of the cooling fan decreases

What it means: RX only: an over-temperature was detected while the cooling fan speed had dropped.^[3]

Likely causes

• Worn or failed cooling fan
• Clogged heat sink fins

First checks, in this order

1. Replace the cooling fan.
2. Clean the heat sink fins.

E24: Input open phase trip

What it means: RX only: with input phase loss protection on (b006 = 01), the drive lost one supply phase for about 1 second or more and tripped to protect itself.^[3][1]

Also on: E24 appears only in the RX manual. The MX2 manual warns that running an MX2 on a lost phase can cause undervoltage or overcurrent trips instead.

Likely causes

• Blown fuse or broken wire on one input phase
• Poor contact in the input breaker or contactor

First checks, in this order

1. Check the input wiring and fuses on all three phases.
2. Check and replace the breaker or contactor if needed.

E35: Thermistor

What it means: The motor thermistor wired to terminals [5] and [L] reads too high, so the drive tripped to protect the motor. The MX2 trips at about 3 kohm (plus or minus 10%), and an open thermistor circuit also trips.^[1][2][3]

Also on: RX manual: Thermistor error (E35), thermistor on the TH terminal. MX2 V2 manual: Thermistor error.

Likely causes

• Motor too hot
• Broken thermistor or open wiring
• Noise on the thermistor wiring
• Input 5 set to PTC (19) while a normal 24 V DC signal is wired to it

First checks, in this order

1. Check the motor temperature and let it cool, then reset with STOP/RESET.
2. Measure the thermistor resistance and check its wiring.
3. Route the thermistor wires away from power cables.
4. Check that C005 is 19 (PTC) only when a thermistor is really wired to input 5. C085 adjusts the thermistor input.

E37: Safe Stop

What it means: The safety inputs GS1/GS2 (safe torque off) were opened with the safety switch on and GS input mode b145 set to trip (01), so the drive stopped its output and tripped. If E37 and E12 happen together, E37 takes priority.^[1][2][3]

Also on: RX manual: Emergency shutoff (E37), triggered by the EMR terminal (S3) with SW1 on; reset through the RS terminal only. MX2 V2 manual: Emergency shutoff.

Likely causes

• Emergency stop or safety relay opened the GS1/GS2 circuit
• Broken wire or loose terminal in the safety circuit
• Only one channel opened because of a wiring fault

First checks, in this order

1. Check why the safety chain opened (e-stop, guard switch, safety relay).
2. Check the wiring of both GS1 and GS2; the EDM output only confirms when both channels work.
3. Check b145 (00 no trip, 01 trip).
4. Reset: the MX2 V1 manual says only an RS input (18) clears E37; the MX2 V2 also accepts STOP/RESET unless b087 is 01.

E38: Low-speed overload protection

What it means: The drive's own electronic thermal protection detected an overload at very low speed (0.2 Hz or lower) and tripped. This protects the inverter, not the motor; motor overload is E05. The trip history can show a higher frequency than the real one. On the MX2 V2 with b910 set to 01 to 03, any inverter overload shows as E38.^[1][2][3]

Also on: RX manual: Overload trip in low speed range (E38). MX2 V2 manual: Overload protection in a low speed range (Inverter overload protection).

Likely causes

• Heavy load or a jam while the motor is at or near zero speed
• High current held at very low frequency for too long
• Inverter too small for the low-speed duty

First checks, in this order

1. Reduce the load in the very low speed range and check the machine for binding.
2. Read d081: the digit after the dot shows what the drive was doing (for example E38.2 means decelerating).
3. Check b910 and the thermal load monitor d104.
4. Check the duty rating b049: heavy duty (00) gives 150% for 60 s, normal duty (01) only 120% for 60 s.
5. If the low-speed load is real, use a larger inverter.

E30: Driver error

What it means: The IGBT gate driver shut off the output to protect the power devices after a very fast overcurrent (about 350% of rated current per the MX2 V2 manual), power device overheating, or a drop in the gate drive supply. The drive cannot retry after this trip.^[1][2][3]

Also on: RX manual: IGBT error (E30).

Likely causes

• Short circuit in the output circuit
• Ground fault in the motor cable or motor
• Damaged IGBT or main circuit element
• Clogged cooling fins

First checks, in this order

1. Check the output cables for shorts.
2. Check the output cables and motor for ground faults.
3. Test the IGBTs as described in the manual's inverter/converter test.
4. Clean the cooling fins.
5. Only a power cycle clears this trip.

E25: Main circuit error

What it means: The drive could not confirm its main circuit is working, because of noise or damage to a main circuit element.^[1][2][3]

Also on: RX manual: Main circuit error (E25).

Likely causes

• Strong electrical noise
• Damaged main element (IGBT)
• Output short circuit (RX manual)

First checks, in this order

1. Take measures against noise (grounding, cable separation, filters).
2. Check the output wiring for shorts.
3. If it repeats, the drive needs repair. The RX manual says power must be switched off to reset it.

E22: CPU communication error

What it means: Communication between the drive's two internal CPUs failed.^[1][2]

Also on: MX2 V2 manual: CPU communication error.

Likely causes

• Strong electrical noise
• Internal fault in the drive

First checks, in this order

1. Look for noise sources and fix grounding and cable routing.
2. Switch the power off and on.
3. If it repeats, the drive needs repair.

E23: Gate array communications error

What it means: RX only: communication between the built-in CPU and the gate array failed.^[3]

Likely causes

• Strong electrical noise
• Loose or disconnected internal cable

First checks, in this order

1. Take measures against noise.
2. Check the internal connectors.
3. If it repeats, the drive needs repair.

E19: Temperature detection error

What it means: MX2 V2 only: the cooling fin temperature sensing circuit found a fault such as a disconnected sensor.^[2]

Also on: Listed in the MX2 V2 (3G3MX2-V2) manual only.

Likely causes

• Faulty temperature detection inside the drive

First checks, in this order

1. The drive is faulty and needs repair.

E26: Analog current input error

What it means: MX2 V2 only: too much current flowed into the analog current input terminal FI, so the drive tripped.^[2]

Also on: Added with the MX2 V2 (3G3MX2-V2); not a fatal fault.

Likely causes

• Short circuit or wrong wiring on the FI input
• Faulty control circuit board

First checks, in this order

1. Check the FI wiring for shorts or a voltage source wired in by mistake.
2. If the wiring is correct, the control board needs repair.

E36: Braking error

What it means: With brake control on (b120 = 01), the drive did not get the brake confirmation signal within b124 after giving the brake release signal, or the output current did not reach the brake release current b126 within the release wait time b121.^[1][2][3]

Also on: RX manual: Brake error (E36). MX2 V2 manual: Brake error.

Likely causes

• Mechanical brake not releasing or not engaging
• Brake confirmation (BOK) signal not wired or not arriving
• b124 too short for the brake
• Motor current not reaching b126

First checks, in this order

1. Check that the brake really opens and closes.
2. Check the wiring of the brake confirmation input (an input set to 44, BOK).
3. Increase b124 if the brake is just slow.
4. Check b126 and b121 against the motor and load.

E40: Operator connection

What it means: Communication between the drive and the remote digital operator (keypad) failed or the cable was unplugged.^[1][2]

Also on: MX2 V2 manual: Digital Operator connection failure (remote operator 3G3AX-OP01).

Likely causes

• Remote operator cable unplugged, loose or damaged
• Keypad removed on purpose while b165 is set to trip

First checks, in this order

1. Check and reseat or replace the operator cable.
2. Check b165, the action on operator loss: 00 trip, 01 decel and trip, 02 ignore, 03 free run, 04 decel and stop.
3. If the keypad is unplugged on purpose, set b165 to 02.

E41: Modbus communication error

What it means: The Modbus RTU (RS-485) master stopped talking to the drive for longer than the timeout, and C076 is set to trip (00).^[1][2][3]

Also on: RX manual: ModBus communications error (E41), trip set by C076.

Likely causes

• Broken or loose RS-485 wiring at SP and SN
• Wrong baud rate, address, parity or stop bits
• Missing or wrong terminating resistors, or cable too long
• Master polling slower than the C077 timeout

First checks, in this order

1. Check the wiring at terminals SP and SN and the terminating resistors.
2. Check C071 (speed), C072 (address), C074 (parity) and C075 (stop bits) against the master.
3. Check the timeout C077 and the action C076.
4. After changing C071, C074 or C075, cycle power or reset with the RS input so the change takes effect.

E60 to E69: Option errors (error in connected option board, the meanings change upon the connected option)

What it means: The installed option board reported an error. Each option board uses these codes for its own meanings, so the option's manual explains the exact one.^[1][2][3]

Also on: RX manual: Option 1 error (E60 to E69), board on option port 1. MX2 V2 manual: Option error (E60 to E68).

Likely causes

• Fault on the option board or its network
• Option board not mounted firmly

First checks, in this order

1. Look up the code in the option board's manual (for example the MX2/RX EtherCAT unit manual, I574).
2. Check that the option board and its housing are mounted firmly and the screws are tight.
3. P001 sets what the drive does on an option error: 00 trip, 01 continue running.

E69: Option timeout

What it means: MX2 V2: communication between the drive and the option unit timed out.^[2]

Also on: On the RX with a 3G3AX-PG01 board, E69 means a PG board connection error (see the RX row).

Likely causes

• Option unit not connected or not seated
• Faulty option unit

First checks, in this order

1. Check that the option unit housing is mounted properly and the fixing screws are tight.
2. If it is mounted properly and still trips, replace the option unit.

E70 to E79: Option 2 error

What it means: RX only: the option board on option port 2 (control terminal side) reported an error.^[3]

Likely causes

• Fault on the port 2 option board
• Option board not mounted firmly

First checks, in this order

1. Check that the board is mounted correctly.
2. Look up the code in the option board's manual.

E80: Encoder disconnection

What it means: The drive lost the encoder feedback: wiring off, a connection error, a failed encoder, or an encoder without line driver output. The MX2 V2 manual says it trips when output is at or above the creep speed P015 but measured speed stays below the starting frequency b082 for the time in P077.^[1][2]

Also on: On the RX, encoder disconnection is E60 (port 1) or E70 (port 2) with the 3G3AX-PG01 board.

Likely causes

• Encoder cable disconnected or wired wrong
• Failed encoder
• Encoder type without line driver output
• P077 too short or P015 too low

First checks, in this order

1. Check the encoder wiring and connectors.
2. Check that the encoder has line driver output.
3. Set P077 slightly longer and P015 slightly higher.
4. Check that P003 is set for encoder feedback (01) and P011 matches the encoder pulses.

E81: Excessive speed

What it means: Motor speed measured by the encoder rose to maximum frequency A004 times the overspeed level P026, or higher.^[1][2]

Also on: MX2 V2 manual: Overspeed. On the RX with a PG board the same idea is E61 or E71.

Likely causes

• Encoder wiring fault giving a false reading
• Encoder pulse count P011 set wrong
• Load driving the motor faster than commanded

First checks, in this order

1. Check the encoder wiring.
2. Check that P011 matches the encoder's pulses per revolution.
3. Check the load conditions and the frequency setting F001.
4. Check P026.

E83: Positioning range error

What it means: In simple position control, the current position went outside the limits set in P072 (forward) and P073 (reverse).^[1][2]

Also on: MX2 V2 manual: Position control range trip. On the RX with a PG board the same idea is E63 or E73.

Likely causes

• Position limits set too tight
• Wrong position data or origin
• Mechanical overtravel

First checks, in this order

1. Check the current position.
2. Check P072 and P073.
3. Check the position settings P060 to P067 and the origin (homing).

E60: Encoder disconnection

What it means: RX with a 3G3AX-PG01 encoder board on option port 1: the encoder wiring is off, badly connected, damaged, or not a line driver type. The same fault on port 2 is E70.^[3]

Also on: On the MX2 this fault is E80.

Likely causes

• Encoder cable disconnected or loose
• Damaged encoder
• Encoder without line driver output

First checks, in this order

1. Check the encoder wiring and connectors.
2. Check the PG board DIP switch SWENC, which turns the A/B and Z phase disconnection checks on or off.

E61: Excess speed

What it means: RX with a 3G3AX-PG01 board on port 1: motor speed went over maximum frequency A004 times the overspeed level P026. Port 2 shows E71.^[3]

Also on: On the MX2 this fault is E81.

Likely causes

• Encoder reading wrong
• Load driving the motor too fast
• P026 set too low

First checks, in this order

1. Check the encoder wiring and settings.
2. Check the load and P026.

E62: Positioning error

What it means: RX with a 3G3AX-PG01 board on port 1: during position control the position error grew past 1,000,000 pulses. Port 2 shows E72.^[3]

Likely causes

• Load too heavy or mechanism jammed
• Encoder fault or wiring problem

First checks, in this order

1. Check the machine for binding.
2. Check the encoder and its wiring.

E63: Position control range trip

What it means: RX with a 3G3AX-PG01 board on port 1: in absolute position control the position went past the forward (P072) or reverse (P073) limit. Port 2 shows E73.^[3]

Also on: On the MX2 this fault is E83.

Likely causes

• Limits set too tight
• Wrong origin or position data

First checks, in this order

1. Check P072 and P073.
2. Check the origin and the position commands.

E69: 3G3AX-PG01 connection error

What it means: RX: the drive detected a connection (mounting) failure of the PG encoder board on port 1. Port 2 shows E79.^[3]

Also on: On the MX2 V2, E69 is Option timeout.

Likely causes

• PG board not seated or loose

First checks, in this order

1. With power off and after the 10 minute wait, reseat the PG board and check its mounting.

E43: Drive Programming invalid instruction

What it means: The Drive Programming (EzSQ) program stored in the drive is damaged, or the PRG input was turned on with no program downloaded.^[1][2]

Also on: MX2 V2 manual groups E43 to E59 as DriveProgramming error and points to the DriveProgramming User's Manual.

Likely causes

• Program missing or corrupted
• PRG input turned on without a program

First checks, in this order

1. Download the program to the drive again.
2. Check the Drive Programming selection A017 and the input set to 82 (PRG).

E44: Drive Programming nesting count error

What it means: The Drive Programming program nests subroutines, if statements or for-next loops more than eight levels deep.^[1][2]

Likely causes

• Program structure too deeply nested

First checks, in this order

1. Rewrite the program to use eight nesting levels or fewer, then download it again.

E45: Drive Programming instruction error

What it means: The drive found a Drive Programming command it cannot execute.^[1][2]

Likely causes

• Program contains a command the drive cannot carry out

First checks, in this order

1. Check the program in the Drive Programming tool and fix the failing command.
2. See the DriveProgramming User's Manual for details.

E50 to E59: Drive Programming user trip (0 to 9)

What it means: A user-defined trip written into the Drive Programming program was triggered. The meaning is whatever the program author set.^[1][2]

Likely causes

• A condition defined in the machine's Drive Programming program

First checks, in this order

1. Check the program or the machine documentation to see what condition sets this user trip.
2. Fix that condition, then reset.

E99: STO Self-diagnosis error

What it means: MX2 V2 only: the drive found a fault in the STO (safe torque off) input terminals or its internal safety circuit. This happens regardless of the b145 setting.^[2]

Also on: Added with the MX2 V2 (3G3MX2-V2); not a fatal fault.

Likely causes

• Fault in the STO input wiring or internal safety circuit
• Strong electrical noise

First checks, in this order

1. Run the periodic functional test of the safety function described in the manual.
2. Take measures against noise.
3. If the internal safety circuit is faulty, the drive needs repair.

001: Frequency upper limit (A061) > Maximum Frequency (A004)

What it means: Parameter conflict warning: the upper frequency limit is set above the maximum frequency.^[1]

Likely causes

• A004 was lowered after A061 was set

First checks, in this order

1. Set A061 at or below A004.
2. d090 shows the latest warning code.

002: Frequency lower limit (A062) > Maximum Frequency (A004)

What it means: Parameter conflict warning: the lower frequency limit is set above the maximum frequency.^[1]

Likely causes

• A004 was lowered after A062 was set

First checks, in this order

1. Set A062 below A004.

005: Output frequency setting/monitor (F001) Multi-step speed reference 0 (A020) > Maximum Frequency (A004)

What it means: Parameter conflict warning: the frequency setting (F001 or A020) is above the maximum frequency.^[1]

Likely causes

• Frequency setting entered higher than A004

First checks, in this order

1. Lower F001/A020 or raise A004 if the motor and machine allow it.

015: Output frequency setting (F001) Multi-step speed reference 0 (A020) > Frequency upper limit (A061)

What it means: Parameter conflict warning: the frequency setting is above the upper frequency limit.^[1]

Likely causes

• Frequency setting higher than A061

First checks, in this order

1. Lower F001/A020 or raise A061.

025: Frequency lower limit (A062) > Output frequency setting (F001) Multi-step speed reference 0 (A020)

What it means: Parameter conflict warning: the lower frequency limit is above the frequency setting.^[1]

Likely causes

• Frequency setting lower than A062

First checks, in this order

1. Raise F001/A020 or lower A062.

031: Starting frequency (b082) > Frequency upper limit (A061)

What it means: Parameter conflict warning: the starting frequency is above the upper frequency limit.^[1]

Likely causes

• b082 set too high or A061 set too low

First checks, in this order

1. Set b082 below A061.

032: Starting frequency (b082) > Frequency lower limit (A062)

What it means: Parameter conflict warning: the starting frequency is above the lower frequency limit.^[1]

Likely causes

• b082 set higher than A062

First checks, in this order

1. Set b082 at or below A062.

035: Starting frequency (b082) > Output frequency setting (F001) Multi-step speed reference 0 (A020)

What it means: Parameter conflict warning: the starting frequency is above the frequency setting, so the motor cannot start at the set speed.^[1]

Likely causes

• Frequency setting lower than b082

First checks, in this order

1. Raise F001/A020 or lower b082.

036: Starting frequency (b082) > Multi-step speed reference 1 to 15 (A021-A035)

What it means: Parameter conflict warning: one or more multi-step speeds are below the starting frequency.^[1]

Likely causes

• A multi-step speed (A021 to A035) set lower than b082

First checks, in this order

1. Raise the low multi-step speeds or lower b082.

037: Starting frequency (b082) > Jogging frequency (A038)

What it means: Parameter conflict warning: the jog frequency is below the starting frequency.^[1]

Likely causes

• A038 set lower than b082

First checks, in this order

1. Raise A038 or lower b082.

085: Output frequency setting (F001) Multi-step speed reference 0 (A020) = Jump frequency

What it means: Parameter conflict warning: the frequency setting falls inside a jump (skip) frequency band.^[1][2]

Likely causes

• F001/A020 inside the band set by A063, A065, A067 plus or minus A064, A066, A068

First checks, in this order

1. Move F001/A020 outside the jump bands, or change the jump frequencies and widths.

086: Multi-step speed reference 1 to 15 (A021-A035) = Jump frequency

What it means: Parameter conflict warning: a multi-step speed falls inside a jump (skip) frequency band.^[1][2]

Likely causes

• A021 to A035 value inside a jump band

First checks, in this order

1. Move that multi-step speed outside the jump bands, or change the jump settings A063 to A068.

091: Free setting V/f frequency 7 > Frequency upper limit (A061)

What it means: Parameter conflict warning: with free V/f, frequency point 7 (b112) is above the upper frequency limit.^[1][2]

Likely causes

• b112 set higher than A061

First checks, in this order

1. Check the free V/f points (b100 to b113) against A061.

092: Free setting V/f frequency 7 > Frequency lower limit (A062)

What it means: Parameter conflict warning: with free V/f, frequency point 7 (b112) is above the lower frequency limit.^[1][2]

Likely causes

• b112 and A062 set in conflict

First checks, in this order

1. Check b112 against A062.

095: Free setting V/f frequency 7 > Output frequency setting/monitor (F001) Multi-step speed reference 0 (A020)

What it means: Parameter conflict warning: with free V/f, frequency point 7 (b112) is above the frequency setting.^[1][2]

Likely causes

• b112 and F001/A020 set in conflict

First checks, in this order

1. Check b112 against F001/A020.

201 to 295: 2nd motor parameter warnings (201, 202, 205, 215, 225, 231, 232, 235, 285, 291, 292, 295)

What it means: The same parameter conflict checks as 001 to 095, but for the second motor settings (A261, A262, A204, A220). For example 201 means A261 is above A204.^[1]

Likely causes

• Second motor limits, maximum frequency or speed settings in conflict

First checks, in this order

1. Match the 2nd motor parameters the same way as the first motor ones (A261 and A262 within A204, A220 within the limits, b082 below them).