Device Configuration

Lobaro devices allow a wide range of configuration adjustments. This page describes the generally valid parameters that are used in the same way for Lobaro devices, although not all products have to support all parameters listed here. Device-specific parameters are explained in the respective documentation. All configuration parameters are stored non-volatile in the Lobaro devices.

How to configure

Any Lobaro device configuration can be set and read out either locally via a PC with the Lobaro configuration USB adapter and the Lobaro Maintenance Tool or remotely when using the Lobaro IoT platform and mobile radio (NB-IoT, LTE-M) or any LoRaWAN network server using downlinks on a special port. Network parameters, such as the APN of the mobile cellular network provider, must usually first be configured correctly locally. Alternatively, possible on request for larger orders, an intimate configuration agreed with the customer can also be installed by Lobaro ex works.

Network Parameters

WAN

Since Lobaro devices include a variety of different technologies for sending data, the "WAN" parameter is one of the most important to control the behaviour of the device. This parameter can be used to set whether NB-IoT, LTE-M or LoraWAN is to be used for data transmission. With LoRaWAN, the type of network join can also be defined (ABP vs. OTAA). Some devices even extend the possible values of the parameter, e.g. for an upload via LAN. In this case, details can be found in the device-specific documentation.

Name

Description

Default Value

Value Description & Examples

WAN

Technology used for connection and data uplinks to backend

lte

lte: use either cellular NB-IoT or LTE-M

```
nbiot: use cellular NB-IoT
```
```
ltem: use cellular LTE-M
```
```
lorawan: use LoRaWAN with OTAA
```
```
lorawan-abp: use LoRaWAN with ABP
```
```
lan: use LAN/Ethernet ( device-specfic)
```

Older Firmware versions

With some older firmware versions, only "lte" or "lorawan" could be configured via the above-mentioned WAN parameter! In these older versions, additional parameters were used to configure the unit behaviour more precisely.