Troubleshooting / Benshaw starter faults

Benshaw Soft Starter Fault Codes

A soft starter fault means the motor will not start or trips while running, and the machine it drives stops: in OEE that is lost availability. These are the fault codes of Benshaw RediStart MX2 and MX3 solid state starters, low and medium voltage: what each code means, the likely causes, the first checks, and how to log it so it stops coming back.

How faults show

MX3: when a fault trips, the remote LCD keypad replaces the main screen with a fault screen showing the fault number and name (for example Fault 48, Bypass/2M Contactor Fault), the STOP LED flashes, and the main status screen comes back only after the fault is reset.

Alarms use the same number with an A instead of an F (for example A02 Motor Overload Alarm) and flash the ALARM LED; an alarm means the condition will become the matching fault if it continues.

The fault log holds the last 9 faults (FL1 is the newest; press ENTER on a log entry to step through the conditions at the time of the fault) and the event recorder holds the last 99 events (E01). MX2: the card mounted LED display shows the fault code, except a thermal overload trip shows F OL and an instantaneous overcurrent shows ioc.

Alarms show as A XX alternating with the meter (A OL for overload, noL for no line), and lockouts show as L OL (motor overload), L Ot (power stack overtemperature) and L CP (low control power). Reset: press RESET. Emergency overload reset: press RESET and DOWN together, which sets the motor overload content to 0.

Auto reset is possible only for faults marked auto reset allowed in the manual appendix, using Auto Fault Reset Time (PFN23 on MX3, P41/PFN10 on MX2) and the reset count limit (PFN24 on MX3). After the limit the starter locks out until a manual reset, and a start command is still needed after an auto reset.

Faults marked controlled fault stop run the selected stop mode before tripping when Controlled Fault Stop Enable (PFN25 on MX3) is On; faults marked shunt trip operate a relay programmed as Shunt FS or Shunt NFS to trip the upstream breaker.

Safety first.
Benshaw: hazard of electric shock, explosion or arc flash. Only qualified personnel familiar with the equipment may do the work; wear appropriate PPE and follow safe electrical work practices (NFPA 70E).

Turn off all power before working on or inside the starter, confirm it is off with a properly rated voltage sensing device, and treat circuits as live until they are de-energized, tested and tagged, including possible backfeeding. More than one disconnect switch may be needed to de-energize the equipment.

Do not open the front cover or connect or disconnect wiring while power is on. On medium voltage starters, wait the designated five minutes after opening the disconnect, then discharge any power factor correction capacitors before testing. When testing SCRs with the starter running, lethal voltages are present.

Sources: LV MX3 manual 890034-02-02 (PDF pages 2, 3 and 10), MX2 manual 890034-01-02 (PDF pages 2, 3 and 10), MV MX3 manual 890034-03-00 (PDF pages 10 and 173). Follow lockout/tagout and your site's safe-work procedures, and check the manual for your exact model before you act.

Quick lookup

Faults stop the motor and the machine it drives, so in OEE they are availability losses.

Type a code or a word (phase, overload, SCR, bypass) to filter the list. Click a code for its causes and first checks. Each code's details name the starters whose manual prints it.

69 codes

CodeName
F01UTS Time Limit Expired
F02Motor Thermal Overload Trip (Motor OL)
F03Slow Speed Time Limit Expired
F04Speed Switch Time Limit Expired
F05Motor PTC Overtemperature
F06Stator RTD Overtemperature
F07Bearing RTD Overtemperature
F08Other RTD Overtemperature
F10Phase Rotation Error, not ABC
F11Phase Rotation Error, not CBA
F12Low Line Frequency
F13High Line Frequency
F14Input power not single phase
F15Input power not three phase
F21Low Line L1-L2
F22Low Line L2-L3
F23Low Line L3-L1
F24High Line L1-L2
F25High Line L2-L3
F26High Line L3-L1
F27Phase Loss
F28No Line
F29PORT Timeout
F30I.O.C. (Instantaneous Over current)
F31Overcurrent
F34Undercurrent
F35Power Factor Leading
F36Power Factor Lagging
F37Current Imbalance
F38Ground Fault
F39No Current at Run
F40Shorted / Open SCR
F41Current at Stop
F46Disconnect Fault (Disconnect Open)
F47Stack Protection Fault (stack thermal overload)
F48Bypass/2M Contactor Fault
F49Inline Contactor Fault
F50Control Power Low
F51Current Sensor Offset Error
F53Tachometer Signal Loss
F54BIST Fault
F55BIST CT Fault
F56RTD Open or Shorted
F60External Fault on DI 1 Input
F61External Fault on DI 2 Input
F62External Fault on DI 3 Input
F63External Fault on DI 4 Input
F64External Fault on DI 5 Input
F65External Fault on DI 6 Input
F66External Fault on DI 7 Input
F67External Fault on DI 8 Input
F71Analog Input Level Fault Trip
F80RTD Module Communication Fault
F81Keypad Communication Fault
F82Modbus Timeout Fault
F84MX to I/O Card Communication Fault (Interboard fault)
F85I/O Card Software version Fault
F86I/O Card Current Offset Error
F87I/O Card Error (real time clock)
F88I/O Card Error (internal CPU)
F89I/O Card Software Watchdog
F90I/O Card Error (internal CPU)
F91I/O Card Program EPROM Checksum
F94CPU Error, SW Fault
F95CPU Error, Parameter EEPROM Checksum Fault
F96CPU Error
F97CPU Error, SW Watchdog Fault
F98CPU Error
F99CPU Error, Program EPROM Checksum Fault

Each code: causes and first checks

F01: UTS Time Limit Expired

Hits OEE: Availability

What it means: The motor did not reach full speed before the up to speed (UTS) timer ran out, so the starter tripped during the start.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. MX2 parameters carry LED numbers as well, for example P9/QST09 for the UTS timer.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Jammed or overloaded motor or driven machine
  • Kick time plus acceleration ramp time longer than the UTS timer
  • Acceleration ramp settings too low to give the motor enough starting torque
  • UTS timer set too short for the load

First checks, in this order

  1. Check the motor and driven load for a jam or overload.
  2. Make sure kick time (CFN12 on MX3, P14/CFN11 on MX2) plus ramp time (QST08) is shorter than the UTS timer (QST09).
  3. Raise the acceleration ramp settings so the motor gets more torque during the start.
  4. If the load allows it, lengthen the UTS timer (QST09).

F02: Motor Thermal Overload Trip (Motor OL)

Hits OEE: Availability

What it means: The electronic motor overload model reached 100% thermal content and tripped the starter to protect the motor.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. Alarm A02 (Motor Overload Alarm) warns first when thermal content reaches the alarm level. On the MX2 LED display this fault shows as F OL. Emergency overload reset: press RESET and DOWN together (sets overload content to 0).

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Mechanical failure, jam or overload on the motor
  • Wrong motor overload settings or service factor
  • Wrong motor FLA or CT ratio setting
  • Poor input power quality or heavy line distortion
  • Power factor capacitors installed after the CTs

First checks, in this order

  1. Check the motor for mechanical failure, a jam or overload.
  2. Check the overload settings (QST03 and PFN28 to PFN35 on MX3, P44 to P47 on MX2) and service factor (QST02).
  3. Confirm motor FLA (QST01) and CT ratio (FUN03).
  4. If it trips while starting, review the acceleration ramp.
  5. Check that power factor capacitors, if fitted, are ahead of the CTs (MX3 manual).
  6. The overload resets only when thermal content drops below the lockout level (PFN34 on MX3).

F03: Slow Speed Time Limit Expired

Hits OEE: Availability

What it means: The starter stayed in slow speed operation longer than the slow speed time limit allows.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • Slow speed run kept on longer than the set limit
  • Slow Speed Time Limit set too short for the job

First checks, in this order

  1. Increase the Slow Speed Time Limit (CFN25 on MX3, P29/CFN23 on MX2) if the process needs longer slow speed running.

F04: Speed Switch Time Limit Expired

Hits OEE: Availability

What it means: The zero speed (speed switch) input did not confirm rotation within the Speed Switch Trip Time, which the starter treats as a stalled motor.[1][3][4]

Also on: Starters: RediStart MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX3 only (not listed in the MX2 manual).

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Motor stalled or accelerating too slowly
  • Speed Switch Trip Time set too short
  • Speed switch or its wiring faulty

First checks, in this order

  1. Increase the Speed Switch Trip Time (PFN26).
  2. Make the motor accelerate faster (review ramp settings).
  3. Check the speed switch and its wiring to the digital input.

F05: Motor PTC Overtemperature

Hits OEE: Availability

What it means: The motor PTC thermistor input reports that the motor windings are too hot.[1][3][4]

Also on: Starters: RediStart MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX3 only (not listed in the MX2 manual). Alarm A05 (Motor PTC Alarm) shows before the fault trip time expires.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Motor overloaded
  • Motor cooling fan not working
  • Debris on the motor blocking cooling
  • High ambient temperature
  • Wrong PTC thermistor type

First checks, in this order

  1. Let the motor cool; this resets the PTC thermistors.
  2. Check the motor cooling fan and clean debris off the motor.
  3. Reduce the load and the ambient temperature.
  4. Verify the PTC thermistor specifications.

F06: Stator RTD Overtemperature

Hits OEE: Availability

What it means: An RTD assigned to the stator group reached its trip temperature.[1][3][4]

Also on: Starters: RediStart MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX3 only (not listed in the MX2 manual). Alarm A06 (Stator RTD Alarm) shows when the RTD reaches its alarm level. Needs the optional remote RTD module.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Motor overloaded
  • Motor cooling fan not working or motor dirty
  • High ambient temperature
  • Wrong RTD settings

First checks, in this order

  1. Let the motor cool.
  2. Check the motor cooling fan and clean debris off the motor.
  3. Reduce the load and the ambient temperature.
  4. Verify the stator RTD specifications and settings.

F07: Bearing RTD Overtemperature

Hits OEE: Availability

What it means: An RTD assigned to the bearing group reached its trip temperature.[1][3][4]

Also on: Starters: RediStart MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX3 only (not listed in the MX2 manual). Alarm A07 (Bearing RTD Alarm) warns first.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Worn bearings
  • Too much load on the bearings
  • High vibration
  • High ambient temperature

First checks, in this order

  1. Verify the bearing RTD specifications.
  2. Reduce the load on the bearings and check vibration.
  3. Replace the bearings if they are worn.
  4. Reduce the ambient temperature.

F08: Other RTD Overtemperature

Hits OEE: Availability

What it means: An RTD assigned to the other group reached its trip temperature.[1][3][4]

Also on: Starters: RediStart MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX3 only (not listed in the MX2 manual). Alarm A08 (Other RTD Alarm) warns first.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Load too high
  • High ambient temperature
  • Wrong RTD settings

First checks, in this order

  1. Verify the RTD specifications and settings.
  2. Reduce the load and the ambient temperature.

F10: Phase Rotation Error, not ABC

Hits OEE: Availability

What it means: The input phase rotation is not ABC while the Input Phase Sensitivity parameter is set to accept ABC only.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. Alarm A10 shows while stopped; the fault trips when a start is commanded.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Input phases wired in the wrong order
  • Input Phase Sensitivity parameter set wrong

First checks, in this order

  1. Check the phase rotation of the input power and correct the wiring if needed.
  2. Check the Input Phase Sensitivity parameter (FUN04, P77 on MX2 LED).

F11: Phase Rotation Error, not CBA

Hits OEE: Availability

What it means: The input phase rotation is not CBA while the Input Phase Sensitivity parameter is set to accept CBA only.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. Alarm A11 shows while stopped; the fault trips when a start is commanded.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Input phases wired in the wrong order
  • Input Phase Sensitivity parameter set wrong

First checks, in this order

  1. Check the phase rotation of the input power and correct the wiring if needed.
  2. Check the Input Phase Sensitivity parameter (FUN04, P77 on MX2 LED).

F12: Low Line Frequency

Hits OEE: Availability

What it means: The line frequency dropped below the low frequency trip point.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. Trip point: Under Freq Trip parameter (PFN15) on the MX3; fixed at 23 Hz on the MX2. Alarm A12 shows first.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Generator speed governor problem
  • Open fuses or open connections on the input
  • Poor line power quality or heavy distortion

First checks, in this order

  1. Measure the input line frequency.
  2. On a generator, check its speed governor.
  3. Check the input supply for open fuses or connections.

F13: High Line Frequency

Hits OEE: Availability

What it means: The line frequency rose above the high frequency trip point.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. Trip point: Over Freq Trip parameter (PFN14) on the MX3; fixed at 72 Hz on the MX2. Alarm A13 shows first.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Generator speed governor problem
  • Poor line power quality or heavy distortion

First checks, in this order

  1. Measure the input line frequency.
  2. On a generator, check its speed governor.

F14: Input power not single phase

Hits OEE: Availability

What it means: The starter is set up for single phase power but sees three phase power.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. Alarm A14 shows while stopped; the fault trips on a start command.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Three phase power connected to a starter set for single phase
  • Single phase supply on the wrong input terminals
  • SCR gate wires not connected properly

First checks, in this order

  1. Verify the input power is single phase.
  2. Check single phase power is on L1 and L3 (LV manuals; the MV MX3 manual says L1 and L2).
  3. Check the SCR gate wires at the control card.

F15: Input power not three phase

Hits OEE: Availability

What it means: The starter is set up for three phase power but sees single phase power.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. Alarm A15 shows while stopped; the fault trips on a start command.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • A missing input phase (open fuse, breaker or connection)
  • SCR gate wires not connected properly
  • On medium voltage starters, a voltage feedback wiring fault

First checks, in this order

  1. Verify the input power is three phase and correct the wiring.
  2. Check the SCR gate wires at the control card.
  3. On medium voltage systems, check the voltage feedback measurement wiring.

F21: Low Line L1-L2

Hits OEE: Availability

What it means: The L1-L2 voltage stayed below the undervoltage trip level for longer than the over/under voltage trip delay.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. Alarm A21 shows while stopped when low line voltage is seen.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Low supply voltage
  • Rated voltage parameter set wrong
  • Open fuse or loose connection on the input
  • On medium voltage starters, voltage measurement wiring fault

First checks, in this order

  1. Measure the actual input voltage.
  2. Check the Rated Voltage parameter (FUN05).
  3. Check the input supply for open fuses or connections.
  4. Check the undervoltage trip level and delay (PFN11 and PFN12 on MX3, P39 and P40 on MX2).

F22: Low Line L2-L3

Hits OEE: Availability

What it means: The L2-L3 voltage stayed below the undervoltage trip level for longer than the over/under voltage trip delay.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. Alarm A22 shows while stopped when low line voltage is seen.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Low supply voltage
  • Rated voltage parameter set wrong
  • Open fuse or loose connection on the input
  • On medium voltage starters, voltage feedback wiring fault

First checks, in this order

  1. Measure the actual input voltage.
  2. Check the Rated Voltage parameter (FUN05).
  3. Check the input supply for open fuses or connections.

F23: Low Line L3-L1

Hits OEE: Availability

What it means: The L3-L1 voltage stayed below the undervoltage trip level for longer than the over/under voltage trip delay.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. Alarm A23 shows while stopped when low line voltage is seen.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Low supply voltage
  • Rated voltage parameter set wrong
  • Open fuse or loose connection on the input
  • On medium voltage starters, voltage feedback wiring fault

First checks, in this order

  1. Measure the actual input voltage.
  2. Check the Rated Voltage parameter (FUN05).
  3. Check the input supply for open fuses or connections.

F24: High Line L1-L2

Hits OEE: Availability

What it means: The L1-L2 voltage stayed above the overvoltage trip level for longer than the over/under voltage trip delay.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. Alarm A24 shows while stopped when high line voltage is seen.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • High supply voltage
  • Rated voltage parameter set wrong
  • Poor line power quality or heavy distortion

First checks, in this order

  1. Measure the actual input voltage.
  2. Check the Rated Voltage parameter (FUN05).
  3. Check the overvoltage trip level (PFN10 on MX3, PFN07 on MX2).

F25: High Line L2-L3

Hits OEE: Availability

What it means: The L2-L3 voltage stayed above the overvoltage trip level for longer than the over/under voltage trip delay.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. Alarm A25 shows while stopped when high line voltage is seen.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • High supply voltage
  • Rated voltage parameter set wrong
  • Poor line power quality or heavy distortion

First checks, in this order

  1. Measure the actual input voltage.
  2. Check the Rated Voltage parameter (FUN05).

F26: High Line L3-L1

Hits OEE: Availability

What it means: The L3-L1 voltage stayed above the overvoltage trip level for longer than the over/under voltage trip delay.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. Alarm A26 shows while stopped when high line voltage is seen.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • High supply voltage
  • Rated voltage parameter set wrong
  • Poor line power quality or heavy distortion

First checks, in this order

  1. Measure the actual input voltage.
  2. Check the Rated Voltage parameter (FUN05).

F27: Phase Loss

Hits OEE: Availability

What it means: While running, the starter lost one or more input or output phases; short line power dropouts can also cause it.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. Alarm A27 shows while running until the fault delay expires.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Open input fuse
  • Open or intermittent supply wiring
  • Open or intermittent motor wiring
  • Loose gate and cathode connections at the control card
  • On medium voltage starters, voltage feedback wiring fault

First checks, in this order

  1. Check the input fuses.
  2. Check the supply and motor wiring for open or intermittent connections.
  3. Check the gate and cathode connections to the control card.
  4. On medium voltage systems, check the voltage feedback measurement wiring.

F28: No Line

Hits OEE: Availability

What it means: A start was commanded but no input voltage was seen for longer than the inline configuration delay.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. Alarm A28 relates to no line being detected when the starter needs to sync. On the MX2 LED display a no line alarm shows as noL.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Open disconnect, fuse or circuit breaker
  • Inline contactor slow to close or not closing
  • Disconnected input wiring
  • SCR gate wires not connected properly

First checks, in this order

  1. Check the input supply for open disconnects, fuses, breakers or loose wiring.
  2. If an inline contactor is used, give it enough time to close with the Inline Configuration delay (I/O24 on MX3, I/O16 on MX2).
  3. Check the SCR gate wires at the control card.
  4. On medium voltage systems, check the voltage feedback wiring.

F29: PORT Timeout

Hits OEE: Availability

What it means: In Power Outage Ride Through (PORT) mode, line power did not come back before the PORT fault timer ran out.[1][3][4]

Also on: Starters: RediStart MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX3 only (not listed in the MX2 manual). Alarm A29 shows while the starter waits for line power to return.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Supply outage longer than the PORT time
  • PORT fault time set too short

First checks, in this order

  1. Restore the line power.
  2. Extend the PORT fault time (FUN10) if the application allows it.

F30: I.O.C. (Instantaneous Over current)

Hits OEE: Availability

What it means: During operation the starter saw a very high current in one or more phases and tripped at once.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. On the MX2 LED display this fault shows as ioc. A relay set to shunt trip operates on this fault.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: yes; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • Short circuit or ground fault in the motor wiring
  • Short circuit or ground fault inside the motor
  • Power factor or surge capacitors on the motor side of the starter
  • Wrong motor FLA or CT ratio setting

First checks, in this order

  1. Check the motor wiring and the motor for short circuits or ground faults.
  2. Check for power factor or surge capacitors on the motor side.
  3. Confirm motor FLA (QST01) and CT ratio (FUN03).

F31: Overcurrent

Hits OEE: Availability

What it means: Motor current stayed above the Over Current Trip Level for longer than the Over Current Trip Delay Time.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. Alarm A31 shows while running until the delay expires.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Jammed motor or load
  • Motor overloaded

First checks, in this order

  1. Check the motor and load for a jam or overload.
  2. Check the trip level and delay (PFN01 and PFN02; P32 and P33 on MX2).

F34: Undercurrent

Hits OEE: Availability

What it means: Motor current stayed below the Under Current Trip Level for longer than the Under Current Trip Delay time.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. Alarm A34 shows while running until the delay expires.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Load lost (for example a broken belt or coupling, or a pump running dry)
  • Trip level set too high for the normal load

First checks, in this order

  1. Find out why the load dropped.
  2. Check the trip level and delay (PFN03 and PFN04; P26 and P27 on MX2).

F35: Power Factor Leading

Hits OEE: Availability

What it means: The motor power factor went above the leading trip level.[1][3][4]

Also on: Starters: RediStart MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX3 only (not listed in the MX2 manual). Alarm A35 shows while running until the delay expires.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Light motor loading
  • On synchronous motors, field supply current problem

First checks, in this order

  1. Check the motor loading.
  2. On synchronous motors, check the field supply current.

F36: Power Factor Lagging

Hits OEE: Availability

What it means: The motor power factor went below the lagging trip level.[1][3][4]

Also on: Starters: RediStart MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX3 only (not listed in the MX2 manual). Alarm A36 shows while running until the delay expires.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Motor loading outside the normal range
  • On synchronous motors, field supply current problem

First checks, in this order

  1. Check the motor loading.
  2. On synchronous motors, check the field supply current.

F37: Current Imbalance

Hits OEE: Availability

What it means: The current imbalance between phases stayed above the Current Imbalance Trip Level for longer than the allowed time.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. Delay: PFN06 on the MX3; fixed at 10 seconds on the MX2. Alarm A37 shows first.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Motor wiring fault, including wrong wiring on dual voltage or 6 lead motors
  • Large input voltage imbalance
  • Internal motor problem

First checks, in this order

  1. Check the motor wiring, including dual voltage and 6 lead connection.
  2. Check for a large input voltage imbalance.
  3. Check the motor for internal problems.

F38: Ground Fault

Hits OEE: Availability

What it means: Ground current stayed above the Ground Fault Trip level for longer than the delay.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. Delay: PFN09 on the MX3; fixed at 3 seconds on the MX2. Alarm A38 shows first. A relay set to shunt trip operates on this fault.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: yes; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Ground fault in the motor wiring or in the motor
  • Wrong motor FLA or CT ratio setting
  • CTs fitted the wrong way round
  • In single phase use, wrong CT count, direction or inputs

First checks, in this order

  1. Check the motor wiring and motor for ground faults.
  2. Megger the motor and cables with them disconnected from the starter.
  3. Confirm motor FLA (QST01) and CT ratio (FUN03).
  4. Check that the white dots on all CTs face the input line.
  5. For single phase, use only two CTs on the L1 and L3 CT inputs.

F39: No Current at Run

Hits OEE: Availability

What it means: While the starter was running, motor current fell below 10% of FLA.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Motor disconnected or load removed
  • CT wiring fault
  • Wrong motor FLA or CT ratio setting
  • Motor driven by the load (regeneration)
  • Loose gate and cathode connections
  • An inline contactor or disconnect opened

First checks, in this order

  1. Check the motor connections and CT wiring to the control card.
  2. Confirm motor FLA (QST01) and CT ratio (FUN03).
  3. Check that the load is still connected.
  4. Check the gate and cathode connections.
  5. Check any inline contactor or disconnect.

F40: Shorted / Open SCR

Hits OEE: Availability

What it means: The starter detected a shorted or open SCR (thyristor) in the power section.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. A relay set to shunt trip operates on this fault. The SCR resistance and voltage tests are in manual section 8.5.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: yes; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • Loose or wrong SCR gate lead wiring
  • Failed (shorted) SCR
  • Input Phase Sensitivity or Starter Type parameter set wrong
  • Motor wiring fault, for example on a dual voltage motor

First checks, in this order

  1. Check all SCR gate leads at the SCRs and at the control card.
  2. Check each SCR with an ohmmeter for shorts (power off: over 50k ohms L to T, 8 to 50 ohms gate to gate).
  3. Check the Input Phase Sensitivity (FUN04) and Starter Type (FUN07) parameters.
  4. Check the motor wiring.

F41: Current at Stop

Hits OEE: Availability

What it means: Motor current was detected while the starter was not running.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. A relay set to shunt trip operates on this fault.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: yes; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • Shorted SCR
  • Bypass contactor stuck closed
  • Wrong motor FLA or CT ratio setting

First checks, in this order

  1. Check the starter for shorted SCRs.
  2. Check that the bypass contactor, if fitted, opens when the starter stops.
  3. Confirm motor FLA (QST01) and CT ratio (FUN03).

F46: Disconnect Fault (Disconnect Open)

Hits OEE: Availability

What it means: A start was commanded but the disconnect feedback signal on the digital input was not present.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: yes; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • Disconnect open
  • Disconnect feedback wiring fault
  • Faulty disconnect auxiliary contact

First checks, in this order

  1. Check the disconnect feedback wiring.
  2. Check that the disconnect is not faulty.

F47: Stack Protection Fault (stack thermal overload)

Hits OEE: Availability

What it means: The electronic overload protection for the SCR power stack detected an overload.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. MX3 Appendix C lists it as Stack Overtemperature / P.S Failure. MX3 alarm A47 (Stack Overload Alarm) shows when stack thermal content passes 105%. The MX2 LED shows L Ot during a power stack thermal lockout.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Motor jammed or overloaded
  • Wrong CT ratio setting (and burden switch on the MX2)
  • Motor load bigger than the power stack rating

First checks, in this order

  1. Check the motor for a jam or overload.
  2. Verify the CT ratio (FUN03) and, on the MX2, the burden switch settings.
  3. If the motor load exceeds the stack rating, consult Benshaw.

F48: Bypass/2M Contactor Fault

Hits OEE: Availability

What it means: The bypass (or 2M) contactor feedback did not match what the starter commanded for longer than the Bypass Confirm time.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. The standard BIST test (FUN22 on MX3) cycles the UTS relay and checks bypass feedback; a mismatch there also gives a Bypass/2M fault.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • Bypass/2M contactor coil or feedback wiring fault
  • Relay driving the bypass contactor not programmed as UTS
  • No supply to the bypass/2M contactor
  • Digital input not programmed as Bypass/2M Contactor Feedback
  • Damaged or faulty bypass contactor

First checks, in this order

  1. Check the bypass/2M contactor coil and feedback wiring.
  2. Check that the relay connected to the bypass contactor is programmed as the UTS function (I/O10 to I/O15 on MX3).
  3. Check that the bypass/2M contactor power supply is present (J4 on MX3).
  4. Check the Digital Input Configuration parameters (I/O01 to I/O08 on MX3).
  5. Check the Bypass Confirm time (I/O25 on MX3, P64/I/O17 on MX2).
  6. Check the bypass contactor for damage.

F49: Inline Contactor Fault

Hits OEE: Availability

What it means: The inline (isolation) contactor did not close, or its feedback did not confirm it.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • Fault in the wiring to the contactor coil
  • Feedback wiring from the auxiliary contact fault
  • Digital input not programmed for inline feedback
  • Damaged inline contactor

First checks, in this order

  1. Check the wiring to the contactor coil.
  2. Check the feedback wiring from the auxiliary contact to the digital input.
  3. Check the in-line fault delay (I/O24 on MX3).
  4. Check the contactor for damage.

F50: Control Power Low

Hits OEE: Availability

What it means: Control power dropped below 90 V while the starter was running.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. The MX2 LED shows L CP during a low control power lockout.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Line voltage dip during starting pulling down control power
  • Wrong control power transformer tap
  • Blown control power transformer fuse
  • Wiring fault between control power source and starter

First checks, in this order

  1. Measure the control power level, especially during starting.
  2. Check the control power transformer tap and fuses.
  3. Check the wiring from the control power source.

F51: Current Sensor Offset Error

Hits OEE: Availability

What it means: The control card self test found a problem with one or more current sensor inputs.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: yes; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • Current flowing through a CT while the starter is stopped
  • Wrong motor FLA, CT ratio or burden switch setting
  • Control card fault

First checks, in this order

  1. Confirm motor FLA (QST01) and CT ratio (FUN03), plus the burden switch on the MX2.
  2. Check that no current flows through the CTs when the starter is not running.
  3. Consult Benshaw if it persists.

F53: Tachometer Signal Loss

Hits OEE: Availability

What it means: No tachometer signal was detected during the start or while running.[1][3][4]

Also on: Starters: RediStart MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX3 only (not listed in the MX2 manual). Alarm A53 shows until a valid tach signal returns or the delay expires.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • Tachometer wiring fault or low signal
  • Tach Full Speed Voltage setting wrong
  • Tach loss time too short for the motor to start turning
  • Initial current too low to start the motor turning

First checks, in this order

  1. Check the tachometer wiring and signal level.
  2. Check the tachometer Full Speed Voltage (FUN13).
  3. Extend the Tachometer Loss Time (FUN14).
  4. Increase the initial current so the motor turns right after the start command.

F54: BIST Fault

Hits OEE: Availability

What it means: The built in self test (BIST) was cancelled because the conditions for the test were not met.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • Disconnect closed during the standard (no line voltage) BIST
  • Line voltage or phase current detected during the standard BIST
  • Disconnect opened or line voltage lost during the powered BIST

First checks, in this order

  1. For the standard BIST, remove line power from the starter input and open the disconnect.
  2. For the powered BIST, keep the disconnect closed and line voltage present for the whole test.

F55: BIST CT Fault

Hits OEE: Availability

What it means: During the powered BIST the starter found a CT on the wrong phase or a CT with reversed polarity.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • CTs swapped between phases
  • CT installed backwards

First checks, in this order

  1. Check CT positions: CT1 on L1, CT2 on L2, CT3 on L3.
  2. Check that the polarity dot on each CT faces the supply line.

F56: RTD Open or Shorted

Hits OEE: Availability

What it means: An RTD input reads open or shorted.[1][3][4]

Also on: Starters: RediStart MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX3 only (not listed in the MX2 manual). Needs the optional remote RTD module.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • Broken or shorted RTD
  • RTD wiring fault

First checks, in this order

  1. Check the condition and wiring of the RTD.

F60: External Fault on DI 1 Input

Hits OEE: Availability

What it means: Digital input 1 is programmed as a fault input and it is signalling a fault.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. Alarm A60 shows while the input is in the fault state but the fault timer has not expired.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • The external device wired to DI 1 (for example a pressure or level switch) has tripped
  • DI 1 configured as a fault input by mistake
  • Wiring or signal level fault on the input

First checks, in this order

  1. Check the external device and wiring on DI 1.
  2. Check the digital input configuration (I/O01; P48 on MX2 LED).
  3. On MX3, check the Digital Fault Input Trip Time (I/O09).

F61: External Fault on DI 2 Input

Hits OEE: Availability

What it means: Digital input 2 is programmed as a fault input and it is signalling a fault.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. Alarm A61 shows first.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • The external device wired to DI 2 has tripped
  • DI 2 configured as a fault input by mistake
  • Wiring or signal level fault on the input

First checks, in this order

  1. Check the external device and wiring on DI 2.
  2. Check the digital input configuration (I/O02; P49 on MX2 LED).

F62: External Fault on DI 3 Input

Hits OEE: Availability

What it means: Digital input 3 is programmed as a fault input and it is signalling a fault.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. Alarm A62 shows first.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • The external device wired to DI 3 has tripped
  • DI 3 configured as a fault input by mistake
  • Wiring or signal level fault on the input

First checks, in this order

  1. Check the external device and wiring on DI 3.
  2. Check the digital input configuration (I/O03; P50 on MX2 LED).

F63: External Fault on DI 4 Input

Hits OEE: Availability

What it means: Digital input 4 is programmed as a fault input and it is signalling a fault.[1][3][4]

Also on: Starters: RediStart MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX3 only (not listed in the MX2 manual). Alarm A63 shows first. Inputs 4 to 8 are on the MX3 I/O card.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • The external device wired to DI 4 has tripped
  • Input configured as a fault input by mistake
  • Wiring fault

First checks, in this order

  1. Check the external device and wiring on DI 4.
  2. Check the digital input configuration (I/O04) and the Digital Fault Input Trip Time (I/O09).

F64: External Fault on DI 5 Input

Hits OEE: Availability

What it means: Digital input 5 is programmed as a fault input and it is signalling a fault.[1][3][4]

Also on: Starters: RediStart MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX3 only (not listed in the MX2 manual). Alarm A64 shows first.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • The external device wired to DI 5 has tripped
  • Input configured as a fault input by mistake
  • Wiring fault

First checks, in this order

  1. Check the external device and wiring on DI 5.
  2. Check the digital input configuration (I/O05) and I/O09.

F65: External Fault on DI 6 Input

Hits OEE: Availability

What it means: Digital input 6 is programmed as a fault input and it is signalling a fault.[1][3][4]

Also on: Starters: RediStart MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX3 only (not listed in the MX2 manual). Alarm A65 shows first.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • The external device wired to DI 6 has tripped
  • Input configured as a fault input by mistake
  • Wiring fault

First checks, in this order

  1. Check the external device and wiring on DI 6.
  2. Check the digital input configuration (I/O06) and I/O09.

F66: External Fault on DI 7 Input

Hits OEE: Availability

What it means: Digital input 7 is programmed as a fault input and it is signalling a fault.[1][3][4]

Also on: Starters: RediStart MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX3 only (not listed in the MX2 manual). Alarm A66 shows first.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • The external device wired to DI 7 has tripped
  • Input configured as a fault input by mistake
  • Wiring fault

First checks, in this order

  1. Check the external device and wiring on DI 7.
  2. Check the digital input configuration (I/O07) and I/O09.

F67: External Fault on DI 8 Input

Hits OEE: Availability

What it means: Digital input 8 is programmed as a fault input and it is signalling a fault.[1][3][4]

Also on: Starters: RediStart MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX3 only (not listed in the MX2 manual). Alarm A67 shows first.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • The external device wired to DI 8 has tripped
  • Input configured as a fault input by mistake
  • Wiring fault or a trip time that is too short

First checks, in this order

  1. Check the external device and wiring on DI 8.
  2. Check the digital input configuration (I/O08).
  3. Benshaw suggests increasing the Digital Fault Input Trip Time (I/O09) if needed.

F71: Analog Input Level Fault Trip

Hits OEE: Availability

What it means: The analog input went above or below the Analog Input Trip Level for longer than the Analog Input Trip Delay.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3. Alarm A71 shows first. MX3 Appendix C calls it Analog Input #1 Level Fault Trip.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Process signal really out of range
  • Analog input parameters set wrong
  • Voltage/current selector switch on the control card in the wrong position
  • Electrical noise or a ground loop on the analog input

First checks, in this order

  1. Measure the analog input to confirm the reading.
  2. Check all Analog Input parameters (I/O16 to I/O20 on MX3, P55 to P59 on MX2).
  3. Check the voltage/current switch (SW1-1 on MX3, SW1 on MX2).
  4. Check the grounding of the analog input wiring.

F80: RTD Module Communication Fault

Hits OEE: Availability

What it means: The starter lost communication with the remote RTD module(s).[1][3][4]

Also on: Starters: RediStart MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX3 only (not listed in the MX2 manual).

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • RS-485 wiring fault between the RTD module and the MX3
  • No 24 VDC supply to the RTD module
  • RTD module address does not match RTD01/RTD02

First checks, in this order

  1. Check the RS-485 wiring to the RTD module(s).
  2. Check the RTD module 24 VDC supply.
  3. Check the module address against parameters RTD01 and RTD02.

F81: Keypad Communication Fault

Hits OEE: Availability

What it means: The control card lost communication with the remote keypad.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • Remote keypad unplugged while the control card was powered
  • Damaged keypad cable or loose connectors
  • Electrical noise on the keypad cable
  • Display interface card loose (MX2)

First checks, in this order

  1. Check the keypad cable and that both connectors are firmly seated.
  2. Route the keypad cable away from high power and high noise wiring.
  3. Only connect or disconnect the remote keypad with control power off (MX2 manual).

F82: Modbus Timeout Fault

Hits OEE: Availability

What it means: The starter did not receive a valid serial (Modbus) message within the Communication Timeout time.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: yes (when Controlled Fault Stop Enable is On); shunt trip fault: no; auto reset allowed: yes. Reset with the RESET key once the cause is fixed.

Likely causes

  • Network wiring fault
  • Wrong communication parameters
  • Remote master (PLC or DCS) stopped polling

First checks, in this order

  1. Check the communication parameters (FUN16 to FUN19 on MX3, FUN10 to FUN13 on MX2).
  2. Check the wiring between the network and the control card.
  3. Check the remote system for the cause of the communication loss.

F84: MX to I/O Card Communication Fault (Interboard fault)

Hits OEE: Availability

What it means: Communication between the two MX3 cards (control card and I/O card) was lost.[1][3][4]

Also on: Starters: RediStart MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX3 only (not listed in the MX2 manual).

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • Cards not mounted together properly or hardware loose
  • Foreign matter between the boards
  • Card fault

First checks, in this order

  1. Check that both cards are mounted together and the mounting hardware is tight.
  2. Check for foreign matter between the boards.
  3. Consult Benshaw if it persists.

F85: I/O Card Software version Fault

Hits OEE: Availability

What it means: The application software version is not compatible with the bottom I/O card.[1][3][4]

Also on: Starters: RediStart MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX3 only (not listed in the MX2 manual).

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • Wrong software version loaded for this I/O card

First checks, in this order

  1. Verify the software version matches the I/O card in use.
  2. Consult Benshaw for the correct version.

F86: I/O Card Current Offset Error

Hits OEE: Availability

What it means: The I/O card self test found a problem with the zero sequence ground fault input.[1][3][4]

Also on: Starters: RediStart MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX3 only (not listed in the MX2 manual).

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • Zero sequence ground fault level turned on with no zero sequence CT connected
  • Current flowing through the zero sequence CT
  • I/O card fault

First checks, in this order

  1. If no zero sequence CT is connected, set ZS GF Lvl (PFN08) to Off.
  2. Check that no current flows through the zero sequence CT.
  3. Consult Benshaw if it persists.

F87: I/O Card Error (real time clock)

Hits OEE: Availability

What it means: The I/O card detected a problem with its real time clock.[1][3][4]

Also on: Starters: RediStart MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX3 only (not listed in the MX2 manual).

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • I/O card hardware fault

First checks, in this order

  1. Consult Benshaw.

F88: I/O Card Error (internal CPU)

Hits OEE: Availability

What it means: The I/O card detected an internal CPU problem.[1][3][4]

Also on: Starters: RediStart MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX3 only (not listed in the MX2 manual).

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • I/O card hardware fault

First checks, in this order

  1. Consult Benshaw.

F89: I/O Card Software Watchdog

Hits OEE: Availability

What it means: The I/O card detected an internal software problem.[1][3][4]

Also on: Starters: RediStart MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX3 only (not listed in the MX2 manual).

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • I/O card software or hardware fault

First checks, in this order

  1. Consult Benshaw.

F90: I/O Card Error (internal CPU)

Hits OEE: Availability

What it means: The I/O card detected an internal CPU problem.[1][3][4]

Also on: Starters: RediStart MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX3 only (not listed in the MX2 manual).

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • I/O card hardware fault

First checks, in this order

  1. Consult Benshaw.

F91: I/O Card Program EPROM Checksum

Hits OEE: Availability

What it means: The I/O card program memory check failed (an internal CPU problem).[1][3][4]

Also on: Starters: RediStart MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX3 only (not listed in the MX2 manual).

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • Corrupted I/O card program memory

First checks, in this order

  1. Consult Benshaw.

F94: CPU Error, SW Fault

Hits OEE: Availability

What it means: The control card is running software that does not match its hardware, or it found an internal software problem.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • Wrong software version for the control card
  • Internal software problem on the control card

First checks, in this order

  1. Verify the software version matches the control card.
  2. LV MX3 manual: replace the card set; MX2 and MV MX3 manuals: consult Benshaw.

F95: CPU Error, Parameter EEPROM Checksum Fault

Hits OEE: Availability

What it means: The stored parameter values are corrupted, which usually happens after the control is re-flashed with new software.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • Control re-flashed with new software
  • Parameter memory corrupted

First checks, in this order

  1. Do a factory parameter reset, then set all parameters again before running (MX3 lists FUN05, FUN03, I/O01 to 08, I/O10 to 15 as the minimum).
  2. If it comes back after the reset, replace the card (LV manuals) or consult Benshaw (MV MX3 manual).

F96: CPU Error

Hits OEE: Availability

What it means: The control card detected an internal CPU problem.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: yes; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • Control card hardware fault

First checks, in this order

  1. LV MX3 and MX2 manuals: replace the card (set); MV MX3 manual: consult Benshaw.

F97: CPU Error, SW Watchdog Fault

Hits OEE: Availability

What it means: The control card detected an internal software problem (watchdog).[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: yes; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • Control card software or hardware fault

First checks, in this order

  1. LV MX3 and MX2 manuals: replace the card (set); MV MX3 manual: consult Benshaw.

F98: CPU Error

Hits OEE: Availability

What it means: The control card detected an internal CPU problem.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • Control card hardware fault

First checks, in this order

  1. LV MX3 and MX2 manuals: replace the card (set); MV MX3 manual: consult Benshaw.

F99: CPU Error, Program EPROM Checksum Fault

Hits OEE: Availability

What it means: The control card program memory is corrupted.[1][2][3][4]

Also on: Starters: RediStart MX2 (RB2, RC2, RX2E) and MX3 (LV RB3, RC3, RX3E; MV MVRMX, MVRXE, MVRMX36). Families: MX2 and MX3.

Starter response: Fault: the starter trips and the STOP LED flashes. Controlled fault stop: no; shunt trip fault: no; auto reset allowed: no. Reset with the RESET key once the cause is fixed.

Likely causes

  • Corrupted program memory

First checks, in this order

  1. Control software must be reloaded into the control card before it can run again.
  2. LV manuals: replace the card (set); MV MX3 manual: consult Benshaw.

Log it, or the same alarm comes back

A starter fault stops the motor and the machine it drives, so in OEE terms it is a breakdown. Log the code, the machine and the minutes lost, every time, even when the starter resets itself.

  • Reason code: the code plus the machine, for example Benshaw MX3 F27, pump 3 starter, so a phase loss that comes back at every start shows up as a pattern.
  • Loss bucket: a stop that needs a reset, a part or a technician is an availability loss (breakdown). Stops shorter than your micro-stop threshold go to performance (minor stops). The six big losses page shows where each one belongs.
  • What to count: how often each code fires per week and the minutes it costs. Two numbers a week turn "that alarm comes up sometimes" into a ranked list. The MTBF and MTTR calculator and the downtime cost calculator do the math.

The free OEE tracker logs each stop with its reason and turns the week into a downtime Pareto, so the code that costs the most rises to the top.

fabrico.io compares soft starters and VFDs. A fault code tells you what the starter measured, not what happened at the machine in the seconds before. Fabrico's camera-based OEE software syncs line camera video with machine data, so you can replay the moment the line stopped next to the trip.

Frequently asked questions

What is Benshaw fault code 48?

On RediStart MX2 and MX3 soft starters, F48 is Bypass/2M Contactor Fault: the feedback from the bypass (or 2M) contactor did not match the command for longer than the Bypass Confirm time (I/O25 on MX3). Check the contactor coil and feedback wiring, that the relay driving it is programmed as UTS, that the contactor supply is present, that the feedback input is configured correctly, and that the contactor itself is not damaged. F48 can do a controlled fault stop but cannot auto reset; clear it with RESET after fixing the cause.

Where is the Benshaw fault codes list PDF?

Benshaw prints the full list in the RediStart user manuals on benshaw.com: section 8.4 Fault Code Table gives the cause and fixes for each code, and the appendix lists every code with whether it allows a controlled stop, shunt trip and auto reset. The LV MX3 manual (890034-02-02, RB3, RC3, RX3E) covers F01 to F99; the MX2 manual (890034-01-02, RB2, RC2, RX2E) covers a smaller set; the MV MX3 manuals use the same codes as the LV MX3.

How do I reset a fault on a Benshaw soft starter?

Fix the cause, then press RESET on the keypad. For a motor overload you can do an emergency overload reset with RESET and DOWN together, which clears the overload content. Faults marked auto reset allowed can reset themselves if Auto Fault Reset Time is set (PFN23 on MX3, P41 on MX2), but a new start command is still needed, and after the reset count limit the starter locks out until someone resets it by hand.

What does F01 UTS Time Limit Expired mean on a Benshaw starter?

The motor did not reach full speed before the up to speed timer (QST09) ran out. Look for a jammed or overloaded load, make sure kick time plus acceleration ramp time is shorter than the UTS timer, raise the ramp settings if the motor lacks starting torque, and only then consider a longer UTS time.

What causes a Benshaw F27 Phase Loss or F28 No Line fault?

F27 means one or more input or output phases were lost while running, often an open fuse, a loose supply or motor connection, a line dropout or loose gate and cathode wiring. F28 means no line voltage was seen when a start was commanded: check disconnects, fuses and breakers, give an inline contactor enough time to close (I/O24 on MX3), and check the SCR gate wires. On medium voltage starters also check the voltage feedback wiring.

What does F40 Shorted / Open SCR mean on a Benshaw RediStart?

The starter detected a shorted or open SCR. Check every SCR gate lead at the SCR and at the control card, test each SCR with an ohmmeter with power off (Benshaw expects over 50k ohms from L to T and 8 to 50 ohms between the gate leads), and check the Input Phase Sensitivity and Starter Type parameters and the motor wiring. It is a shunt trip fault and cannot auto reset.

Sources

Codes and meanings follow the manufacturer documentation below. Wording is ours, simplified for the shop floor; the manual for your exact model and software version wins if it differs.

  1. RediStart Solid State Starter Control User Manual, RB3, RC3, RX3E Models (MX3), publication 890034-02-02, February 2008, Benshaw Inc., hosted on benshaw.com
  2. RediStart Solid State Starter Control User Manual, RB2, RC2, RX2E Models (MX2), publication 890034-01-02, August 2008, Benshaw Inc., hosted on benshaw.com
  3. RediStart Solid State Starter User Manual, MVRMX and MVRXE Models, 1500 to 7200VAC (MX3), publication 890034-03-00, Benshaw Inc., hosted on benshaw.com (file dated 2020-05-07)
  4. RediStart Solid State Starter Control User Manual, MVRMX36 Models, 10KV to 13.8KVAC (MX3), publication 890034-06-00, Benshaw Inc., hosted on benshaw.com
  5. Benshaw Manuals and Product Specification Guides page, benshaw.com

See the moment the motor tripped

Fabrico, a light MES with computer vision, syncs camera footage with machine and timeline data, so you can replay the exact moment the line stopped and review the cause next to the starter's fault. Cameras also catch short stops and a line that is switched on but not producing, the losses nobody writes down. Machines connect through a PLC, a Fabrico IoT device or an AI camera.

Book a Fabrico demo
The lookup stays free.

Related: TECO VFD fault codes · electric motor · centrifugal pump · conveyor · how to track downtime

Other alarm code lookups: FANUC: servo amplifier · spindle amplifier | Siemens: MICROMASTER 440 · MASTERDRIVES · SINAMICS G120 · SINAMICS V90 servo · SINAMICS V20 · SINAMICS G110 | ABB: ACS550 drive · ACS800 drive · robot IRC5 · DCS800 DC drive | Okuma: OSP alarms | Haas: alarm lookup | Mitsubishi: MELSERVO servo · FR-D700 and FR-E700 inverters · FX PLC | Allen-Bradley: Kinetix and Ultra3000 · MicroLogix · PowerFlex 753 and 755 · PowerFlex 70 and 700 · 1336 and 1305 | Yaskawa: V1000 drive · SERVOPACK servo · Motoman robot | Delta: VFD drives · ASDA servo | Eaton: DC1 and SVX9000 drives | Control Techniques: Commander SK and M200 | Kollmorgen: AKD servo | Lenze: SMVector, 8200, 8400, i500 | Magnetek: IMPULSE and DSD 412 | Omron: MX2 and RX inverters · G5 and 1S servo · CP1 and CJ2 PLC | WEG: CFW500, CFW300, CFW11, CFW08 | Hitachi: WJ200 inverter · SJ700 and SJ-P1 | Toshiba: E3, Q9, P9, S15, nC3, AS3 | AutomationDirect: GS10, GS20, GS4, GS1 to GS3 | Festo: CMMT servo drives | Videojet: 1000 Line CIJ printers | Lincoln Electric: Power Wave welders | Fronius: TPS and TPS/i welders | Beckhoff: TwinCAT ADS, NC and BK1120 | Universal Robots: CB3 and e-Series cobots | Pilz: PNOZ safety relays | SICK: S3000, S300, microScan3 | SANYO DENKI: SANMOTION servo | Parker: SSD 590+, 690+, AC10 | KEB: COMBIVERT F5 | Epson: robot RC700, RC90 | B&R: ACOPOS servo | Schneider Electric: Lexium 32 servo | Bosch Rexroth: IndraDrive | Vacon: NX, VACON 100 and 20 | Fuji Electric: FRENIC-Mini, Multi, Ace, MEGA | LS Electric: S100, G100, iG5A | Panasonic: MINAS A6 and A5 servo | Invertek: Optidrive E3, P2, Eco | SEW-Eurodrive: MOVITRAC B and MOVIDRIVE B | HEIDENHAIN: iTNC 530 and TNC | NORD: NORDAC SK 200E and SK 500E | Baldor: Series 15H and 18H drives | Atlas Copco: Elektronikon compressors and VSD | Inovance: MD290, MD200, MD500, MD310 | INVT: Goodrive GD20, GD200A, GD350 | TECO: A510, F510, E510, L510s | Hyundai: N700E, N700, N300 inverters | Ingersoll Rand: Intellisys compressors | Miller: Welders

Related tools: full troubleshooting directory · OEE calculator · downtime cost · MTBF / MTTR · glossary

OEE essentials: OEE calculator · What is OEE · How to improve OEE · Six big losses · Availability · TEEP · Cost of downtime · OEE benchmark · Free OEE tracker · Free OEE software · How to track downtime · How to implement OEE · Light MES vs full MES