Industrial networks
Earlier articles
Troubleshooting
Why CODESYS EtherCAT master xError stays false on cable pull
`EtherCAT_Master.xError` stays FALSE because the master does not latch slave loss into the application variables when restart handling is off; the engineering tool reads device state directly, so it still shows the error. Tick `Automatically restart slaves` on the master and `Enable Diagnosis for Devices` for the extended instance, then pull-test: the loss reaches the program and the slave rejoins when the cable returns.
Troubleshooting
Troubleshooting ControlNet scanning of legacy 1771 specialty I/O
When a legacy 1771 specialty module will not scan over ControlNet, separate three layers before touching hardware: the chassis backplane allows two master/slave connections and each expander-class module takes one, the TIC-chip ASIC conflict applies to specific pairs only, and RSLogix 5000 gives you no configuration wizards for 1771 block transfer. Bench-test the exact module-and-chassis combination before go-live.
How-to
Read and write Logix tags from CODESYS with CIP GenericService
Read a Logix tag from CODESYS with CIP service 16#4C against the tag's Symbol Object instance at class 16#6B: send a two-byte element-count body, expect a two-byte type word first (16#C4 is DINT), and take the DINT value from bytes 2-5. Write with service 16#4D, sending type word, element count, then data. Rebuild the name-to-instance table after every download or online edit, because the controller reassigns instance numbers.
How-to
Reach a CompactLogix through a ControlNet bridge in RSLinx
When autobrowse through a 1784-U2CN ControlNet path lists the bridge's EtherNet/IP module but no CompactLogix or third-party EtherNet/IP devices, add the target IP address manually under that module's Ethernet port in RSWho or the FactoryTalk Linx browse tree, then select the resulting device as the online path in the Logix programming software. The devices are reachable; only discovery fails, and a manual entry needs no discovery.
How-to
Link an SLC 5/05 and MicroLogix 1100 over DH-485
Run a dedicated DH-485 serial network: a 1761-NET-AIC+ on the SLC 5/05 serial channel and a 1763-NC01 from the MicroLogix 1100, unique node addresses at each end, 120 Ω termination at both bus ends. A 20-word exchange at a 1 s period loads 9600 bit/s to about 25%, and a heartbeat watchdog set to three missed cycles makes the link fail safe.
Selection guide
How to select a CODESYS fieldbus master for industrial Ethernet
Select the master around the device, not the connector: the 750-340 is a PROFINET IO coupler, and a PROFIBUS station needs a different coupler. Confirm three matches — device protocol, runtime master package, supported network adapter — then size the bus cycle from the process budget; the worked example clears a 10 ms sensor-to-actuator budget at a 2 ms cycle and fails it at 4 ms. Bench-test a laptop NIC only if the runtime documents it.
How-to
How a PLC runs two Modbus networks at the same time
Yes. Each serial port is its own independent link: the HMI polls the PLC on one port while the PLC acts as master, or slave, on a separate RS-485 Modbus RTU network. The two links share no settings — only their endpoints must match — and PLC copy logic moves any data between them.
Troubleshooting
Connecting STARTER to a PROFIBUS drive through an S7-300
Being online with the S7-300 does not put STARTER online with the drive. Confirm the drives are on PROFIBUS, make the drive's station address match the one the project expects, select the routed path through the S7-300 in STARTER, and save the new parameters to EEPROM with P0971 = 1.
How-to
CompactLogix MSG to SLC 5/04 through a DH+ gateway
The CIP path in the CompactLogix MSG ends at the 1756-DHRIO module in the remote chassis. On the MSG configuration tab, change the communication method from CIP to DH+, then enter Channel A and the SLC 5/04 node address in the DH+ fields; the SLC is never part of the path itself.
Selection guide
Choosing PLC to SCADA communication over long distances
For PLC-to-SCADA communication over long distance, choose the transport by reach and connection behavior: fiber Ethernet for a continuous long link (one span rated 2 km), RS-485 where serial fits, extenders or radio on existing pairs, dial-up or leased-line modems on phone service. Direct copper Ethernet fails at 100 m per segment; the SCADA driver or OPC service, not the PLC's ASCII modem commands, carries the protocol.