IMDTouchKnowledge BaseShop main store

How-to

Connecting two HMI panels to control one machine

HMI and touchscreens Published 4 min read

Short answer

Yes. Connect the two DOP-107EV panels over Ethernet in a Host-Client arrangement: the Host keeps the controller link, and the Client controls the machine from its own screen. Each panel uses its own internal HMI memory, so any value both operators must see belongs in the controller, not in panel memory.

On this page
  1. What Host-Client means on this pair
  2. The address plan, with numbers
  3. Configure the pair
  4. Put the shared values in the controller
  5. Two operators, one machine
  6. When to connect both panels to the controller instead
  7. Questions asked

Yes — two DOP-107EV panels can both control one machine, and the supported way is a Host-Client arrangement over Ethernet rather than any electrical parallel wiring. One panel is the Host: it holds the connection to the controller and the master project. The other is the Client: it reaches the Host over the network and controls the machine from its own screen. The rule that decides whether the pair works in practice is that each panel uses its own internal HMI memory, so a value written on one screen does not appear on the other — everything both operators must see belongs in the controller.

What Host-Client means on this pair #

No electrical parallel connection is involved; parallel control is delivered by the network. The arrangement assigns the two panels distinct roles:

  • The Host runs the master project and holds the connection to the controller.
  • The Client connects to the Host's IP address over Ethernet and gives the operator full control from its screen.
  • Internal HMI-memory data is used separately on each screen, and that is the constraint the rest of this article plans around.

Make the panel with the shortest, cleanest cable run to the controller the Host, because the Host is the panel that keeps the machine when the link between the panels is down.

The address plan, with numbers #

The segment is standard Ethernet (IEEE 802.3): each station already carries a unique factory MAC address, and a switch joins them. What you must get right is unique IP addresses on a single subnet:

Device Role Address Subnet mask
Panel 1 Host, master project, controller link 192.168.1.1 255.255.255.0
Panel 2 Client, second control screen 192.168.1.2 255.255.255.0
Controller Machine logic 192.168.1.10 255.255.255.0

Check the subnet by ANDing each address with the mask:

  • 192.168.1.1 AND 255.255.255.0 = 192.168.1.0
  • 192.168.1.2 AND 255.255.255.0 = 192.168.1.0
  • 192.168.1.10 AND 255.255.255.0 = 192.168.1.0

All three stations fall on 192.168.1.0/24 with no duplicate addresses, so one switch carries the whole segment and no router is needed; the Client's connection setting points at 192.168.1.1. Keep each cable run below 100 m, the 100BASE-TX channel limit, and add a switch when a run must be longer.

Configure the pair #

  1. Address the panels in their network settings pages: Host 192.168.1.1, Client 192.168.1.2, mask 255.255.255.0 on both.
  2. Commission the Host alone. With the Client off the segment, confirm every command and display works from Panel 1, so any fault that appears later is provably in the link, not the project.
  3. Point the Client at the Host. In the connection settings of the project software, set the panel the Client links to as 192.168.1.1.
  4. Verify the pair in both directions: a command issued on the Client must change the state you read on the Host, and a command issued on the Host must show on the Client.
  5. Prove the failure mode: pull the Client's cable and confirm the Host still controls the machine, then reconnect and confirm the Client resumes.

Put the shared values in the controller #

Because the two memories are separate, place every value by one rule:

  • Anything both operators must see — mode bits, setpoints, jog and start commands, sequence step numbers — goes in controller registers that both panels read and write.
  • Panel-local internal memory is right only for values the other screen never reads or acts on, such as a local screen animation state.
  • A value that must match on both screens has already outgrown panel memory: move it to the controller and update both projects before commissioning.

Two operators, one machine #

Two control points mean the machine can be started from a screen the other operator is not watching. Keep emergency stop and personnel protection in the hardwired safety chain, never in either panel, and treat both screens as live at all times.

With two writers on the same register, the last write wins, so latch momentary commands in the controller: a rung that captures the press ensures a short button push from either panel is acted on. Program mode selection as controller state rather than screen-local flags, so the mode is where the logic says it is regardless of which screen touched it last.

When to connect both panels to the controller instead #

Host-Client costs the Host one controller connection and leaves you one master project to maintain, which is why it is the right choice for a DOP-107EV pair with a single controller connection available. Choose direct connections instead when the controller accepts multiple simultaneous HMI sessions and you want each panel standing on its own; over serial, that design becomes sharing one RS-485 PLC port between multiple HMIs, a wiring and addressing job of its own.

If the Host-Client link drops intermittently under vibration or cabinet heat, work the physical segment first — cable, connector, switch — because the checks behind diagnosing intermittent HMI to PLC Ethernet comms hangs apply to this segment unchanged.

Questions asked

Can both DOP-107EV screens command the machine at the same time?

Yes. Set the panels up as Host and Client over Ethernet and the Client controls the machine from its own screen. Treat it as a second live control point rather than a viewer: a controller register simply holds the last value written, so any rule about which operator wins has to be programmed in the PLC.

Do the two panels share internal HMI memory?

No. Internal-memory data is used separately on each screen, so a value written to panel memory on one side never reaches the other. Any value both screens must display or act on, such as setpoints, mode bits and commands, belongs in a controller register that both projects read and write.

Do I need a switch between the two panels?

Use one switch and the question disappears. It joins the Host, the Client and, when the controller is on Ethernet too, the controller on one segment, and it keeps every run under the 100 m 100BASE-TX limit. When the Host reaches the controller over serial, the segment is simply the switch and the two panels.

What happens if the Client loses its link to the Host?

The Host keeps the controller connection, so you lose the second screen, not control of the machine. Reconnect the cable and the Client resumes. The emergency stop is unaffected either way, because it lives in the hardwired safety chain rather than in either panel.

Keep reading

  • How-to

    Connecting One NS-Series HMI to a Redundant CS1D and a CP1H

    Yes. One NS-series panel hosts both controllers: a duplex CS1D pair whose Ethernet units keep a single system IP address through CPU changeover, so the panel never selects a CPU, plus a CP1H reached through its CIF41 as a second host. Both links run FINS over Ethernet simultaneously.

    HMI and touchscreens

  • Troubleshooting

    Getting Unconfirmed Alarm Status Out of a C-More Panel

    No tag on the EA9 exports alarm-confirmation state to the PLC, so the buzzer cannot follow the C-more confirm action. Latch the alarms in the PLC, acknowledge them with a panel pushbutton that writes a PLC bit, and run the buzzer while any alarm stays unacknowledged; the PLC to Panel Beep ON/OFF tag can mirror the same state onto the panel beep.

    HMI and touchscreens

  • Selection guide

    How to Select a Low Cost HMI With EtherNet/IP Support

    A low cost HMI qualifies for an EtherNet/IP job only when its installed driver reads and writes your controller's application variables — for Omron NJ/NX that means tag-name access, because device and address codes cannot be used with NJ/NX tag data. An Ethernet port on the datasheet proves nothing. Qualify the driver on the bench first, then compare screen size and cost.

    HMI and touchscreens

Troubleshooting SNTP clock sync on a Windows CE panel