IMDHMIControls LibraryShop main store

Troubleshooting

Why online editing slows a DH+ network and how to fix it

Industrial networks Published 6 min read

Short answer

Editing slows because an online edit, every HMI poll and every controller MSG shares one 57.6 kbit/s token-passing DH+ trunk, and the edit bursts are the largest frames on it. Raise the whole segment to 230.4 kbit/s when every node supports it and the trunk is within 2,500 ft; otherwise segment DH+ and bridge through a ControlLogix gateway so editing stops competing with every station.

On this page
  1. What one DH+ trunk delivers
  2. Why an edit hurts more than a poll
  3. The arithmetic a rate change buys you
  4. Diagnose before changing anything
  5. Raise the segment to 230.4 kbit/s
  6. Segment the trunk and bridge with a ControlLogix gateway
  7. Move the engineering and HMI access off the trunk
  8. Apply one change, then re-measure
  9. Questions asked

Online editing slows this network because DH+ is one shared, token-passing trunk: the programming workstation, the PanelView, the InTouch node and the eight controllers all wait for the same token on the same 57.6 kbit/s pair, and an edit session pushes the largest bursts that trunk ever carries. Minimal controller messaging does not make the segment lightly loaded — HMI polling plus edit verification is the load. Fix it in this order: if every node on the segment supports 230.4 kbit/s and the trunk is within 2,500 ft, raise the entire segment to 230.4 kbit/s; otherwise split the nodes across DH+ segments and bridge them with a ControlLogix gateway, so an edit stops competing with every station in the area.

What one DH+ trunk delivers #

DH+ rate Maximum trunk length Trunk termination
57.6 kbit/s 10,000 ft (3,048 m) 150 Ω
115.2 kbit/s 5,000 ft (1,524 m) 150 Ω
230.4 kbit/s 2,500 ft (762 m) 82 Ω

These are the documented limits from the ControlLogix DH+ and remote I/O user manual and the DH+ implementation guidance. Three rules come with the table: every device on the trunk must be configured for the same rate, each dropline is limited to 100 ft (30.5 m), and 230.4 kbit/s is the ceiling of the network — there is no higher DH+ rate to move to later.

Why an edit hurts more than a poll #

Ten stations share this trunk: three PLC-5 processors, five SLC 5/04 processors, a PanelView terminal and the InTouch node. A station transmits only while it holds the token, so every frame — a poll, a MSG, a verification — waits for the token to rotate through all ten. The HMI polls are small and steady. An online edit is not: connecting uploads the program for comparison, each verified change writes a block back, and the session repeats this while you work. The signature of this fault is that every station slows while you edit and recovers when you log off; a failing cable instead shows rising retry and error counters, and a single bad workstation interface slows only itself.

HMI polling alone loads a trunk like this — the same shared-medium behavior behind slow SLC 5/04 DH+ communications to Ignition SCADA. Even minimal controller MSG traffic rides the same token rotation, and string data passed between a PLC-5 and an SLC 5/04 has its own failure mode, covered in resolving PLC-5 to SLC 5/04 string MSG data corruption.

The arithmetic a rate change buys you #

Compute the wire-rate floor of a transfer before changing anything. Worked example: uploading a 57,600-byte project file at the full segment rate.

  • Payload in bits: 57,600 byte × 8 bit/byte = 460,800 bit
  • At 57.6 kbit/s = 57,600 bit/s: 460,800 bit ÷ 57,600 bit/s = 8.0 s
  • At 115.2 kbit/s = 115,200 bit/s: 460,800 bit ÷ 115,200 bit/s = 4.0 s
  • At 230.4 kbit/s = 230,400 bit/s: 460,800 bit ÷ 230,400 bit/s = 2.0 s

Because 230.4 kbit/s is exactly four times 57.6 kbit/s, the floor drops exactly 4:1; 115.2 kbit/s buys 2:1. These are floors, not predictions — token overhead, interleaved polls and retries sit on top, and they are what you feel. Use the floor as the decision number: measure your timed upload, compare it to the floor, and if the measured time is a large multiple of the floor, contention owns the segment and a rate change alone will not finish the job.

Diagnose before changing anything #

  1. Time one full upload and one verified online edit with everything connected. Record the seconds.
  2. Stop the InTouch application, close the extra programming sessions, and repeat the same timed actions. A large improvement names traffic, not hardware.
  3. Read the counters on the communication interfaces: retries and errors that are nonzero and rising mean fix the media first.
  4. List every station and its node address; confirm no duplicates. Each station lengthens the token rotation you are waiting on.
  5. Measure the installed trunk and each dropline against the table above. Droplines over 100 ft (30.5 m) are faults at any rate.
  6. Record the exact catalog number and revision of every processor, interface and terminal, and confirm from its own documentation which DH+ rates it supports. Older processors stop at 57.6 kbit/s, and one such node caps the segment.
  7. Write down the configured rate, termination and node address of every device before the outage, so a single change stays traceable.

Raise the segment to 230.4 kbit/s #

Take this branch when the diagnosis shows clean counters, every node supports the top rate, and the trunk is at most 2,500 ft. Schedule the outage, set every device to the same 230.4 kbit/s, re-terminate the trunk at 82 Ω, then verify each station communicates and repeat the timed upload. If one node tops out at 57.6 kbit/s, the segment rate stays at 57.6 kbit/s — or that node moves behind a bridge. If the trunk measures between 2,500 ft and 5,000 ft, 115.2 kbit/s is your ceiling, and that still halves the floor of every transfer.

Segment the trunk and bridge with a ControlLogix gateway #

Split the network when the station count and the mixed HMI, MSG and editing traffic stay high at any rate, or when one legacy node pins the segment. A ControlLogix chassis carrying DH+, Ethernet and ControlNet bridge modules joins the segments while each keeps its local traffic: the PanelView polls the controllers on its own segment, and the engineering workstation reaches any controller from the Ethernet side. The routing work follows the pattern in passing CompactLogix MSG traffic to an SLC 5/04 through a DH+ gateway, with the PC side set up as in reaching a PLC-5/30 DH+ network from a PC HMI driver.

Two limits on the gateway. It moves protocol boundaries, not traffic: do not route every HMI poll and every edit session across one bridge, or you rebuild the bottleneck on the far side. And before commissioning a route, compare the revision and firmware of early Ethernet bridge modules against your Ethernet processors — the earliest ControlLogix Ethernet modules used a different Ethernet protocol than the PLC-5 Ethernet processors, corrected in later revisions.

Move the engineering and HMI access off the trunk #

This is also the growth plan for the new areas. Put each area's controllers and their local PanelView on one DH+ segment, move the InTouch PCs onto Ethernet behind the gateway, and let the gateway — not one long trunk — carry only the traffic that genuinely crosses areas. Keep that engineering and supervisory Ethernet separated from the business network by design, and keep the controllers an area's operators watch on that area's own segment.

Apply one change, then re-measure #

Take a verified, restorable backup of every controller and HMI configuration first, and record node addresses, rates, module revisions and firmware. One safety note belongs here: on early PLC-5 Ethernet processors below the 5/40E, an online search run during an online editing session has been reported to clear the controller's memory — do not test search functions on those processors, and keep the backup current. Then change the rate, or complete the segment split — never both in one outage — and repeat the timed upload and edit from the diagnosis list. If the upload lands close to its floor and editing no longer disturbs the HMIs, the job is done; if it stays a multiple of the floor, the segment still carries too much traffic and the next branch is segmentation.

Questions asked

Can I set only the processors I edit to 230.4 kbit/s and leave the rest of the trunk at 57.6?

No. Every device on a DH+ trunk must be configured for the same baud rate, so one 57.6-only node caps the whole segment. Either keep the common rate or move that node to its own segment behind a bridge. Inventory first: older processors and some interfaces top out at 57.6 kbit/s, and those set your ceiling.

Our trunk measures 4,000 ft. Which DH+ rate can we run?

115.2 kbit/s. The documented trunk limits are 10,000 ft at 57.6 kbit/s, 5,000 ft at 115.2 kbit/s and 2,500 ft at 230.4 kbit/s, so 4,000 ft rules out only the top rate. At 115.2 kbit/s you double the wire rate; going to 230.4 requires shortening the trunk below 2,500 ft or segmenting the network.

Will a higher baud rate fix retry errors and intermittent dropouts?

No. Retries and dropouts point at the physical layer: termination, shield grounding, connectors, damage. A higher rate makes marginal media worse, not better. Terminate the trunk at 150 ohms for 57.6 and 115.2 kbit/s and 82 ohms at 230.4 kbit/s, drive the error counters to zero first, then change the rate.

Does bridging DH+ through a ControlLogix gateway make editing faster by itself?

Only if it also separates traffic. The gateway moves protocol boundaries, not bytes off the trunk: an edit routed across it still crosses the same DH+ segment. Speed returns when the controllers and their local HMI sit on one segment and the engineering workstation reaches the gateway over Ethernet instead of a dropline on the shared trunk.

How do I prove DH+ is the bottleneck before buying hardware?

Time one upload with everything connected, then repeat it with the HMI application stopped and the extra programming sessions closed. If the same job drops from minutes toward the wire floor of 8 s for a 57,600-byte file at 57.6 kbit/s, the trunk is the constraint. Record the retry and error counters before and after the same test.

Keep reading

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

    Industrial networks

  • Comparison

    PROFINET versus DeviceNet for machine and panel I/O

    Choose by controller ecosystem first: PROFINET is industrial Ethernet at 100 Mbps with line, star and ring topologies, while DeviceNet is a CAN-based trunk running 125 to 500 kbps. Speed only decides when the panel needs dense or fast I/O. PROFINET for new high-speed machines, DeviceNet where the Rockwell-era devices and wiring already exist.

    Industrial networks

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

    Industrial networks