Scope of this technical record
Functional circuit record linking ACS800 output-stage short-circuit events to the driver and IGBT assembly boundary.
No gate-driver energised testing values are asserted on this page. Use qualified procedures and exact board drawings where available.
The gate-drive path in fault analysis
The output bridge receives commands through gate-driver electronics and delivers switched phase output to the motor. When the converter reports SHORT CIRC, a damaged IGBT is one possible result, but the repair analysis must also cover the circuitry that drove and protected that device. A gate-driver failure can be a secondary consequence of an IGBT event, or the initiating cause of repeated failure.
A useful circuit page therefore documents the relationship rather than pretending to supply universal readings: control/interface command, driver assembly, upper and lower switching devices for U/V/W phases, motor-output path and fault localisation.
Relationship to INT SC INFO
The ACS800 firmware makes the diagnostic relationship unusually actionable by providing phase-leg location information for short-circuit events: U, V and W phases, with upper- and lower-leg distinctions. This evidence can be bound to the driver/power assembly record so that inspection focuses on the affected section and associated components.
Phase-leg interpretation
| Firmware evidence | Hardware area to correlate | Repair caution |
|---|---|---|
| U/V/W upper-leg short indication | Corresponding upper switch and driver path | Do not assume only the semiconductor was affected |
| U/V/W lower-leg short indication | Corresponding lower switch and driver path | Review complementary switching/protection context |
| No credible localisation retained | Whole output path remains uncertain | Do not make narrow parts assumptions |
Failure recurrence prevention
Before any returned-to-service test, document that output-side causes have been considered and that the replacement assembly matches the installed unit. Repeat failure after an apparently successful module replacement is a strong indication that the repair boundary was too narrow or the external initiating condition remains present.
Evidence required before describing a gate-drive repair
A gate-drive page must not manufacture precision from a fault code. A publishable case needs an identified assembly, an identified fault location or damage area, a documented inspection of associated switching and protection hardware, and a controlled confirmation result. A case that merely says “IGBT changed and machine works” is not sufficient to establish a reusable driver diagnosis.
As real cases accumulate, the page can connect specific assembly identifiers to failure patterns such as one phase-leg event, recurring failure after replacement or short circuit following output-cable damage. Until then, the page correctly remains a functional relationship and decision framework rather than an unsupported component-level test manual.
Field record checklist
- Preserve phase-leg localisation evidence.
- Tie any assembly replacement to exact identifier and fault context.
- Review output cable/motor and protection/driver boundary before energising.
Technical basis and reference documents
This is an independent editorial technical reference. Original manufacturer documentation remains controlling for installation, repair and commissioning decisions.
Fault tracing, PPCC LINK (5210), SHORT CIRC (2340), FAULTED INT INFO and INT SC INFO.