Industrial networks
Earlier articles
How-to
How to add a DeviceNet drive node to an SLC 500
You cannot add the node from RSLogix alone. A DeviceNet configurator such as RSNetWorx for DeviceNet is required, reached either by pass-through over your DH-485 connection or through a DeviceNet interface card, and on a 1747-SNB or 1747-SDN scanner you place the drive's input and output words in the scan list by hand.
Troubleshooting
How a SCADA client reads a small PLC over EtherNet/IP
An Ethernet link to a MicroLogix is not a working SCADA read: the controller serves data through PCCC commands carried over EtherNet/IP, and a client without that application service gets every read rejected. Check the driver's documented controller list for PCCC over EtherNet/IP or use the controller's documented Modbus TCP server, then prove one read-only value end to end.
Troubleshooting
Fixing CODESYS Modbus TCP server exception 0x0002
Exception 0x0002 means the CODESYS Modbus TCP server holds no point at the address the client requested. The Data Model start-address fields are offsets within each data type's standard range, so entering 10001 for Discrete Inputs pushes the first bit to reference 20002. Set each start address to 0, confirm the client's notation, then prove one point with a scanner.
Troubleshooting
Fixing a TwinCAT EtherNet/IP slave connection from an Omron PLC
The CIP1 fault is a Forward Open mismatch: each Omron direction must carry the full serialized TwinCAT assembly, not the process variables alone. With 2 bytes in and 2 bytes out, the 4-byte ConnCtrl on outputs and ConnState on inputs make each direction 6 bytes, and the instances must follow producer and consumer roles. If a capture shows the request and a rejection, read the sizes and instances the originator actually serialized.
Troubleshooting
Fix robot Profinet output writes over OPC UA
Set the Profinet Internal Device Input Size and Output Size to 64 bytes each, under Controller tab, Configuration, I/O System, Profinet Internal Device, and robot output writes reach the PLC array. The failing direction, not the OPC UA status number, identifies the cause: a Bad-class write with the other direction working means the output byte image is missing.
Explainer
Designing a 1734-AENT Point I/O fiber ring on EtherNet/IP
Yes — enable IGMP snooping on all seventeen switches: the input data a 1734-AENT adapter produces is multicast, so without it every switch floods the ring and all sixteen adapters reject each other's packets. Full-duplex switching ends collisions but not congestion, each fiber span must meet its own optic's distance limit, and ring recovery must beat four times the RPI.
How-to
Connecting an S7-1200 to a PROFIBUS slave through a CM 1243-5
An S7-1200 cannot speak PROFIBUS from any built-in port: its onboard Ethernet is PROFINET. PROFIBUS DP-V1 master duty needs the CM 1243-5 communications module in the S7-1200 rack. Confirm the remote device is a PROFIBUS slave, import its GSD into TIA Portal, give it a bus address no other station uses, and terminate the segment at both ends.
How-to
Configure ControlLogix MSG reads and writes to a PLC-5
DH+ is peer-to-peer token passing, so there is no master or slave to configure: make the ControlLogix the single initiator with one MSG instruction per direction, each on its own MESSAGE control tag, configured as a PLC-5 typed read or typed write with the route browsed on the Communication tab. Verify the transferred value at the destination address, not the online session.
How-to
Configure a PowerFlex 525 on EtherNet/IP from an Omron NJ301
The tag data link fails after a good ping because the NJ, as the EtherNet/IP originator, must send the drive's chosen output assembly plus a 32-bit Run/Idle header: error 0x0127 means the output connection size is wrong. Import the revision-matched EDS, select the target assemblies it lists, create Input and Output network variables of exactly those sizes with the header included, and register them on the Tag Set tab.
How-to
Choosing the DeviceNet configuration connection path
RSNetWorx for DeviceNet cannot reach a 1769-SDN through the MicroLogix 1500 serial port: that port talks to the controller, not to the trunk. Configure the scanner from a direct DeviceNet interface such as a 1770-KFD or 1784-PCD, or route through a Logix controller port such as Ethernet on an L32E. RSNetWorx is still required for scan-list work; Auto-Configure covers only simple I/O blocks.
Explainer
Can a Modbus write change PLC outputs?
Yes, but not by outrunning the scan. On a Modicon CPU the communication interface reaches data memory only between scans, so a write is applied whole and the next scan either consumes it or overwrites it. The real exposure is that Modbus TCP authenticates nothing: any host that can reach the CPU can write an unprotected holding register your logic unpacks into outputs, so pack status into read-only words, keep commands in a separate writable range, and enforce write protection with an IP access control list.
Troubleshooting
Why Modbus RTU drive polling on one serial port is slow
Modbus RTU carries one request-response transaction at a time, and at 19.2 kbit/s each drive transaction costs 40-60 ms, so 18 drives polled with a read and a write each need about 1.5-2.5 s per cycle no matter how the messages are chained. Cut the transaction count, schedule command writes ahead of status reads, set each drive's communication-loss timeout above the finished cycle, and change networks when the arithmetic cannot meet the update rate.