Yaskawa D1000 Drive Fault Codes
Complete guide to Yaskawa D1000 Regenerative Converter fault codes. Learn to troubleshoot DC bus errors, input phase loss, and power quality alarms using DriveWizard.
D1000 Fault Codes Reference Table
Below is the complete reference list of faults and alarms specific to the converter unit. Please refer to this table to identify the issue currently displayed on your keypad.
YASKAWA D1000 Fault Displays, Causes, and Possible Solutions
| Fault Code and Meaning | Cause and Remedy |
|---|---|
| Aov Power Supply Overvoltage |
Cause: The input power supply voltage is too high.
Remedy: Reduce the voltage to within the range in the power supply specifications. |
| AUv Power Supply Undervoltage |
Cause:
Remedy:
|
| bUS Option Communication Error |
Cause:
Remedy:
|
| CE MEMOBUS/Modbus Communication Error |
Cause: Faulty communications wiring or an existing short circuit.
Remedy:
|
| CoF Current Offset Fault |
Cause: An error occurred in the power supply detection circuit (automatic current offset adjustment failed).
Remedy: Cycle the power supply and check operation. If the fault occurs again, replace the board or converter. |
| CPF00, CPF01, CPF11 to CPF22, CPF26 to CPF35 Control Circuit Error |
Cause:
Remedy:
|
| CPF02 A/D Conversion Error |
Cause: Control circuit is damaged (A/D conversion error).
Remedy: Cycle power to the converter. If the problem continues, replace the control board or the entire converter. |
| CPF03 Control Board Connection Error |
Cause:
Remedy:
|
| CPF06 EEPROM Memory Data Error |
Cause:
Remedy:
|
| CPF07, CPF08 Terminal Board Connection Error |
Cause: There is a faulty connection between the terminal board and the control board.
Remedy: Turn off the power and reconnect the terminal board. If the problem continues, replace the control board or the entire converter. |
| CPF23 Control Board Connection Error |
Cause: Hardware is damaged.
Remedy: Turn off the power and check the connection between the control board and the converter. If the problem continues, replace the control board or the entire converter. |
| CPF24 Unit Capacity Detect Fault |
Cause: Hardware is damaged (converter capacity cannot be detected).
Remedy: If the problem continues, replace the control board or the entire converter. |
| E5 MECHATROLINK Watchdog Timer Error |
Cause: Data has not been received from the PLC (watchdog timed out).
Remedy: Execute DISCONNECT or ALM_CLR, then issue a CONNECT command or SYNC_SET command and proceed to phase 3. Refer to the MECHATROLINK Option Technical Manual. |
| EF0 Option Card External Fault |
Cause:
Remedy:
|
| EF1 to EF8 External Fault (Input terminals S1 to S8) |
Cause:
Remedy:
|
| Err EEPROM Write Error |
Cause:
Remedy:
|
| Fan Internal Fan Fault |
Cause:
Remedy:
|
| Fdv Power Supply Frequency Fault |
Cause:
Remedy:
|
| FUA AC Fuse Blowout The power supply fuse is open. |
Cause: The power supply fuse is open. Remedy:
|
| FUd DC Fuse Blowout The DC converter output fuse is open. |
Cause: The main transistor failed. The DC circuit fuse is open. The drive failed. Remedy:
|
| GF Ground Fault Current exceeded Ground Short Detection Level at power supply side. |
Cause: A damaged cable is creating a short circuit. Excessive leakage current at the drive output. Hardware problem. Wiring of detection circuits (r1, ℓ1, t1) or main circuits is incorrect. Remedy:
|
| nSE Node Setup Error A terminal assigned to node setup closed during run. |
Cause: The node setup terminal closed during run. A Run command was issued while the node setup function was active. Remedy:
|
| oC Overcurrent Output current greater than specified level. |
Cause: A momentary power loss occurred. One of the cables has shorted out or there is a grounding problem. The load is too heavy. Remedy:
|
| oFA00 Option Card Connection Error (CN5-A) Option compatibility error. |
Cause: The option card installed into port CN5-A is incompatible with the converter. Remedy:
|
| oFA01 Option Card Fault (CN5-A) Option not properly connected. |
Cause: The option card connection to port CN5-A is faulty. Remedy:
|
| oFA05 to oFA06 oFA10 to oFA11 oFA12 to oFA17 oFA30 to oFA43 Option Card Error (CN5-A) |
Cause: Option card or hardware is damaged. Communication Option Card Connection Error (CN5-A). Remedy:
|
| oFb00 Option Card Fault (CN5-B) Option compatibility error. |
Cause: The option card installed into port CN5-B is incompatible with the converter. Remedy:
|
| oFb01 Option Card Fault (CN5-B) Option not properly connected. |
Cause: The option card connection to port CN5-B is faulty. Remedy:
|
| oFb02 Option Card Fault (CN5-B) Same type of option card is currently connected. |
Cause: An option card of the same type is already installed in option port CN5-A. Remedy:
|
| oFb03 to oFb11 oFb12 to oFb17 Option card error (CN5-B) |
Cause: Option card or hardware is damaged. There is a fault in the option card. Remedy:
|
| oFC00 Option Card Connection Error (CN5-C) Option compatibility error. |
Cause: The option card installed into port CN5-C is incompatible with the converter. Remedy:
|
| oFC01 Option Card Fault (CN5-C) Option not properly connected. |
Cause: The option card connection to port CN5-C is faulty. Remedy:
|
| oFC02 Option Card Fault (CN5-C) Same type of option card is currently connected. |
Cause: An option card of the same type is already installed in option port CN5-A or CN5-B. Remedy:
|
| oFC03 to oFC11 oFC12 to oFC17 Option Card Error (CN5-C) |
Cause: Option card or hardware is damaged. There is a fault in the option card. Remedy:
|
| oFC50 to oFC55 Option Card Error (CN5-C) |
Cause: Option card or hardware is damaged. Remedy:
|
| oH Heatsink Overheat Temperature exceeded pre-alarm level (L8-02). |
Cause: Surrounding temperature is too high. Load is too heavy. Internal cooling fan is stopped. Remedy:
|
| oH1 Overheat 1 Heatsink temperature exceeded converter overheat level. |
Cause: Surrounding temperature is too high. Load is too heavy. Internal cooling fan is stopped. Remedy:
|
| oL2 Converter Overload Thermal sensor triggered overload protection. |
Cause: Load is too heavy. Converter capacity is too small. The converter does not operate. Remedy:
|
|
oPr External Digital Operator Connection Fault The external operator has been disconnected from the converter. |
Cause: External operator is not properly connected to the converter. Remedy:
|
|
ov Overvoltage Voltage in the DC bus has exceeded the overvoltage detection level. (200 V Class: ~410 V, 400 V Class: ~820 V) |
Cause:
Remedy:
|
|
PF2 Input Power Supply Fault Abnormal oscillation in the main circuit DC bus continued. |
Cause:
Remedy:
|
|
PF3 Input Phase Loss Detection The voltage balance in the three-phase power supply has broken down. |
Cause:
Remedy:
|
|
SC Input Short-circuit / Main Transistor Failure Short circuit or ground fault is detected. (Note: Fault reset signals are not accepted to prevent accidents). |
Cause:
Remedy:
|
|
SrC Phase Order Fault The phase order detection direction for the input power supply changed after the power supply was turned on. |
Cause:
Remedy:
|
|
Uv1 Main Circuit Undervoltage The main circuit DC voltage became equal to or lower than the set value (200 V: ~190V, 400 V: ~380V). |
Cause:
Remedy:
|
|
Uv2 Control Power Supply Voltage Fault Voltage is too low for the control converter input power. |
Cause: Internal circuitry is damaged. Remedy:
|
|
Uv3 Undervoltage 3 (Soft-Charge Bypass Circuit Fault) The soft-charge bypass circuit failed. |
Cause: The relay or contactor on the soft-charge bypass circuit is damaged. Remedy:
|
|
Uv4 Gate Drive Board Undervoltage Voltage drop in the gate drive board circuit. |
Cause: Not enough power is being supplied to the gate drive board. Remedy:
|
|
vrE Resonance Detection A filter resonance fault was detected or there is a harmonic component on the power supply side. |
Cause:
Remedy:
|
| AEr Communication Option Station Number Setting Error |
Cause: Station number is set outside the possible setting range. Remedy:
|
| Aov Power Supply Overvoltage |
Cause: The input power supply voltage is too high. Remedy:
|
| AUv Power Supply Undervoltage |
Cause: The power supply voltage is low, a phase loss occurred, or voltage detection failed. Remedy:
|
| bb Baseblock |
Cause: External baseblock signal was entered via one of the multi-function input terminals (S1 to S8). Remedy:
|
| bUS Option Communication Error |
Cause: Connection broken, option damaged, improper connection, or data error due to noise. Remedy:
|
| CALL Serial Communication Transmission Error |
Cause: Communications wiring is faulty, programming error on master side, circuitry damaged, or termination resistor setting incorrect. Remedy:
|
| CE MEMOBUS/Modbus Communication Error |
Cause: Data error due to noise, incompatible protocol, CE detection time (H5-09) set too short, PLC hardware/software problem, or cable disconnected. Remedy:
|
| CoF Current Offset Fault |
Cause: A fault occurred in the current detection circuit. Remedy:
|
| CrST Cannot Reset |
Cause: Fault reset was being executed when a Run command was entered. Remedy:
|
| CyC MECHATROLINK Communications Cycle Setting Error |
Cause: The communications cycle of the MECHATROLINK option card is out of range. Remedy:
|
| E5 MECHATROLINK Watchdog Timer Error |
Cause: There is no continuity in the watchdog timer in the data that is sent by the host controller. Remedy:
|
| EF0 Option Card External Fault |
Cause: An external fault was received from the PLC (with F6-03 set to 3), or there is a problem with the PLC program. Remedy:
|
| EF1 External Fault (Input Terminal S1) |
Cause: An external device has tripped an alarm function, wiring is incorrect, or multi-function contact inputs are set incorrectly.
Remedy:
|
| EF2 External Fault (Input Terminal S2) |
Cause: External fault at multi-function input terminal S2.
Remedy:
|
| EF3 External Fault (Input Terminal S3) |
Cause: External fault at multi-function input terminal S3.
Remedy:
|
| EF4 External Fault (Input Terminal S4) |
Cause: External fault at multi-function input terminal S4.
Remedy:
|
| EF5 External Fault (Input Terminal S5) |
Cause: External fault at multi-function input terminal S5.
Remedy:
|
| EF6 External Fault (Input Terminal S6) |
Cause: External fault at multi-function input terminal S6.
Remedy:
|
| EF7 External Fault (Input Terminal S7) |
Cause: External fault at multi-function input terminal S7.
Remedy:
|
| EF8 External Fault (Input Terminal S8) |
Cause: External fault at multi-function input terminal S8.
Remedy:
|
| Fan Converter Internal Circulation Fan Fault |
Cause: An internal circulation fan or MC power supply is faulty (2A0130 or 4A0130 to 4A0370).
Remedy:
|
| Fdv Power Supply Frequency Fault |
Cause:
Remedy:
|
| HCA Current Alarm |
Cause: Load is too heavy (Current exceeded 150% of rated current).
Remedy:
|
| LT-1 Cooling Fan Maintenance Time |
Cause: The cooling fan has reached 90% of its expected performance life.
Remedy:
|
| LT-2 Capacitor Maintenance Time |
Cause: The main circuit and control circuit capacitors have reached 90% of their expected performance lives.
Remedy:
|
| LT-3 Soft Charge Bypass Relay Maintenance Time |
Cause: The DC bus soft charge relay has reached 90% of expected performance life.
Remedy:
|
| oH Heatsink Overheat |
Cause:
Remedy:
|
| oL2 Converter Overload |
Cause:
Remedy:
|
| ov DC Bus Overvoltage |
Cause:
Remedy:
|
| PAUv Power Supply Undervoltage Pre-Alarm |
Cause:
Remedy:
|
| PF3 Input Phase Loss Detection |
Cause:
Remedy:
|
| SE MEMOBUS/Modbus Test Mode Fault |
Cause: A fault occurred during MEMOBUS/Modbus Communications Test Mode.
Remedy:
|
| SrC Phase Order Fault |
Cause:
Remedy:
|
| Uv Undervoltage |
Cause:
Remedy:
|
| vrE Resonance Detection |
Cause: There is noise on the power supply line.
Remedy:
|
|
Err EEPROM Write Error A verification mismatch occurred when writing data to the EEPROM. |
Cause: 1. The data was corrupted by noise when writing data to the EEPROM. 2. EEPROM Hardware Failure. Remedy:
|
|
oPE01 Converter Capacity Setting Fault Converter capacity and the value set to o2-04 do not match. |
Cause: The drive model selection (o2-04) and the actual capacity of the converter are not the same. Remedy: Correct the value set to o2-04. |
|
oPE02 Parameter Range Setting Error Use U1-18 to find parameters set outside the range. |
Cause: Parameters were set outside the possible setting range. Remedy: Set parameters to the proper values. Note: When multiple errors occur simultaneously, other errors are given precedence over oPE02. |
|
oPE03 Multi-Function Input Selection Error A contradictory setting is assigned to multi-function contact inputs H1-01 to H1-08. |
Cause: The same function is assigned to two multi-function inputs. Excludes “Not used” and “External Fault.” Remedy:
|
|
oPE04 Terminal Board Mismatch Error The converter or the removable terminal block with parameter backup was replaced. |
Cause: The converter was replaced (but the removable terminal block with parameter backup was not replaced), OR the removable terminal block was replaced. Remedy:
|
|
oPE05 Run Command Selection Error The settings for the Run Command or Bus Voltage Command are not correct. |
Cause: The Run command is assigned to an option card (b1-18 = 3 or b1-02 = 3) and an input option card is not connected to the converter. Remedy: Reconnect the input option card to the converter. |
|
oPE07 Multi-Function Analog Input Selection Error A contradictory setting is assigned to multi-function analog inputs H3-02, H3-10, or H3-06. |
Cause: At least two of these parameters have the same setting: H3-02, H3-10, or H3-06. Remedy: Change the settings to H3-02, H3-10, and H3-06 so that functions no longer conflict. |
|
oPE30 Incorrect Input Voltage Adjustment The input voltage offset adjustment has not been performed. |
Cause:
Remedy: For information on clearing the fault, consult with your Yaskawa representative or the nearest Yaskawa sales office. |
| CoPy Writing Parameter Settings (flashing) |
Cause: The operator is currently writing parameter settings to the converter. Remedy: Status display only. Wait for the task to complete. |
| CPyE Error Writing Data |
Cause: An error occurred while attempting to write data to the converter. Remedy: Press any key on the operator to clear the error. Check connections and compatibility. |
| CSEr Copy Unit Error |
Cause: A hardware or data error occurred within the Copy Unit. Remedy: Press any key on the operator to clear the error. If the problem persists, replace the Copy Unit. |
| dFPS Model Mismatch |
Cause: The model number of the drive does not match the data being copied. Remedy: Press any key on the operator to clear the error. Ensure the source and target drive models match. |
| End Task Complete |
Cause: The requested copy/verify task has finished successfully. Remedy: Status display only. No action required. |
| iFEr Communication Error |
Cause: Data communication between the operator/copy unit and the converter was interrupted. Remedy: Press any key to clear. Check the cable connection between the operator and the converter. |
| ndAT Model, Voltage Class, Capacity Mismatch |
Cause: The model, voltage class, or capacity specifications do not match between the saved data and the converter. Remedy: Press any key to clear. Parameters can only be saved when voltage class, capacity, control mode, and software version match (See Note 3). |
| rdEr Error Reading Data |
Cause: An error occurred while reading data from the converter. Remedy: Press any key to clear the error. Retry the read operation. |
| rEAd Reading Parameter Settings (flashing) |
Cause: The operator is currently reading parameter settings from the converter. Remedy: Status display only. Wait for the task to complete. |
| vAEr Voltage Class, Capacity Mismatch |
Cause: The voltage class or capacity of the converter does not match the data in the copy unit. Remedy: Press any key to clear. Verify the converter rating plate matches the intended configuration. |
| vFyE Parameter Mismatch |
Cause: Parameter settings in the converter and those saved to the copy function are not the same. Remedy: Press any key to clear. Review parameters to identify differences. |
| vrFy Comparing Parameter Settings (flashing) |
Cause: The system is currently comparing the parameters in the converter with the saved data. Remedy: Status display only. Wait for the task to complete. |
How to Read D1000 Faults via DriveWizard
Troubleshooting a converter requires analyzing the interaction between the grid and the DC Bus. In 2026, standard multimeters are often insufficient for catching fast power spikes. Use these tools instead:
- U2 Fault Trace Parameters: Access the “Black Box” history directly via the keypad.
- U2-01: Current Fault Code.
- U2-04 thru U2-20: These monitors freeze the data at the moment of the trip. Pay specific attention to U2-11 (DC Bus Voltage) and U2-13 (Input Terminal Status) to see if the unit tripped due to a grid surge or an external command.
- DriveWizard Industrial: By connecting a PC via USB or Serial, you can use the **Oscilloscope function**. This is critical for the D1000 to visualize the AC Input Waveform and ensure the regeneration synchronization is matching the grid frequency.
Frequently Asked Questions (FAQ)
Q: What is the difference between an Alarm and a Fault on the D1000?
A:
- Alarm (Flashing): The unit detects a non-critical issue (like High Heatsink Temp) but continues to regulate the DC bus.
- Fault (Solid): The unit detects a critical failure. The D1000 immediately stops the “Gate” (transistor switching), stopping the conversion of power. The connected inverters will likely trip on “Under Voltage” (Uv) shortly after.
Q: How do I reset a Yaskawa D1000 fault?
A: After verifying the incoming power lines are stable:
- Press the RESET button on the keypad.
- Trigger the “Fault Reset” digital input (Terminal S4).
- Cycle the main AC input power (Wait for the DC Bus light to extinguish).
Q: Why does the D1000 trip on “PF” (Input Phase Loss)?
A: The D1000 monitors the input power ripple. If one phase of the incoming 3-phase power sags or is lost, the DC bus ripple increases, triggering a PF fault. Check your input fuses, circuit breakers, and incoming voltage balance.
Comments
Post a Comment