Poll Modbus devices at scale, automatically
Continuously read Modbus TCP devices across your fleet, sync configuration live from the platform database, and stream data to all systems.
What it is
The Modbus TCP Client Service polls Modbus TCP devices (energy meters, controllers, sensors) across your network on a configurable schedule. It automatically discovers, adds, and removes devices from a central database—no service restart needed. Decoded register values flow in real-time to your historians, analytics dashboards, and OPC servers through the platform's message network.
Key benefits
Live device data without manual configuration changes
Add or remove Modbus devices in the database, and the service detects the change within seconds. No service restarts, no downtime—your fleet stays synchronized.
Optimized performance at scale
One dedicated worker thread per connection eliminates per-cycle overhead. TCP sockets stay open across reads, and device-specific decoders are cached, so polling thousands of meters runs efficiently.
Transparent data flow to downstream systems
Decoded Modbus values broadcast automatically to historians, OPC servers, the .NET GUI, and message brokers—no ETL plumbing required.
Built-in diagnostics without stopping service
Enable per-device or per-connection diagnostic logs on demand from the database. Logs rotate automatically; toggle logging on/off at runtime without a restart.
Capabilities
- Poll Modbus TCP devices with persistent connections
- Auto-sync device lists and polling config from database in real time
- Decode make-specific Modbus registers and broadcast to message bus
- Per-device and per-connection diagnostic logging with runtime on/off control
- Health monitoring via REST API (connection count, poll freshness)
- Configurable retry logic and connection timeouts
- Support for mixed baud rates and protocol variants per device make
- Graceful shutdown with in-flight request drainage