IMDHMIControls LibraryShop main store

Troubleshooting

How to reach a PLC-5/30 DH+ network from a PC HMI driver

Industrial networks Published 6 min read

Short answer

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.

On this page
  1. Why no driver change creates a DH+ connection
  2. Route 1: DF1 over the channel 0 serial port
  3. Measure the serial load before you buy a bridge
  4. Route 2: the Ethernet-to-DH+ bridge
  5. Where the fault sits, layer by layer
  6. Bring the route up in order
  7. The decision for your case
  8. Questions asked

The driver is the last decision, not the first. A PLC-5/30 has no Ethernet port: its communications are the DH+ terminal on channel 1 and the serial port on channel 0. A PC HMI therefore reaches it over exactly one of two physical routes — DF1 through channel 0, or an Ethernet-to-DH+ bridge — and the driver follows from the route: SerialDF1forPLC5Com for the serial link, EthernetIPtoDHRIOforPLC5Com1 for the bridge. EthernetIPforPLC5Com1 is ruled out because it needs an Ethernet port at the processor, and a /30 has none.

Why no driver change creates a DH+ connection #

DH+ is its own network: a token-passing protocol with its own media, signaling and octal node addresses. DF1 is a serial protocol with its own framing and port settings. EtherNet/IP rides Ethernet. No amount of configuration turns one into another, so a PC — which has Ethernet and maybe a serial port, but no DH+ interface — connects only through hardware that terminates one of those media:

  • SerialDF1forPLC5Com needs a serial connection to channel 0 on the processor.
  • EthernetIPforPLC5Com1 needs an Ethernet port at the processor; only the Ethernet variants of the PLC-5 family carry one, and the /30 is not one of them.
  • EthernetIPtoDHRIOforPLC5Com1 needs an Ethernet route to a bridge module whose far side sits on the DH+ network.

Swapping between drivers changes none of that. If the physical path is absent, every driver times out, and installing more communication software on the PC adds nothing.

Route 1: DF1 over the channel 0 serial port #

Use the processor serial port with SerialDF1forPLC5Com when one HMI talks to one PLC-5/30. With a single PC and a single processor, DF1 full-duplex point-to-point is the mode; half-duplex master exists for multi-drop serial chains.

Match the driver to the channel 0 configuration exactly — baud rate, parity, stop bits, CRC or BCC error checking, duplex mode and station address — and read those values from the processor's channel configuration rather than guessing; 19200 baud is the usual PLC-5 default. The serial defaults differ across controller families, which is part of why DF1 reads work on an SLC 500 but not a PLC-5 when settings are copied between them. A modern PC without a serial port uses a USB-to-RS-232 adapter on channel 0; a modern laptop RSLogix 5 setup guide covers that link end to end.

Measure the serial load before you buy a bridge #

"Serial is slow" is a guess, not a measurement. Worked example with illustrative numbers for a 19200 baud DF1 link using 1 start, 8 data and 1 stop bit — 10 bits per character:

  • Character time: 10 bits ÷ 19200 bit/s = 0.52 ms.
  • One-word poll, roughly 30 characters of command, response and control overhead: 30 × 0.52 ms ≈ 15.6 ms.
  • 240 words polled one at a time: 240 × 15.6 ms ≈ 3.7 s per full refresh — misses a 1 s update target by nearly four times.
  • Four block reads of 60 words, about 155 characters per transaction: 4 × (155 × 0.52 ms) ≈ 0.32 s — meets 1 s with three times margin.

The decision: for one HMI reading a few hundred words at 1 s updates, DF1 with block reads is sufficient and bridge hardware buys you nothing. Buy the bridge when several PCs or several processors must share the link, or when the tag count and update rate need better than about 0.3 s. DH+ at its common 57.6 kbit/s is only three times 19200 baud, and that bandwidth is shared by every station on the network — the bridge is about reach and sharing, not a large speed multiplier.

Route 2: the Ethernet-to-DH+ bridge #

The documented native bridge is the 1756-DHRIO or 1756-DHRIOXT module in a ControlLogix chassis; its user manual describes it as a bridge for DH+ messaging and for CIP traffic, which is exactly what an HMI and programming software need. The full route is: PC on Ethernet → ControlLogix chassis → 1756-DHRIO channel configured for DH+ → DH+ network → your PLC-5/30's node. Give the bridge channel a unique node address in the network's octal scheme and set its data rate to match — every station on one DH+ network runs the same rate. On the PC, select EthernetIPtoDHRIOforPLC5Com1 and point it at the chassis and the target node.

The same bridge also carries controller-side traffic: routing a ControlLogix MSG to a PLC-5 over DH+ covers that direction. If you have no chassis, standalone EtherNet/IP-to-DH+ gateway modules bridge the same way and are documented to carry HMI and programming software traffic, so the route and the driver choice stay the same.

A reachable chassis is a precondition, so ping it first — but a successful ping proves only the Ethernet segment, not the channel configuration, the DH+ wiring, the node address or the data request.

Where the fault sits, layer by layer #

Symptom Layer at fault
Every driver times out; nothing browses No physical DH+ path exists between the PC and the network — hardware, not software
SerialDF1forPLC5Com cannot open or read Settings mismatch with channel 0, or another program such as RSLinx holds the COM port
EthernetIPforPLC5Com1 never connects The processor has no Ethernet port; a /30 never will
Bridge route reaches the chassis but no PLC Channel not configured for DH+, wrong node address, or a physical-layer fault on the network
Reads work, then drop as screens open Polling load — word-at-a-time polling — or a duplicate node address
Ping succeeds, data never arrives Only the Ethernet segment is proven; the fault is downstream of it

Bring the route up in order #

  1. Inventory the endpoints: the HMI computer's interfaces, channel 0, the DH+ terminal, and any existing bridge or gateway. Confirm the DH+ terminal is not being treated as the serial port.
  2. Serial route: verify every channel 0 setting against the processor configuration, then confirm nothing else holds the COM port.
  3. Bridge route: confirm the module sits in the chassis, the chosen channel is configured for DH+, and its node address and rate match the network.
  4. Check the DH+ physical layer: termination, conductor continuity and shield treatment.
  5. Read one known word from a stable address and compare it against the value shown at the processor.
  6. Enable screens one at a time and watch for timeouts that appear only as polling grows.
  7. Test writes last, to a single address, with the machine in a state where an unexpected value cannot move it.

If RSLinx still cannot see the processor once the route is proven, a PLC-5 that stays invisible in RSLinx after a processor swap has its own causes.

The decision for your case #

  • One HMI, one PLC-5/30, updates around a second: use channel 0 with SerialDF1forPLC5Com, poll tags as blocks, and spend nothing on bridge hardware.
  • Several PCs, several processors, or updates faster than about 0.3 s on a few hundred words: install a 1756-DHRIO bridge, or an equivalent standalone gateway, and use EthernetIPtoDHRIOforPLC5Com1.
  • A processor that actually carries an Ethernet port: use EthernetIPforPLC5Com1 directly — but that is never a PLC-5/30.

Questions asked

How many stations can one DH+ network carry?

Node addresses run from 00 to 77 octal, 64 stations in total, and every station on one network must be unique and run the same data rate. Count your bridge channel, programming stations and all processors before adding anything: a duplicate address shows up as intermittent loss of every node, not as a clean error.

Can RSLinx share its connection with the HMI driver?

Not directly. RSLinx is a separate communication server that supplies drivers for its own clients, and a PC HMI component like SerialDF1forPLC5Com opens the serial port or the Ethernet route itself. If the serial port is already open in RSLinx, the HMI driver cannot open it at the same time; close one before the other connects.

Do I need a ControlLogix chassis for the bridge route?

The documented native bridge is the 1756-DHRIO or 1756-DHRIOXT module, which does need a ControlLogix chassis, slot and power supply. Standalone EtherNet/IP-to-DH+ gateway modules do the same job without a chassis and appear as a bridge node on the network, so the routed driver path stays the same.

Can both 1756-DHRIO channels be used for DH+?

Yes. Each of the module's two channels can be configured for DH+ or Remote I/O, so one module can bridge two DH+ networks or one of each. Each channel needs its own unique node address on the network it joins and must match that network's data rate.

Keep reading

  • 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.

    Industrial networks

  • How-to

    How to route a ControlLogix MSG to a PLC-5 over DH+

    The CIP path is 1,5,2,10.60.28.60,1,2 and it ends at the 1756-DHRIO: out the local backplane to the ENBT/A in slot 5, over Ethernet to the bridge ENBT/A at 10.60.28.60, then across the bridge backplane to the DHRIO in slot 2. DH+ carries no CIP, so Channel A and DH+ node 67 are set on the message's communication tab, never appended to the path.

    Industrial networks

  • How-to

    Passing SLC 5/03 data to a CompactLogix over Ethernet

    Put a DF1-to-Ethernet gateway on the SLC 5/03's free Channel 0 serial port: an ENI-style unit lets the CompactLogix message SLC data-table addresses, and a protocol-mapping converter moves SLC files into CompactLogix tags on its own schedule. For one analog value between nearby panels, wire an analog output straight to an analog input instead. Configure Channel 0 for DF1 full duplex, add staleness logic, and prove the link with two test values across the range.

    Industrial networks