Integrations
Vendor agnostic. Protocol agnostic. Built for a mixed plant.
Connect the equipment and systems you already use through the appropriate interface. Different formats are mapped into the same shared context, so the project can grow without being tied to one equipment brand.
How an integration is scoped
Three steps, and the third one is real work
- 01Identify the interfaceWhat the device already speaks, over what physical connection, and whether it is reachable from where the hub will sit.
- 02Map the dataWhich registers, points or messages matter, what they mean, their scaling and units, and the address each one will carry.
- 03Confirm it against your deviceTest the path on the actual model and firmware, and record what read, what wrote, and what did not.
Share the model number, register map, API or communication documentation and we will confirm the integration path and test it against your equipment. The path depends on the device model, the interface available and what the project needs — which is why the answer comes back per device rather than as a compatibility list.
What it reads and writes
Grouped by what the connection is for
Industrial equipment
Direct connections or a suitable adapter, according to the device and the project.
- Modbus RTU and TCP
- OPC UA
- Siemens S7
- BACnet
- PROFIBUS
- PROFINET
- EtherNet/IP
- CANbus
Information exchange
Moving equipment events and business context between systems.
- MQTT
- Sparkplug B
- HTTP / REST
- Signed webhooks
- CSV
Field signals
Reading or acting on a physical signal, through the right input or output variant.
- Digital inputs
- Pulse counters
- Analogue inputs
- Relay and digital outputs
Site connectivity
The network or field bridge appropriate to where the equipment actually is. Ordinary Ethernet is a network; EtherNet/IP above is a protocol that runs on one.
- Ethernet
- Wi-Fi
- LoRa bridge
- LTE uplink, where a site needs it
Scoped per device
Named here because they come up, and each needs a defined adapter and a check against the specific model before it is part of a scope.
- M-Bus
- J1939
- CANopen
- SQL / ODBC
Whose equipment
Work with what is already in your plant
Examples of equipment ecosystems we can assess and integrate through the appropriate interface. This is a compatibility discussion — not a partner list, and not a customer list.
Automation and control
Controllers, drives and machine interfaces.
- Siemens
Schneider Electric
ABB
Rockwell Automation
Mitsubishi Electric
Omron
Beckhoff
WAGO
Phoenix Contact
Delta
Power and building equipment
Switchgear, generation, refrigeration and building plant.
Eaton
CHINT
Danfoss
CAREL
Victron Energy
Names and marks belong to their owners. Listing one says we can assess and integrate that equipment through a suitable interface, and nothing more — it is not a partnership, an endorsement or a resale arrangement.
Tell us what you are trying to read
Send the model and whatever communication documentation you have. We will come back with the interface, what it would take to map it, and what has to be confirmed on your actual device.