Industrial networks
EtherNet/IP, PROFINET, Modbus, serial links, OPC UA and fieldbus: setup, faults and design.
Latest articles
Troubleshooting
Reaching PLC-5 and SLC 500 data through a ControlLogix DH+ bridge
Yes. An OPC UA server reaches PLC-5 and SLC 500 processors through a ControlLogix Ethernet-to-DH+ bridge when its Allen-Bradley driver documents routed legacy access. Confirm the driver, inventory the bridge modules, build each connection path to the DH+ node, and prove one read — the 1756-DHRIO carries 32 connections per DH+ channel.
Troubleshooting
Why online editing slows a DH+ network and how to fix it
Editing slows because an online edit, every HMI poll and every controller MSG shares one 57.6 kbit/s token-passing DH+ trunk, and the edit bursts are the largest frames on it. Raise the whole segment to 230.4 kbit/s when every node supports it and the trunk is within 2,500 ft; otherwise segment DH+ and bridge through a ControlLogix gateway so editing stops competing with every station.
Troubleshooting
How to reach a PLC-5/30 DH+ network from a PC HMI driver
Pick the physical route before the driver. A PLC-5/30 has no Ethernet port, so the working options are DF1 over the channel 0 serial port with SerialDF1forPLC5Com, or a 1756-DHRIO bridge in an Ethernet-reachable ControlLogix chassis with EthernetIPtoDHRIOforPLC5Com1. Serial at 19200 baud carries a typical screen load in well under a second when tags are read as blocks, so measure before you buy the bridge.
Troubleshooting
Why explicit and implicit EtherNet/IP messaging do not interwork
Explicit messaging is request/response CIP over TCP between a client and a server; implicit messaging is a scheduled I/O connection between a scanner and an adapter. The four roles are implemented and configured independently, so one endpoint can lack exactly the mode the other needs, and a reachable IP address proves nothing. Match each endpoint's documented roles, assemblies and byte lengths before you blame the network.
Troubleshooting
Speeding Up Modbus RTU Writes Behind Polled Reads
The writes are slow because the Modbus client driver owns the serial port and services one enabled instruction at a time, so a write queues behind every enabled read. Put each transaction in its own stage, put the write stages first, and advance the chain on completion; a write then waits at most one in-flight transaction.
Troubleshooting
Why a Micro850 will not read tags over a DF1 I/O server
A Micro850 serves variables through a Modbus map you build in Connected Components Workbench, not through DF1 or ABLOGIX I/O servers, because its memory has no data-table files for those drivers to read. Map each variable, poll the mapped range with an independent Modbus client on unit identifier 1, and set the tag address to the offset that actually answers.
How-to
Set up a PSTX softstarter on EtherNet/IP with a ControlLogix
Set parameter group 12 on the PSTX first: 12.02 FB interface connector to Anybus, 12.03 Fieldbus control to On, and a static address in 12.05, 12.06 and 12.07 with 12.08 DHCP OFF. Then add a Generic Ethernet Module in Studio 5000 with input assembly instance 100 at 12 words and output assembly instance 150 at 5 words; any other size and the starter rejects the connection.
Explainer
What an EtherNet/IP IO-Link master exposes to your PLC
Full access to every port is decided by three documented items: the mode each port is configured in, the master's EtherNet/IP data map, and your PLC's client functions. Process data travels on the cyclic I/O connection; parameters need explicit CIP requests, and at 100 devices polled every 10 ms you would need 10,000 transactions per second, so bulk data belongs on the assembly connection.
Selection guide
Choosing a CP-341 or gateway for an S7-300 Modbus RTU slave
For an S7-300 that must answer as a Modbus RTU slave, a PROFIBUS DP-to-Modbus RTU gateway is the lower-effort route: no separately licensed loadable driver and no serial code in the CPU. Choose the CP-341 with its Modbus Slave (RTU) driver only when the link must be independent of the fieldbus or when you need a per-write flag such as CP_NDR. Before ordering, confirm the exact gateway variant runs DP slave and Modbus RTU slave simultaneously.
How-to
Read a CP1W-CIF41 IP address from PLC memory over USB
Connect to the CPU over USB with CX-Programmer, read the CP1W-CIF41 address words in hexadecimal, CP1E Port 2 at D1303, CP1H/CP1L at D32003 or D32303, and convert the four bytes to dotted decimal. The default 192.168.250.1 is a shipping reference only, so trust the words and confirm with ping.
Troubleshooting
Connecting Factory I/O to a local CODESYS soft PLC over OPC UA
Yes: OPC UA only carries tag values, so the ladder or structured text must run in the CODESYS runtime. Fix the connection in order: prove the engineering path through the Gateway to the runtime first, then the OPC UA endpoint at port 4840, then map each scene point to one variable. Keep Control I/O out of it, because Factory I/O runs one driver at a time.
Troubleshooting
Why ctrlX I/O Engineering shows bits instead of byte mapping nodes
The mapping tree follows the installed ESI descriptions. With only the Balluff BNI ECT-508-105-Z015's own ESI present, ctrlX I/O Engineering and native CODESYS both show bits; the byte nodes came from mixing other Balluff ESI files, a defect reported fixed in release 1.20. Map the bits now and update the tool.