VFD Modbus RTU communication can replace multiple discrete and analog signals with one serial link between a PLC, HMI, SCADA system, or industrial computer and a variable frequency drive. The master can send commands and frequency references while reading operating data and faults.
Most commissioning problems are not caused by a defective drive. They come from mixing up the RS485 physical layer with the Modbus protocol, mismatching serial settings, using the wrong slave address or register offset, or forgetting to enable communication as the command source. A structured Modbus RTU troubleshooting process finds these errors faster than changing several PLC blocks at once.
VFD RS485 communication should be verified from the cable and serial format through to the register map and command-source settings.
This guide explains a repeatable VFD Modbus RTU communication setup and troubleshooting method, using the M-Driver 800 series manual as the model-specific example. It also shows how to connect PLC to VFD using RS485 without skipping the command-source checks.
Table of Contents
Understand RS485 and Modbus RTU
Prepare the wiring
Match address, baud rate, and data format
Enable remote command and frequency sources
Verify function codes and registers
Test one drive before building the network
Diagnose no response
Diagnose intermittent communication
Diagnose read works but run fails
Document and hand over the system
1. RS485 Is the Physical Layer; Modbus RTU Is the Protocol
RS485 defines a differential electrical interface for multi-device serial networks. Modbus RTU defines how a master addresses a slave, requests data, writes values, receives a response, and checks a frame with CRC.
Both layers must be correct. A PLC can transmit perfect Modbus frames and still receive nothing if the pair is reversed or the cable is disconnected. The wiring can also be correct while every request fails because baud rate, parity, slave address, function code, or register mapping is wrong.
The official Modbus serial-line guide describes a master-slave bus and RTU framing. Always use the drive manufacturer’s communication chapter for its terminals, parameters, supported functions, and register map.
2. Prepare the Wiring for VFD RS485 Wiring Troubleshooting
The M-Driver 800 series manual identifies S+ and S− as the positive and negative 485 differential-signal terminals and G as communication common. It recommends twisted pair or shielded cable.
Before energizing the control system:
Connect the corresponding differential terminals consistently through the bus.
Use a line or daisy-chain topology rather than uncontrolled star branches.
Keep communication wiring away from motor output and other high-noise power cables.
Follow the controller, drive, and project instructions for shield and reference grounding.
Use termination only according to the RS485 network design and equipment instructions.
RS485 naming is not universal: some devices use A/B, D+/D−, +/−, or S+/S−, and vendors may not use A/B labels consistently. Confirm polarity from both manuals rather than matching letters blindly.
3. Match Address, Baud Rate, and Data Format
Every serial setting must match between the master and the drive. These VFD communication parameters should be recorded in the commissioning sheet.
For the 800 series, the manual documents:
| Parameter | Function | Documented options |
| F7-00 | Inverter address | 1–249; address 0 is used for broadcast |
| F7-01 | Baud rate | 9600, 19200, 38400, 57600, or 115200 bps |
| F7-02 | Data format | 8-N-2, 8-E-1, 8-O-1, or 8-N-1 |
| F7-03 | Communication timeout | 0.0–60.0 s; 0.0 disables timeout detection |
Each slave on one bus needs a unique address. Baud rate, data bits, parity, and stop bits must match exactly. A timeout value must also be longer than the worst expected interval between valid messages. The 800 series manual states that when the configured interval is exceeded, the drive reports Err16; this is the documented VFD communication timeout fault for this series.
4. Enable Communication as the Control Source
Receiving valid frames does not automatically mean the drive will accept remote run and frequency commands.
In the 800 series application example:
F0-00 = 2 selects communication control for start and stop.
F0-01 = 8 selects communication as the target-frequency source.
These settings answer a common symptom often described as “PLC can read VFD but cannot start”: the PLC can read status values, but the motor does not run or the frequency reference has no effect. Verify local/remote selection, interlocks, stop inputs, fault state, and command-source parameters before rewriting the PLC program.
The parameter numbers above are specific to the cited 800 series manual. Do not copy them to another series without checking its manual.
5. Verify Function Codes and Register Mapping
The 800 series manual documents function code 0x03 for reading and 0x06 for writing. It also states that one request can read up to 12 consecutive addresses without crossing the final available address.
Its communication map includes:
Register 0x01 for communication frequency setting
Register 0x02 for control commands
Register 0x03 for relay control
Register 0x04 for analog-output control
Parameter registers from F0-00 through F9-36 mapped to 0xF000 through 0xF924
Monitoring registers U0-00 through U0-71 mapped to 0x1000 through 0x1047
Register notation can create off-by-one errors. Some PLC software displays the protocol address, while other software adds a 4xxxx reference number or uses decimal notation. Confirm what the master expects before changing the drive address. When searching for a VFD Modbus register address, always verify whether the software expects a protocol offset or a displayed reference number.
Also check scaling. A value written to a frequency-reference register may represent a percentage or scaled integer rather than hertz. Use the exact description in the register table.
6. Test One Drive Before Building the Full Network
Start with one controller, one converter if needed, one drive, and a short known-good cable. Keep the motor stopped until reading is stable.
Use this sequence:
Read one documented monitoring register.
Confirm the slave address in the response.
Verify the returned value and scaling.
Write a non-motion parameter only if the manual permits it.
Test frequency reference with the run command still disabled.
Verify interlocks and then test run/stop at low risk.
Add other drives one at a time, assigning unique addresses.
Save the working request and response frames. They become a reference when the final PLC program or long cable is introduced.
7. Troubleshoot a VFD Modbus No Response Condition
When the master receives no valid reply, check in this order:
Drive power and display
Correct communication port and converter mode
S+/S− polarity and communication common
Unique slave address
Identical baud rate and data format
Modbus RTU mode rather than ASCII or a transparent mode mismatch
Correct function code and register address
Request CRC and frame timing
Then disconnect other slaves and test one drive. This separates a device-level problem from a bus-level problem.
8. Troubleshoot an Intermittent VFD Communication Fault
If communication works on the bench but fails when motors run, investigate electromagnetic interference, cable routing, shield and reference practice, topology, termination, connector quality, and ground-potential differences.
Texas Instruments RS485 design guidance explains that termination should match the cable’s characteristic impedance and that multipoint buses generally terminate at both ends. Apply this only with the equipment and network design in view; adding resistors at every node can overload the bus.
Temporarily reducing baud rate can help identify a signal-integrity margin problem, but it is not a substitute for correcting wiring and noise coupling. Compare error counters and captured frames with motors stopped and running.
9. If Reading Works but Run or Speed Control Fails
Successful monitoring proves that the physical link, basic framing, and at least some addressing are correct. It does not prove that remote commands are enabled.
Check:
Command source and frequency source
Drive ready state and active fault
External stop or enable inputs
Local/remote selection
Correct write function and register
Value scaling and byte order in the master
PLC logic that may overwrite the command
Test one function at a time. First prove a stable read, then a frequency write, then a controlled run command. Avoid changing several parameters and PLC blocks simultaneously.
10. Document the Working Configuration
Record the drive model, manual revision, terminals, cable type, topology, termination locations, shield practice, slave addresses, baud rate, data format, timeout, function codes, register map, scaling, PLC program version, and acceptance results.
For replacement drives, do not assume a same-kW unit from another series uses the same parameters or registers. Compare the new manual and update the PLC mapping before commissioning.
FAQ
Why does my VFD Modbus RTU network show no response?
The usual causes are wrong polarity, slave address, baud rate, parity/stop bits, function code, register address, converter mode, or CRC. Test one drive with a short cable first.
Why can the PLC read the VFD but not start it?
The communication link may be working while the command source remains set to the keypad or terminals. On the cited 800 series, verify F0-00 and F0-01 plus interlocks and faults.
What causes an intermittent VFD communication fault?
Common causes include power-cable interference, unsuitable topology, termination errors, poor connectors, grounding or common-mode issues, duplicate addresses, and a timeout shorter than the network scan interval.
Can I use the 800 series register map for another M-Driver series?
No. Use the communication chapter and register table for the exact series and manual revision.
Conclusion
Reliable PLC VFD communication comes from checking the system layer by layer: RS485 wiring, serial format, slave address, Modbus function and register, command-source settings, and network signal integrity.
For M-Driver 800 series support, provide the full drive model, manual revision, PLC or HMI model, converter model, wiring diagram, F7 settings, command-source settings, request/response frames, fault code, and a description of whether the problem is constant or intermittent.
