Industrial networks
Earlier articles
Troubleshooting
Fix PROFINET connect errors between a controller and an S7-1200
Separate the engineering port and the PROFINET port onto different IP layers on different physical ports, connect the controller to the S7-1200 directly or through a PROFINET-capable switch, make the device name and address match the project, and run the PROFINET IO task at priority 1 or 0. A scan that finds the S7-1200 proves discovery only; the connect stage is where DB814006 appears.
Selection guide
Connecting ControlLogix to RS232 and RS485 serial devices
Convert the RS232 devices to RS485 at the electrical layer, then pick one master for the whole pair: 1734 ASCII modules for fixed-length or delimited frames, an in-chassis Modbus RTU module for a pure Modbus bus, or an EtherNet/IP-to-serial gateway with a protocol builder when variable-length checksummed frames share the wire with Modbus RTU. One master serializes every transaction behind the 3.5-character silent gap, 3.65 ms at 9600 baud.
How-to
Configure MicroLogix 1100 Channel 0 for Modbus RTU
On the tested MicroLogix 1100 (1763-L16BBB rev. B), Channel 0 is a serial port with a selectable driver — DF1, Modbus RTU Slave or Modbus RTU Master — set in RSLogix Micro under Channel Configuration while Channel 1 keeps carrying Ethernet. Slave mode creates the data files, binary for coils and contacts and integer for input and holding registers; master mode runs MSG instructions against the stations you poll.
How-to
Can one S7 CPU PN port run Modbus TCP and S7 comms together
Yes. A 414-5H's integrated PN interface runs a Modbus TCP server for the DCS and S7 communication for the operator station on the same port, because both are TCP-based services on one IP stack. What decides the project is the CPU's connection-resource total, the station's transport type, the loaded response delay against each timeout — and on an H pair, the fact that Modbus sessions break at switchover unless you use the redundant option on a CP 443-1 pair.
Troubleshooting
Why IO-Link hub outputs stay off despite a valid process image
Setting output bits in the master's I/O mapping commands a hub point, but it cannot turn an input-configured point into an output. Configurable hubs ship with points defaulting to inputs, documented for the Balluff BNI004L and BNI007Z families, and the direction is assigned through the IO-Link parameter path at ISDU index 41h on those hubs. A vendor function block or the master's parameter tool writes it; after that write the same cyclic bits energize the points.
Troubleshooting
Why explicit writes to Omron assemblies fail over EtherNet/IP
Your Set Attribute message carries service code E, which is Get Attribute Single, so it reads, succeeds and writes nothing — and the two codes are transposed, since Set Attribute Single is 10 hex. Even corrected, CS/CJ-series EtherNet/IP units do not accept explicit writes to assembly instances, because that service is optional in the specification. Carry the 240 bytes on a Generic Ethernet Module connection or use CIP Data Table Read and Write messages.
Troubleshooting
Why DF1 reads work on an SLC 500 but not a PLC-5
The DF1 link layer is identical on both processors, so your cable, baud and channel settings are not the fault. The difference is the PCCC command dialect: SLC 500 and MicroLogix answer protected typed logical reads that address data by byte offset, while the PLC-5 answers typed reads that address words. An RTU speaking only the SLC dialect reads nothing from a PLC-5 — set it to PLC-5 mode or get PLC-5 support from the vendor.
Troubleshooting
Why a TM200 READ_VAR reads Modbus data only once
READ_VAR runs one Modbus transaction per rising edge of Execute, so a held Execute never refreshes the data. Drop Execute false for at least one scan, keep Abort off the request rung, and gate each relaunch on Done, Aborted or Error — that sequence turns a single read into continuous polling.
Troubleshooting
Why a Schneider M251 does not appear in RSLinx
RSLinx and FactoryTalk Linx browse one transaction: the EtherNet/IP List Identity request, and a device appears only when the port you are cabled to answers it. Ping and Schneider software prove IP reachability, nothing more. Enable the M251's EtherNet/IP service on the connected port, browse through the right PC adapter, and register the M251 EDS when the entry shows a red X with a yellow question mark.
How-to
Using a PLC as a Modbus RTU to Profibus gateway
Keep the regulator and let one PLC carry both buses. Poll the regulator over Modbus RTU on a fixed cyclic interval, map every register to a defined PROFIBUS DP location with documented scaling, and hand the BMS a data-valid flag instead of stale values. Terminate each bus at its own two ends; never join RS-485 and PROFIBUS into one network.
Troubleshooting
Troubleshooting intermittent PROFIBUS dropouts on an S7-400 network
Save and read the CPU diagnostic buffer before touching anything: the earliest OB86/OB85 entries, mapped against the physical segment drawing, tell you whether the losses share one repeater segment. On a bus that ran seven years and began failing after an encoder tie-in was relocated and re-terminated, one physical-layer fault at that tie-in or its segment's end termination explains all three DP indicators and the self-recovery.
How-to
Set up Micro850E implicit messaging to a Kinetix 5100 servo
The implicit connection to a Kinetix 5100 is created in the Micro850E controller's EtherNet/IP module configuration under Ethernet > Modules, not by a UDFB. The drive is added as a natively supported motion slave, the UDFBs then run above the active connection producing commands and decoding status, and the same controllers accept up to eight generic EtherNet/IP slave devices.