Some Lobaro devices do support mobile connections like NB-IoT or LTE-Cat-M1. This page contains background information and technical details related to the mobile connections.
See: LTE Network Config |
Content
The signal strength of the LTE-M1 or NB-IoT network can be derived from the RSRP and RSRQ dimensionless values.
| Coverage | LTE RSRP | LTERSRP (dBm) | RSRQ | RSRQ (dB) |
|---|---|---|---|---|
Average power received | Average power received (dBm) | Average receive quality | Average receive quality (dB) | |
| Excellent (4/4) | 80 - 97 | -60 to -44 | 28 - 34 | -5.5 to -3 |
| Good (3/4) | 60 - 79 | -80 to -61 | 21 - 27 | -9 to -6 |
| Mid Cell (2/4) | 40 - 59 | -100 to -81 | 14 - 20 | -12.5 to -9.5 |
| Cell Edge (1/4) | 20 - 39 | -120 to -101 | 7 - 13 | -16 to -13 |
| Unstable (0/4) | 0 - 20 | -140 to -121 | 0 - 7 | -19.5 to -16.5 |
The actual value of your devices connection statistics is shown in the Lobaro platform under "Device Properties".
For "unstable" network coverage Lobaro can not guarantee the correct function of the cellular uplinks and battery runtimes under all conditions. Please consider a different location for the particular device.
There are multiple ways to trace where a mobile device is.
In General the following information is required and transmitted in the device status packets:
Here are some resources to use:
| Resource | Description | |
|---|---|---|
| Lookup Cells |
platform.eNodeB.towerID (based on CI ) var ci = parseInt("01DD4E02",16);
| |
| https://my.unwiredlabs.com/dashboard/login | LTE Location API Account required |
|
Newer firmware of Lobaro products report potential ESM (EPS Session Management) and EMM (EPS Mobility Management) errors in their status uploads.
Source: ETSI TS 124 301 V14.5.0 - Table 9.9.3.9.1: ESM cause information element
E.g.: +CNEC_EMM: 19 is error code 19 which is 0b10011 which corresponds to ESM failure (see table below)
Source: ETSI TS 124 301 V14.5.0 - Table 9.9.4.4.1: ESM cause information element
CNEC_ESM: 27,0 is error code 27 with cid 0, and 27 is binary 1b11011 which corresponds to Missing or unknown APN
Please see: https://iotcreators.com/network/?#G
For testing the coverage you can use our hardware with our USB Config Adapter and the Lobaro Maintenance Tool to observe the log during connection.
Or test yourself using a professional 3rd party network tester e.g. from ENQT.
Today Lobaro is using the Nordic nRF9160 in most of it's products. Beside that Lobaro Firmware the Modem Firmware from Nordic is running on a separate core.
| Parameter | Beschreibung | Values |
|---|---|---|
| conMode | ||
| reg | Registration |
|
| tac | Tracking Area Code | |
| ci | Cell ID | |
| psm | PSM Activity Timer (T3324) | See for info: |
| tau | Long-Periodic TAU Timer (Extended T3412) | |
| SNR | Signal to Noise Ratio |
The Lobaro Hardware does not support remote Modem Firmware updates. This might change in future but brings additional hardware requirements like external memory.
When enabling both LTE-M and NB-IoT in a Lobaro Firmware that runs with Modem Firmware < 1.3.0 the Modem can not do a fallback to LTE-M when NB-IoT is not available and thus the firmware only uses NB-IoT in that case.
With Modem Firmware >= 1.3.0 a proper fallback is implemented.
The nrf9160 SIBA only supports NB-IoT but not LTE-M. Since late 2021 Lobaro only uses the nrf9160 SICA which supports both NB-IoT and LTE-M.
