ACS580 Fault 2310 — Overcurrent

Overview\n\nABB ACS580 Fault Code 2310 stands for Overcurrent. This critical fault indicates that the Variable Frequency Drive (VFD) has detected output current levels that exceed its preprogrammed, native software limit or its hardware's maximum safety threshold. This safe state tripping mechanism acts immediately to protect the drive's internal components, primarily the Insulated-Gate Bipolar Transistors (IGBTs), from catastrophic thermal or overcurrent destruction.\n\nWhen the internal current transducers detect an instantaneous surge or sustained current exceedance, the ACS580 instantly shuts down its firing circuits and flashes the diagnostic warning code. To prevent lasting damage to your material handling equipment, HVAC systems, or industrial pumps, you must isolate the root cause before attempting to repeatedly reset the drive.\n\n## Symptoms\n\nWhen an ACS580 experiences an overcurrent event, operators and technicians may observe several distinct system behaviors:\n\n* Immediate Trip on Run Command: The drive immediately faults out on 2310 as soon as the run/start signal is activated, before the motor even begins to rotate.\n* Trip During Acceleration: The motor starts to turn, but the drive trips during the ramp-up phase when moving toward set speed.\n* Intermittent Mid-Cycle Trips: The drive operates normally for variable durations but trips unexpectedly during heavy load phases of the process cycle.\n* Audible Motor Humming/Squealing: The electric motor emits loud high-pitched noise or hums deeply without rotating, followed immediately by the 2310 fault code.\n* Flashing Red LED: The drive's Assistant Control Panel displaying a red indicator light with the diagnostic screen showing code 2310 and real-time operational stamps.\n* Elevated Motor Temperature: Before the overcurrent trip occurs, the motor shell may feel excessively hot to the touch.\n\n## Possible Causes\n\nAn overcurrent fault can originate from mechanical, electrical, or software-related root causes. The most common issues include:\n\n* Motor Windings or Cable Faults: A phase-to-phase or phase-to-ground short circuit within the motor's stator windings or the run of motor cabling.\n* Excessive Acceleration Ramps: Acceleration time set too low in the system parameters, causing the drive to dump excessive energy to overcome load inertia.\n* Mechanical Overload or Jam: Seized bearings, jammed gearboxes, blocked fan impellers, or process buildup in pumps forcing the motor to draw locked-rotor amps.\n* Incorrect Motor Parameters: Out-of-sync configuration values in Group 99 (such as nominal motor current, voltage, or frequency) mismatching actual motor nameplate data.\n* Long Motor Cables: Excessive cable distance between the VFD and motor, creating massive capacitive charging currents that simulate an output short.\n* Degraded Inverter Bridgework: Damaged internal power electronics, such as degraded or fully shorted IGBTs.\n* Improper Motor Control Mode: Running Vector control without an updated Identification Run (ID Run), or using Sensorless Vector when Scalar control is better suited.\n\n## Step-by-Step Troubleshooting\n\nFollow these structured diagnostic steps to isolate and resolve the overcurrent condition. Ensure all Lockout/Tagout (LOTO) protocols are observed and active DC bus voltages have fully discharged (wait at least 15-20 minutes after powerdown and verify with a reliable multimeter before touching terminals).\n\n### Step 1: Perform the Isolation Test (VFD vs. Motor/Cables)\n1. Power down the drive completely using appropriate safety disconnects.\n2. Wait for the internal capacitors to discharge. Verify zero voltage on terminals UDC+ and UDC- relative to ground.\n3. Disconnect the motor cables from the output terminals U2, V2, and W2 at the bottom of the ACS580.\n4. Navigate to Parameter 99.04 (Motor control mode) using the keypad and set it to Scalar (momentarily if currently in Vector).\n5. Power up the drive and issue a run command to ramp the open-output drive to its target frequency (e.g., 50 Hz or 60 Hz).\n* If the drive still trips on 2310 with no motor connected: The VFD's internal current sensors or output IGBT bridge are damaged. The drive must be repaired or replaced.\n* If the drive runs cleanly without tripping: The issue lies within the motor cables, the motor windings, or the mechanical drive load. Proceed to Step 2.\n\n### Step 2: Megohmmeter testing of Motor and Cabling\n1. Keep the motor cables disconnected from the internal drive terminals.\n2. Use a high-quality Megohmmeter (Megger) to test the insulation resistance of the motor cables and windings.\n3. Inject an appropriate voltage (typically 500V or 1000V DC depending on the motor rating) between each phase terminal (U, V, W) and protective earth ground.\n4. Measure the phase-to-phase insulation resistance between the individual leads.\n* Acceptable standard threshold: Readings should ideally exceed 100 Megohms. If any reading measures near 0 Megohms or is significantly degraded (below 5-10 Megohms on older motors), a short circuit exist. Inspect the cable junction box, check for water ingress, or replace the layout cabling or motor.\n\n### Step 3: Mechanical Load Auditing\n1. Decouple the motor shaft from the mechanical load (uncouple the belt, shaft coupling, or gearbox input).\n2. Attempt to rotate the motor shaft manually. It should spin freely without binding.\n3. Rotate the input shaft of the driven machine manually to check for seized bearings, foreign material jams, or mechanical transmission drag.\n4. Reconnect the motor cables to the VFD and run the motor uncoupled. If the fault does not reoccur when uncoupled, the issue resides entirely in your external mechanical load.\n\n### Step 4: Examine Parameter Setup & Ramp Groups\n1. Check the motor nameplate against Group 99 (Motor data) parameters, specifically:\n * 99.06 Motor nominal current\n * 99.07 Motor nominal voltage\n * 99.08 Motor nominal frequency\n * 99.09 Motor nominal speed\n2. Correct any configuration mismatch immediately. Even slight variance can upset the current calculation algorithm.\n3. Check your acceleration time parameters in Group 23 (Speed reference ramp) or Group 28 (Frequency reference chain).\n4. If 23.11 (Acceleration time 1) is set lower than 3-5 seconds, increase it to 10-15 seconds (or higher for high-inertia fans or centrifuges). This reduces the torque demand on spin-up.\n\n### Step 5: Conduct Inverter Diode (IGBT) Diagnostics with Multimeter\nIf the drive faulted in Step 1, verify the integrity of the power semiconductors:\n1. Set your digital multimeter (DMM) to the Diode Test function.\n2. Place the positive (red) probe on the drive's negative DC terminal (UDC-). Connect the negative (black) probe to output terminal U2. Note the voltage drop (typically around 0.3V to 0.7V for a functioning diode).\n3. Repeat for V2 and W2 output terminals. Ensure readings across all phases are symmetric within 0.05V.\n4. Place the negative (black) probe on the positive DC terminal (UDC+), then touch the positive (red) probe to U2, V2, and W2. Note the drops.\n5. Swap probe orientations. If any measurement indicates a raw 0.00V short-circuit reading, your IGBT module is blown and the power board must be replaced.\n\n## Recommended Actions\n\n* Sway to Scalar Mode: If you do not require dynamic speed accuracy or high low-end torque control, configure Parameter 99.04 to Scalar. It is highly forgiving of minor electrical fluctuations and asymmetric cabling issues.\n* Conduct an Identification Run: If Vector control is necessary, always run an ID run by selection in Parameter 99.13 (ID run requested). Ensure the motor is uncoupled during this process for optimal magnetic modeling.\n* Install Output Chokes / dV/dt Filters: If the run distance from the ACS580 to the motor exceeds 100 feet (approx. 30 meters), output capacitance charging currents can spike. An external line reactor or dV/dt filter will smooth these waveforms.\n* Evaluate Line Voltages: Ensure incoming utility voltage does not dip significantly during start-up. Voltage sag under load causes proportional current rise.\n\n## Recommended Replacement Parts\n\nIf the hardware has degraded based on your diagnostic results, we recommend utilizing high-quality replacement parts to restore system uptime:\n\n* Replacement IGBT Power Modules: Crucial if diode tests verified a direct short in the internal power semiconductors.\n* ACS580 Control Panel Assembly: If the display is unresponsive or fails to display fault logs clearly during troubleshooting.\n* Internal Current Transducers / CTs: Replace if the drive reports phantom overcurrent faults when isolated containing zero output current.\n* Auxiliary Cooling Fans: Degraded thermal management can trigger erratic operation of power components; replace fans displaying high operating hours.\n* VFD-Rated Motor Cable: Replace routing with shielded, low-impedance cables designed to block destructive ground currents.\n\n## Related Articles\n\n* Selecting the Right Output Filter for ABB ACS580 Drives\n* How to Perform an ID Run on ABB ACS Drives\n* Replacing the IGBT Module on ABB Industrial Drives\n* Understanding ABB ACS580 Control Modes: Scalar vs Vector\n\n## FAQ\n\n### Q: Can I run my ACS580 drive if the overcurrent fault only occurs once a week?\nNo. An overcurrent fault indicates the drive is working right on its physical hardware threshold. Repeatedly resetting is very dangerous and can turn a minor motor cable problem into a catastrophic VFD explosion, costing thousands in extra board damage.\n\n### Q: Why does the 2310 overcurrent fault happen immediately when the motor starts, but not when running?\nThis is generally caused by highly stiff loads requiring a large starting torque, or incorrect starting configurations. Also, dynamic breakdowns in winding insulation commonly trigger right as the first high-amplitude PWM voltage spikes reach the cold coils.\n\n### Q: What is the main difference between overcurrent (2310) and earth leakage (2330)?\nWhile both involve abnormal raw current flow, Fault 2330 is tripped exclusively when current is escaping the closed-loop system directly to earth ground (e.g. wet or nicked wires). Overcurrent 2310, conversely, handles symmetric or asymmetric phase-to-phase demands that exceed VFD output limits.\n\n### Q: Can a bad encoder feedback cause a fault 2310?\nYes. If you configured your run process in Closed Loop Vector mode and the encoder has mechanical slippage, signal interference, or wrong channel wiring, the encoder speed reading may drop to zero. The drive will then pump maximum current to try to bring the spin up, instantly triggering an overcurrent fault.