VFD and motor
drive monitoring
Speed, motor current, fault codes and run hours from the variable frequency drives on your fans, pumps and conveyors, read over Modbus and sent to one cloud view.
THE PROBLEM
Every drive keeps a fault history that nobody reads
A modern VFD is a good instrument. It measures output frequency, motor current, DC bus voltage, heatsink temperature and power, and keeps a log of its last faults. On most sites that information is seen only on the keypad, by an electrician who has already been called because the motor stopped.
Trends in drive data are what predict trouble: current creeping up on a fan with a clogged filter, repeated overvoltage trips on a decelerating load, a heatsink running hot because the panel fan failed. Reading drives continuously turns those trends into planned maintenance work.
HOW WE SET IT UP
Drive data on a schedule that suits the bus
Confirm the register map per model
Every drive family uses its own parameter numbering, scaling and word order. We confirm the map for each model before commissioning, so speed reads in hertz or rpm and current reads in amps.
Set the polling rate deliberately
Many drives share one RS485 line. We choose how often each value is read so the bus is not overloaded: fast for status and faults, slower for run hours and energy.
Read alongside the existing control
Where a PLC already controls the drives over Modbus, the gateway can read from the PLC or join the network as a slave, so the control link is left as it is.
Faults to the right person
Fault codes are recorded with their time in RIOD Live and sent by SMS, WhatsApp or email to the maintenance team, with the history kept for root-cause analysis.
AT A GLANCE
VFD monitoring in brief
- What is read
- Output speed or frequency, motor current, fault and warning codes, run status, and power, energy or temperature where the drive exposes them
- Hardware
- RS485 Modbus IoT gateway, Modbus RTU over RS485 and Modbus TCP over Ethernet, master or slave
- Connectivity
- Ethernet, Wi-Fi or 4G, chosen per site. MQTT over TLS 1.2
- Power
- 12 V adapter from the panel supply, in a plastic, metal or custom enclosure
- Where data goes
- RIOD Live, or your own server, with API access, PDF and Excel exports with audit trails, and AI access through MCP
- Configuration
- Register map and polling rate confirmed per drive model and set in the cloud application
- Bus planning
- Addresses, baud rate and termination checked during commissioning
FAQ
Questions buyers ask us
What data can I read from a VFD over Modbus?
Most drives expose output frequency, motor current, run status, fault codes and often power, energy, DC bus voltage and heatsink temperature. The exact list depends on the drive model and its Modbus register map.
How often can VFD values be read?
It depends on the number of drives on the bus, the baud rate and how many registers you read from each. We set the polling rate per value during commissioning so status and faults stay fast while slower values are read less often.
Will monitoring interfere with our PLC controlling the drives?
We plan the connection around your existing control. The gateway can read from the PLC, or sit on the network as a slave, so the PLC keeps its role as master of the drives.
Can we monitor drives from different manufacturers together?
Yes. Each model gets its own register map in the cloud application, and the readings appear side by side with common names and units.
Want to see what your drives are telling you?
Send us the drive models and how they are wired today. We will confirm the registers and the polling plan.