Scope of this technical record
Use this workflow before re-energizing an ACS800 that has reported 2340 or has had IGBT, AGDR, driver or output-stage repair work.
This workflow defines evidence order, not live probing instructions. Qualified personnel must make the drive safe, verify stored energy is discharged and follow the exact ACS800 hardware documentation.
ACS800 short-circuit pre-power route
The route defines stop conditions before re-energising a repaired output stage.
Pre-power evidence order
The safe sequence is field evidence first, then static output-stage evidence, then driver relationship, then repair boundary. Reversing the sequence turns the drive into a test load for expensive modules.
A good workflow answer states what was proven, what remains unknown and what condition must be satisfied before any staged power check.
Pre-power check sequence
| Step | Evidence to capture | Decision produced |
|---|---|---|
| 1. Fault history | Exact 2340 timing and prior repairs | New fault or repeat failure |
| 2. External path | Motor cable, motor, output accessories | External cause cleared or still suspect |
| 3. Static bridge | U/V/W and module evidence | Bridge area credible or abnormal |
| 4. Driver path | AGDR label, connector, driver channel condition | Driver route clear or needs repair |
| 5. Service decision | Evidence package and risk | Repair, donor unit, staged test or modernization |
Stop conditions before any energizing
Stop if the motor/cable path is not documented, if a driver connector is damaged, if the same module failed after a previous repair, if the cabinet has conductive dust or vibration damage around the output stage, or if the type code/module identity is unknown.
The final decision should not be 'try it and see'. It should be a written boundary: external correction, module repair, AGDR repair, feedback/protection investigation, donor-unit match or modernization.
Field record checklist
- Fault history
- Motor/cable proof
- Static bridge evidence
- Driver connector photos
- Module identity
- Repair boundary
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.
Routes ACS800 2340 cases through motor cable, motor winding, terminal box, output accessories and output contactor evidence before internal power-stage repair is assumed.
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.
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.
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