Skip to main content

Edge — Configuration

The Edge Add-On extends the Gateway V4 with 2× Ethernet, wired M-Bus, Modbus RTU/ASCII (RS-485) and Modbus TCP in a DIN-rail form factor.

Compatible product: Gateway V4 + Edge

Firmware pre-release

Available starting with firmware v0.11.0 (pre-release).


Ethernet Configuration

Both Ethernet ports are configured using the EdgeEth parameter. Each entry specifies ip,netmask,gateway or dhcp. The two port configs are separated by |.

Syntax:

<ETH1-config>|<ETH2-config>

Example — ETH 1 static, ETH 2 DHCP:

192.168.1.91,255.255.255.0,192.168.1.1|dhcp
PortLabelUsage
ETH 1LANModbus TCP (currently only this port)
ETH 2WANUplink (planned)
note

No spaces allowed. Only IPv4 supported. DNS not supported — use IP addresses directly.


Modbus Configuration (modbusCmdConf)

The Edge uses a unified modbusCmdConf format that covers RS-485 (RTU/ASCII) and Modbus TCP in a single parameter. Each interface group is separated by ;, with the interface specifier and commands separated by /.

Syntax:

<interface>/<commands>;<interface>/<commands>

Interface specifiers:

InterfaceExampleDescription
Modbus RTUR,9600,8N1RS-485, RTU mode
Modbus ASCIIA,19200,7E1RS-485, ASCII mode
Modbus TCP192.168.1.200TCP, default port 502
Modbus TCP (custom port)192.168.1.200:1234TCP, custom port

Supported command codes: 01 Read Coils · 02 Read Discrete Inputs · 03 Read Holding Registers · 04 Read Input Registers

Example — RS-485 + Modbus TCP combined:

R,9600,8N1/010300000003,FA0400080002;192.168.1.200/010380000001
  • R,9600,8N1/... — Modbus RTU over RS-485
  • FA04... — internal gateway sensor (special address FA)
  • 192.168.1.200/... — Modbus TCP to ETH 1, port 502
Different from standard Modbus format

This format uses / (interface↔commands) and ; (between groups) — different from the standard Modbus Add-On which uses :.


Wired M-Bus

The Edge also supports wired M-Bus meter reading. See the M-Bus Add-On documentation for configuration details.