IMDTouchKnowledge BaseShop main store

Selection guide

Selecting an HMI That Talks Modbus RTU to Remote I/O

HMI and touchscreens Published Updated 9 min read

Short answer

Select the HMI whose exact software release documents a Modbus RTU client driver that can open the serial port, or route the data through a supported communications server. Prove the choice by polling one module and reading the driver diagnostics before comparing graphics or scripting.

On this page
  1. Does the HMI software support Modbus RTU over RS-485?
  2. How do I verify a specific HMI release before committing?
  3. Should the HMI use a native driver or a communications server?
  4. How many modules can share one RS-485 segment?
  5. How fast will the display update over RS-485?
  6. How do I prove the link works before building screens?
  7. Why does a live tag show the wrong value?
  8. What control functions belong outside the HMI scripts?
  9. Which features should I compare only after the link passes?
  10. Questions asked

Select the communications path before the screen editor. An HMI for RS-485 remote I/O earns its place with three facts about its exact software release: a documented Modbus RTU client driver, runtime access to a serial port, and coverage of the read and write functions the modules use. A package with a strong graphics reputation can still be the wrong choice for a string of remote I/O modules, and a brand name proves nothing about one release's driver list. The order below gives you the verification steps, the segment limits and timing you can plan against, and the one-module test that settles compatibility before a single screen object exists.

Does the HMI software support Modbus RTU over RS-485? #

Only if the exact release documents a Modbus RTU client driver that can open a serial port; an RS-485 port alone proves the electrical layer, not the protocol, and a Modbus TCP driver cannot reach a serial segment without a gateway.

RS-485 is the electrical standard: a differential pair shared by every device, where one master transmits and the others answer. Modbus RTU is the message protocol that normally rides on it, and the Modbus specification defines what a frame carries: a station address, a function code, the data, and a 16-bit CRC check, with each RTU frame separated by a silent interval. Up to 19,200 baud the interval is at least 3.5 character times. At higher rates, the Modbus Serial Line Protocol and Implementation Guide V1.02 recommends a fixed 1.75 ms frame gap. The remote I/O families you would pair with it, Advantech's ADAM-4000 series for one, offer analog, RTD, thermocouple, digital, relay and counter I/O with Modbus RTU over RS-485.

Two things still have to line up. The module must actually be running the mode the driver speaks: the family name does not settle it, so record each installed module's model, configured command mode, station address and serial format from its communications manual. And the HMI driver must operate as the client, the side that initiates the requests.

"Does WinCC support Modbus RTU?" is a release-level question, not a brand-level one. WinCC, InTouch and CIMPLICITY have carried different communication options across their releases, and a colleague's recollection, however confident, is not a supported-device list. What you buy against is the driver documentation for the release you will actually install. If that release has no driver for your devices, you face the fork covered in when the HMI software has no driver for your PLC: change the release, change the data route, or put a protocol layer in between.

How do I verify a specific HMI release before committing? #

Run five checks on the exact release number before comparing any feature list: driver presence, client operation, serial-port access from the runtime, driver and runtime licensing, and coverage of the read and write functions the modules use.

What to confirm Where to look Why it decides the selection
Modbus RTU client driver The release's supported-device list and the channel setup in the engineering software The HMI must initiate the requests; nothing else reads the modules
External communications-server route The HMI's interface documentation and the server's own driver list A supported server can supply serial Modbus when the native driver is absent
Serial-port access at the runtime Runtime platform documentation and the operating system's port setup A driver is useless if the runtime cannot open the COM port
Driver and runtime licensing The vendor's license terms for the deployed configuration The editor's feature list says nothing about what a running station is licensed for
Required read and write functions The driver's function support against the module register map Reading input registers and writing coils or holding registers must both be covered if operators set values

Run the checks with the manufacturer's evaluation software against one bench module, not against a datasheet summary. An hour on the bench answers what a week of feature comparison cannot.

Should the HMI use a native driver or a communications server? #

Take the native driver for one panel reading one string of remote I/O; take the communications server only when it is the documented route to the modules or when several applications must share the same serial data.

The native driver means one component, one configuration and one place to look when a value stops moving, which makes it the simplest arrangement to commission and the simplest to fault-find. The server route adds a machine, a license and a configuration of its own, and it earns that overhead when the server must feed several clients at once or when it is the only supported path to the devices. For a small direct-I/O job, the options compared in how to select lightweight HMI software for Modbus I/O control are usually enough. When the chosen runtime is PC-based, the machine-side station is a touchscreen computer, and industrial panel PCs are the hardware class that fills that spot.

How many modules can share one RS-485 segment? #

For an initial layout, budget up to 32 devices on a conventional RS-485 segment, including the one client. The actual limit depends on the transceiver loads, biasing, and the documented device limits. Use a second segment when the design exceeds those limits or when your measured poll cycle is too slow.

The 32-device planning figure and the range of Modbus station addresses solve different problems. Only documented lower-load devices and a compatible biasing design justify a larger un-repeated segment. Run a trunk with short drops, terminate the two physical ends, and apply biasing as the interface manuals specify. Check the terminal mapping from each wiring diagram because vendors may label the pair differently. Give each addressed module a unique station address.

How fast will the display update over RS-485? #

At 9,600 baud with 8E1 framing, one successful one-register read takes at least about 25.2 ms of serial time. Ten such reads need at least about 252 ms. Module response delays, driver scheduling and screen refresh add time. Measure the complete cycle with the selected hardware.

For back-to-back polling in steady state, count the request, the reply and two frame gaps. One gap separates the request from the reply. The other separates that reply from the next request. At 9,600 baud, an 8E1 character takes 11 bit times and each minimum gap is about 4.0 ms.

Register reads Request and reply Minimum time per transaction
One register 8-byte request and 7-byte reply (8 + 7 + 3.5 + 3.5) × 11 ÷ 9,600 = 25.2 ms
Four contiguous registers in one request 8-byte request and 13-byte reply (8 + 13 + 3.5 + 3.5) × 11 ÷ 9,600 = 32.1 ms

Four separate one-register requests use at least 100.8 ms. Grouping saves wire time when the device exposes the registers as one legal block. At 19,200 baud the one-register wire minimum falls to 12.6 ms. Measure the actual time from the end of the request to the start of the reply and use that value if it exceeds the minimum gap. Test the driver with one device disconnected as well. A timeout and retries can extend the whole poll cycle while other modules are still healthy.

Bench-test one module with one client and read the driver's diagnostic counters before drawing a single object; the split among requests sent, replies received, timeouts and exception responses names the failing layer immediately.

What the diagnostics show Where the fault lives Next check
No requests leaving the station Channel or port setup Driver activation, serial-port selection, license state, channel enabled
Requests sent, zero valid replies Physical link or device settings Wiring, termination, baud, parity, stop bits, command mode, station address
A Modbus exception response instead of data Request against the module map Function-code support and address bounds in the module register map
Valid replies with wrong values Interpretation in the tag Addressing convention, data type, word order, scaling
Right value in the tag monitor, wrong on screen Object binding The object's data source, expression, limits and formatting

Match the serial format at both ends before anything else, and keep one client on the pair during commissioning: a second polling application breaks request and response sequencing. When requests leave and nothing returns, the wiring and addressing faults behind a silent Modbus device have their own path in fixing Modbus device no-response over RS-485.

Why does a live tag show the wrong value? #

A wrong-but-plausible value almost always means the address convention or the scaling is off by one layer: Modbus references are one-based, the wire address is zero-based, and conversion must be applied exactly once.

Module manuals list register references such as 30001 for the first input register and 40001 for the first holding register. The address field carried in the frame is zero-based, so 30001 goes out as 0. Driver address boxes differ: some want the reference, some the offset. Worked example: a manual lists channel 0 at 30001 and channel 3 at 30004, so in an offset-style driver channel 0 is entered as 0 and channel 3 as 30004 - 30001 = 3. Entering 1 "to be safe" reads channel 1, a valid reply from the wrong point with perfect communications.

Scaling is the second layer, shown here as an illustrative example. A module returning raw 12-bit counts, 0-4095 for a 0-10.0 V input, scales at 10.0 V / 4095 counts = 0.00244 V per count, so 2048 counts displays as 2048 x 0.00244 = 5.00 V. If that same module is configured for engineering units instead and returns 5000 for 5.00 V, applying the raw-count scaling shows 5000 x 0.00244 = 12.2 V on the screen with zero communications errors. Confirm from the module configuration whether the register holds counts or engineering units, then scale once. For 32-bit values spanning two registers, fix the word order from the module manual before trusting any of them.

What control functions belong outside the HMI scripts? #

Put automatic sequences and protective functions in the controller or the machine’s safety system. If communication stops, output behavior depends on each module’s configured response and on the independent machine controls.

A panel crash or disconnected cable stops new commands. An output may hold its last command or transition to a configured fallback on communication timeout. For example, The Advantech ADAM-4000 series user manual documents a communication watchdog on the ADAM-4055. Check whether the exact module and operating mode support that feature, and bench-test the timeout, the output indication and the behavior when communication recovers. Use a safe test load for the bench check. Emergency stops and protective interlocks belong in the machine safety system. Verify that the display marks stale values and disables commands as appropriate.

Compare graphics, scripting and vendor support only among candidates that passed the one-module test; build a single evaluation screen with one live input, one communications status object and one operator write, and keep it as your acceptance test.

That evaluation screen is the deliverable that separates the candidates: it proves the driver, the tag, the binding and one operator action in one object each. After it passes, the remaining comparisons are real but secondary, namely how the editor fits the people who will maintain the application, whether the scripting covers the interactions you actually need, and whether the application file backs up and restores cleanly. Reject any candidate that cannot be bench-tested before purchase, however strong its feature list looks, because you would be buying the one thing you could not verify.

Questions asked

Can a Modbus TCP HMI driver reach RS-485 modules through a converter?

Yes, through a Modbus TCP to Modbus RTU gateway. For a transparent gateway, set the HMI to the gateway IP and use the Unit ID for the downstream module, accounting for any configured address mapping. Match the gateway's serial settings to the modules. A gateway that polls and caches values independently may require a poll list and register map.

Does a datasheet that lists Modbus support mean the panel can read my modules?

No. Many panels advertise a Modbus server mode, which waits to be polled by a supervisory system and never initiates requests, so it cannot read remote I/O at all. You need the client role documented for the exact release, together with the read and write function codes your modules use.

Do I need a PLC between the HMI and the I/O modules?

Not for display and operator commands. The HMI is the Modbus client and polls the modules directly over the RS-485 pair. Add a controller when the machine needs logic that must keep running with the panel down: interlocks, sequencing, or any action that should not depend on a screen being alive.

What do the common Modbus exception codes tell me?

Code 01 means the module does not implement the requested function. Code 02 means the address falls outside the module's register map. Code 03 means a field in the request was invalid, such as an unsupported register count. Code 04 means the server had a failure while trying to complete the request. A valid exception from the addressed module confirms the request reached that module and a reply came back.

What serial settings should I start with on a new segment?

Use the settings the module documentation lists, and make every device on the pair identical. For planning, 9600 baud with 8 data bits, even parity and one stop bit is the common Modbus RTU combination, and ten one-register reads take at least about 252 ms of serial time at that speed. Measure the full poll cycle and display update on the bench.

Corrections

  • : Corrected the Modbus RTU polling-time calculation, distinguished gateway modes and clarified remote output behavior on communication loss.

Keep reading

  • How-to

    Setting Up DOPSoft Modbus RTU for an HMI to Drive Link

    Select Modbus as the manufacturer in DOPSoft, choose RTU Hex Address Master (ASCII Hex Address Master only on a drive set to ASCII), copy the drive's serial parameters into the COM port — the factory frame is 9600, 8/Even/1 in RTU at station 1 — and prove the link with one read at a hex address such as 2000 (= 8192 decimal).

    HMI and touchscreens

  • Troubleshooting

    Fixing HMI Modbus Device No Response Over RS-485

    Device no Response means the slave never returned a valid frame to that request. When a PC polling tool reads the same scanner, the bus is probably carrying two masters: run one master at a time, then copy the known-good read's serial settings, station address, and register offset into the HMI.

    HMI and touchscreens

  • How-to

    Adding a Modbus RTU Driver and External Variables in Vijeo Designer

    Add one Modbus RTU equipment driver on the HMI serial port, set the baud, parity and stop bits every slave shares, and give each device a unique slave address. Then create one external variable per value, pointing it at that device and its documented register with the matching data type. Mismatched serial settings or duplicate addresses show up as read timeouts, so commission one device at a time.

    HMI and touchscreens