IMDTouchKnowledge BaseShop main store

How-to

Connecting an HMI directly to a VFD over Modbus RTU

Drives and motion Published 9 min read

Short answer

Yes. An HMI with a Modbus RTU master driver can start, stop, set speed and read status and faults from a Modbus-ready VFD with no PLC — after the drive's run-command and frequency-reference parameters point at the serial port, and after communication loss stops the drive in a defined way. Keep the hardwired emergency stop.

On this page
  1. Can an HMI control a VFD without a PLC?
  2. What does the HMI need before you start?
  3. How do you wire the RS-485 connection to the drive?
  4. Which serial settings and slave address match the drive?
  5. Which registers run the drive and set the speed?
  6. How do you switch the drive's command and speed sources to Modbus?
  7. What happens to the drive when the Modbus link drops?
  8. Is the commanded speed the same as the measured RPM?
  9. How do you commission the link before production?
  10. Questions asked

A Modbus-ready VFD can be run straight from an HMI, with no PLC in the loop: the HMI's Modbus RTU master driver writes the run command and the speed reference into the drive's holding registers and reads back status, current and fault codes over two RS-485 wires. The whole setup lives in four places — the RS-485 bus, the serial settings, the drive's register map, and the two drive parameters that hand the run command and the frequency reference to the serial port. Two limits decide whether the swap is sound: communication loss must stop the drive in a defined, parameterized way, and the value you write is a speed request, never a measured RPM. The sections below walk wiring, settings, registers, source switching and commissioning in the order you meet them at the bench.

Can an HMI control a VFD without a PLC? #

Yes — any HMI that runs a Modbus RTU master driver on a serial port can start, stop, set speed and read status from a Modbus-ready VFD with no PLC in the loop, provided the drive's run-command and frequency-reference parameters are switched to that port.

On a Modbus RTU network only the master initiates a message, so the HMI takes the master role and the drive answers as a slave; nothing moves on the bus unless the HMI asks. Functionally that covers starting and stopping the drive, changing speed, reading output current and bus voltage, enunciating and clearing drive faults, and switching preset speeds. What it does not cover is logic. An HMI holds screens and tags, not a program, so interlocks, permissive chains and timed sequences have to live in the drive's own parameter set or stay hardwired. If the application leans on sequence logic, size that gap before you delete the PLC — or before you promise the HMI alone can do the job.

What does the HMI need before you start? #

The HMI needs a serial RS-485 port or a converter that provides one, a Modbus RTU master driver with a drive-type device selection, and tags for run, stop, reference, status and fault objects — everything else on the operator side is screen design.

The master driver is a device-type selection in the HMI configuration software: pick the serial port, pick Modbus RTU, and the HMI then addresses any register on the bus through device tags. A USB-to-RS-485 converter fills the gap when the panel has no serial port. If the operator station is a PC-based HMI rather than a dedicated terminal, the same master driver runs in the HMI runtime on industrial panel PCs mounted at the machine. Driver coverage for serial Modbus RTU is broad across HMI brands, but verify it for your model before the panel is committed — the points that matter in selecting lightweight HMI software for Modbus I/O control are the same points this job needs.

How do you wire the RS-485 connection to the drive? #

Run one twisted, shielded pair daisy-chained device to device and terminate 120 Ω across the A and B conductors at the two physical ends only; RS-485 is specified to 1,200 m (4,000 ft) at 100 kbps and below, far more than a machine cell needs.

Most drives expose RS-485 on control-board terminals, some on an RJ-45 socket; the manual names the A and B terminals and the shield point. Daisy-chain HMI to drive, drive to next drive, and never run star branches off one terminal, because stubs reflect signals. A termination resistor at every tap loads the bus down; only the two ends get one. Tie the shield to chassis ground at a single point so it cannot carry current between boxes. If the drive offers only an RS-232 service port instead, a short point-to-point cable works, and the pin-out discipline in building the RS-232 Modbus cable between an HMI and a controller carries over.

Which serial settings and slave address match the drive? #

Set both ends to the drive manual's serial format — on a factory-fresh drive expect 9600 baud, 8 data bits, even parity, one stop bit and slave address 1, the Modbus serial-line defaults — and mirror them in the HMI driver's port setup, parity included.

A baud, parity or stop-bit mismatch shows up as timeouts and CRC errors, not as wrong data; the HMI Modbus no-response walkthrough for RS-485 works that fault from the cable inward. The entries live in the drive's communication parameter group, and a change has to happen at both ends in the same sitting or the bus goes silent. Every slave on the bus keeps its own address, so a second drive joins by setting a fresh address and pointing its tags at it. Raising the baud rate shortens scan time, but recheck the termination and the poll list before you ship the change.

Which registers run the drive and set the speed? #

The drive's Modbus communication manual publishes the register map: a control register whose bits command run, stop and direction, a speed-reference register in the units the map states, a status word, and an output-frequency or speed read-back, with addresses that belong to each drive family.

The map is a separate document from the parameter list — drive makers publish it as a register table with an address, a read/write flag, a units column and usually example values. Pull four entries from it: the control register, the speed reference, the status word, and the read-back. Two habits prevent most screen bugs. First, some manuals print register numbers offset by one from the Modbus address; check the manual's own convention before you type a number into a tag. Second, the reference register's units are whatever the map says. If the map scales the reference in 0.01 Hz steps, then 45.00 Hz is written as 45.00 ÷ 0.01 = 4500; in 0.1 Hz steps the same 45.00 Hz is 450. Set the tag's scaling once so the operator keeps typing engineering units and the register gets what the map wants.

How do you switch the drive's command and speed sources to Modbus? #

Two drive parameters decide everything: the run-command source and the frequency-reference source must both select the serial channel — until they do, writes to the control and reference registers are accepted but ignored, which looks exactly like a dead link when the wiring is fine.

The entries sit in the parameter groups named for command source, reference source or communications; the parameter list states which selection hands control to the serial channel. Record the original values before changing anything — those values are what the pushbutton and potentiometer wiring depends on, and restoring the old panel later means restoring them. Check the priority order too: many drives rank terminal inputs above the serial channel, so an asserted terminal run input or a wired reference can outrank Modbus writes even after the sources are switched. If the drive ignores run commands once the sources point at the bus, suspect a live terminal input before you suspect the HMI.

Decide the communication-loss behavior before you remove anything hardwired: the drive's loss parameter can trip, coast, ramp-stop or hold last reference, so set it to a defined stop, keep the HMI's poll cycle several times faster than that timeout, and leave the hardwired stop circuit in place.

Size the timeout against the HMI's write cycle with real numbers. With a 1,000 ms communication-loss timeout in the drive and a 250 ms HMI write cycle, the limit is reached after 4 × 250 ms = 1,000 ms — four missed cycles — so keep the worst screen polling at least three times inside the window. Test it with the motor uncoupled: run the drive, unplug the RS-485 connector, and time the reaction against the parameter. The safety function stays hardwired no matter what the parameter does. NFPA 79 requires the emergency stop to de-energize the machine without depending on a communications path, and article on NFPA 79 hardwired versus PLC safety functions walks through that split in detail. The comm-loss parameter protects the process; the E-stop circuit protects the people.

Is the commanded speed the same as the measured RPM? #

No — the value you write is a request and the value you read back from a frequency or speed register is the drive's own estimate, so treat commanded and measured as different tags and keep an independent tach or encoder when the process needs true shaft RPM.

An open-loop drive without an encoder estimates shaft speed from output frequency minus slip. On a 4-pole motor at 60 Hz, synchronous speed is 120 × 60 ÷ 4 = 1800 RPM, and a typical full-load slip of 2 to 3 percent leaves about 1745 to 1765 RPM at the shaft — fine for a mixer display, not for a speed-controlled process. The drive's own read-back register is only as good as that motor model. An encoder feedback card closes the loop and yields a true speed value, but it reaches your screens only if the communication map documents a feedback register; confirm it and compare it against the independent tach across the operating range before trusting it. Slip is also why a motor settles a little under the value you wrote — why a spindle runs below commanded RPM shows the same effect from the machine-tool side.

Commission offline and prove each function in order — comms, then monitor, then speed, then run — because a wrong reference source can spin the motor the moment a register write lands; never test run commands with the process connected.

  1. Record the drive's original parameter values — command source, reference source, communication-loss action, baud rate, slave address — so the old pushbutton-and-potentiometer panel can be put back.
  2. Wire and terminate the bus, power the HMI and the drive, and set the HMI driver's serial port to match the drive exactly.
  3. Prove the link with a read first: poll the status register and confirm the values track the drive's keypad. One clean read confirms polarity, baud, parity and address together.
  4. Write a low speed reference with the drive stopped and confirm the keypad echoes it, which proves the register address and the scaling.
  5. Switch the run-command source to the serial channel and test start and stop with the motor uncoupled and the process disconnected.
  6. Switch the reference source to the serial channel, run at the low reference, and step the speed up while watching current.
  7. Set the communication-loss action, run again, and unplug the connector to time the stop against the parameter you chose.
  8. Compare the drive's speed read-back against the independent tach across the operating range — and only then retire the potentiometer and the timer.

If every step passes, the HMI replaces the PLC for this duty; if the sequence logic or fail-safe timing cannot be carried by the drive's own parameters and the hardwired circuits, the PLC stays in the loop.

Questions asked

Can one HMI run more than one VFD on the same bus?

Yes. Give every drive on the bus a unique slave address between 1 and 247, point each HMI tag at the right address and register, and let the HMI poll them in turn — on Modbus RTU only the master initiates a message, so idle drives stay silent until polled. Watch scan time: every added drive adds its poll time to each screen update, so keep the poll list to the tags a screen actually shows.

Can a PLC and an HMI both talk to the same drive?

Only one Modbus RTU master may own an RS-485 segment; two masters garble each other's frames. Either make the HMI the only master, give the drive a second communication port and hang the PLC there, or separate the segments with a gateway. A PLC that only watches the drive can also be polled as a slave if its firmware supports slave mode.

Which Modbus function codes do the run command and speed write use?

Reads use function code 03, read holding registers, for the status word, output frequency and fault codes. A single-register write uses 06; a multi-register write, such as a control word and reference sent together, uses 16. Drive firmware varies in which write it accepts for the control register, so test both 06 and 16 against the map's documented examples before building screens on one.

Can the HMI take over the mixer timer the old relay held?

The screen can hold the recipe time and stop the drive when it expires, but a screen timer dies with a power cycle, a screen change or a failed HMI. If an un-timed stop ruins the batch, keep the relay or PLC timer and let the HMI only set the value the operator enters. If the operator can simply restart the mix, the screen timer is enough.

Keep reading

  • 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

  • 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 an XBTGT HMI to an M241 PLC over Modbus TCP

    Delete the Generic Modbus TCP slave from the M241 device tree and activate the Modbus server on the controller's Ethernet interface instead — that slave makes the M241 a client, so both devices poll and neither answers. Then map Vijeo Designer driver address 40001 to PLC word %MW0, keep TCP port 502 open between panel and controller, and shift the address map by one word if a test read lands one register off.

    HMI and touchscreens