IMDTouchKnowledge BaseShop main store

Selection guide

How to Select Lightweight HMI Software for Modbus I/O Control

HMI and touchscreens Published 8 min read

Short answer

Select on three gates in order: a driver that speaks Modbus RTU (and Modbus TCP if the LAN path is required), a tag license at least 20 percent above your counted total, and a runtime that runs the exported project on a clean PC. A 56-device floor plan counts 154 tags, so a 150-tag edition already fails. Prove one floor plan, one popup, one live indicator and one write before you pay.

On this page
  1. Count tags before you compare packages
  2. Match the driver to both network paths
  3. Require a standalone runtime
  4. What the package must pass
  5. The proof project before you pay
  6. Packaged HMI or custom code
  7. The decision
  8. Questions asked

Select lightweight HMI software on three gates, in this order: the driver list, the counted tag total, and a standalone runtime. The package must speak Modbus RTU to your gateway over RS-485 and, if the local-area-network path is required, the exact protocol the gateway serves on Ethernet — usually Modbus TCP. Its tag license must sit at least 20 percent above your counted total, and its runtime must run the exported project file on a PC that has never had the development tool installed. Count tags before comparing feature lists: one floor-plan project with 56 field devices counts 154 tags once popups, alarms and navigation variables are included, which overruns a 150-tag limited edition. A four-object proof on a clean runtime PC settles everything else before you pay.

Count tags before you compare packages #

Every animated object on the screen is the end of a chain that ends in a tag, and a limited edition counts every tag the project defines — not the number of devices drawn on the floor plan. Field reads, command writes, separate feedback, internal variables, alarm bits and system tags all draw against the same license.

Tag category What it covers Count per item
Field status read Door lock state, light state, camera power 1 per monitored point
Command write Unlock, light on/off, fan start 1 per command
Feedback read Fan run status separate from the start command 1 per verified command
Internal Popup and navigation variables, intermediate logic 1 per variable
Alarm Door held open, fan fault, global acknowledge 1 per condition
System Heartbeat write, link status read About 2 per project

Worked example: one floor of a secure facility #

  • 16 door locks: 16 status reads + 16 command writes = 32 tags
  • 20 lights: 20 status reads + 20 command writes = 40 tags
  • 8 intercom stations: 8 status reads + 8 acknowledge commands = 16 tags
  • 8 cameras: 8 power reads + 8 select commands = 16 tags
  • 4 smoke evacuation fans: 4 commands + 4 status reads + 4 run feedback = 12 tags
  • Field subtotal: 32 + 40 + 16 + 16 + 12 = 116 tags
  • 14 popup and navigation internal tags
  • 21 alarm tags: 16 door-held-open bits, 4 fan fault bits, 1 global acknowledge
  • 3 system tags: heartbeat write, link status read, operator level
  • Total: 116 + 14 + 21 + 3 = 154 tags

Fifty-six visible devices produced 154 tags — 2.75 tags per device on this class of project. A 150-tag edition is over budget by 4 tags before the first change order, and the headroom rule gives 154 × 1.2 = 184.8, so plan for 185 tags. Select a license of at least 200 tags or the unlimited edition, and read the vendor's tag-count report before buying: some licenses count only device tags, others count every internal tag, and the report is the authority.

Match the driver to both network paths #

Your field devices sit on a dedicated fieldbus and reach the HMI through a gateway that converts them to Modbus. That gives two paths, and each needs its own driver configuration — a LAN connection is not serial Modbus with a different cable.

Path Driver the package must list Verify against the gateway document
Modbus RTU over RS-485 Modbus RTU serial driver Unique station addresses in the 1-247 range, identical baud, parity and stop bits, observed polarity, 120 Ω termination at both bus ends
LAN to the gateway The exact Ethernet protocol the gateway serves, usually Modbus TCP Gateway IP address and port, plus the unit ID that routes requests to the serial side

A "communicate over the LAN" requirement is not a protocol. Open the gateway document, find the Ethernet section, and take the protocol name from it: if the gateway serves Modbus TCP, any package listing Modbus TCP qualifies; if it serves a vendor protocol, only packages naming that exact driver qualify, and no panel fixes that. The same protocol-first discipline applies to Selecting a Modbus TCP HMI Panel for an Existing Controller.

Two addresses identify every object, and they are different layers. The gateway's Modbus address — station number on serial, unit ID plus register on Ethernet — selects which device answers the request; the fieldbus address inside the gateway selects which physical input or output that register represents. Take the data type, table and location for each point from the gateway's mapping document, never from HMI defaults.

Modbus exposes four tables — coils (read/write bits), discrete inputs (read-only bits), input registers (read-only 16-bit) and holding registers (read/write 16-bit) — and each table has its own function codes and its own start address, so a tag pointed at the wrong table returns nothing or a neighboring point.

When commissioning, split the fault by scope: every point stale points at the physical link or the shared serial settings; one point wrong points at that mapping. If a tag reads correctly online while its icon stays wrong, the binding is wrong, not the driver — the layer split that also explains Why HMI Indicators Stay Off Over Modbus RTU Polling. At 9600 baud a single-register round trip costs about 20 ms including turnaround, so 154 one-point polls refresh the floor plan in roughly 3 s; map contiguous points into block reads so one transaction carries many tags and the screen stays responsive.

If more than one panel shares the RS-485 bus, treat it as a multidrop network and apply the wiring and addressing covered in Connecting Multiple HMIs to One PLC Over 200 ft Serial.

Require a standalone runtime #

The architecture that survives deployment is two modules: a configuration tool where you design the screens, and a runtime that loads the exported project file and runs with no development tool installed. Verify that the export produces a file the runtime loads directly — not a project that only opens back inside the development environment.

Then test on a clean PC: install nothing but the runtime, copy the exported file over, run it. That one test catches license caps below your tag count, graphics referenced by absolute paths on the development machine, missing fonts and resources, and version mismatches between tool and runtime. Package graphic resources with the project or reference them relatively; a project that displays during design and fails at runtime is almost always pointing outside itself.

What the package must pass #

Criterion Minimum to accept How you verify
Modbus RTU driver Configurable station address, baud, parity, stop bits One live serial connection in the proof project
Ethernet protocol driver The gateway's documented Ethernet protocol, named exactly Driver list plus one live connection
Tag capacity Counted total plus 20 percent headroom Tag-count report on the finished skeleton
Standalone runtime Runs the exported project with no development tool present Clean-PC run
Graphic import Floor-plan file as background, icon files for indicators and pushbuttons Proof project
Popup subpanels Opened from the background screen and closed without a restart Proof project
Write path Command write plus an independent feedback read Operate one pushbutton and watch the feedback tag
Alarms Bit conditions with acknowledge One door-held-open alarm

The proof project before you pay #

  1. Import the real floor-plan graphic as the background of one screen.
  2. Bind one indicator to a live status point and watch it follow the field for several minutes.
  3. Bind one pushbutton to a real command and confirm it on an independent feedback tag, never on the value you just wrote. Do this on a bench gateway or an out-of-service zone — a write to a door release is a security event, not a test.
  4. Build one popup and open it from the floor plan.
  5. Export the project, copy it to the clean runtime PC, and run it there.
  6. Read the tag-count report, multiply the planned total by 1.2, and compare the result with the license you are about to buy.

Prove the chain object by object on the real gateway, the same discipline as Testing HMI Simulation Against a Live PLC, before the project grows past the point where a failure is easy to localize.

Packaged HMI or custom code #

A custom application can do everything a lightweight package does — animation through object properties, communications through a commercial OPC or DDE server — and none of it comes free: driver integration, project-file design, deployment, diagnostics, security, testing and long-term maintenance all become code you own. The packaged HMI resolves this class of project because floor-plan import, icon import, popup navigation, driver handling, project export and the standalone runtime are already product functions. Write the custom application only when owning that entire lifecycle is the point of the project, not a way to save a license fee.

The decision #

  • Gateway on RS-485 only: any package with a Modbus RTU driver and a tag license above your headroom figure passes; run the four-object proof anyway.
  • LAN path required: the gateway's Ethernet protocol name decides — Modbus TCP qualifies any package that lists it, and a vendor protocol disqualifies every package that does not name it.
  • 154 counted tags on the worked floor: buy at least the 200-tag license or unlimited; the 150-tag edition is out.
  • Custom code: no, unless owning the software lifecycle is deliberate; otherwise the first driver update you do not have to write decides it for you.

Questions asked

How do I estimate the tag count before the screens exist?

Write the point schedule while the screens are still on paper: every door, light, intercom, camera and fan, one line each, marked monitor, command or feedback. Multiply the device count by 2.75 for a first estimate, then replace that with the real schedule total plus 20 percent before you buy. The schedule, not the icon count on the floor plan, is the number the license has to cover.

Can one Modbus driver serve both the RS-485 link and the LAN path?

One project can hold both connections, but they are two driver configurations, not one. The serial side needs station address, baud, parity and stop bits matched to the gateway; the Ethernet side needs the gateway's IP address, port and the unit ID that routes to the serial side. The Ethernet connection only works at all if the gateway actually serves Modbus TCP, so confirm that in the gateway document first.

Why not write a small custom application instead of buying HMI software?

You can, and the first version will even look easy. Budget what the package gives you for free: a maintained Modbus driver, a project-file format, popup navigation, alarm handling and a runtime, plus the years of maintenance after the original author moves on. Write the custom application only when owning that software lifecycle is a deliberate goal of the project rather than a way around a license fee.

What problems does running the project on a clean runtime PC catch?

It catches license caps below the tag count, graphics referenced by absolute paths on the development machine, missing fonts and resources, and version mismatches between the development tool and the runtime. Keep one clean machine or virtual machine for exactly this test and repeat it after every tool update and before every delivery, because each of those faults appears only on a PC that has never seen the development environment.

Keep reading

  • Selection guide

    Selecting a Modbus TCP HMI Panel for an Existing Controller

    A replacement HMI qualifies when its Modbus TCP client driver reproduces the working panel's tag map exactly: data area, raw address, word order and write behavior. A connection that polls proves reachability, not correctness — prove one known tag and one supervised write before rebuilding the screens.

    HMI and touchscreens

  • Troubleshooting

    Why HMI Indicators Stay Off Over Modbus RTU Polling

    Indicators on internal tags animate from HMI memory with no serial traffic; an indicator bound to a PLC tag needs a completed Modbus RTU read of the right address in the right data area. Confirm the PLC bit changes, then read the request and response, then fix the address at one known point.

    HMI and touchscreens

  • How-to

    Connecting Multiple HMIs to One PLC Over 200 ft Serial

    RS-232 on good cable can reach 200 ft at 9600 baud, but RS-232 connects exactly two devices, so three HMIs cannot share one PLC port. Put an RS-232-to-RS-485 adapter at the PLC and at each panel, daisy-chain one twisted pair, and terminate only the two ends. Confirm the PLC port's protocol accepts more than one master before ordering adapters.

    Industrial networks