Industrial networks
Earlier articles
Selection guide
How to choose between Modbus, Profibus and CANopen
Match the protocol to the PLC master that already exists, not to the datasheet that impressed you. Then fit the cable run to the bit rate, because CAN-based trunks shorten as speed rises, and mix protocols one segment at a time through gateways or the PLC itself. A fourteen-device example shows the arithmetic.
Troubleshooting
Why the CODESYS EtherNet/IP scanner runs in demo mode
The scanner runs in demo mode because the installed Fieldbus communication IEC 61784 license covers the PROFINET controller stack, not the EtherNet/IP scanner. Activate the EtherNet/IP Scanner add-on license on the control running the CODESYS runtime and restart it; the 30-minute limit and the license message then clear.
How-to
Connect an Omron PLC to Smart Function Kit Pressing
Use EtherNet/IP between the Omron NX/NJ/NY PLC and the Smart Function Kit Pressing: Omron's EtherCAT runs CoE, the kit's runs SoE, and the two profiles cannot exchange data. Load the Sysmac Studio example project and drive the kit with the SFK_Command, SFK_Fast_Variable_Access, SFK_SerialNumberConverter and SFK_GetNotification blocks.
Troubleshooting
Why Micro850 explicit writes fail to SMC EX600 outputs
Your read works and the write does not because the Micro850 has no EtherNet/IP I/O scanner: its explicit Class 3 messages never supply the Class 1 output ownership the EX600 waits for, so the module holds every channel fail-safe. Set the EX600 documented output force condition, keep service 16 on class 4, instance 150, attribute 3, member 0, and build the write buffer to the documented output image.
How-to
Why RSLinx shows no processor name for a MicroLogix 1100
The MicroLogix 1100 Ethernet port reports its IP address and module type to RSWho, not the processor name, and no RSLinx or controller setting changes that. Label machines by creating one Ethernet Devices driver per machine, named for the machine, holding only that machine's addresses in its station mapping.
Troubleshooting
Fix a Raspberry Pi PROFINET device not reachable in TIA Portal
Discovery in TIA Portal's name-assignment dialog proves only that the Pi's link is visible. Reachability arrives when the CODESYS runtime lets the S7-1200 write the adapter address: set Adapter.0.EnableSetIpAndMask=1 under [SysSocket] in /etc/CODESYSControl_User.cfg, restart the runtime, and retry name assignment on a current runtime.
How-to
Connecting third-party Modbus TCP devices to a Modicon MC80
Yes. A Modicon MC80 under Control Expert Classic exchanges data with any third-party Modbus TCP device through explicit READ_VAR and WRITE_VAR calls plus the device's register map — there is no ESD or EDS import, no IO Scanning and no DTM support. Run the MC80 as the TCP client, keep the exchange in the coil and holding-register tables, and latch each result in the reader so a 16 ms update survives a slower PLC poll.
How-to
Driving a WAGO 750-653 Modbus RTU module from CODESYS
On a CODESYS Control Win V3 soft PLC, WagoAppPlcModbus cannot reach a 750-653 behind a 750-354 EtherCAT coupler, because those blocks need WAGO controller firmware. Drive the module's raw process image yourself: set the serial parameters, move each fragment with the control/status byte toggle handshake, and frame the Modbus RTU request and response in your task. Each fragment costs at least two task cycles, so a full transaction takes ten cycles or more.
Troubleshooting
Why Modbus RTU sends to slave address 0 instead of your device
Address 0 on a Modbus RTU bus is the broadcast address: slaves execute broadcast writes but never reply, so any client waiting for a response times out. If your capture shows 0 as the first byte, the request that actually executes carries the broadcast — verify the CRC, read the raw first byte, then fix the slave ID at the source that feeds that request.
How-to
Setting up a CODESYS Modbus TCP client to talk through a gateway
In CODESYS, Modbus TCP is an application library, not a fieldbus add-on: reference the Modbus TCP Client SL library, point the client at the gateway's IP on port 502 with the gateway's unit ID, and split the map into contiguous blocks of at most 125 registers per request. Every value is a cached copy whose worst-case age is the gateway poll cycle plus your client's map refresh time, so budget both against the freshness the process needs.
Troubleshooting
MicroLogix 1000 not found in RSLinx after a channel change
The MicroLogix 1000 is missing from RSLinx because the channel-configuration download changed its serial port from DF-1 to DH-485, so the DF-1 driver and Auto-Configure can never verify against it. Reach the controller through DH-485 with a 1747-UIC at its default 19200 baud, go online, set Channel Configuration back to DF-1, download, and re-run Auto-Configure.
Troubleshooting
Fix PROFINET device ID read errors in CODESYS scans
A device that answers DCP discovery can still fail the later RPC-based identity read, so the scan reports it cannot read the ID number. Capture one failed scan with the controller diagnostic log and let the trace pick the fix: adapter binding, a filter on the path, a rule for the returning process, or a runtime mismatch.