ABB fault record

2340 / SHORT CIRC: Output Short-Circuit, Phase-Leg or Power-Stage Fault

The ACS800 reports SHORT CIRC / 2340 at enable, first PWM, acceleration, steady operation or after a repaired module is returned to service.

Fault service record13 min read

Scope of this technical record

Use this page when an ACS800 reports SHORT CIRC / 2340 and the case must be separated into external output fault, IGBT module fault, AGDR gate-driver fault, current/protection feedback or repeat-failure route.

Safety boundary

Treat 2340 as a destructive output-stage stop condition until proven otherwise. Do not repeat start commands or energize a replacement module while motor/cable, driver and bridge evidence remain unknown.

ACS800 SHORT CIRC route

1Output cable
2Phase info
3IGBT
4Gate driver
5Pre-power stop

SHORT CIRC is handled as a destructive output-stage event until evidence clears it.

2340 is not one single repair action

The panel may show one fault code, but the service route has several different boundaries. If the fault appears only with the motor connected, the first question is external output evidence. If it appears with the output path absent under a qualified procedure, the case moves toward bridge, driver or protection evidence. If it appears again after a module or AGDR replacement, the case becomes a repeat-failure investigation.

A useful record preserves the trip timing: power-up, enable, first PWM, acceleration, steady load, deceleration or after a previous repair. This timing often matters more than the fault name because it tells the technician whether the short is being discovered before output, at switching, or under machine load.

SHORT CIRC timing matrix

Fault timingFirst evidence routeStop before
At enable / first PWMStatic bridge, driver readiness, output path stateRepeated reset
Only with motor connectedMotor cable, terminal box, output accessoriesModule replacement
Under load or accelerationLoad, ramp, cable stress, current feedbackIgnoring external cause
After previous repairAGDR, IGBT, connector and original causeInstalling another module

External output proof protects replacement hardware

The output path includes drive output terminals, output contactor, cable, shield, motor terminal box, motor winding and any accessories on the motor side. A wet terminal box, damaged cable, output capacitor, surge device or contactor problem can make a repaired drive fail again as soon as output is enabled.

External proof must be performed with the drive made safe and according to qualified procedures. Do not insulation-test through drive electronics. The record should state whether the motor/cable path was proven absent, abnormal or still unknown.

Internal evidence should identify the boundary

Internal evidence should not simply say 'power module bad'. The record should explain whether the affected area is a U/V/W phase leg, an IGBT module, AGDR driver channel, current/protection feedback path, connector/harness route or a combination after a destructive event.

If AGDR or module hardware has been changed before, include the run time after repair and whether the same leg or module failed again. That history changes the service decision from a one-time replacement into a root-cause route.

Field record checklist

  • Fault timing
  • Motor connected state
  • Output accessory list
  • Cable/motor evidence
  • Phase-leg clue
  • AGDR label
  • Module label
  • Previous repair outcome

Technical basis and reference documents

This is an independent editorial technical reference. Original manufacturer documentation remains controlling for installation, repair and commissioning decisions.

ACS800 Standard Control Program Firmware ManualABB Library

OEM basis for ACS800 SHORT CIRC 2340, PPCC LINK 5210, FAULTED INT INFO and INT SC INFO context.

ACS800 hardware manualABB Library

OEM basis for hazardous-drive safety, cabinet structure, power-module and control/interface hardware context.

ACS800 SHORT CIRC field-service discussionPLCtalk

Public field discussion showing why 2340 cases can involve AGDR/module evidence, vibration, dust and repeat-failure conditions.

Diagnostic workflow

Evidence intake

Turn this record into a qualified service request

A repair decision is much more reliable when the request includes the exact identity of the drive, the first fault evidence and the machine condition when the symptom appeared.

  • Complete drive type code / MLFB or nameplate model
  • Fault code, fault value and first event before reset
  • When the event appears: power-up, enable, ramp, run, decel or stop
  • Motor/cable connected or isolated during the symptom
  • Visible board, option-card, module and connector identifiers
  • Previous repair history, replacement parts and repeat-failure pattern
Prepare request →