Five DL06 PLCs must share one HMI across a 1,100-foot span, with stations 280–350 feet apart and each PLC already linked to a Durapulse VFD over Modbus. Choose the architecture from the required communication paths and physical port inventory—not from a cable run that happens to work.
Check which devices must exchange data
Write down each required conversation before choosing Ethernet or serial. “The PLCs are connected” can mean each reports to the HMI, each PLC exchanges data with a central PLC, or all PLCs exchange data with one another. These are different traffic patterns and can require different port assignments.
| Required path | Architecture implication | Next check |
|---|---|---|
| Every PLC to the shared HMI | Use a network and HMI driver arrangement that can address all five PLCs. | Check HMI driver support and PLC Ethernet/serial interfaces. |
| One PLC coordinates the other four | A master/slave serial arrangement may fit if the selected protocol and modules support the required roles. | Check which device initiates requests and which device answers. |
| PLC-to-PLC exchange plus HMI access to each PLC | Allow for multiple communication paths or a network with the necessary addressing and drivers. | Map every connection, including the existing VFD links. |
Record the required data, who initiates each read or write, and how quickly the information must update. Do not size the network around the HMI alone if the PLCs must also exchange data. Then inventory the installed PLC ports, any communication modules, HMI interfaces, and VFD interfaces; proceed to the distance check.
Measure every cable segment before choosing copper Ethernet
Read the planned cable length from the station layout, including the HMI and switch locations. A standard twisted-pair Ethernet copper link is limited to 100 m (about 328 ft) between active devices. Treat each PLC-to-switch, switch-to-switch, and HMI-to-switch cable as a separate link; an active Ethernet switch starts a new link but does not make an overlength link compliant.
The stated 280–350-foot station spacing straddles that limit. A 280-foot link is within 100 m in length, while 350 feet is over it. A 1,100-foot overall route can use multiple compliant links, but only if switches receive power, fit the environment, and can be placed so every copper segment remains within the applicable limit. The historical suggestion of three or more switches is only a rough layout estimate; determine the count from actual endpoint-to-endpoint distances and the chosen devices.
Some installations have operated with longer runs, including reported runs around 400–420 feet, but a successful connection on one route is not proof of reliable performance or a design limit. Do not use an intermittent or marginal long link as the production plan. If a switch location cannot keep every copper segment within specification, assess fiber and compatible media conversion or a suitable fiber switch, or redesign the path.
Once the physical route is known, mark each link’s measured length and proposed medium. If using copper, split any overlength segment with an appropriate powered switch. If using fiber, confirm connector, fiber type, distance rating, and transceiver/media-converter compatibility from the equipment documentation. Then check the serial alternative and port conflicts.
Check whether RS-422 can support the traffic pattern
Read the communication roles required on the serial network: identify the master that initiates requests and the devices that answer. A single-master RS-422 design can be a fit when one PLC polls the others and the HMI does not need to initiate requests on that same network. The stated design guidance treats an HMI as a master; if the HMI must communicate with all PLCs, it cannot simply be added as a second master on the same single-master network.
A separate serial network may resolve that conflict, but it requires a port/module plan. The proposed D0-DCM arrangement was raised for the case where a master PLC and HMI both need access to the PLCs; the exact module count depends on how each link is wired and which device owns each port. Do not buy a D0-DCM for every PLC by assumption. First identify the relevant PLC port, its current use, supported protocol, and whether the required simultaneous VFD and inter-PLC/HMI connections need separate interfaces.
RS-422 does not eliminate the need to account for the existing Modbus links to the Durapulse drives. Determine whether each VFD link is serial or Ethernet, which physical interface carries it, and whether the PLC can support another independent connection for the HMI or other PLCs. If the port inventory leaves no compatible interface, return to a switched Ethernet or mixed Ethernet/fiber design.
Compare the symptom with the likely network cause
Take readings while the system is operating: link status at each endpoint, actual cable length, PLC/HMI communication status, and whether VFD communication remains healthy. A path can appear connected while a protocol, addressing, or port-role mismatch prevents useful data exchange.
| Observed symptom | Likely cause to check | Next measurement |
|---|---|---|
| One PLC works locally but drops out at a distant station | Overlength copper link, poor termination, or switch/power issue | Measure each segment separately; check link status at both ends. |
| HMI reaches some PLCs but not others | HMI driver/address configuration, PLC path, or missing network interface | Test each PLC address and confirm HMI configuration for each target. |
| PLC polling works until the HMI is connected | Two initiators on a single-master serial network | Identify who initiates requests and which network each device occupies. |
| HMI access works but a VFD link fails | Competing use of a PLC interface, changed serial settings, or wiring issue | Compare the VFD link’s port and communication configuration before and after the change. |
| Link LEDs are on but values do not update | Protocol, addressing, register/tag mapping, or request configuration mismatch | Check PLC/HMI diagnostics and a known test value end to end. |
Use the results to choose the next branch: fix physical-link faults before changing PLC logic; resolve port-role conflicts before adding serial devices; and correct addressing or tag mapping only after link and protocol paths are verified.
Choose the architecture that matches the measured layout
For a design in which all five PLCs and one HMI need network access, switched Ethernet is the straightforward topology if each copper segment can meet its length limit and the installed DL06 interfaces and HMI support the needed connection method. Where the 1,100-foot route or station spacing makes copper links impractical, use fiber for the long backbone or a mixed fiber/copper layout with compatible switches or media converters. Keep copper drops short and document each active-device-to-active-device link.
Choose RS-422 only when the data flow and master/slave roles fit it, and when the required separate HMI and VFD communication paths can be assigned to compatible interfaces. A mixed design can be appropriate—for example, a serial control path with a separately engineered HMI path—but verify every interface and protocol rather than assuming that one module serves all traffic.
For the HMI, verify that the exact panel model and software can address all five PLCs using the selected protocol. A historical C-more suggestion indicated multi-PLC support but manual tag entry; treat that as a planning warning, not a guarantee for the panel/software version on the shelf. Confirm current import capabilities and driver limits in the applicable documentation before building the tag database.
Build and test the selected network in a controlled sequence
- Document the topology: list all five PLCs, the HMI, the VFDs, every port/module, device role, and each cable segment’s measured length.
- Select Ethernet, RS-422, or a mixed arrangement from the traffic and port checks. Confirm compatible interfaces and protocol support against the exact equipment documentation.
- Install switches or fiber components so no copper segment exceeds its specified limit. Verify switch power and environmental suitability; label both ends of each link.
- Configure device addressing and communication settings according to the selected equipment and protocol documentation. Keep the existing VFD communication settings unchanged unless the port/interface plan requires a documented change.
- Configure the HMI to address each PLC separately. Build and verify its tags against the target PLC’s actual data map; do not presume tags can be imported from multiple controllers.
- Test one PLC-to-HMI path, then add the remaining PLCs one at a time. Where required, test PLC-to-PLC exchanges and each PLC-to-VFD link independently.
Record the resulting addresses, port assignments, cable media/lengths, HMI target mapping, and observed diagnostics. This record gives the next shift a baseline for separating a physical fault from a device or configuration fault.
Verify every path before returning the system to service
Check that the HMI reads and writes the intended test points at all five PLCs, that PLC-to-PLC data reaches its intended destination if required, and that all five VFD Modbus links remain healthy. Confirm updates continue during normal operating conditions, not only during a brief bench test. Inspect diagnostics for communication errors or timeouts and recheck link status along the entire route.
Keep a temporary restore distinct from the permanent repair. A temporary switch relocation or isolated test connection can help identify a failed segment, but do not leave a copper run beyond its specified link length as the production fix. The permanent repair is a documented compliant path, validated device/driver configuration, and a successful test of every required data path.
FAQ
How many switches do five DL06 PLCs need across 1,100 feet?
There is no fixed count from total route length alone. Place active switches so each copper Ethernet segment stays within its specified limit, then count the switch-to-device and switch-to-switch links in the actual layout.
How do I connect the HMI and PLCs over RS-422?
First assign the master and slave roles. If both a PLC and HMI need to initiate communication, plan separate compatible networks/interfaces rather than placing two masters on one single-master network.
How do I know whether each DL06 needs a D0-DCM?
Inventory the ports already used by the VFD Modbus link and identify the interface needed for PLC-to-PLC and HMI traffic. Determine module count from the actual topology and supported port/protocol configuration, then verify it against the DL06 and module documentation.
Stop commissioning if a required path depends on an overlength copper segment, a serial master-role conflict, or an unverified port/module combination. Capture the topology, measured link lengths, device models, and communication diagnostics, then contact AutomationDirect official technical support for model-specific interface and driver confirmation.