This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF9160 Modem Firmware 1.3.0 fails in LTE connection

Hi, 

I was using NCS 1.5.0 and Modem firmware 1.2.3. 

I have latest DK of nRF9160. 

It was running properly without issue specially LTE connection. 

But after I migrated from 1.2.3 to 1.3.0 modem firmware, I have noticed LTE connection failure sometimes. 

I get below print on pc terminal 

LTE Link Connecting ..

After that I don't get anything. Which means it fails to connect with LTE. 

When this issue happens I try to reset nRF9160 through  "nrfjprog --reset" but after system reset also I get same issue. 

Issue gets resolved only after I do power off and power on.  

Regards,

Smitesh Mali

Parents
  • I’m not aware of that the mfw 1.3.0 requires a certain nRF Connect SDK version. You will however get most out of it using it together with the upcoming nRF Connect SDK v1.6.0, since it also contains samples that will demonstrate the usage/API of the new modem features. nRF Connect SDK v1.6.0 will be released soon.

    Btw: if you still would like to provide me with an application log, I would recommend you to build your application with following configuration commando:

    CONFIG_AT_CMD_LOG_LEVEL_DBG=y

    This will visualise all the AT commands being send.

    Thanks and regards,

    Markus

Reply
  • I’m not aware of that the mfw 1.3.0 requires a certain nRF Connect SDK version. You will however get most out of it using it together with the upcoming nRF Connect SDK v1.6.0, since it also contains samples that will demonstrate the usage/API of the new modem features. nRF Connect SDK v1.6.0 will be released soon.

    Btw: if you still would like to provide me with an application log, I would recommend you to build your application with following configuration commando:

    CONFIG_AT_CMD_LOG_LEVEL_DBG=y

    This will visualise all the AT commands being send.

    Thanks and regards,

    Markus

Children
  • Hi Markus,

    I have been trying to catch the instance where it does not connect for the last 2 days and it has not happened yet. Testing any fix will be just as challenging as issue happens randomly.

    In you preious post you mentioned that you observed the same behavior, do you have a fix?

    Our asset tracker does not have any means to power cycle the board. can you confim if toggle the 'enable' pin will reboot and fix the issue? My concern is that if it happens, we will not have a way to recover from it since rebooting does not fix it.

    Regards

    Noaman

Related