Failure to initialize lwm2m carrier library

RE: Failure to initialize lwm2m carrier library

Øyvind — Wed, 25 Aug 2021 09:12:01 GMT

Hi Jacek,
Glad to hear! 🙂

Kind regards,
Øyvind

RE: Failure to initialize lwm2m carrier library

Jacek Majda — Tue, 24 Aug 2021 14:29:48 GMT

Hi Øyvind,

As advised, I built the project, editing the prj.conf of Asset Tracker to the following:

1. CONFIG_LTE_NETWORK_MODE_LTE_M_GPS=n
2. CONFIG_LTE_NETWORK_MODE_NBIOT_GPS=y

This resulted in a speedy connection of Asset Tracker application to LTE network.

Thanks for assistance.

Regards,

Jacek

RE: Failure to initialize lwm2m carrier library

Øyvind — Mon, 23 Aug 2021 07:04:55 GMT

Hi Jacek,

Happy to hear that you found the solution. Note that if you are on a NB-IoT network, then you should use either the procompiled FW i.e. img_app_bl\nrf9160dk_asset_tracker_nbiot_2021-06-25_7a076c22.hex or build from NCS project, editing the prj.conf of Asset Tracker to the following:

CONFIG_LTE_NETWORK_MODE_LTE_M_GPS=n
CONFIG_LTE_NETWORK_MODE_NBIOT_GPS=y

The Getting Started chapter of our nRF Connect SDK documentation is a good starting point along with Working with nRF91-series.

Kind regards,
Øyvind

RE: Failure to initialize lwm2m carrier library

Jacek Majda — Sun, 22 Aug 2021 11:12:12 GMT

Hello,

I did follow your advice to try and build asset tracker leaving out C.Make parameter: -DOVERLAY_CONFIG=lwm_carrier_overlay.conf and it did work. I was able to connect to LTE network, although only after a 10 minutes delay from the time I did reset the board.

So the problem has been solved, thanks for your advice.

I did run this asset tracker application (that I built using SES) several times and each time it took 10 minutes after resetting the board, before the connection to LTE network was established. This was in contrast to the prebuilt nRF9160:Asset Tracker application, which did establish connection to LTE network within a few seconds after resetting the board , each time I ran this application.

After analysis of the log file of the nRF Conect LTE Link Monitor (for the asset tracker application that I built using SES and leaving out the CMake parameter), I noticed that:

1. After 10 minutes from starting the Asset Tracker, a message: "Network connect attempt timed out" was logged.

2. The above message was followed by another message: "lte_le:Using fallback network mode".

3. And a few seconds later, the message: "asset_tracker:connected to LTE Network" was logged.

4. The connection to LTE Network was also confirmed by LED4 turning permanently ON on my nRF9160 DK board.

I did search for info on the LTE_USE_FALLBACK and I found that:

1. The fallback network mode will be used when the selected mode fails.

2. If LTE-M is selected as the network mode, NB-IoT will be the fallback mode and vice versa.

I checked which AT commands could be used to check and set the required network mode (which is the NB-IoT network mode in my case) and I found that:

1. The AT command: AT%XSYSTEMMODE? can be used to check the selected mode

2. The AT command: AT%XSYSTEMMODE=0,1,1,0 can be used to set the NB-IoT network mode.

Subsequently, I run the asset tracker application that I built using SES and leaving out the CMake parameter, as advised by you and I used the AT%XSYSTEMMODE? command to check which network mode was used by this application during the first 10 minutes after the reset.

As expected, I found that this application was using the LTE-M network mode during the first 10 minutes after reset, and only when the fullback network mode (NB-IoT) was activated 10 minutes later, the connection to LTE network was established.

I must say that I have learned a lot from this exercise.

Thank for your assistance in this regard.

Jacek

RE: Failure to initialize lwm2m carrier library

Øyvind — Fri, 20 Aug 2021 14:24:01 GMT

Hello,

[quote user=""]2. In the SES, I selected: Tools>Options>nRF Connect and I added the following CMake parameter: -DOVERLAY_CONFIG=lwm2m_carrier_overlay.conf[/quote]

Is there a reason for doing this? Do you need the carrier library? Is this result the same (Stuck after LWM2M_CARRIER_EVENT_CONNECTING) if you try to run the lwm2m_carrier sample? (nrf\samples\nrf9160\lwm2m_carrier) nRF9160: LwM2M carrier — nRF Connect SDK 1.6.1 documentation (nordicsemi.com). This is a more light weight sample that can help rule out issues.

Can you please provide more information on your location? What kind of SIM are you using?

Are you able to build asset tracker leaving out CMake parameter: -DOVERLAY_CONFIG=lwm2m_carrier_overlay.conf?

Thank you!

Kind regards,
Øyvind