...
| Info |
|---|
Remote Configuration is also supported after initial network connection. |
Networking Parameters
| Name | Description | Default Value | Value Description & Examples |
|---|---|---|---|
WAN | Radio technology used for connection to backend | lte |
|
Host | Hostname / IP of the Lobaro Platform API Not used for LoRaWAN uplink | 94.130.20.37 | 94.130.20.37 = |
platform.lobaro.com  DNS is not supported yet | |||
Port | Port number of the Lobaro Platform API Not used for LoRaWAN uplink | 5683 |
NB-IoT Parameters (WAN = "lte", "nbiot", "ltem")
...
LoRaWAN Parameters (WAN = "lorawan", "lorawan-abp")
| Name | Description | Default Value | Value Description & Examples |
|---|---|---|---|
DevEUI | DevEUI used to identify the Device | Device's own DevEUI as printed on label | 8 bytes = 16 hex digits, e.g. 0123456789abcdef |
JoinEUI | EUI used for OTAA (aka AppEUI) | Individual default value for each device | 8 bytes = 16 hex digits, e.g. 0123456789abcdef |
AppKey | AES Key used for LoRaWAN | Individual default value for each device | 16 bytes = 32 hex digits, e.g. 0123456789abcdef001122334455667788 |
SF | Minimal Spreading Factor used | 12 | 7-12, used after reset, can be decreased by ADR during operation (but not increased) |
| Warning |
|---|
When changing Keep the value for |
OTAA - Over the Air Activation
...
Modbus related Parameters
| Name | Description | Default Value | Values Description & Examples |
|---|---|---|---|
MbCmd | List of Modbus Commands with Cron and Modbus parameters (see below). | 0 0/5 * * * *:R,9600,8N1:010300000003 | One or more entries of Modbus commands to be executed by the device. Each entry starts with a Cron expression defining when to execute the commands followed by the bus parameters used to address the Modbus slave devices. Each entry can contain multiple commands. See description below for a detailed explanation. † |
† See also our Introduction to Cron expressions.
MbCmd defines, what Modbus commands are executed on the Bus, when, and what Modbus Configuration to use for them. The configuration is very flexible and allows complex setups, that include executing different commands at individual intervals or times or using multiple diffent Modbus parameters to address incompatible Slaves on the same installation. Any Modbus command can be sent, including writing registers or diagnostic messages.
The default value of 0 0/5 * * * *:R,9600,8N1:010300000003 shows a very basic example with a single entry executed every 5 minutes using Modbus RTU to read 3 consecutive holdingregisters from a single slave device.
The parameter consists of up to 32 entries with individual Cron expression and Modbus configuration. Multiple entries are separated by semicolon. Each entry can have multiple Modbus commands to execute on activation, separated by comma.
| Code Block | ||
|---|---|---|
| ||
MbCmd = "<Entry1>;<Entry2>;...;<Entry32>" Entry = "<Cron>:<MbParm>:<Command1>,<Command2>,...,<CommandN> MbParm = "<Protocol>,<Baud>,<SymbolCfg>" Protocol = "R" for Modbus RTC, "A" for Modbus ASCII Baud = Baud rate, any of: 2400, 4800, 9600, 19200, 38400, 57600, 115200 SymbolConfig = Token string defining Data Length, Parity, and Stop Bits. Any of: "7E1", "7E2", "8N1", "8N2" Command = "<bytes to be sent in hex without checksum>" |
Modes of operation (work cycle)
...
| View file | ||||
|---|---|---|---|---|
|