Its own cellular link
It does not depend on the company network or on IT opening a port: the gateway’s SIM sends the data.
How it works
One gateway per area, and all of that area’s data in one place.
- 01
Receives
The vibration sensors, thermal cameras and lubricators in the area talk to the gateway.
- 02
Reads
Through the Modbus port, the gateway reads what the plant already has: drives, meters, PLCs.
- 03
Stores
Without signal, the queue stays on the gateway, with the time of each reading, until the network is back.
- 04
Delivers
Over the cellular network, everything goes up to the IoTData platform, with history and alerts.
What the gateway solves
4G IoT gateway
The gateway is why the sensor needs neither a cable nor its own internet connection, and why the plant does not have to replace what already works.
Modbus RTU and TCP
Reads drives, energy meters and PLCs using each manufacturer’s register map, configured on the platform, without rewriting firmware for every brand.
Local buffering
A dropped signal does not become a gap in the history: the gateway stores and delivers later, with the time each reading was taken.
Our own firmware
The code running on the gateway is ours, and the people who designed it fix it when something fails, without a ticket to an outside manufacturer.
Where there is no cellular coverage
For points with no coverage, we also offer the DG satellite network, which delivers within minutes.
An API for your systems
What reaches the platform flows on through an API to your ERP, your maintenance system or your SCADA.
Data sheet
What is already defined, and what comes with the proposal.
| Network | 4G cellular |
|---|---|
| Wireless devices | Data Frontier vibration sensors, thermal cameras and lubricators |
| Field protocols | Modbus RTU (RS-485) and Modbus TCP |
| Without signal | Local buffering, delivered when the network is back |
| Platform | IoTData Cloud, with REST API |
| Sensors per gateway | On request |
| Power supply | On request |
| Mounting | On request |
| Ingress protection | On request |
Where it says on request, the value depends on the model and comes in the data sheet that accompanies the proposal. We would rather do that than publish a number we cannot guarantee for your application.
Where to use it
Predictive maintenance
Brings together the vibration sensors, thermal cameras and lubricators of one area of the plant.
Solar plants
Reads the inverters over Modbus and sends generation, status and alarms to the plant dashboard.
Utilities and metering
Energy, flow and level meters that already have a Modbus output join the same dashboard.
Designed, built and supported by the same team.
The board, the firmware, the integration and the platform are Data Frontier’s, engineered and built in Brazil. When something fails, the people who designed it are the ones who answer, with no outside supplier pointing at someone else. About the company.
Frequently asked questions
What people ask before requesting the data sheet.
Do I need to connect the gateway to the company network?
No. It has its own cellular connection. If IT prefers the plant network, the site survey looks at how.
How many sensors does one gateway handle?
It depends on distance, walls and sensor type, and is set out in the proposal. The site survey defines how many gateways the area needs.
Will it read my drive or my PLC?
If the equipment has Modbus RTU or TCP and the manufacturer publishes the register map, yes. The map is configured on the platform.
What if the cellular signal is weak?
The gateway keeps the queue and delivers when the signal returns. For points with no coverage at all, the DG satellite network delivers within minutes.
Data sheet and proposal
Tell us what needs to reach the platform.
An engineer replies, not a bot. Tell us the sensors and the Modbus equipment in the area: that is what defines the gateway.
Other equipment
