Diagnostic workflow

ABB ACS800 PPCC LINK 5210 Diagnostic Workflow

Entry symptom: An ACS800 displays PPCC LINK / 5210, with or without a module suffix, after power-up, reset, output enable or a previous board/module repair.

Diagnostic workflow12 min read

Scope of this technical record

Use this workflow to convert ACS800 PPCC LINK / 5210 into a control-power, link-medium, branch-interface or repair evidence decision.

Safety boundary

Follow qualified isolation and discharge procedures before internal checks. Do not repeatedly reset or re-enable output with uncertain link or power-stage evidence.

ACS800 PPCC workflow route

1Power
2Link medium
3Branch
4Signal 03.19
5Escalate

The workflow turns 5210 into a branch-specific evidence package.

ABB acs800 ppcc link diagnostic evidence image

ABB acs800 ppcc link diagnostic diagnostic route diagram
The image keeps this ABB case on an evidence route before board or module replacement.

Step 1 — classify when the fault appears

The timing determines the first safe route. Power-up PPCC cases prioritise control supply and link readiness. Post-repair PPCC cases prioritise cable positions, branch mapping and board revision evidence. PPCC combined with output-stage faults requires the destructive-fault route to be respected before powered attempts.

Workflow route by timing

TimingFirst routeEvidence to retain
At control power-upRMIO/RDCU supply and link readinessPanel state, 24 V state, link condition
After module workOriginal branch and connector routeBefore/after photos, labels, fault order
With suffix/module clueINT/AINT/PBU mappingPhysical branch map
With output-stage faultStop and isolate output routeMotor/cable and bridge evidence

Step 2 — choose the evidence package

A technician should leave this workflow with one package: control-power package, link/connector package, branch-interface package, output-stage package or modernization package. Each package has different photos, measurements and risks.

If the package cannot be completed because the drive type code, branch layout or original cable positions are unknown, the immediate task is identification support. A parts recommendation without that evidence is too weak for a high-value legacy drive.

  • Control-power package: panel state, 24 V wiring, RMIO/RDCU label and load evidence
  • Link package: fibre/connector condition, route, strain and cleaned/unchanged state
  • Branch package: INT/AINT/PBU labels, module map and suffix information
  • Output-stage package: external motor/cable proof and static bridge evidence when co-faults exist

Field record checklist

  • Fault timing
  • Control supply
  • PPCC medium
  • Branch map
  • Labels
  • Co-faults
  • 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.

ACS800 Standard Control Program Firmware ManualABB Library

OEM basis for ACS800 fault messages, PPCC LINK context and interface-related status evidence.

ACS800 hardware manualABB Library

OEM basis for cabinet-drive hardware safety, RMIO/control-board and module arrangement context.

ACS800 PPCC field discussionMike Holt forum

Public field-service discussion showing why fibre-link condition and control-power readiness can matter in PPCC diagnosis.

Linked records

Evidence intake

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
Prepare request →