02 Features
Gateway and protocols
The node connects to what is already there: serial buses, industrial networks, radio meters. It powers on, recognises and starts talking.
Illustrative figures.
How it works
It connects to what you have
Nothing is replaced and nothing is reprogrammed. The node listens to the field as it is, whatever shape the data arrives in.
One container per protocol
Each protocol runs isolated from the others on the same gateway. A Modbus device that stops answering does not stall the OPC-UA reader beside it.
Configuration happens in the UI
Registers, points and rates are declared from the gateway Hub, not by editing files on site. The same configuration is reused on a twin plant.
The link is opened from inside
The gateway opens the connection to the platform itself, encrypted and signed. No inbound port has to be opened on the plant network.
Nothing is lost if the line drops
Readings buffer locally and are recovered when the connection returns, carrying their original timestamps rather than the time they arrived.
What it speaks
Whatever shape it takes
A meter from the nineties and a modern API end up in the same history, on the same timestamp. No format is privileged.
New drivers on requestWhere it is used
In every industry, no exceptions
The protocol changes, the way of working does not. It is why the same measurement layer sits under plants that have nothing in common.
Nearby features
The step before and the step after
What does your plant
actually speak?
Send us the list of what you have in the field: we will say what reads straight away and what needs a dedicated driver.
We use a technical cookie to remember your choice and, only if you accept, Google Analytics to count visits in aggregate. Closing the banner is the same as rejecting. You can change your mind at any time from “Manage cookies” at the bottom of the page. Cookie policy · Privacy notice