Toshiba G7 Fault Codes List
Troubleshoot your Toshiba G7 adjustable speed drive with our updated fault code guide. Learn to interpret OC, OL, and EF trips, view the LCD trip history, and reset faults.
Toshiba G7 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.
Toshiba G7 Drive Fault Codes List
| Fault Code and Meaning | Cause and Remedy |
|---|---|
| CM1 Comm1 Error |
Cause: Internal communications error. Remedy:
|
| CM2 Comm2 Error |
Cause: External communications error. Remedy:
|
| EMG Emergency Off |
Cause: Output signal from the ASD is terminated and a brake may be applied if so configured. Remedy:
|
| MOFF Main Undervoltage |
Cause: Undervoltage 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 Overvoltage |
Cause: DC bus voltage exceeds specifications. Remedy:
|
| OT Overtorque |
Cause: Torque requirement in excess of the setting of F616 or F617 for a time longer than the setting of F618. Remedy:
|
| POFF Control Undervoltage |
Cause: Undervoltage 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 Undercurrent |
Cause: Output current of the ASD is below the level defined at F611 and remains there for the time set at F612. Remedy:
|
| Autotune Error Autotune Malfunction |
Cause: Autotune readings that are significantly inconsistent with the configuration information. Remedy:
|
| Communication Error Comms Malfunction |
Cause: System communication failure. Remedy:
|
| CPU Fault Processor Error |
Cause: Internal processor error. Remedy:
|
| DC Bus Undervoltage Bus Voltage Low |
Cause: DC Bus voltage dropped below limit. Remedy:
|
| DC Fuse Open Internal Fuse Blown |
Cause: Internal DC bus fuse is open. Remedy:
|
| Dynamic Braking Resistor Overcurrent DBR Overcurrent |
Cause: ASD inability to discharge the bus voltage during regeneration. Remedy:
|
| Earth Fault Ground Fault |
Cause: Current leakage to Earth Ground detected. Remedy:
|
| EEPROM Data Fault Memory Error |
Cause: Internal EEPROM malfunction. Remedy:
|
| Encoder Loss Signal Missing |
Cause: Encoder signal missing while running during closed-loop operation. Remedy:
|
| Gate Array Fault Hardware Failure |
Cause: Defective Gate Array or Gate Array malfunction. Remedy:
|
| Input Phase Loss Phase Missing |
Cause: 3-phase input to the ASD is low or missing. Remedy:
|
| Load Drooping Load Error |
Cause: Load requirement is in excess of the capabilities of the motor. Remedy:
|
| Load End Short Circuit Output Short |
Cause: Improper wiring at the ASD output to the motor. Remedy:
|
| Low Current Current Low |
Cause: Improper Low Current detection level setting. Remedy:
|
| Option Fault Card Error |
Cause: Optional device malfunction. Remedy:
|
| Output Phase Loss Motor Phase Lost |
Cause: 3-phase output from the ASD is low or missing. Remedy:
|
| Overcurrent During Acceleration Accel OC |
Cause: Overcurrent detected while ramping up speed. Remedy:
|
| Overcurrent During Deceleration Decel OC |
Cause: Overcurrent detected while ramping down speed. Remedy:
|
| Overcurrent During Run Run OC |
Cause: Overcurrent detected at constant speed. Remedy:
|
| Over Speed Speed Limit Exceeded |
Cause: Result of a motor speed that is greater than the commanded speed when using an encoder for speed control. Remedy:
|
| PG Type/Connection Error Encoder Error |
Cause: ASD is configured to receive a signal from a shaft-mounted encoder and no signal is being received. Remedy:
|
| Phantom Fault System Fault |
Cause: In a multiple ASD configuration a faulted ASD signals the remaining ASDs that a fault has occurred. Remedy:
|
| Position Deviation Error Position Error |
Cause: Operating in the Position Control mode and the resulting position exceeds the limits of the F631 setting. Remedy:
|
| Sink/Source Setting Error Jumper Error |
Cause: Logic setting mismatch. Remedy:
|
| Torque Proving Fault Brake Logic Error |
Cause: Torque proving logic failed. Remedy:
|
| Typeform Error Firmware Mismatch |
Cause: Firmware information loaded into the Gate Driver board is inconsistent with the device. Remedy:
|
| U/V/W Phase Short Circuit Output Short |
Cause: Low impedance at the U, V, or W lead of the ASD output. Remedy:
|
How to Read G7 Faults via LCD Keypad
The G7’s greatest asset is its user-friendly keypad. In 2026, you don’t necessarily need a laptop to diagnose a trip if you know how to navigate the EOI:
- Trip History: The G7 stores the last 4 faults in its memory. Press the MON (Monitor) button and scroll to the “Trip History” section. It will show the fault code (e.g., Trip 1: OC1) and the sequence in which they occurred.
- Status at Trip: Inside the Trip History menu, you can select a specific fault and press ENT (Enter). This displays the “Status at Trip,” showing the output frequency, current, and voltage at the exact moment the drive failed.
- Monitor Mode: Real-time monitoring allows you to watch the “Input Terminal Status” to see if an external interlock or E-Stop is physically triggering the drive to stop.
General Troubleshooting Steps
Before resetting a major fault on the G7, perform these checks:
- Overcurrent (OC1/OC2/OC3): The G7 is sensitive to short circuits. OC1 is during acceleration, OC2 during deceleration, and OC3 during run. Disconnect the motor leads and perform a megger test on the motor.
- Ground Fault (EF1/EF2): “EF” indicates an Earth Fault. This is often caused by moisture in the conduit or compromised motor insulation. Do not repeatedly reset an EF fault, as it can blow the input transistors.
- Overload (OL1/OL2): OL1 is the Motor Thermal Overload; OL2 is the Drive Inverter Overload. If OL1 occurs, check if the motor cooling fan is clogged. If OL2 occurs, the load may be too heavy for the drive size.
Frequently Asked Questions (FAQ)
Q: What is the difference between “OFF” and a Fault?
A: If the display simply says OFF, the drive is not faulted; it is in a “Ready” state but lacks a Run command. A Fault (like E or OC) will flash the “TRIP” LED and require a manual reset.
Q: How do I reset a Toshiba G7 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 supply (Power OFF/ON).
Q: What does the “E” code mean?
A: The E code indicates an “Emergency Off.” This is usually triggered when the drive receives a stop command while in a failure mode, or if the “Emergency Stop” parameter is activated via a digital input. Check your E-Stop buttons and wiring continuity.
Comments
Post a Comment