No real device
It does not open a serial port, read a PLC, or connect a camera or gateway outside the browser.
M4 / SAFE SIMULATOR
Press run to watch a synthetic message move through four layers. This is a browser-local simulation: it does not call a device, send data outside, or replace a site acceptance test.
01 / RUN THE PATH
Each step lights up in order so an engineering team can see the boundary: a device emits a signal, edge normalizes and buffers it, Local API exposes a contract, and the consumer receives it.
Emits one sample point.
RS485 / MODBUS RTUNormalizes and keeps the message on site.
BUFFER / LOGICOpens the JSON contract to a consumer.
REST / JSONReceives and handles it as business data.
APP / SCADA / CRMNo message has been emitted. This is illustrative data, not customer data.
{
"source": "gateway-rs485-demo",
"captured_at": "2026-08-06T09:30:00+07:00",
"points": [
{
"key": "line_01.temperature",
"value": 28.4,
"unit": "degC",
"quality": "good"
}
]
}LOCAL SIMULATION / SYNTHETIC DATA
02 / HONEST DEMO
Use the demo to understand the architecture and prepare survey questions, not to infer site-specific speed, SLA, or compatibility.
It does not open a serial port, read a PLC, or connect a camera or gateway outside the browser.
The payload stays on the page; real endpoint, auth, retry, and mapping are agreed in the handover record.
The step rhythm is illustrative, not iNut Edge latency, throughput, or an SLA.
The diagram, point list, protocol, network, and acceptance criteria still need checking against the real system.
NEXT STEP
Open the Integration Guide for the reference schema or share your system diagram so iNut can start from its first data point.