Documentation
The Edge Gateway guide, chapter by chapter, and one page each for the Modbus Client, the Modbus Scanner, the Modbus Simulator and the OPC UA Explorer, plus 10 reference articles in the engineering hub.
Edge Gateway guide
Design a gateway on this site, in the Edge Logic Editor, and run it on your own device. This guide takes one data flow at a time, from a field device to each output, and then follows the design from the editor to a running service.
- 1Edge GatewayDesign a gateway on this site, in the Edge Logic Editor, and run it on your own device. This guide takes one data flow at a time, from a field device to each output, and then follows the design from the editor to a running service.
- 2The Edge Logic EditorA canvas, a palette and an inspector. A node is a device, a step or an output; a wire is the path a value takes. Every save is a version.
- 3Modbus to MQTTA Modbus device, published to a broker as one message per tag, or grouped per device.
- 4Modbus to HTTP / RESTA Modbus device, posted to an HTTP endpoint one message at a time or as JSON arrays, with the authentication the API expects.
- 5Modbus to SQL databaseA Modbus device, written as rows into SQLite on the gateway or into PostgreSQL, MySQL / MariaDB or SQL Server.
- 6Modbus to OPC UA ServerThe gateway as an OPC UA server: every routed tag a variable that SCADA and MES clients browse and subscribe to.
- 7Modbus to BACnet/IPThe gateway as one BACnet device: numbers as Analog Inputs, booleans as Binary Inputs, for a building management system to read.
- 8Modbus to WebSocketLive values for a dashboard or an application: a snapshot on connect, then one message per update.
- 9Any device to Modbus Server (slave)The gateway as a Modbus slave: tags from any protocol, served as registers and coils to equipment that only speaks Modbus.
- 10Modbus RTU/ASCII to Modbus TCPThe Modbus converter: slaves on a serial RTU or ASCII bus, reached by a Modbus TCP client (master) through the gateway, which acts as the Modbus TCP server for it. A gateway service beside the flow, not a step in it.
- 11OPC UA to MQTTThe other direction: the gateway as an OPC UA client, reading variables from a PLC, a SCADA or a machine controller and sending them to a broker, an API, a database or a dashboard.
- 12Logic and routing nodesCondition, Join, Inject, Catch, Expression, Cast, Debounce, Batch, JSON template and Throttle: how each is drawn, and what the runtime does with it on the device.
- 13Validating a designThree checks before anything is built, each naming the node it belongs to.
- 14DownloadingA static installer per platform, the same for everyone, and an activation bundle per device: one small zip with your design and a licence for that machine.
- 15Installing on the deviceRun the Edge Gateway Console: it shows the device code. Give it the activation bundle and it installs the Edge Runtime as a service and shows it running; from then on it is the gateway's console.
- 16Activation, the licence and the trial windowA device code typed into this site, a licence bound to that machine, and nothing online on the device, ever.
- 17Running: the service, secrets and diagnosticsWhere the files are, how credentials get onto the device, and where to look when something does not arrive.
The free tools
Modbus Client
Poll Modbus devices, watch decoded values as they change, write a register when you mean to, chart trends and log to a file. A tab per server; several servers at once.
Modbus Scanner
Find the Modbus devices on a network, find the registers a device answers, work out what the values are, name them, and take the map with you. It reads. It never writes.
Modbus Simulator
A Modbus slave on your own machine: TCP, RTU or ASCII, with the register map, data types, byte order and value behaviour of the device you are developing against. This is the simulator's user guide.
OPC UA Explorer
Find the OPC UA servers on the networks your PC is on, open one, and see its address space with every variable's value, data type, access level and status. Read-only.