Scope of this technical record
Use this path when ACS800 2340 evidence must be mapped to U/V/W phase legs, IGBT module condition, driver relationship and repair boundary.
Do not interpret this page as a powered measurement procedure. It is a safe-service evidence map for qualified industrial-drive personnel.
ACS800 IGBT phase-leg route
Phase-leg evidence identifies where to look; it does not by itself prove why the leg failed.
Phase-leg evidence is location, not root cause
A U/V/W phase or module clue helps focus inspection, but it does not automatically explain why the leg failed. The root cause may be a motor cable, output contactor, load condition, driver channel, feedback/protection route or previous repair error.
A good phase-leg record states both the affected location and the cause boundary that remains to be proven. This prevents the same drive from receiving another module while the initiating condition is still present.
Bridge evidence matrix
The evidence should be organized so the final conclusion is clear enough for repair, donor-module sourcing or modernization planning.
IGBT / phase-leg evidence
| Evidence | Supports | Still must check |
|---|---|---|
| Static short in one leg | Internal bridge damage | Driver and external output cause |
| Fault clears without motor | External path involvement | Motor/cable/accessory root cause |
| Same leg repeat | Driver or repeated external route | AGDR channel and cable route |
| No localization retained | Broad output-stage uncertainty | Do not narrow the parts request too early |
Field record checklist
- Phase clue
- Module label
- Fault timing
- Motor/cable state
- Static bridge result
- Driver relationship
- Repair decision
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.
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