A1000 Fault oC — Overcurrent

Overview

The oC (Overcurrent) fault on a Yaskawa A1000 variable frequency drive (VFD) indicates that the drive's output current has dramatically exceeded its rated safety threshold. Typically triggering at approximately 200% of the drive’s nominal current rating, this critical protective fault instantly shuts down the output transistors (IGBTs) to prevent catastrophic electrical damage to the drive, motor, and internal sensing circuits. An oC fault is a high-priority hardware safety shutdown and must be fully diagnosed before simply resetting the drive, as repeating resets on a dead short can permanently damage the unit.

Symptoms

When an oC fault occurs, it presents itself in several predictable ways across the plant floor:

• Digital Operator Display: The LED/LCD screen of the A1000 displays a solid or flashing oC red alarm notification.
• Sudden Process Interruption: The motor instantly coasts to a stop without deceleration ramps because the drive immediately cuts output power.
• Intermittent Tripping: The motor may run fine at low speeds but trips instantly during acceleration or upon reaching a specific high-load operating frequency.
• Instant Trip on Start: The drive trips immediately when a RUN command is issued, even before the shaft can rotate a fraction of a turn.
• Status Indicators: The "ALM" LED on the face of the drive lights up bright red, and configured fault relay contacts (such as terminals M1-M2) change state to halt safety interlocks.

Possible Causes

An overcurrent condition on the Yaskawa A1000 can arise from external mechanical issues, electrical failures in the motor or cabling, poor tuning, or internal drive component failure. Common causes include:

1. Output Short Circuit or Ground Fault: Damaged insulation in the motor leads, water or carbon dust in the motor terminal box, or a short circuit between phases (U-V, V-W, or W-U).
2. Excessive Mechanical Load: A locked rotor, mechanical jam, seized bearing, or a process overload that requires torque far beyond the drive's output capacity.
3. Aggressive Acceleration/Deceleration Times: Acceleration time parameter (C1-01) is set too short for the inertia of the connected load, forcing the drive to dump current to try to meet the ramp.
4. Incorrect V/f Pattern or Motor Parameters: The drive is applying too much voltage at low speeds, saturating the motor’s magnetic cores and causing current spikes.
5. Drive Size Mismatch: The VFD is undersized for the motor horsepower or duty cycle required by the application.
6. Damaged Internal IGBT Module: A shorted or degraded output transistor inside the Yaskawa A1000 itself, preventing clean current phase output.
7. Faulty Current Sensing Circuitry: Failed Hall-effect current transformers (CTs) or a degraded gate driver circuit board reporting incorrect analog current levels back to the control board.

Step-by-Step Troubleshooting

Follow these systematic steps to isolate the root cause of the oC error. Work safely: ensure all input power is disconnected, locked out, and wait at least 5 to 10 minutes for the internal DC bus capacitors to fully discharge (confirming with a multimeter that the charge light is off and DC bus voltage is near 0V before touching wiring).

Step 1: Perform the "Split Test" (Isolate Drive from Motor)

To determine if the fault is inside the VFD or downstream in the load/cabling:

1. Disconnect the motor cables from the drive terminals U/T1, V/T2, and W/T3.
2. Temporarily change the control method parameter A1-02 to 0 (V/f Control). If the drive was using Open Loop Vector, it might trip if it tries to run a vector algorithm with no motor connected.
3. Turn the drive on and issue a RUN command with a low frequency reference (e.g., 10 Hz).
4. Analyze the outcome:
   • If the drive still trips on oC with no motor connected, the damage is internal to the VFD (likely a blown IGBT module or a faulty current sensor).
   • If the drive runs successfully without tripping, the VFD is mechanically and electrically capable of producing output. The issue lies downstream in the cables, motor, or mechanical load.

Step 2: Test Output Terminals with a Multimeter (Static Diode Check)

If the VFD tripped with no motor connected, perform a static check on the main transistors:

1. Make sure input power is completely disconnected and discharged.
2. Set your digital multimeter to the Diode test setting.
3. Place the Red lead on the negative DC bus terminal (- or B2) and touch the Black lead to each output terminal (U/T1, V/T2, W/T3). Note the readings (typically around 0.3V to 0.5V).
4. Place the Black lead on the positive DC bus terminal (+1 or +2) and touch the Red lead to each output terminal (U/T1, V/T2, W/T3).
5. If any output phase measures a direct short (0.0V) or open loop (OL) in both directions, that transistor phase is damaged and the VFD must be repaired or replaced.

Step 3: Inspect Motor and Output Cabling

If the VFD passed the split test, check the fields:

1. Check the motor output cables for signs of physical wear, pinch points, or exposure to excessive heat.
2. Disconnect the cable at both the drive and the motor. Run an insulation resistance test (Megohmmeter/Megger) between each conductor (U, V, W) and the ground line. Warning: Never megger the motor while it is connected to the VFD terminals, as high megger voltages will instantly destroy the drive's output transistors.
3. Check the winding resistance of the motor coils using a low-resistance ohm meter. Winding values must be closely balanced across all three phases (U-V, V-W, W-U). High deviations point to a shorted motor turn.

Step 4: Examine Mechanical System and Sizing

1. Check if the motor shaft can be rotated freely by hand (strictly observe safety protocols and lockouts).
2. Look for process jams, clogged lines, cold product in mixers, or failed gearboxes.
3. Review the motor nameplate against the drive's rating parameters in Group E to ensure the correct motor rated current is inputted into parameter E2-01 (or E5-01 for PM motors).

Step 5: Speed up Acceleration and Deceleration Parameters

If the oC fault occurs strictly during acceleration or deceleration cycles:

1. Increase the acceleration time C1-01 and deceleration time C1-02.
2. Enable Stall Prevention during acceleration (L3-01 = 1). This temporarily pauses the acceleration ramp if the motor draws too much current, preventing an overcurrent trip.
3. If using overexcitation deceleration, check L3-04 settings. Improper overexcitation parameters can generate massive currents during deceleration.

Recommended Actions

• Increase Ramp Settings: If the system displays intermittent oC trips only during high inertial starts, increase start-up times to reduce peak dynamic demands.
• Verify Auto-Tuning: If running in Vector control modes, re-run rotational auto-tuning (T1-01 = 0). Out-of-tune motor maps yield bad current calculations, driving excessive magnetizing currents.
• Install Output Reactors: In cases where motor leads exceed 100 feet (30 meters), the high capacitance of the cable leads to excessive charging current spikes. Installing an AC output reactor near the VFD output terminal blocks will buffer these spike currents.
• Refurbish or Replace internal components: If the drive's internal diode check failed, the power core must be serviced.

Recommended Replacement Parts

When restoring your Yaskawa A1000 drive, utilizing high-quality replacement parts is essential to prevent secondary component failures:

Related Articles

• Migrating from Yaskawa A1000 to GA700 Series
• Step-by-Step VFD Static Diode and IGBT Testing Procedures
• Understanding and Solving VFD Overcurrent Faults Under Heavy Load

FAQ

Q: Can I run a quick auto-tune on my Yaskawa A1000 to solve a persistent oC fault?

A: Only if the fault occurs during running or speed changes, indicating poor motor tuning. If the oC trips instantly upon pressing the START key, the VFD is likely sensing a hard short circuit. Auto-tuning will not run in this condition and could further stress damaged output circuits.

Q: Why does the drive trip oC even when the motor is not running?

A: If the drive trips on oC immediately when powered up or when a run command is requested before the motor spins, it usually indicates either a completely failed IGBT (stuck closed) or a damaged current transformer (CT) feedback circuit which falsely reports anomalous current levels to the main ASIC chip.

Q: What is the difference between an oC (Overcurrent) and an oL1 (Motor Overload) fault?

A: The oC fault is an instantaneous, sub-millisecond hardware protective trip triggered by peak current spikes (typically 200%+ of rating). The oL1 fault is an inverse-time software thermal overload protection, designed to monitor motor heating based on moderate, prolonged overcurrent draws over minutes.

Q: Can a bad dynamic braking resistor cause an oC fault on deceleration?

A: Yes. If the braking resistor is set incorrectly, has shorted internally, or if the braking transistor module in the drive is damaged, regenerative current from the motor cannot dissipate quickly enough, leading to erratic output control loops and causing an intermittent overcurrent trip.