If the relay outputs are electronic (solid-state semiconductor outputs), ensure that the OSSD (Output Signal Switching Device) pulses are not out of sync. Preventive Maintenance Tips
While Yaskawa uses standard fault prefixes—such as for hardware failures and UV for undervoltage—the H66 code specifically points toward a Communication or Interface Error between the drive's control board and an external digital operator or option card.
Review your to see if the H66 error coincided with other alarms like undervoltage or overcurrent, which might suggest a broader power issue. 3. Mitigate Electrical Noise
A simple : Command a small position move forward, then backward. If you hear a “clunk” before motion, backlash is excessive. yaskawa error code h66
: Verify that the jumpers between H1-HC and H2-HC are secure if you are not using an external safety device. External Signal
If you have completed all the steps above and the H66 error persists immediately upon powering up the drive, you may be dealing with a hardware failure.
Understanding why this fault triggers is the first step toward fixing it. The discrepancy usually stems from one of four areas: 1. Wiring Issues : Verify that the jumpers between H1-HC and
Appendix — quick checklist (for technicians)
Access n6-01 (Latch Detection Level) and n6-02 (Latch Detection Time). Try increasing the tolerance:
indicates that the voltage in the drive's internal DC bus has exceeded the overvoltage detection level. For 200 V class drives, this safety trip triggers when the DC bus reaches approximately 410 V, while 400 V class drives trip at 820 V. Google Colab 6.3 Drive Alarms
The drive has lost connection with or cannot identify an installed option card (such as a PG-B3 feedback card or a fieldbus communication card).
Understanding and Troubleshooting the Yaskawa H66 Error Code
This fault indicates the voltage in the DC BUS has exceeded the overvoltage detection level. This value is 410 V for 200 V drives, Google Colab 6.3 Drive Alarms, Faults, and Errors
Ensure all communication cables (RJ45, serial DB9, or fiber optic) are plugged tightly into the option card and the upstream switch or PLC. Step 3: Analyze the External Network and PLC
If the relay outputs are electronic (solid-state semiconductor outputs), ensure that the OSSD (Output Signal Switching Device) pulses are not out of sync. Preventive Maintenance Tips
While Yaskawa uses standard fault prefixes—such as for hardware failures and UV for undervoltage—the H66 code specifically points toward a Communication or Interface Error between the drive's control board and an external digital operator or option card.
Review your to see if the H66 error coincided with other alarms like undervoltage or overcurrent, which might suggest a broader power issue. 3. Mitigate Electrical Noise
A simple : Command a small position move forward, then backward. If you hear a “clunk” before motion, backlash is excessive.
: Verify that the jumpers between H1-HC and H2-HC are secure if you are not using an external safety device. External Signal
If you have completed all the steps above and the H66 error persists immediately upon powering up the drive, you may be dealing with a hardware failure.
Understanding why this fault triggers is the first step toward fixing it. The discrepancy usually stems from one of four areas: 1. Wiring Issues
Appendix — quick checklist (for technicians)
Access n6-01 (Latch Detection Level) and n6-02 (Latch Detection Time). Try increasing the tolerance:
indicates that the voltage in the drive's internal DC bus has exceeded the overvoltage detection level. For 200 V class drives, this safety trip triggers when the DC bus reaches approximately 410 V, while 400 V class drives trip at 820 V.
The drive has lost connection with or cannot identify an installed option card (such as a PG-B3 feedback card or a fieldbus communication card).
Understanding and Troubleshooting the Yaskawa H66 Error Code
This fault indicates the voltage in the DC BUS has exceeded the overvoltage detection level. This value is 410 V for 200 V drives, Google Colab 6.3 Drive Alarms, Faults, and Errors
Ensure all communication cables (RJ45, serial DB9, or fiber optic) are plugged tightly into the option card and the upstream switch or PLC. Step 3: Analyze the External Network and PLC