PortDock

Setting up a VFD for Modbus — protocol, station, baud rate, command source, saving

The order to set up a drive for Modbus RTU: protocol, station number, baud and parity, power cycle, run and frequency source, comm loss action, saving.

Tools for this guideModbus Master Windows program · freeSerial Windows program · freeModbus RTU Request Builder web · no installSerial Timing Calculator web · no install

To run a drive from a PLC or PC over Modbus RTU you change a few drive parameters. The names differ by maker, but the order is much the same, and missing one step gives either «no reply» or «replies, but the motor will not run». The examples below are manufacturer manual values collected in this site's device maps (page numbers on each device page).

1. Select the Modbus protocol

2. Station number — some defaults never reply

Station 0 is broadcast, so the device does not reply. The FR-E800 Pr.117 defaults to 0 and the Schneider ATV320 Add defaults to OFF, so left as shipped they answer nothing. Set 1 to 247, unique on the RS-485 line. The Yaskawa V1000 H5-01 defaults to 1F (31), so a request to station 1 gets no reply.

3. Baud rate, parity and stop bits

DriveStation defaultBaud / format defaultRun and frequency via comm
LS ELECTRIC S100CM.01 = 19600 bps 8N1DRV = 3, Frq = 6 (Int485)
Mitsubishi FR-E800Pr.117 = 0 (no reply)19200 bps 8E1—
Yaskawa V1000H5-01 = 1F (31)9600 bps 8N1b1-02 = 2, b1-01 = 2
Schneider ATV320Add = OFF (no reply)19200 bps 8E1—
OMRON 3G3M1y11 = 19600 bps 8N1F02 = 4, F01 = 14
OMRON 3G3JXC072 = 14800 bps 8N1A002 = 03, A001 = 03

Defaults differ, so match the master (PLC or PC) to the drive or the drive to the master. Every device on one line must use the same baud rate and format. «—» means the value is not in the device map; check the manual.

4. Communication changes apply after a reset or power cycle

Many drives do not apply communication parameters right away. The FR-E800 needs an inverter reset; the ATV320, V1000 and 3G3JX need a power cycle. The 3G3JX C07x parameters cannot be changed over Modbus, only from the operator. If the settings look right but nothing replies, check for the power cycle first.

5. Run command and frequency reference source

If the drive replies but the motor does not turn when you write a run command, this is the usual cause. A drive picks the source of the run command (forward, reverse, stop) and of the frequency reference separately: terminals, keypad or communication. Set both to communication, as in the last column of the table, for Modbus run commands and frequencies to take effect. Changing only one gives half a result, such as «the frequency changes but it will not run».

6. What to do when communication stops

If the cable comes out while running over communication, a drive may keep running on the last command. The OMRON 3G3M1 uses y18 (timeout, default 0 = no check) and y12 (trip immediately, decelerate to stop, keep running, etc.); the ATV320 watches for loss with tto (default 10 s). Set this deliberately for the machine's safety.

7. Saving values written over communication

8. Test with a read first

After setting up, read a read-only value such as status or output frequency before writing anything. If the read works, station, baud rate and wiring are right. Then write the frequency reference, and the run command last. For no-reply troubleshooting see the «No reply from a Modbus device» guide; for turning manual addresses into wire addresses see the address notation guide. Whether a drive's addresses are 1-based or 0-based differs by model; each device map notes it in «Addressing» with the manual's frame examples.

Sources

Published 2026-10-30