Scope of this technical record
Use this workflow when an ACS800 has repeated 2340 trips, failed again after module replacement or damaged AGDR/IGBT hardware more than once.
Repeated output-stage failure is a stop condition. Do not energize another replacement module until the driver, output path and original initiating cause have been documented.
ACS800 AGDR / IGBT repeat-failure route
A repeat module failure is a stop condition until the driver and external initiating cause are documented.
A repeated failure changes the diagnosis
After a first destructive fault, the damaged part may be the symptom. After a second destructive fault, the missing evidence is usually the problem. The record must reconstruct what was replaced, why it was replaced, how long it operated and what failed next.
The repeated-failure route keeps three possibilities open: the external output fault was never removed, the AGDR/driver path is damaging new modules, or the IGBT/module damage has damaged the driver/protection path in return.
Repeat-failure decision table
The table below helps classify the next service action from evidence rather than from the repeated fault label alone.
AGDR / IGBT repeat-failure classification
| Evidence | Likely route | Do next |
|---|---|---|
| Same leg fails again | Driver/channel or external phase route | Compare AGDR channel and output cable path |
| New module fails at first run | Original cause not cleared | Stop and reconstruct external plus driver proof |
| Visible AGDR damage | Driver route affected | Do not fit module alone |
| Fault only with motor connected | External output route | Clear motor/cable/accessory boundary first |
Repair or modernization boundary
When repeated failures involve scarce modules, mixed board revisions or uncertain driver damage, modernization may be more reliable than repeated donor parts. The service record should present that decision as an equipment-risk judgment, not as a sales conclusion.
The final evidence package should include the original failure, every replaced part, module and AGDR labels, output path proof, contamination/vibration conditions and the controlled test result that followed the repair.
Field record checklist
- Original fault
- Replaced parts
- Run time after repair
- Same leg or different leg
- AGDR condition
- Output path proof
- Contamination/vibration notes
Technical basis and reference documents
This is an independent editorial technical reference. Original manufacturer documentation remains controlling for installation, repair and commissioning decisions.
OEM basis for ACS800 SHORT CIRC 2340, PPCC LINK 5210, FAULTED INT INFO and INT SC INFO context.
OEM basis for hazardous-drive safety, cabinet structure, power-module and control/interface hardware context.
Public field discussion showing why 2340 cases can involve AGDR/module evidence, vibration, dust and repeat-failure conditions.
Linked records
The drive has detected a severe output-side or inverter-bridge condition. A usable service route must separate motor/cable/accessory faults, phase-leg location evidence, IGBT module condition, AGDR gate-driver condition, current-feedback context and prior repair history before another power stage is energized.
This path separates control/interface command, AGDR driver health, isolated driver supply, gate output, IGBT phase-leg condition and motor-output evidence after an ACS800 SHORT CIRC event.
Maps SHORT CIRC evidence from fault timing and localization into U/V/W phase-leg inspection, IGBT module condition, driver relationship and output-stage repair boundary.
Routes ACS800 2340 cases through motor cable, motor winding, terminal box, output accessories and output contactor evidence before internal power-stage repair is assumed.
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