IMDTouchKnowledge BaseShop main store

Comparison

Panel PC HMI or PLC plus HMI for meter data display

Panel PCs and displays Published 7 min read

Short answer

Run the meter vendor's software on an industrial panel PC and read the meter directly when the operator screen is the only consumer of the values and the software's driver covers the meter's Modbus link. Put a PLC between meter and screen when the same values feed control logic, alarms or other equipment, and prove either path by interrupting the link to confirm a bad-quality indication instead of a stale number.

On this page
  1. Two ways to put meter values on a screen
  2. When the panel PC reads the meter directly
  3. When a PLC belongs between meter and screen
  4. Worked example: one power meter feeding one operator screen
  5. Prove the path before you trust the number
  6. The decision for each case
  7. Questions asked

For a power meter feeding an operator screen, the short path is usually the right one: run the meter vendor's visualization software on an industrial panel PC and let it read the meter over Modbus directly. Put a PLC between the meter and the screen when the same values also feed control logic, alarms, interlocks or other equipment — the controller then owns the values and the HMI only displays them. The direct route crosses one communication link and needs three commissioning points; the PLC route crosses two links and needs five. Count those, match them to what consumes the data, and prove whichever you build by breaking the link on purpose: a commissioned screen shows bad quality when the meter disappears, never a frozen number that looks live.

Two ways to put meter values on a screen #

Both architectures end at the same glass; they differ in who collects the data. A PLC exists to run real-time logic and talk to field devices. An HMI exists to show an operator what is happening. When the meter's numbers are only for looking at, the collection job can sit in the screen's own software. When the numbers drive decisions, they belong in the controller, and the screen becomes a window onto controller tags.

Point of comparison Panel PC reads the meter directly PLC between meter and screen
Links a value crosses 1 (meter to panel PC) 2 (meter to PLC, PLC to HMI)
Commissioning points 3 5
Control logic can use the values No — they never enter a controller Yes — they live as controller tags
Collection when the screen application closes Stops with the software The PLC keeps polling the meter
Where scaling happens Once, in the vendor software Once, in the PLC; scaling again in the HMI corrupts the value
Driver the project depends on The software's driver must cover the meter The HMI's driver must cover the PLC
What a screen fault stops Display and collection together Only the display

When the panel PC reads the meter directly #

A visualization client can poll a Modbus device itself; a PLC is not a required middleman. The direct route works when the vendor software's driver covers the interface the meter actually presents — Modbus TCP on the network or Modbus RTU on a serial line — at the address and register map the meter documents. Confirm that driver coverage before anything else, because it is the one dependency the whole screen hangs on; the walkthrough of which HMI software works with which HMI panel hardware applies directly to this check.

Commissioning is short: set the meter's communication settings, define the device in the software, bind the tag to the display object. Keep the meter values read-only on the screen and allow a write only where a procedure deliberately intends one.

If the screen takes hard use, splitting the computer from the touch display keeps a cracked glass from taking the software installation with it, at the cost of a second device, a second mount and one more failure point — for a small meter screen, the all-in-one panel computer is usually still the simpler build.

When a PLC belongs between meter and screen #

The moment one of the meter's quantities must drive logic — an alarm, an interlock, a load-shedding decision, a value shared with another system — the PLC route stops being optional. A controller exists to execute that logic in real time and talk to field devices, and a screen application is the wrong home for a decision that must run whether anyone is watching or not. Reading an energy meter into a controller over Modbus TCP is a routine, documented pattern on everything from compact PLCs to redundant controller systems.

This architecture also simplifies the screen side. The HMI only needs a driver for the PLC, and PLC drivers are the best-covered part of any HMI package. The meter protocol work — data types, word order, register maps — happens once, in the controller, and when it carries a 32-bit quantity across Modbus, register order decides whether the number comes out right; the check for displaying a PLC real value over Modbus covers it.

One safety rule comes with the route: any meter value feeding an interlock or protective function must live in the controller that owns that function, because a closed screen application must never take a protection with it.

Worked example: one power meter feeding one operator screen #

The case as asked: one power meter with a Modbus interface, one operator screen, and nothing else consuming the values.

  • Direct path (vendor software on the panel PC): 1 communication link, meter to panel PC, and 3 commissioning points — the meter's communication settings, the software's device definition, the screen binding.
  • PLC path: 2 communication links, meter to PLC and PLC to HMI, and 5 commissioning points — the meter's settings, the PLC's device definition for the meter, the controller tag, the HMI's device definition for the PLC, the screen binding.

Rule: every link is a failure point between a working meter and a trusting screen, and every mapping is a place where an address, a data type, a word order or a scale factor can turn a live value into a stable, wrong one.

Arithmetic: direct path, 1 link + 3 points; PLC path, 2 + 5. Extra link: 2 - 1 = 1. Extra points: 5 - 3 = 2. Silent-error surface: 5 / 3 ≈ 1.7 times the direct path.

Result: both routes produce an identical screen, but the direct one reaches it across one link and three commissioning points, the PLC one across two links and five.

Decision: with only eyes on the data, build the direct path. The threshold is the second consumer — the moment any of these values must also drive an alarm, an interlock or another device, the balance flips, because the two extra commissioning points then buy a single controlled data model instead of a duplicate, and collection survives a closed screen.

Prove the path before you trust the number #

A numeric object holding a plausible number is not a commissioned object. Run this sequence on either architecture before building out the remaining screens:

  1. Bind one measurement you can change on demand — a phase current you can load and unload — and leave the rest of the screen for later.
  2. Change the measured condition and watch the screen value move the same way as the meter's own display.
  3. Compare magnitude and unit against that local indication. A stable but implausible number means an address, a data type, a word order or a scale is wrong, and the fix is to apply the scale once, in one place.
  4. Break the link on purpose — unplug the cable or drop the meter's power for a moment — and confirm the screen flags bad quality or a communication fault instead of freezing the last value as if it were current.
  5. Restore the link and confirm collection resumes by itself, without recreating the device.

The deliberate interruption is the step most often skipped, and it is the only one that separates a live screen from a frozen one. If the meter sits on RS-485 and the screen reports no response instead of a value, work through fixing HMI Modbus device no response over RS-485 before blaming the architecture.

The decision for each case #

  • Display only, and the vendor software covers the meter's Modbus interface: build the direct path. The software belongs on a touchscreen computer at the machine — the job industrial panel PCs are built for — and the three-point commissioning above is the whole project.
  • Display only, but the software has no driver for the meter's interface: build the PLC path. Controllers carry broad Modbus support and the HMI only has to talk to the PLC, so the driver gap gets absorbed where it costs the least engineering.
  • Values feed logic, alarms, interlocks or other equipment: build the PLC path. The controller reads the meter, owns the values as tags, and serves them to the HMI; show the controller's copy even for eyes-only extras, so the screen never holds the only copy of a value that equipment depends on.

Questions asked

Can the panel PC software and a PLC both read the same meter at the same time?

Over Modbus TCP, usually yes: the meter is a server and most units accept several simultaneous client connections, but check how many concurrent connections the meter's documentation allows before you plan on it. Over serial Modbus RTU, no — the line is one master polling at a time. If two masters must share a serial meter, you need hardware that explicitly supports multi-master access, or you give the polling to one device and let the second read from that device's data.

How fast should the screen refresh meter values?

For an operator reading kilowatts or energy totals, about once per second is generous, because electrical values move slowly compared with what a person reads. Poll faster only when a trend must catch a short event, and remember every extra poll adds load to the meter and the link. Set the client's response timeout shorter than one or two refresh intervals, so a dead link shows bad quality within seconds instead of looking like quiet data.

Does the meter vendor's software replace the PLC entirely?

Only for visualization and recording. The vendor software reads, displays and often logs meter values, and for a display-only screen that is the whole job. It does not run interlocks or machine logic. The moment a measurement must trip an alarm, open a breaker or feed another device, that decision belongs in a controller, and the PLC path becomes the honest architecture even though the screen itself could technically live without one.

Is a serial Modbus meter slower to display than an Ethernet one?

Usually, yes. A Modbus RTU line carries one request at a time at its configured baud rate, so every added register block stretches the update interval, while a Modbus TCP meter answers clients over a switched network with far more throughput. Distance and device count limit RS-485 in ways Ethernet switches do not. If a serial meter answers with no response after the build, treat it as a wiring or addressing fault first, not as a reason to change architecture.

Keep reading

  • How-to

    Running a PLC-hosted visualization on a remote HMI panel PC

    The PLC-hosted visualization reaches a panel PC through a panel-side PLC HMI client deployment: install the client for the panel platform, confirm the license, run the remote-client deployment that selects the hosting PLC, verify the network path, and start the client from a CE shell command. Downloading TargetVisualization to the PLC only feeds a monitor connected to the controller; it installs nothing on the panel.

    HMI and touchscreens

  • Explainer

    Where JavaScript and WebAssembly Actually Run on an HMI

    JavaScript and WebAssembly execute in the HMI client's browser engine — the panel itself, a panel PC, or a desktop browser — never inside the PLC, which only serves the files and exposes data through a documented interface. Decide on the rendering route the installed runtime provides, then verify rendering, module execution, and the data path in that order.

    HMI and touchscreens

  • Troubleshooting

    Why HMI SFTP Cannot See the SD Card Data Log Files

    On a PanelView Plus 7 Series B terminal, the SFTP service publishes internal storage only; the SD card and USB drives never appear to a remote client. A data log whose path root is removable media cannot be retrieved remotely until you redirect it to internal storage or copy it at the terminal with the file explorer application.

    HMI and touchscreens