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.
Additional Parameter Information
In addition to the information on this page and in the device-specific documentation, each Lobaro device provides additional information about the configuration parameters supported by the respective firmware via the serial log interface. This information appears directly after starting / resetting the device and can be read out via the Lobaro Maintenance Tool.
Network Selection Parameters
WAN
For hybrid Lobaro devices that 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 cellular IoT (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 |
|
Older Firmware versions
With some older firmware versions, only "lte" or "lorawan" could be configured successfully via the above-mentioned WAN parameter! On these older versions, additional parameters are available to configure the unit behaviour more precisely.
| Name | Description | Default Value | Value Description & Examples |
|---|---|---|---|
OTAA | LoRaWAN Activation: OTAA or ABP | true | true = use OTAA, false = use ABP |
UseNbiot | Cellular Technology: Try to connect with NB-IoT | true | |
UseLtem | Cellular Technology: Try to fallback to LTE-M (if supported) | false |
These additional parameters are no longer available on units with newer firmware versions! Consider a firmware update if available.
Cellular Parameters (NB-IoT, LTE-M)
| Name | Description | Default Value | Value Description & Examples |
|---|---|---|---|
APN | Mobile operator APN | iot.1nce.net | 1NCE: iot.1nce.net Vodafone Easy Connect: lpwa.vodafone.com (l = little L) |
Operator | Optional: Mobile Operator Code (5 digit: MCC+MNC) | 26201 | 26201 (= 1nce, Deutsche Telekom), For other operators see here. |
Band | Optional: Cellular LTE Band to try | "8", "20", "8,20" or "3,8,20", Empty = Auto detect (longer connecting time) | |
PIN | Optional: Sim Card PIN to use | Empty or 4 digits (e.g. 1234) |