Control / inverter-interface communication

ABB ACS800 PPCC Control-to-Inverter Interface Path

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.

Circuit path record11 min read

Scope of this technical record

Use this path to follow ACS800 PPCC evidence from control power through the link and inverter-interface hardware before any board replacement decision.

Safety boundary

This is a service evidence map for qualified personnel. Do not access internal control or interface hardware until all hazardous supplies and stored energy are made safe.

ACS800 PPCC interface route

1RMIO supply
2PPCC link
3INT / AINT
4PBU branch
5Inverter boundary

The circuit path keeps 5210 on link and supply evidence.

ABB acs800 ppcc control power interface evidence image

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

A PPCC path has three different service zones

The PPCC route begins at the control electronics, passes through a link medium and ends at inverter-interface electronics. In some arrangements it then continues through branch hardware to a particular inverter module. Each zone must be proven separately because the symptom at the panel can be the same when the failed zone is different.

Control-power evidence includes RMIO/RDCU supply, external 24 V wiring, panel state and any branch loads. Link evidence includes fibre or connector condition and routing. Interface evidence includes INT/AINT board identity, branch mapping and module relationship.

Interface path evidence

ZoneEvidenceRepair boundary
Control sideRMIO/RDCU power, external 24 V, panel stateControl unit or supply route
Link mediumFibre/connector condition, routing, strainCable/link service
Interface sideINT/AINT label, PBU branch, module suffixInterface or branch route
Power stageOnly if output-stage evidence existsAGDR/IGBT route, not PPCC alone

What not to infer from the path

The PPCC path does not, by itself, prove a motor, cable or IGBT failure. It also does not prove that the first named board is bad. It proves that the communication/status route between control and inverter interface is not credible enough for operation.

The correct evidence package ties the fault to timing, control supply, link condition and physical branch identity. That package is what makes board repair or donor-board selection possible.

Field record checklist

  • Control unit power
  • External 24 V
  • PPCC medium
  • INT/AINT label
  • PBU branch
  • Module suffix
  • Output-stage co-fault

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.

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 →