IMDTouchKnowledge BaseShop main store

How-to

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

HMI and touchscreens Published 6 min read

Short answer

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.

On this page
  1. What the CS1D does at CPU changeover
  2. Two hosts, one panel
  3. An address worksheet, with numbers
  4. Configuring the two hosts in CX-Designer
  5. Verifying both links and the changeover
  6. The decisions
  7. Questions asked

Yes to both questions. One NS-series panel, an NS15 here, serves the duplex CS1D and the CP1H at the same time, because CX-Designer treats each controller as a separate host and the panel polls the hosts independently. The CS1D side needs no HMI redundancy logic at all: with duplex-configured CS1D-ETN21D Ethernet units, the pair presents one IP address to the network, ownership of that address follows the active CPU through changeover, and the panel keeps aiming at the same destination. FINS and Ethernet are not alternatives to choose between: FINS is the application protocol carried over Ethernet, for the CS1D pair and for the CP1H's CIF41 alike. What one panel does not give you is panel redundancy. Build it as two hosts, verify each link, then prove the changeover.

What the CS1D does at CPU changeover #

A duplex CS1D transfers control between its two CPUs; keeping external clients connected through that transfer is the job of the duplex Ethernet units, not the HMI. In the duplex configuration the two CS1D-ETN21D units hold one system IP address: the unit serving the active CPU owns the address, and at changeover ownership moves to the unit on the newly active CPU. The CS1D-ETN21D Operation Manual defines the local IP address setting and the duplex sections around exactly this behavior, and the CS1D Duplex System Operation Manual covers the changeover itself.

Two consequences for the panel:

  • One host entry pointed at the system IP address. No screen, macro or setting on the NS that selects CPU A or CPU B, because there is nothing to select.
  • A short interruption at changeover. The panel logs a communications error for the swap window and recovers on its own retry; how many seconds that takes is a number you measure in the test below, not one you assume.

Before relying on any of this, read the full catalog numbers and the unit versions off the hardware labels. The duplex manual manages CPU units by unit version because functionality differs across unit upgrades, and the address-swap behavior belongs to the CS1D-ETN21D duplex units; a single-system Ethernet unit does not provide it.

Two hosts, one panel #

In CX-Designer every controller connection is a host entry in the project, and every address you place on a screen belongs to one of those hosts. The CS1D and the CP1H therefore coexist as two entries:

  • The CS1D host uses the CS/CJ Series Ethernet driver, aimed at the system IP address that survives changeover.
  • The CP1H host is a second entry aimed at the CIF41's address, with its own host name and its own FINS destination.

Two rules keep the project honest. First, identical memory text in two controllers is not the same data: an address string that exists on both the CS1D and the CP1H still belongs to exactly one host, and the host decides which controller answers. Second, adding controllers to one panel is the easy direction; the inverse case of several HMIs sharing one PLC over RS-485 is where multidrop discipline starts.

An address worksheet, with numbers #

Work the addresses out on paper before downloading anything. The values below are an illustrative example; substitute your own and redo the checks.

Device Role IP address Subnet mask FINS node
NS panel HMI 192.168.1.5 255.255.255.0 5
CS1D duplex pair primary host 192.168.1.10 255.255.255.0 10
CP1H (CIF41) second host 192.168.1.21 255.255.255.0 21

The arithmetic:

  • Subnet check: 192.168.1.5 AND 255.255.255.0 = 192.168.1.0, and the same operation on .10 and .21 gives 192.168.1.0. All three devices sit on one subnet, so no router and no FINS routing enter the design.
  • Node check: with the node-from-final-octet conversion set on the Ethernet interfaces, the FINS nodes are 5, 10 and 21, three distinct nodes with no duplicate claims on the network.
  • Destination check: each host entry also carries the FINS network number set on the units and a destination unit number; unit 0 addresses the CPU in both controllers.

Two of these settings live outside the project: the panel's own address is set in the display's offline setup, and the CS1D system address is set on the Ethernet unit through the duplex procedure in its manual. Do both before commissioning the panel.

Configuring the two hosts in CX-Designer #

  1. Save the current project and record the panel's working settings, so a failed download leaves you a recovery point.
  2. Read the catalog numbers and unit versions from the CPUs and both Ethernet units, and confirm the Ethernet units are CS1D-ETN21D in the duplex configuration.
  3. Set the CS1D system address on the Ethernet unit per the duplex procedure, and give the CIF41 its own address on the CP1H, before touching the panel project.
  4. Set the panel's own address and FINS node in the display's offline setup mode.
  5. In the project's host settings, add the CS1D host: its own host name, the CS/CJ Series Ethernet driver, and the system IP address, FINS node and destination unit from the worksheet.
  6. Add the CP1H host with a different host name, the CIF41's address and its FINS node from the worksheet.
  7. Assign every object to the correct host, including read objects, write objects and controls such as a multi-function button that sets a bit and changes screens, which carries a host assignment like anything else.
  8. Build one diagnostic screen holding a live-changing CS1D value and a live-changing CP1H value, both read-only.
  9. Transfer the project and compare each on-screen value against that controller's online monitor in its programming software.

Verify each host the way you would when testing an HMI project against a live PLC: one known value per controller, checked against the controller's own online monitor, with writes disabled. A successful ping on both addresses proves the network path only, so a panel that pings but shows communication errors has an addressing problem, not a cable problem.

Then prove the behavior this design rests on. Perform the CPU changeover only with the machine in an approved commissioning state: the duplex system transfers outputs to the standby CPU, and that is a controlled event, not a communications test to improvise on a running process. With both diagnostic values live, run the documented changeover and watch three things:

  • The CS1D value freezes, the panel logs a communications error, then the value resumes without anyone touching the panel.
  • How many seconds the freeze lasted; write it down, because that measured figure is your system's recovery time.
  • The CP1H value never stops updating, which is the proof that the two hosts are genuinely independent.

If the CS1D value does not resume after changeover, the address did not follow the active CPU: go back to the duplex Ethernet settings and the unit versions, not to switching logic on the panel.

The decisions #

  • One host entry for the redundant CS1D, aimed at the single system IP address, with no CPU-selection logic anywhere in the NS project.
  • Yes, the CP1H joins the same panel at the same time as a second host through its CIF41. FINS over Ethernet serves both connections, because Ethernet and FINS are transport and protocol, not competitors.
  • One panel is not redundant. When the operator station itself must survive a failure, the answer is a second panel aimed at the same two destinations, not more configuration on this one.

Questions asked

Do both CS1D-ETN21D units get typed with the same IP address?

No. You set the address through the duplex configuration the unit's manual defines: the local IP address belongs to the Ethernet unit, and the duplex pair manages which unit answers for it. Manually entering one identical address on both units outside that procedure gives you two devices claiming one address, which is an address conflict, not redundancy.

Does this setup give me a redundant HMI?

No. CPU redundancy lives at the controller; the single NS remains a single point of failure, and losing it hides both the CS1D and the CP1H. If the process needs operator-station redundancy, the fix is a second panel aimed at the same two destinations, not additional settings on the one panel.

Should I pick FINS or Ethernet for each connection?

The question dissolves once the layers are separate: Ethernet is the network, FINS is the application protocol riding on it. Both hosts in this project are FINS over Ethernet, the CS1D pair through the CS1D-ETN21D units and the CP1H through the CIF41. There is no mode conflict between them.

How long is the communications interruption at CPU changeover?

It is a measured number, not a figure to design in blind. Run the changeover test with a live-changing value on screen, note how many seconds the value freezes and the communications error lasts, and record that as your system's recovery time. Re-measure after any CPU or Ethernet unit version change.

Keep reading

  • Troubleshooting

    Connecting a CompactLogix PLC to an HMI over EtherNet/IP

    A CIP transport unsupported fault on a Generic Ethernet/IP module in a CompactLogix project means the connection was built the wrong way around. For HMI tag access, delete the module, select the panel's Rockwell PLC driver, point it at the controller IP, and rebuild the tags — no assembly instances, I/O sizes, or EDS file.

    HMI and touchscreens

  • How-to

    Connecting an HMI Panel to an S7-1500 PLC

    Confirm the HMI's documented driver covers the S7-1500 for your exact panel model and software revision, put the panel and CPU on the same subnet, permit the connection in the CPU protection settings, then validate one known PLC tag before building screens. A working Ethernet link alone proves nothing about tag access.

    HMI and touchscreens

  • How-to

    Connecting an Omron CV1000 PLC to WinCC over an OPC server

    Classic WinCC has no Omron CV-series channel, so the working route is an OPC server that speaks Host Link to the CV1000 and OPC DA to WinCC. Configure the server against the PLC first, prove one read, then build WinCC tags from the server's item addresses. Use the documented CV1000-CPU01-EV1 Host Link reference values: ASCII, 7 data bits, even parity, 2 stop bits, unit 00, 9600 or 19200 bps.

    HMI and touchscreens