Telegauge gathers data from devices on your network using custom pollers that continually collect, send, and store data for real-time display.
Polling Loop Life-cycle
- Most devices (like MODBUS) allow third-party services to periodically download their current values.
- The poller initializes and tests connections to each configured device.
- At the set polling rate, the poller connects and retrieves a block of data.
- Each value is compared to the previous value; changes trigger widget updates.
- If historical storage is enabled and the value changes enough (deadband), or after a set time, the value is written to the database.
- The poller disconnects and waits for the next cycle.
Event Loop Life-cycle
- Some devices notify Telegauge directly when new data arrives (event-driven).
- This reduces lag even further, as there's no polling delay.
- When a new event occurs, Telegauge updates widgets and stores the value in the database.
- Few devices support this, but Telegauge is ready for them.
Protocols
Telegauge supports the following protocols:
Modbus TCP
Modbus TCP is a protocol that allows devices to communicate over a network.
stable
100%
API
Generic internet API support for collecting random data.
testing
50%
BACnet
BACnet is a protocol that allows devices to communicate over a network.
experimental
20%
Etherenet/IP
Another real-time protocol favored by Allen-Bradley
planned
0%
(as of July 2025)
Devices
Modern industrial equipment is designed with connections in mind.
Your industry likely already has a lot of network-connectable devices, capable of supplying data. If not, chances are good that older devices can be retrofitted with appropriate sensors and pickups.
Generators
Collect power data, and track uptimes
Tanks
Monitor tank levels, and changes over time
Pumps
Track starts and stops, as well as run levels
Valves
Track open and closed states
Flow
Gather data from flow meters and track it
Temps & Pressures
Talk to a variety of sensors