Scope of this technical record
Use this ACS800 hub when a case must be routed between PPCC interface faults, RMIO/RDCU control power, SHORT CIRC 2340, motor/cable evidence, AGDR gate-driver evidence, IGBT module evidence and a repair or modernization decision.
ACS800 service involves hazardous line voltage, stored DC-link energy and internal module connections. Qualified industrial-drive personnel must isolate all supplies, verify discharge and preserve original board, fibre and output-cable positions before internal work.
ACS800 evidence route
ACS800 pages split interface and power-stage faults before expensive board decisions.
ABB acs800 evidence image
Use the first symptom to choose the route
ACS800 service decisions are expensive because the same drive family can present communication-interface faults, control-power trouble and destructive output-stage faults. The first decision is not which board to buy. The first decision is whether the evidence belongs to control electronics, inverter-interface communication, an external output fault, a gate-driver boundary or a power module.
A PPCC LINK case begins with control supply, link medium and interface branch evidence. A SHORT CIRC case begins with output timing, motor/cable proof, phase-leg evidence and driver/module boundaries. Mixing those routes can replace good interface boards or destroy replacement output modules.
ACS800 first-route selector
| Observed case | First route | Do not do first |
|---|---|---|
| PPCC LINK / 5210 | RMIO/RDCU supply, PPCC medium, INT/AINT or PBU branch | Order an IGBT module |
| SHORT CIRC / 2340 at enable | Output path, phase-leg evidence, AGDR/IGBT boundary | Repeated start attempts |
| 2340 only with motor connected | Motor cable, terminal box, output accessories and load | Internal board replacement |
| 2340 after module repair | Previous repair history, driver channel, external initiating cause | Fit another module without driver proof |
The power-stage route needs both external and internal evidence
A 2340 event can be caused by a motor cable or motor winding short, by output accessories connected where they do not belong, by a failed IGBT module, by a damaged gate-driver path or by a feedback/protection route that makes the bridge unsafe. The record must state when the fault appeared and what was connected at that moment.
The AGDR and IGBT boundary is especially important after a repeat failure. A failed semiconductor can damage the driver. A weak driver can destroy a new semiconductor. A contaminated or vibration-damaged cabinet can disturb connectors and repeat the same fault after reassembly.
Evidence needed before repair, donor unit or modernization
A useful ACS800 service package includes type code, frame, fault timing, motor/cable proof, phase-leg or module clue, AGDR label, output-module label, photos of driver connectors and any previous repair history. Without those facts, the safest answer is evidence collection rather than a parts decision.
When the output path is clear and internal damage is proven, the next decision is whether the installed module and driver can be repaired, whether a donor unit is compatible, or whether modernization is more reliable than continuing to source scarce assemblies.
Field record checklist
- Type code and frame
- Exact fault text
- Trip timing
- Motor/cable proof
- Phase-leg clue
- AGDR label
- IGBT/module label
- Prior repair history
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.
Model records
Fault records
The ACS800 reports SHORT CIRC / 2340 at enable, first PWM, acceleration, steady operation or after a repaired module is returned to service.
The ACS800 displays PPCC LINK / 5210, sometimes with a module suffix or branch clue, and the drive cannot safely continue output operation.
The ACS800 reports PPCC LINK, commonly as code 5210, and output operation is blocked or unreliable.
The ACS800 trips on SHORT CIRC during an enable/start attempt or immediately under load.
Board and assembly records
Captures the driver evidence needed to decide whether SHORT CIRC 2340 belongs to external output wiring, IGBT/module damage, AGDR driver damage, current/protection feedback or repeat-failure investigation.
Documents whether a destructive output-stage event is external-output, IGBT/module, AGDR driver, current-feedback or protection-route related before a power module or donor unit is sourced.
Documents the control-to-inverter interface route used when PPCC LINK, branch evidence or control-board power behaviour is part of the service case.
Provides motor-control, I/O and status handling evidence that must be separated from inverter-interface or output-stage failures.
Captures the physical branch evidence needed before a PPCC LINK case is turned into an INT, AINT, PBU, cable or inverter-module repair request.
Forms the repair-critical gate-driver and IGBT switching assembly boundary for applicable ACS800 power hardware.
Carries control-to-inverter interface communication and status used in PPCC LINK troubleshooting.
Circuit and diagnostic records
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.
The PPCC path connects the control side to inverter-interface electronics. Service evidence must keep control supply, PPCC medium, INT/AINT interface and PBU branch routing separate.
This path records how control-board power, external 24 V use, panel state and I/O board identity affect PPCC and dark-control symptoms on ACS800 systems.
This path maps the inverter-interface side of a PPCC case, especially where INT/AINT interface electronics or a PBU branch route the fault to a specific inverter module.
The PPCC diagnostic path links control electronics to inverter interface electronics. A credible repair record must treat supply state, link medium, interface-board status and parallel-module branching as separate test regions.
For applicable higher-power ACS800 hardware, the AGDR-linked driver/module assembly is a repair-critical boundary between the inverter interface control path and the power semiconductor switching stage.
ACS800 SHORT CIRC / 2340 appears during enable, first PWM, acceleration, load operation, or after an output-stage repair.
An ACS800 reports 2340 again after an IGBT, power module, AGDR assembly or output-stage repair, or the same phase leg repeatedly fails.
An ACS800 displays PPCC LINK / 5210, with or without a module suffix, after power-up, reset, output enable or a previous board/module repair.
The ACS800 panel is dark, unstable, externally powered, or reports PPCC-related trouble during a control-power transition.
A PPCC LINK case, cabinet drive or parallel inverter arrangement points toward a specific interface branch, INT/AINT board or module route.
An ACS800 displays PPCC LINK / 5210 or a parallel inverter module reports a PPCC link suffix.
An ACS800 reports SHORT CIRC / 2340, particularly after a failed module or when a replacement power component is under consideration.
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