ABB ACS800 PPCC LINK 5210 Diagnostic Workflow

Entry condition and objective

Use this workflow when ACS800 indicates PPCC LINK or PPCC LINK xx, particularly where the machine is down and there is pressure to change a board rapidly. The objective is to preserve useful fault localisation, identify the actual link architecture and determine whether the likely failure resides in supply, interconnection, interface hardware or a broader power-unit event.

The workflow deliberately stops before unsupported live component probing. The most valuable first result is a defensible isolation of the fault boundary.

Phase 1 — capture evidence before disturbing the drive

Record the complete panel message and whether a module number follows the PPCC indication. Capture the equipment type designation, frame/module arrangement, fault history and recent maintenance or power-stage replacement. Where the site permits parameter/status retrieval before isolation, capture the relevant internal localisation information for parallel modules.

• Exact fault text and timestamp
• Whether the drive is single or parallel inverter arrangement
• Any active powerfail, short-circuit or temperature fault accompanying PPCC LINK
• Control supply method and relevant prior configuration changes

Phase 2 — isolate and inspect the link boundary

After applying lockout/tagout and confirming that the DC link is discharged according to the appropriate hardware manual, inspect the physical PPCC route. Determine whether the configuration uses a galvanic link or fibre-optic link; in a parallel system, identify the PBU branch and numbered inverter module.

Look for disturbed connectors, incorrectly routed or damaged fibre, contamination at fibre ends, missing board supply or evidence of previous unlabelled board swapping. Fibre handling itself can create a second problem, so identify and label the original route before disconnecting any connection.

Phase 3 — controlled decision and recordkeeping

A replacement decision should name the proven failed boundary and preserve the evidence used. For a board replacement, retain the original identifier, revision, the fault/status data and the successful confirmation method. When the fault is cleared only after reconnecting or reseating a link, record this as an interconnect event rather than claiming a board repair.

Where fault recurrence, unidentifiable board revisions or compounded power-stage indications remain, the appropriate output is a specialist repair or modernization decision—not another speculative swap.

Case closure and maintenance feedback

Once the communication path is restored, return the evidence to the maintenance record: fault state before work, affected branch or link, repaired or replaced item, restored status and any recommended monitoring. Where the cause involved contamination, vibration, cable routing or auxiliary power stability, the maintenance response should include prevention, not only restoration.

The commercial value of this workflow lies in the quality of future inquiries. A user who submits the recorded branch, board label and verified supply/link finding can receive far more accurate repair or replacement guidance than a user who submits only a fault message. The website should guide users toward that evidence standard.