ALLINLET Edge
ALLINLET Edge is currently a configuration registry and export function. It lets engineers describe the sources at a site, review them in one place and export that definition for use with a gateway they operate. It is not, at present, an installable runtime.
What is delivered today
In the platform you can record the sources that live at a site: a Modbus TCP meter at a given address, an OPC UA server endpoint and the node identifiers of interest, an MQTT broker and its topic filters, a LoRaWAN network server application. Each entry holds addressing, intervals, units and the intended measurement names. The registry gives the integration team and the site team a shared, reviewable description of what should be collected.
The configuration can be exported so it can be applied to gateway software or documented in a commissioning pack. The resulting data then reaches ALLINLET Cloud or Enterprise through the normal connectors, for example over MQTT or HTTPS.
What is not delivered
These capabilities may be considered in future, but this page will not describe them as available until they are.
- No ALLINLET agent is installed on site hardware.
- No signed release packages, update channel or remote management of gateways.
- No offline runtime that buffers and forwards data on behalf of the platform.
- No guarantee that an exported configuration is compatible with a particular third-party gateway; mapping is checked during commissioning.
Typical use
A water utility has pumping stations with PLCs exposing Modbus registers. The site gateway is an existing industrial router with a protocol converter. Engineers record each register, scaling factor and unit in the Edge registry, export the list, and configure the router to publish values over MQTT with TLS. ALLINLET then receives the topics and applies the same names and units that were agreed in the registry, so both sides refer to one definition.
Prerequisites
- A gateway, historian or protocol converter you already own and operate.
- Register maps, node sets or topic structures from the equipment vendor.
- An outbound or zone-crossing path from the gateway to Cloud or Enterprise.
- Someone on site who can confirm values against local displays during commissioning.
Payload meaning
The registry defines what each value represents: the physical quantity, unit, scaling, data type and expected interval. Keeping this in one place avoids the common failure where a raw register value of 2315 is read as 2315 degrees instead of 231.5 volts.
Limitations
Because there is no local runtime, data buffering during network outages depends entirely on the gateway you use. Configuration drift between the registry and the gateway must be managed through your change process. Not every catalogue protocol has a registry template; templates are added as connectors are validated.
Further reading
Catalogue listings describe possible integration paths. Implementation and validation status is confirmed for each source during project scoping; no certification, service level or price is implied by this page.
Plan your data integration
Share your devices, protocols and network constraints, and we will propose a first validated connection.