IMDTouchKnowledge BaseShop main store

Selection guide

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

HMI and touchscreens Published 6 min read

Short answer

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.

On this page
  1. What an EtherNet/IP listing actually promises
  2. The driver list is the specification, not the brochure
  3. The NJ/NX rule that disqualifies FINS-only panels
  4. Access routes compared
  5. The bench test that qualifies a candidate
  6. Worked example: a poll never sees a short event
  7. The decision, case by case
  8. Questions asked

A low cost HMI qualifies for an EtherNet/IP job on one condition: its installed driver reads and writes your controller's application variables, proven on the bench before anything else is compared. The Ethernet port on the datasheet proves nothing, and neither does the protocol name — EtherNet/IP is CIP carried over Ethernet, and many inexpensive panels carry the port while their Omron support stops at FINS device addressing. On Omron NJ/NX controllers that gap is decisive: with tag data in use, device codes and address codes cannot be used, so the panel must reach variables by name or through a fixed-address mapping you build and document. The checks below turn that into a pass or fail.

What an EtherNet/IP listing actually promises #

EtherNet/IP is the ODVA-managed adaptation of CIP to Ethernet: CIP is the protocol, EtherNet/IP is its Ethernet carrier, and "EIP" on a specification sheet means that stack, not a separate protocol. What the listing never tells you is which data the panel can address. Two CIP services dominate, and they are not interchangeable: explicit messaging, where the HMI requests named data on demand, and cyclic I/O assemblies, predefined datasets exchanged on a fixed schedule. Operator screens live on explicit messaging; a device that advertises assemblies may never serve a tag.

The panel's role is fixed, too. Beijer's Allen-Bradley Ethernet/IP driver help states that the HMI's EtherNet/IP driver acts as the master, meaning the controller must answer the requests your panel actually sends. Data-access models differ even between controllers that all speak CIP: a Siemens application example serves process values from a SIMATIC through its built-in EtherNet/IP driver acting as a CIP server, while Parker's ACR EtherNet/IP programmer's guide accepts tags only as parameter numbers such as "P4012". Neither model is wrong; each demands a driver written for it.

One safety note belongs here: CIP Safety is a distinct profile, documented by Rockwell for EtherNet/IP and ControlNet, and an HMI tag driver takes no part in it. Emergency stops and guard paths stay in the safety controller and the hardwired circuits.

The driver list is the specification, not the brochure #

The brochure describes the platform; the editor installed on your PC holds the fact. Open the candidate's engineering software and read its driver list before comparing screens, and record panel model, editor release and driver name as one combination, because driver scope changes between releases. Pro-face's EtherNet/IP driver help, for instance, notes that CPU Series B and C support the CIP protocol, and tells users to select Control/Compact/Flex Logix Native when native tag names are used on external devices — native tags are their own selection inside the driver, per controller family.

The same discipline exposes missing support fast. The Omron driver list in Crimson 3.0 held two entries, "G9SP-Series via FINS" and "Master via FINS": a safety-controller family and a protocol role, neither of which is NJ/NX variable access. A panel with such a list is not condemned, but it is unqualified until the mapping route below is built on purpose. If the editor lists no driver for your controller family at all, that is a different problem with different outs, covered in when the HMI software has no driver for your PLC.

The NJ/NX rule that disqualifies FINS-only panels #

Pro-face's Omron CS/CJ/NJ Series EtherNet/IP driver documentation contains the decisive line for this selection: when tag data is used on CJ2, NJ, NX1P, NX1 or NX7 series, device code and address code cannot be used. NJ/NX application data lives in variables, not in the CJ-era memory map, so an inexpensive panel whose Omron support consists of FINS device addresses has nothing to read.

Two legitimate routes forward exist. The first is a driver that addresses NJ/NX variables by name; verify variable visibility, name syntax, data types, array and string handling, and write permission in the NJ/NX-series CPU Unit software user's manual, and in the NX-series EtherNet/IP Unit user's manual (W627) when an NX unit terminates the connection.

The second keeps the controller as owner: pin the variables the screen needs to fixed memory addresses in the controller project and let a FINS driver read those addresses. That mapping is a design branch, not a setting — it exists only if your controller configuration supports fixed-address assignment for those variables. Once built, the table of variable, address, data type and write ownership becomes a maintained interface document that later controller edits can silently break.

Access routes compared #

The method is controller-first whatever the protocol; on plants that also speak Modbus, the same check sequence applies to selecting a Modbus TCP HMI panel for an existing controller.

Route What you must verify What it costs later
Driver with NJ/NX tag access Variable visibility, name syntax, data types, string and array handling, write permission Least: the screen follows controller variable names
FINS device-address driver plus fixed-address mapping That the controller can pin the needed variables to fixed addresses, and that the mapping table exists An interface document to maintain; edits can break screens silently
PC-based HMI runtime or gateway middleware Runtime driver coverage, licensing, host hardware at the machine A software layer and a computer to support, in exchange for wide driver choice

When no terminal driver qualifies, the move is up one tier: run the HMI or SCADA runtime with a proven CIP driver on industrial panel PCs at the machine, and settle the terminal-versus-display question separately.

The bench test that qualifies a candidate #

  1. Install the candidate's editor and open its driver list; write down panel model, editor release and driver name together.
  2. In the controller, create three test variables: one BOOL, one 32-bit integer, one string.
  3. Build one screen with an object on each and go online; all three must display live values.
  4. Write back from the screen: toggle the BOOL, step the integer, and confirm both in the controller's own watch view.
  5. Check the edges: signed versus unsigned range on the integer, full string length, and the driver's behavior on a write to a read-only variable.
  6. Record the result against the combination from step 1. A panel that passes step 4 is qualified at any price tier; a panel that fails it is disqualified at every price tier.

Worked example: a poll never sees a short event #

Illustrative inputs: a reject-diverter bit pulses for 200 ms, and the driver's effective poll cycle for your tag count measures 500 ms. A sample lands inside the pulse with probability 200 ms / 500 ms = 0.4, so on average the screen shows 2 pulses in 5 and misses 3. No editor or faster screen fixes that; sampling cannot observe events shorter than its own period.

The decision: latch the event in the controller, let the HMI poll the latch bit at leisure and command the reset from the screen, and poll directly only for states that persist longer than two poll cycles. Forgetting to latch is a classic control failure — the same shape as a machine that re-engages after overcurrent because nothing latches the trip.

The decision, case by case #

  • NJ/NX with native variables: buy a panel whose installed driver names NJ/NX tag access, after the three-variable bench test passes. FINS-only panels are fallback hardware, not candidates.
  • A FINS-only panel is the affordable option: qualify it only against a fixed-address mapping you have built in the controller and written down; without that table it cannot see NJ/NX data and is out.
  • The application needs cyclic I/O assemblies: an HMI tag panel is the wrong device class; use a scanner or gateway that owns the assembly and put the HMI behind it.
  • No terminal driver qualifies: move the visualization to a PC-based runtime and choose the touchscreen computer for the location.
  • Short events must appear on screen: the controller latches, the HMI reads and resets; nothing shorter than two poll cycles is ever polled directly.

Questions asked

Are EtherNet/IP, EIP and CIP the same thing?

EtherNet/IP is CIP carried over Ethernet under ODVA management, so the three abbreviations describe one stack, not three options. The trap is older or casual listings where Ethernet IP means plain Ethernet with the Internet Protocol and carries no CIP at all. The only proof that a panel speaks the industrial stack is a driver document that names your controller family.

Can a FINS device-address driver read NJ/NX variables?

Not as it stands. One vendor's Omron driver documentation for CJ2, NJ, NX1P, NX1 and NX7 states that with tag data in use, device codes and address codes cannot be used. The route that works is deliberate: pin the variables the screen needs to fixed memory addresses in the controller project and let the FINS driver read those addresses, keeping the variable, address, type and write-ownership table as a maintained document.

Does tag browsing prove the driver is compatible?

No. Browsing is a convenience layer; a driver can accept manually entered variable names while its browse view returns nothing. If a correct manual entry reads and writes, the communication path is proven and the empty browse list is an editor limitation. If neither browsing nor a correct manual entry works, the fault is in the driver or controller configuration, not the graphics.

Will a 500 ms poll catch a 200 ms status pulse?

On average, no: the pulse occupies 200/500 = 40% of the poll period, so about 3 of every 5 pulses fall between samples. Latch the pulse in the controller, poll the latch bit and reset it from the screen. Poll directly only for states that persist longer than two poll cycles.

What do I do when no terminal driver qualifies?

Move the visualization up one tier: run an HMI or SCADA runtime with a proven CIP driver on a touchscreen computer at the machine, or insert a gateway between controller and display. Middleware and PC runtimes add licensing and a host to maintain, so treat them as architecture changes, not accessories. The panel choice then becomes a display choice.

Keep reading

  • Selection guide

    Selecting a Compact HMI for ControlLogix Over Ethernet

    Select a compact HMI only by a documented ControlLogix tag-based EtherNet/IP client driver plus its matched software and firmware set: the C-More CM5-T4W documents ControlLogix through 1756-ENBT or 1756-ENET/B bridges with CM5-PGMSW 8.0 or later, and PanelView 5310 terminal firmware from the same release pairs with View Designer 8.01.00 and needs Logix firmware 27 or later. CompactLogix-only support, such as the PanelView 800 documented list, disqualifies a terminal for this station.

    HMI and touchscreens

  • 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

  • Troubleshooting

    Why an HMI Transfer Fails in Initial Start Mode Despite Ping

    Ping success proves only that the panel's IP stack answers. On a new Magelis XBTG in Initial Start Mode, run three checks in order: build in the engineering version that still supports the target (Vijeo Designer 6.2 for XBTG), clear the license so the download command activates, then load runtime and application over one transport at a time.

    HMI and touchscreens