Industrial networks
Earlier articles
Troubleshooting
SCADA gateway cycles Connecting and Disconnected: subnet fix
When one SCADA gateway cycles between Connecting and Disconnected while another reaches the same PLC, the endpoints disagree about addressing. In the case behind this article a /16 site network met a PLC still set to /24: the test gateway reached the PLC, but the PLC sent its replies to a router that was not there. Compare both masks with the AND arithmetic shown, then test the PLC's TCP service port from the gateway host instead of ping.
How-to
Safe Modbus writes to PLC output registers from SCADA
A Modbus write can command physical outputs whenever PLC logic copies the written word to output commands, so never map one word as both status and command. Keep a PLC-written status word that clients only read, route remote control through a separate request register validated against permissives each scan, and verify the map before go-live.
Troubleshooting
Reading Modbus TCP from a ControlLogix PLC without a gateway
Yes — ControlLogix reads Modbus TCP without a gateway card through Rockwell's sample Modbus TCP driver, but only on controller firmware version 20 or later with socket-capable Ethernet hardware such as a 1756-EN2xx module at firmware 5.007 or later. If either side misses the gate, use a standalone EtherNet/IP to Modbus TCP converter. When the driver runs, prove one request against a known-good PC client and match unit ID, start address and count field by field.
Troubleshooting
Reading Modbus RTU writes into a CJ1W-SCU31-V1 slave area
The CJ1W-SCU31-V1, configured as a Modbus RTU slave, stores each master write in its allocated slave data area by itself, so there is no ladder receive instruction to add. If the area starts at D0, holding register 40001 maps to D0 and 40010 to D9, and the CJ2M ladder reads those D words directly. Fix the Micro850 MSG_MODBUS errorID 21 local channel configuration error before testing any data.
How-to
Passing SLC 5/03 data to a CompactLogix over Ethernet
Put a DF1-to-Ethernet gateway on the SLC 5/03's free Channel 0 serial port: an ENI-style unit lets the CompactLogix message SLC data-table addresses, and a protocol-mapping converter moves SLC files into CompactLogix tags on its own schedule. For one analog value between nearby panels, wire an analog output straight to an analog input instead. Configure Channel 0 for DF1 full duplex, add staleness logic, and prove the link with two test values across the range.
Troubleshooting
Modbus exception 02 when a read crosses a register map gap
The exception is correct: a Modbus block read requests consecutive registers, so a span from 754 through 788 includes the undefined 764-767 gap and the meter rejects it with exception 02, illegal data address. Read the 754-763 setup block at startup and after configuration changes, keep continuous reads inside the 768+ measurement area, and publish the last fully accepted set to your calculation logic.
How-to
Linking Modbus RTU BMS SCADA to a redundant S7-1500R
Use one Modbus RTU-to-TCP gateway as the Modbus TCP client, and run the Modbus TCP server on the S7-1500R system IP address that switched communication moves to the surviving CPU. The BMS keeps polling its RS-485 link unchanged; on a switchover the TCP session drops and the gateway reconnects. Set the comm-fail timeout to the measured gap plus one poll interval: 3 s at a 1 s rate in the example.
How-to
How to route a ControlLogix MSG to a PLC-5 over DH+
The CIP path is 1,5,2,10.60.28.60,1,2 and it ends at the 1756-DHRIO: out the local backplane to the ENBT/A in slot 5, over Ethernet to the bridge ENBT/A at 10.60.28.60, then across the bridge backplane to the DHRIO in slot 2. DH+ carries no CIP, so Channel A and DH+ node 67 are set on the message's communication tab, never appended to the path.
How-to
How to read CompactLogix tags from a C# SCADA application
Yes: a C# application reads a CompactLogix by acting as an EtherNet/IP client that requests the controller's symbolic tag read and write services over TCP port 44818. For ten tags, build that client directly and skip the OPC server; choose the documented Modbus TCP sample code for 5370 processors only when you need a register interface.
How-to
How to map a 1747-SDN scanner for DeviceNet drive control
Seeing the drive in an RSNetWorx browse is not an I/O connection. Put the drive in the 1747-SDN scanlist, read the M-file words the scanner mapping assigns, and reference those mapped words in the SLC 5/04 ladder. A node address is not an integer-file offset: the mapping view, not node 10, decides where each command and status word lives.
How-to
How to connect PROFINET IO to a CompactLogix through a gateway
A CompactLogix cannot act as a PROFINET IO controller, so an EtherNet/IP-to-PROFINET gateway does the job: it is an EtherNet/IP adapter to the controller's scanner and the PROFINET IO controller to the field devices. The one reported gotcha on a 1769-L18ER-BB1B with a PLX82-EIP-PNC was byte swapping on both the input and output maps, fixed in the gateway rather than in ladder.
How-to
How to build a virtual PLC test bench for protocol practice
One laptop runs the whole bench: a Modbus TCP server simulator, a master test client, a Node-RED OPC UA server and a SCADA trial connect over loopback, so you can practice addressing, sessions, scaling, alarms and fault diagnosis without a PLC. Work through three bounded projects and finish with seven pass criteria you can defend.