Scope of this technical record
Use this record to document RMIO/RDCU, INT/AINT and PPCC branch evidence before a board repair, donor-board purchase or modernization decision.
This record does not authorize board removal. It defines what qualified technicians should document before internal service work changes the evidence.
ACS800 RMIO / INT-AINT evidence route
Board identity and link route must be known before parts decisions.
ABB acs800 rmio int aint interface evidence image
Board names must be tied to their route
The same ACS800 support request may mention RMIO, RDCU, INT, AINT, PPCC or PBU. Those names are useful only when tied to the function in the fault path. RMIO/RDCU evidence belongs to control and I/O handling. INT/AINT evidence belongs to inverter interface. PBU evidence belongs to branch routing.
A good record includes label photos, cable route photos, board revision where visible, the fault order and whether any board was already replaced. Without that information, a donor-board decision is weak.
Evidence for repair intake
The evidence should make it possible to decide whether the case is a control unit issue, interface-board issue, branch routing issue, connector/link issue or output-stage co-fault.
Board evidence checklist
| Evidence | Why it matters | Decision supported |
|---|---|---|
| RDCU/RMIO label | Identifies control-unit family | Control repair or donor-unit route |
| INT/AINT label | Identifies interface side | Interface repair route |
| PBU/branch photo | Maps module route | Branch-specific investigation |
| Fault order | Separates first cause from secondary faults | Safe service route |
| Previous parts | Flags repeat-failure risk | Cause review before replacement |
Field record checklist
- RDCU/RMIO label
- INT/AINT label
- Branch photos
- Fault order
- Previous parts
- Output-stage co-faults
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 circuit records
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 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.
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