Features:
- Role separation: prevents the controller Basic Unit from being confused with the visually related expansion hardware.
- Evidence-led receiving: uses exact markings and physical arrangement for comparison without inventing undocumented ratings.
- Migration readiness: turns the existing terminal and I/O relationships into a recoverable cabinet inventory.
For a legacy MasterPiece 40 installation, the key maintenance decision is whether to preserve the controlling Basic Unit or use the outage to begin a wider platform migration.
The visible markings establish identity and arrangement, while electrical behavior and wiring responsibility remain governed by the plant drawings; this keeps the receiving decision tied to the actual cabinet.
Before removal, the cabinet should be documented as a connected system so either an exact replacement or a migration design can recreate the required control and I/O relationships.
Apter Power supports legacy-system sourcing and condition review for the ABB MASTERPIECE 40 CT473 GJR6101400R5 MasterPiece 40 Basic Unit, based on exact identity and cabinet context.
ABB MASTERPIECE 40 CT473 GJR6101400R5 MasterPiece 40 Basic Unit Manuals,Datasheets,Link
Important Notice: No qualified exact-model English PDF is attached. Use the complete product model in every document request.
- Platform: retain MasterPiece 40 in the equipment record.
- Type: match the CT473 marking before procurement.
- Article: use GJR6101400R5 as the full material check.
- Primary assembly: treat the unit as the controller base, not an expansion.
- I/O boundary: preserve every documented terminal assignment.
- Expansion relation: record any connected CX472 unit before isolation.
- Obsolete platform: plan around the complete installed system.
- Application record: recover logic, I/O, and operational sequences.
- Acceptance: define functional tests before removing the original controller.
- Legacy controller support: exact Basic Unit replacement in an installed MasterPiece 40 system.
- Outage preparation: terminal, logic, and expansion-unit documentation.
- Migration discovery: recovery of the original controller and I/O boundary.