Technical Specifications

FAQ

1. What is the main function of the ABB Bailey PBA200?
The PBA200 is a Process Bus Adapter used in ABB Bailey control-system architectures. Its primary role is to provide the communication interface between the compatible BRC controller and the process-bus network connected to the I/O system. In remote I/O applications, it provides the required path between the controller-side process bus and the HNET/termination-unit side of the system.

2. Which ABB Bailey systems are associated with the PBA200?
The PBA200, ordering number PHCBRCPBA20000, is associated with ABB Bailey INFI 90 and Symphony control-system architectures. ABB documentation also identifies the PHCBRCPBA20000 as a Process Bus Adapter used in remote I/O upgrade configurations, where it is installed together with compatible remote I/O modules, termination units, and process-bus cables.

3. What is the relationship between the PBA200, HNET, and the Termination Unit?
The PBA200 provides the required interface between the controller’s process-bus side and the HNET/Termination Unit side of the remote I/O architecture. This allows process data to travel between the controller and connected I/O equipment. The complete communication path depends on the installed controller, PBA cable, termination unit, HNET network, and remote I/O configuration.

4. Can the PBA200 be used in redundant controller configurations?
Yes. The PBA200 can be used in compatible redundant process-bus architectures. ABB documentation describes configurations using two PBAs and a redundant processor bus adapter cable. In a redundant installation, the cable and connector arrangement must follow the specific controller and PBA architecture because incorrect redundancy wiring can prevent proper communication or failover operation.

5. What should be checked if the remote I/O system cannot communicate with the controller?
Start by checking whether the PBA200 is correctly installed in the controller rack. Then inspect the PBA cables, connectors, Termination Unit connections, and HNET communication path. The status of the associated remote I/O module and controller should also be checked. If the physical connections are correct, review system diagnostics and communication status to determine whether the problem originates from the PBA200, cable, termination unit, remote I/O module, or controller.

6. What can cause intermittent communication through a PBA200?
Intermittent process-bus communication can be caused by loose or damaged PBA cables, poor connector contact, incorrect termination, unstable HNET connections, or problems with the associated remote I/O hardware. Mechanical vibration can also contribute to intermittent contact problems in older installations. Monitoring communication diagnostics and event records while inspecting the physical connections can help identify whether the problem is hardware-related or associated with the network configuration.

7. What precautions should be taken when replacing the PBA200?
Before replacement, place the affected control system in the appropriate maintenance condition and follow the site’s shutdown and electrical isolation procedures. Confirm that the replacement unit is PBA200, ordering number PHCBRCPBA20000, and verify compatibility with the installed BRC controller and remote I/O architecture. Before disconnecting cables, identify their original connector positions and inspect the connectors for damage or contamination. For redundant systems, pay particular attention to the redundant PBA cable arrangement.

8. How should the PBA200 be tested after replacement?
After installation, verify that the PBA200 is securely installed and that all controller, PBA, HNET, and Termination Unit connections are correctly restored. Check the controller and remote I/O diagnostics for communication alarms. Confirm that the remote I/O modules are recognized and that process data is exchanged correctly. In redundant configurations, also verify the redundant communication path and confirm that the system maintains the expected communication and failover behavior.