The available evidence shows a layered ControlLogix architecture, but it does not establish which network owns each remote I/O rack. The presence of Dupline, Modbus, Ethernet, and a ProSoft module does not by itself prove the communication path between a rack and the central controller.
Separate the Confirmed Components from the Unknown Links
| Component | Confirmed function or connection | What remains unknown |
|---|---|---|
| ControlLogix controllers | Control the crushing and conveyor system. | Which controller owns each remote rack and over which network. |
| CPU-less remote racks | Contain I/O, RTD, and encoder-counter modules. | The rack adapter type and its controller connection. |
| Dupline | Connects pull-cord switches distributed along conveyors over a two-wire fieldbus. | Where its controller-side interface terminates and how its data enters ControlLogix. |
| ProSoft module | Reportedly provides a Modbus interface. | Its Modbus role, peers, mapped data, and relationship to remote I/O. |
| Ethernet | Exists in the installation. | Whether it carries controller, remote I/O, supervisory, or other traffic. |
Why Remote I/O Panels and Dupline Can Coexist
The two systems can serve different collection layers. The CPU-less racks concentrate nearby I/O, RTD measurements, and encoder signals in distributed panels. Dupline carries the pull-cord signals positioned along conveyors, some of which exceed 5 km. This arrangement reduces long parallel cable runs while accommodating both panel-mounted signals and widely dispersed field devices.
Do not interpret the ProSoft module as proof that Modbus connects every remote rack to the ControlLogix CPU. It may exchange data with remote I/O, a Dupline interface, or another device; the evidence does not identify its peer or data map.
Trace the Actual Communication Path
- Trace the two-wire Dupline cable from the pull-cord switches to its interface. Record the interface's controller-side cable and destination.
- Identify the communication adapter in each CPU-less rack. Compare its physical port and cable destination with the ControlLogix project configuration to determine the owning controller and network.
- Inspect the ProSoft module configuration and wiring. Record its protocol mode, communication channel, peer addresses, and mapped ControlLogix tags without assuming that it owns the remote racks.
- Trace the Ethernet connections and match each connected device to the controller configuration and network drawings.
- Under the site's approved test procedure, operate a permitted pull-cord test point and observe where its state first appears, then follow the mapped value through the Dupline interface, any gateway, and the ControlLogix logic.
The resulting path should identify each link explicitly: field device, fieldbus or wiring, interface or rack adapter, controller network, and consuming ControlLogix tag. If the drawings, module configuration, and observed signal path disagree, treat the architecture as unresolved until the discrepancy is corrected.
FAQ
Does Modbus connect the remote I/O racks to ControlLogix?
The evidence does not confirm that. Identify each rack's communication adapter and its configured owner before assigning Modbus that role.
What does Dupline do in this conveyor system?
Dupline connects pull-cord switches distributed along the conveyors through a two-wire fieldbus. Trace its controller-side interface to determine how those states enter ControlLogix.
Why use remote I/O panels when the conveyor already has Dupline?
The remote panels contain I/O, RTD, and encoder-counter modules, while Dupline carries distributed pull-cord signals. They can therefore collect different device groups within the same control architecture.