IMDTouchKnowledge BaseShop main store

How-to

Networking DirectNET PLCs and Multiple HMIs the Clean Way

Industrial networks Published 4 min read

Short answer

Build it as two DirectNET segments: one existing D3-340 polls the other PLCs as slaves, and a D3-422-DCU on that master gives both operator panels one multidrop port. Convert RS-232 to RS-485 only where the port inventory shows an RS-232-only node. Polling four slaves per scan refreshes the panels in about 200 ms, fast enough for status and setpoints.

On this page
  1. Inventory every port before buying hardware
  2. Make one existing PLC the DirectNET master
  3. Put both panels on one multidrop port
  4. Wire the trunk and convert only what needs it
  5. Configure stations and data ownership
  6. Worked example: polling load and update time
  7. Commission one link at a time
  8. Questions asked

Use DirectNET with one of the existing D3-340 PLCs as master, and put both operator panels on a D3-422-DCU fitted to that master. The DCU attaches to the front of the CPU and power supply assembly and provides a multidrop DirectNET port, which is exactly what a two-panel installation needs. Convert RS-232 to RS-485 only where the port inventory proves an endpoint is RS-232-only, and let the controller you are adding join as a slave instead of forcing it into the master role. The whole job is five PLCs and two panels on two DirectNET segments, with the master PLC as the only device on both.

Inventory every port before buying hardware #

The wiring plan and the converter count fall out of one table, so build that table first:

  • Write down the model and both communication ports of each of the five PLCs. Both ports on the D3-340 and the D3-350 CPUs can serve as DirectNET slave ports, so port availability decides the master, not CPU model.
  • Write down each panel's documented serial interface. Whether a panel has a native multidrop-capable port is a fact in its documentation; do not assume it in either direction.
  • Mark the ports that already carry a programming cable or another device.
  • The inventory is done when every node is either documented compatible or carries a named converter requirement — not a bulk order of converters on a guess.

Make one existing PLC the DirectNET master #

Commit to this arrangement: one existing D3-340 polls the other four PLCs as DirectNET slaves, and the controller you are adding becomes slave number five. Every status value moves slave to master, every setpoint moves panel to master to owning slave, and the panels never talk to a slave directly. The tradeoff is real: the master becomes the single point of failure for shared data. Accept it, because each machine still runs on its own CPU — losing the network costs you overview and remote adjustment, not control.

Put both panels on one multidrop port #

One panel connects to a D3-340 port directly; two panels do not simply double that, they need a multidrop port. The D3-422-DCU connects directly to the front of the CPU/power supply assembly and provides that multidrop DirectNET port. Fit it to the master and keep the programming port free. For the full component picture, see networking DL340 PLCs and HMIs over DirectNET.

Wire the trunk and convert only what needs it #

Each segment is a multidrop trunk with taps, not a chain of back-to-back cables: follow the drop spacing and termination practice in DirectNET RS-422 multidrop cabling with T-connectors. Where the inventory shows an RS-232-only node, put one RS-232-to-RS-485 converter at that node and only that node. Ground the cable shield at one end of each trunk. One safety note: de-energize the segment and verify zero volts across the pair before landing a new node on a live installation.

Configure stations and data ownership #

  1. Give every node on each segment a unique station number: master plus four slaves on the PLC trunk, two panels on the panel trunk.
  2. Set identical line settings for speed and parity across a segment. The values are the ones printed in each device's manual, and mismatched settings are the classic cause of a silent trunk.
  3. Map data before programming: for each value, name the source PLC, the master table address it lands in, and its direction of travel.
  4. Program one slave poll and one panel transaction first.
  5. Expand to the remaining nodes only after that first exchange moves the right data in both directions.

Worked example: polling load and update time #

Take the actual node count — one master polling four slaves — with 50 ms per healthy exchange and a 100 ms timeout as example planning figures:

  • Healthy cycle: 4 × 50 ms = 200 ms, which is the fastest the panel status can refresh through that one master scan.
  • One slave offline: 3 × 50 ms + 1 × 100 ms = 250 ms, and the remaining transactions continue.
  • Setpoint path: the panel writes the master's table in one transaction of about 100 ms, then the master relays it on the next poll of the owning slave, so 100 ms + 200 ms = 300 ms worst case end to end.

Decision: 200–300 ms is well inside what compressor status and refrigeration setpoint adjustment need, so build it as a single polled master and stop there. The panel traffic rides the DCU port and adds no load to the PLC trunk.

  1. Verify trunk wiring against the cabling guide with the segment powered down.
  2. Bring up the master and one slave; confirm a read and a write in both directions.
  3. Add the remaining slaves one at a time, confirming the earlier ones still exchange correctly.
  4. Connect one panel; verify status values plus one controlled setpoint write to a non-critical address.
  5. Add the second panel and re-check the first.

A powered panel proves nothing on its own. The test that counts is the receiving device showing the intended source value and a write changing only its designated target.

Questions asked

Does the new PLC I have to add need to be the DirectNET master?

No. Choose the master by port availability and scan headroom, not by age. Both ports on the D3-340 and D3-350 CPUs can serve as DirectNET slave ports, so any chassis can be polled. Put the new controller wherever it does the most control work and let an existing PLC with a free port run the polling.

Can both panels share the CPU port I already use for programming?

Not cleanly. A single panel connects to a D3-340 port directly, but loading the same port with programming traffic and a second panel leaves you debugging three variables at once. The D3-422-DCU gives the two panels their own multidrop port on the front of the CPU and power supply assembly, which keeps the programming port free.

How many RS-232 to RS-485 converters does this network need?

One per RS-232-only node on a multidrop segment, and none for nodes whose documented interface already suits multidrop. The count comes out of the port inventory, not the device count: a five-PLC, two-panel network can need anywhere from zero to seven converters depending on what each port actually is.

What happens on the panels if one slave PLC drops off the network?

The master's poll to that station times out and the remaining transactions continue. With a 100 ms timeout per dead station, one lost PLC stretches the polling cycle from 200 ms to 250 ms, and the panels keep every other machine's data because they read the master's table, never the slaves directly. Only the offline machine goes stale on screen.

Keep reading

  • How-to

    Connecting Multiple HMIs to One PLC Over 200 ft Serial

    RS-232 on good cable can reach 200 ft at 9600 baud, but RS-232 connects exactly two devices, so three HMIs cannot share one PLC port. Put an RS-232-to-RS-485 adapter at the PLC and at each panel, daisy-chain one twisted pair, and terminate only the two ends. Confirm the PLC port's protocol accepts more than one master before ordering adapters.

    Industrial networks

  • Troubleshooting

    Why an HMI Freezes or Updates Slowly Over Serial

    A panel-wide freeze or slow updates over serial is a link fault — driver, PLC port, wiring, or startup timing — not a screen-object fault. Test the two field-proven fixes first: a 10-second startup delay before the first poll, and a port set to four-wire RS-422 at 19,200 baud. Fix an isolated stale tag separately, by address and data type.

    HMI and touchscreens

  • Explainer

    Designing HMI Screens for Clear Operator Decisions

    High performance HMI design under ANSI/ISA-101.01-2015 makes abnormal conditions easier to spot than normal operation: normal running renders flat and gray, saturated color appears only on deviations, and every icon, font and color follows one documented project style. Verify the style mechanism on a single screen before scaling to the full library.

    HMI and touchscreens