Modbus Register Maps
Addresses, data types, byte and word order, and scaling for every point on a meter, drive or controller.
Platform
Device Profiles
A profile captures a device model: its points, scaling, units and quirks. Apply it to every identical device on every site.
Why It Matters
Most of the work in an IoT project is understanding one device model: which register is which, how a payload is laid out, what a KNX group address means. A profile records that once, so the second and the hundredth device are configuration, not engineering.
- Reusable across devices and sites
- Scaling and byte order captured once
- Imports from ETS projects
- Checked against a known reading
What It Does
KNX From ETS
Import the ETS project so group addresses arrive named, located and typed.
LoRa Payload Decoders
One decoder per sensor model turns raw bytes into named values, with battery and signal health.
BLE Services
Map GATT characteristics and advertisement fields to tags, and filter out unknown devices.
Reuse Across Sites
Apply the same profile to every identical device, and update them together when it improves.
Verified Against Reality
Check a profile against a known reading before it is rolled out to a whole site.
Device Profiles Questions
Do I have to write profiles myself?
You can, or send the device manual and the engineering team will build and verify the profile.
Can profiles be shared between sites?
Yes. A profile belongs to the device model, not the site, so identical devices anywhere reuse it.
More From the Platform
Start With One Site. Prove It on Real Devices.
Tell us which protocols are on site. We will scope a pilot that reads your real devices.