Skip to main content

Ethernet — Configuration

The Ethernet Add-On adds a single Ethernet port to the Gateway V4, enabling IP connectivity and Modbus TCP reading.

Compatible product: Gateway V4 + Ethernet


WAN Parameter​

The Ethernet Add-On extends the standard WAN parameter with additional values for Ethernet-based uplink:

ValueDescription
lteCellular uplink (NB-IoT or LTE-M)
lorawanLoRaWAN uplink
ethernetEthernet as sole uplink
ethernet+lteEthernet as primary uplink with automatic LTE fallback (default)
  • ethernet: Data is sent exclusively via the Ethernet port. The cellular modem is not used.
  • ethernet+lte: Ethernet is used when available. If the Ethernet connection is unavailable, the device automatically falls back to LTE.

Ethernet Configuration​

KeyTypeDefaultDescription
ipAddressStringdhcpEthernet IP configuration: dhcp for automatic address assignment, or ip,netmask,gateway for a static address. Optional fourth field for a DNS server: ip,netmask,gateway,dns

Example — static:

192.168.1.91,255.255.255.0,192.168.1.1

Example: static with DNS server:

192.168.1.91,255.255.255.0,192.168.1.1,192.168.1.1

Example — DHCP:

dhcp
Gateway V4 + DIN-Rail

This page describes the single-port Gateway V4 + Ethernet. The Gateway V4 + DIN-Rail has two Ethernet ports and uses a two-entry ipAddress syntax, see DIN-Rail configuration.


Modbus Configuration​

KeyTypeDefaultDescription
modbusCmdConfString—Modbus interface parameters and list of commands (see below)
modbusInternalAddressNumber250Modbus address for internal gateway sensors
addonAccumulateNumber1Readouts to accumulate before upload (1–15)
loraFormatNumber5LoRaWAN payload format: 1 = Verbose, 4 = Compact with timestamp, 5 = Compact without timestamp

Modbus TCP commands are added to the modbusCmdConf parameter using an IP address as the interface specifier. The interface and commands are separated by /, multiple interface groups by ;.

Syntax:

<ip>/commands;<ip:port>/commands
  • 192.168.1.222 → Modbus TCP, default port 502
  • 192.168.1.222:1234 → Modbus TCP, custom port

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

Example:

192.168.1.200/010380000001,020300010002
Different from standard Modbus format

Modbus TCP entries must use / between interface and commands, because : separates the TCP port. Multiple interface groups are separated by ;. The Modbus Add-On supports Modbus RTU and ASCII over RS-485 only and uses : as separator.