Toshiba H9 Fault Codes List
Troubleshoot your Toshiba H9 HVAC drive with our updated fault code guide. Learn to interpret OC, OL, and EPH trips, view the LCD trip history, and reset faults.
Toshiba H9 Fault Codes Reference Table
Below is the complete list of trip codes and alarms. Please refer to this table to match the code on your LCD display with the specific hardware or parameter issue.
H9 ASD Faults, Alarms, and Notification Codes
| Fault Code and Meaning | Cause and Remedy |
|---|---|
| Atn Autotune active |
Cause: Atn indicates that the Autotune function is active. Remedy:
|
| dbOn DC Braking |
Cause: This code conveys the DC Injection function being carried out. Remedy:
|
| CM1 Comm1 Error |
Cause: Internal communications error. Remedy:
|
| CM2 Comm2 Error |
Cause: External communications error. Remedy:
|
| E Emergency Off |
Cause: Output signal from the ASD is terminated and a brake may be applied if so configured. Remedy:
|
| MOFF Main Under-Voltage |
Cause: Under-voltage condition at the 3-phase AC input to the ASD. Remedy:
|
| OC Over-Current |
Cause: ASD output current greater than F601 setting. Remedy:
|
| OH Overheat |
Cause: ASD ambient temperature excessive. Remedy:
|
| OJ Timer |
Cause: Run-time counter exceeded. Remedy:
|
| OLI ASD Overload |
Cause: Load requirement in excess of the capability of the ASD. Remedy:
|
| OLM Motor Overload |
Cause: Load requirement in excess of the capability of the motor. Remedy:
|
| OLR Resistor Overload |
Cause: Excessive current at the Dynamic Braking Resistor. Remedy:
|
| OP Over-Voltage |
Cause: DC bus voltage exceeds specifications. Remedy:
|
| OT Over-Torque |
Cause: Torque requirement is in excess of the setting of F616 or F617 for a time longer than the setting of F618. Remedy:
|
| POFF Control Under-Voltage |
Cause: Under-voltage condition at the 5, 15, or the 24 VDC supply. Remedy:
|
| PtSt Reference Point |
Cause: Two speed-reference frequency setpoint values are too close to each other. Remedy:
|
| UC Under-Current |
Cause: Output current of the ASD is below the level defined at F611 and remains there for a time longer than the setting of F612. Remedy:
|
| E-10 Sink/Source Setting Error |
Cause: Sink/Source configuration is incorrect. Remedy:
|
| E-11 Brake Sequence Response Error |
Cause: Braking sequence error. Remedy:
|
| E-12 Encoder Signal-Loss Error |
Cause: ASD is configured to receive a signal from a shaft-mounted encoder and no signal is being received while running. Remedy:
|
| E-13 Speed Error |
Cause: Result of a motor speed that is greater than the commanded speed when using an encoder for speed control. Remedy:
|
| E-17 Key Failure |
Cause: Key failure detected. Remedy:
|
| E-18 Analog (Terminal) Input Loss |
Cause: V/I signal loss. Remedy:
|
| E-19 CPU Communication Error |
Cause: CPU data Transmit/Receive error. Remedy:
|
| E-20 V/f Control Error |
Cause: Torque processing error. Remedy:
|
| E-21 CPU Processing Error |
Cause: Software processed incorrectly. Remedy:
|
| E-22 Logic Input Voltage Error |
Cause: Incorrect voltage applied to the discrete input terminals. Remedy:
|
| E-23 Optional Expansion Input Terminal Board 1 Error |
Cause: Optional Expansion Input Terminal Board 1 is defective. Remedy:
|
| E-24 Optional Expansion Input Terminal Board 2 Error |
Cause: Optional Expansion Input Terminal Board 2 is defective. Remedy:
|
| E-25 Stop Positioning Retention Error |
Cause: Load movement while stopped. Remedy:
|
| E-26 CPU2 Fault |
Cause: CPU malfunction. Remedy:
|
| E-50 / E-51 Sink/Source Setting Error |
Cause: Sink/Source configuration is incorrect. Remedy:
|
| EEP1 EEPROM Fault |
Cause: EEPROM write malfunction. Remedy:
|
| EEP2 / EEP3 EEPROM Read Error |
Cause: EEPROM read malfunction. Remedy:
|
| EF1 / EF2 (Earth) Ground Fault |
Cause: Ground fault at output. Remedy:
|
| EPHI Input Phase Failure |
Cause: 3-phase input to the ASD is low or missing at the R, S, or T input terminals. Remedy:
|
| EPHO Output Phase Failure |
Cause: 3-phase output from the ASD is low or missing at the U, V, or W output terminals or at the input to the motor. Remedy:
|
| ERR2 RAM Fault |
Cause: Internal RAM malfunction. Remedy:
|
| ERR3 ROM Fault |
Cause: Internal ROM malfunction. Remedy:
|
| ERR4 CPU Fault |
Cause: CPU malfunction. Remedy:
|
| ERR5 Communication Error |
Cause: Communication time out error or malfunction. Remedy:
|
| ERR6 Gate Array Fault |
Cause: Main Gate Array is defective. Remedy:
|
| ERR7 Low-Current |
Cause: Improper Low-Current detection level settings. Remedy:
|
| ERR8 Option Device Fault |
Cause: Option device error. Remedy:
|
| ERR9 Flash Memory Fault |
Cause: Flash memory malfunction. Remedy:
|
| ETN Autotune Error |
Cause: Autotune readings that are significantly inconsistent with the configuration information. Remedy:
|
| ETN1 Autotune Error 1 |
Cause: Autotune adjustment required. Remedy:
|
| ETN2 Autotune Error 2 |
Cause: Autotune adjustment required. Remedy:
|
| ETN3 Autotune Error 3 |
Cause: Problem with Motor Constant readings. Remedy:
|
| ETYP Typeform Error |
Cause: Firmware information (typeform) loaded into the Gate Driver board is inconsistent with the device. Remedy:
|
| None No Errors |
Cause: No active faults. Remedy:
|
| OC1 Over-Current During Acceleration |
Cause: Over-Current condition during startup/acceleration. Remedy:
|
| OC1P Overheat During Acceleration |
Cause: Overheating detected during acceleration. Remedy:
|
| OC2 Over-Current During Deceleration |
Cause: Over-Current condition during deceleration. Remedy:
|
| OC2P Overheat During Deceleration |
Cause: Overheating detected during deceleration. Remedy:
|
| OC3 Over-Current During Run |
Cause: Over-Current condition during constant speed run. Remedy:
|
| OC3P Overheat During Run |
Cause: Overheating detected during run. Remedy:
|
| OCA1 / OCL U-Phase Over-Current |
Cause: Low impedance at the U lead of the ASD output. Remedy:
|
| OCA2 / OCL V-Phase Over-Current |
Cause: Low impedance at the V lead of the ASD output. Remedy:
|
| OCA3 / OCL W-Phase Over-Current |
Cause: Low impedance at the W lead of the ASD output. Remedy:
|
| OCR Dynamic Braking Resistor Over-Current |
Cause: ASD inability to discharge the bus voltage during regeneration. Remedy:
|
| OH2 External Overheat |
Cause: Excessive-heat signature received at the TB3 terminals. Remedy:
|
| OL1 ASD Overload |
Cause: ASD Overload detected. Remedy:
|
| OL2 Motor Overload |
Cause: Motor Overload detected. Remedy:
|
| OLR Dynamic Braking Resistor Overload |
Cause: Resistor Overload detected. Remedy:
|
| OP1 Over-Voltage During Acceleration |
Cause: Motor running during restart. Remedy:
|
| OP2 Over-Voltage During Deceleration |
Cause: Over-Voltage detected during deceleration. Remedy:
|
| OP3 Over-Voltage During Run |
Cause: Over-Voltage detected during run. Remedy:
|
| OT Over-Torque |
Cause: Torque requirement by the load is in excess of the setting of F616 or F617 for a time longer than the setting of F618. Remedy:
|
| SOUT Step-Out (for PM Motor Only) |
Cause: Step-Out condition detected. Remedy:
|
| UP1 Main Power Under-Voltage |
Cause: Input 3-phase voltage is too low. Remedy:
|
| UP2 Control Power Under-Voltage |
Cause: Under-voltage condition at the 5, 15, or the 24 VDC supply. Remedy:
|
How to Read H9 Faults via LCD Keypad (EOI)
The H9’s Electronic Operator Interface (EOI) is designed for facility managers and HVAC technicians. In 2026, you can access deep diagnostic data directly from the wall-mounted keypad without needing a laptop:
- Trip History: The H9 records the last 4 faults. Press the MON (Monitor) button and scroll down to “Trip History.” This will show you the chronological order of failures.
- Status at Trip: By selecting a specific past trip and pressing ENT (Enter), you can view the “At-Trip” data. This includes the output frequency, current, and voltage at the exact moment the drive tripped—crucial for diagnosing if a pump was ramping up or running steady.
- Terminal Status: You can view the status of the input terminals (RES, S1, S2, etc.) to see if an external safety interlock, such as a “Fireman’s Override” or “Freeze Stat,” triggered the shutdown.
General Troubleshooting Steps
Before resetting an HVAC drive, ensure you check the mechanical systems:
- Overcurrent (OC1/OC2/OC3): Short circuit or ground fault. For HVAC, check for water intrusion in the motor conduit or a locked rotor on a pump. Perform a megger test if the fault persists.
- Overload (OL1/OL2): OL1 is Motor Overload; OL2 is Drive Overload. Check for slipping belts, closed dampers preventing airflow (causing backpressure), or seized bearings on the fan shaft.
- Input Phase Failure (EPH1): This indicates a loss of one of the incoming power phases. Check your building’s fuses or circuit breakers immediately, as running on single-phase can damage the drive’s input rectifier.
Frequently Asked Questions (FAQ)
Q: What is the difference between a Warning (C code) and a Fault?
A: A Warning (flashing codes starting with “C”, like CM00) alerts you to a condition—such as high current—but allows the fan or pump to keep running. A Fault (codes like OC or E) instantly stops the output to protect the equipment.
Q: How do I reset a Toshiba H9 fault?
A: You can reset the drive using one of these methods:
- Press the STOP/RESET key on the keypad twice.
- Momentarily close the RES (Reset) terminal to CC (Common).
- Cycle the main power (Turn OFF, wait for the screen to go black, Turn ON).
Q: Why does the drive display “OFF”?
A: OFF means the drive is powered and ready but has no “Run” command. In HVAC, this often means the Building Automation System (BAS) is not calling for the unit to run, or the “Auto/Manual” switch is in the wrong position.
Comments
Post a Comment