Hello. After I updated the firmware on Thingy 91, it no longer registers on the network via LTE - the LTE indicator in LTE monitor blinks between yellow and red, and I get the CEREG 2 reply for the at command. It used to work with a preloaded example properly. My board version is 1.0.0. I'm using the iBasis SIM card, and I tried all available firmwares in the images_full folder, according to instructions on nordic tutorial.
Hi, the modem firmware I uploaded is up to date. I followed the Getting Started guide step by step, and I used J-link for uploading both 52 and 91 firmware.
My location is Larvik, Norway and I have succeeded to connect to the network previously on the nRF9160 DK board, so I think the coverage is not the issue. I also tried both iBasis and Telia SIM cards inserted in thingy with same results. Also, the preloaded asset tracker worked before updating the firmware.
What I think is the issue here, is that for some reason the asset tracker falls into boot loop. That's what I get in the LTE Link Monitor.
What I noticed is that the asset tracker cannot connect to the nRF Cloud (it worked before I updated the firmware) and then decides to shut down the modem and boot again
.
I also get different results on the indicators in LTE Link Monitor. Sometimes the LTE diode is blinking red/yellow, sometimes it's green (regardless of that the device is always in the boot loop), and all I do is just turn off and on the device.
I tried uploading both LTE-M and NB-IoT firmware and got the same results.
I once managed (just by restarting Thingy) to get this output with apparently successful connection, but it was also in the boot loop.
My plan is to check the LTE connection using other application that does not connect to nRF Cloud. Maybe it is just the preloaded asset tracker that is failing and the LTE Link Monitor indicators are not working properly.
Hi Maciek,
It looks like a nrf cloud issue. Most likely the certification you need to be able to connect to nRF Cloud (which asset tracker does) is corrupted (deleted, overwritten or something else).
How you can fix this is to follow this guide: https://devzone.nordicsemi.com/nordic/cellular-iot-guides/b/getting-started-cellular/posts/nrf-cloud-certificate-update
So after you have provisioned new certificates you should be able to run Asset Tracker application.
When using LTE link monitor just as a serial terminal, please turn OFF "automatic requests":
Since this can interfere with your application if you suddenly send some AT commands that messes with your application.
Best regards,
Martin l.
Hi Maciek,
It looks like a nrf cloud issue. Most likely the certification you need to be able to connect to nRF Cloud (which asset tracker does) is corrupted (deleted, overwritten or something else).
How you can fix this is to follow this guide: https://devzone.nordicsemi.com/nordic/cellular-iot-guides/b/getting-started-cellular/posts/nrf-cloud-certificate-update
So after you have provisioned new certificates you should be able to run Asset Tracker application.
When using LTE link monitor just as a serial terminal, please turn OFF "automatic requests":
Since this can interfere with your application if you suddenly send some AT commands that messes with your application.
Best regards,
Martin l.
