Can't add dev kit to nRF cloud

[AdrianH]

Hi,

I followed both the quick start and manual steps to register my new nFR9160-DK in the nRF cloud, but I can't add the device.  The SIM registers OK, but LED3 changes to a triple flash rather than a double.  It looks from the Cellular Monitor that the SIM card is not registering with a provider.  This page would not let me upload the trace file, so I have attached a screenshot.  Can you please let me know if this is just a problem with iBasis network coverage?

Many thanks,

Adrian

[Øyvind]

Hello, 

Where are you located? You can find the iBasis coverage list here: https://www.nordicsemi.com/-/media/Software-and-other-downloads/3rd-party/iBasis-simplified-coverage-map-for-web.pdf. Are you able to test with another local SIM, to verify if there is a problem with the SIM?

Can you open the Serial Monitor to view log output? Also, please refresh dashboard to get a list of AT command output to share with me.

Could you share the mtrace file from the Celluar Monitor with me? 

Thanks.

Kind regards,
Øyvind

[AdrianH]

Hi Øyvind,

Thanks for your reply.  I'm located in the UK - according to the map there should be coverage.  I've attached the mtrace file.  Sorry, I'm new to this and unsure how to check the other info.

trace-2023-10-24T13-02-45.759Z.mtrace

[AdrianH]

Hi Øyvind,

I have managed to get the Serial Monitor working.  Can you please let me know the AT commands I need to execute to diagnose the problem?

[AdrianH]

Additional info from Serial Monitor:

[Øyvind]

Hello, from the output I can see that you are running Modem Shell. Could you try running the Asset Tracker v2 application? This should allow you to provision kit to nRF Cloud. The error you have in the serial monitor corresponds to bad message and invalid argument - nrfxlib/nrf_modem/include/nrf_errno.h

Under the nRF9160 DK product page you can find a precompiled firmware package under the Downloads tab. This will allow you to program a precompiled version of the Asset Tracker, there is also a debug version that has modem logging enabled under Debug.

Kind regards,
Øyvind

[AdrianH]

I've tried everything you have suggested with no luck.  The device finds the Telefonica LTE-M network, but won't register with it.  In Cellular Monitor, the parameter Connection Evaluation Result sits at state 6 (not registered).

[Øyvind]

Could you please provide the mtrace file that Cellular Monitor collects? This way I can see what is going on in the modem. 

The cellular monitor has a button with Refresh Dashboard on the left hand side. Can you please click on this after starting modem trace?  This should provide the output with details for me to evaluate.

Thank you.

[AdrianH]

Hi,

Please find the mtrace file attached.  I have requested a trial pack of sim cards from O2 at they are the only provider of LTE-M in the UK.

trace-2023-10-26T10-52-46.762Z.mtrace

[Øyvind]

AdrianH , sorry about the late reply. For some reason your answers have not been picked up the system and not notified me about them. I will have a look at the trace file. Make sure to ping me when answering, hopefully I will be notified

[Dominic]

Hey, I’ve just heard a rumour that Telefonica have revoked LTE-M roaming in the UK, so this might be the reason. I haven’t found any official announcement, and 1oT have not heard.

[AdrianH]

Interesting - let's see what Øyvind comes back with.

[Øyvind]

Yes, the O2 network has made some changes to the roaming policy in their network, starting end of October. 

From the modem traces that provided I can see that there is a reject cause 15 - No suitable cells in tracking area. This EMM cause is sent to the UE if it requests service, or if the network initiates a detach request, in a tracking area where the UE, by subscription, is not allowed to operate, but when it should find another allowed tracking area or location area in the same PLMN or an equivalent PLMN.

I would reach out to O2 / Telefonica for more information. Please test with an O2 / Telefonica SIM