Edge Gateway
Running: the service, secrets and diagnostics
Where the files are, how credentials get onto the device, and where to look when something does not arrive.
On the device
| Where | What |
|---|---|
%ProgramData%\ModbusLogic\Gateway · /var/lib/modbuslogic-gateway | The data directory: license.json, designs/<design>/project.json, secrets.enc, buffer/ for store & forward, logs/gateway.log, a Modbus Server's assigned register map |
http://127.0.0.1:8787 | The management API and commissioning diagnostics on the device: connection state, tag reads with raw and decoded values, response times, protocol exceptions, destination connectivity, health |
modbuslogic-edge secrets set <destination-id> <field> | Credentials, entered on the device and encrypted there: an MQTT or database password, an HTTP token or API key, a WebSocket token. Never in a design, never in a package |
modbuslogic-edge license status | The installed licence: tier, expiry, the design it is bound to |
The service log is the first place to look when something does not arrive: a device that refuses an address, a broker that rejects a connection, a destination waiting for a secret that was never set, an expression whose input tag is bad. Each line names the device, destination or route and the reason.
What the live view shows
- Devices: up or down, the last response time, the last error.
- Values: device · tag · value · quality, as they change.
- Routes: published, suppressed (a deadband, a Condition, a Debounce or a Throttle held it back) and skipped (not usable and not reported) counts.
- Destinations: connected or not, sent, failed, buffered, the last error.
The Modbus Simulator is the quickest way to see all of this without hardware; every data-flow chapter has a test-bench section, starting with MQTT. The editor chapter is here.