Compressor controller
integration
Run state, load and unload hours, delivery pressure, alarms and service counters from your compressor controllers, read over Modbus and shown together in one place.
THE PROBLEM
Compressed air is expensive, and the compressor room is unwatched
Compressors are among the largest electrical loads in many factories, and they run whether the air is used or not. A machine that spends most of its hours unloaded, two compressors fighting each other on pressure bands, or a leak that keeps them loaded through the weekend all show up in the controller data.
Each controller already counts loaded hours, total hours and starts, and knows when a filter or oil change is due. With several brands in one compressor room, though, nobody sees those numbers side by side.
HOW WE SET IT UP
Every compressor, mapped once
Map each controller model
Every compressor controller has its own register map. We obtain the map for each model, confirm addresses and scaling, and set it in the cloud application before going to site.
Load, unload and pressure
Loaded and unloaded hours with delivery pressure show how well the compressors match demand, and whether the pressure setpoint is higher than the plant needs.
Service and alarm alerts
Service counters and alarms such as high discharge temperature are read and sent to the maintenance team or the service contractor before they become a breakdown.
Add energy for the full picture
A Modbus energy meter on each compressor feeder joins the same gateway, so air output can be read against the electricity it costs.
AT A GLANCE
Compressor integration in brief
- What is read
- Run state, load and unload, delivery pressure, discharge temperature, alarms, running and service hours where available
- 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
- Register maps
- Prepared per controller model and confirmed before commissioning
- Mixed fleets
- Different brands shown side by side with common names and units
FAQ
Questions buyers ask us
Can air compressors be monitored over Modbus?
Many compressor controllers offer Modbus RTU or TCP, sometimes through an optional communication module. Typical points are run state, load status, pressure, temperatures, alarms and service hours.
Why do we need the register map for each compressor model?
Each manufacturer and controller generation numbers and scales its data differently. With the correct map, a register becomes a named value in the right units. We confirm the map per model before commissioning.
How does compressor data help reduce energy use?
Load and unload hours show how much time each machine runs without producing air. Combined with pressure and energy readings, that shows where setpoints, sequencing or leaks are costing power.
Can the service contractor see the data too?
Yes. Access can be shared in RIOD Live, and alerts for service counters and alarms can go to the contractor as well as your team.
Want to see what your compressor room is doing?
Send us the compressor makes and controller models. We will confirm the maps and show what the data will tell you.