Scope of this technical record
Use this workflow when ACS800 PPCC evidence points toward INT/AINT interface boards, PBU branches or a named inverter module.
Document branch positions before any change. Moving fibres or branch cables without photos can destroy the evidence needed for a safe repair decision.
ACS800 branch evidence workflow route
The workflow protects the original branch evidence before cables or boards are moved.
ACS800 branch evidence workflow
Build the branch map before parts decisions
The branch map should identify the physical route from control unit to interface board and, where fitted, from PBU branch to inverter module. This map turns a vague communication fault into a serviceable interface case.
A branch map also protects good hardware. If a suffix points to one route, unrelated modules and boards should not be exchanged until that route is proven.
Branch evidence workflow
| Step | Evidence | Decision |
|---|---|---|
| 1 | Original cable/fibre positions | Preserve route |
| 2 | INT/AINT/PBU labels | Identify target hardware |
| 3 | Module suffix / branch clue | Map fault to cabinet |
| 4 | Connector and route condition | Link service or board route |
| 5 | Prior repair history | Repeat-failure or compatibility route |
Field record checklist
- Original branch photo
- Interface labels
- PBU branch
- Fault suffix
- Connector condition
- Prior repairs
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 fault messages, PPCC LINK context and interface-related status evidence.
OEM basis for cabinet-drive hardware safety, RMIO/control-board and module arrangement context.
Public field-service discussion showing why fibre-link condition and control-power readiness can matter in PPCC diagnosis.
Linked records
The drive has lost credible communication or status between control electronics and inverter-interface electronics. The service route must separate RMIO/RDCU control-power evidence, fibre or galvanic PPCC link condition, INT/AINT interface state and PBU branch/module routing before any board is replaced.
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 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.
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