Issue setting up SIM on Thingy:91 / adding device on nRF Cloud

[maurits]

Hello,

I have been following the steps in Exercise 1 of Lesson 1 of the Cellular IoT Fundamentals course. I have a Thingy:91. I have followed the steps so far

- flashed the modem firmware (1.3.5)

- programmed the application firmware (Asset Tracker v2)

- made an nRF Cloud account and added the iBasis SIM 

- I have run the instructions in Cellular Monitor. After a lot of trial and error I managed to get to this stage, where supposedly everything is working. 

However, in nRF Cloud, when I go to add the device using IMEI in the format nrf-123456789012345, I get "There was an error adding your device: No device found for this id. The device has not yet been just-in-time provisioned." The device continues to blink in green three times with a short pause in between.

Looking at the troubleshooting steps for this error code:

1. Verify the values and try again. For Nordic Semiconductor products, please see the solution for nRF Code 40411, above. <- done, it's nrf- + a 15-digit code
2. Ensure that the device's SIM card or eSIM is activated and functioning. If using an iBasis SIM card that is packaged with a Nordic Semiconductor product such as a Development Kit, activate the card on nrfcloud.com and then (re-)boot the device to connect. <- I have successfully activated the SIM followed by a reboot
3. Check the LED status indicators to ensure the device indicates it has connected. <- unclear what this means
4. (Re-)flash the latest modem firmware. <- I have flashed the modem firmware
5. Flash new device certificates obtained from the CreateDeviceCertificateendpoint. <- not sure how to do this or whether it would help?
6. Move to a location with a better LTE connection. <- Cellular Monitor indicates an LTE connection

I've attached the Wireshark capture file.241120 Thingy 91 Wireshark.pcapng

Any ideas?

[maurits]

Since I cannot seem to edit my original question, I'll add some more information here.

I tried updating the certificates using this guide. I could then get the dashboard in Cellular Monitor to update properly, but otherwise the problems are the same.

I also tried to get debug-level logs from the Asset Tracker V2 application by editing prj.conf and flashing app_signed.hex. Output:

[00:00:13.272,003] <inf> app_event_manager: MODEM_EVT_LTE_DISCONNECTED  
[00:00:13.308,929] <err> nrf_cloud_integration: nrf_cloud_disconnect, error: -13  
+CSCON: 0  
%CESQ: 255,0,255,0  
+CEREG: 2  
[00:00:14.958,709] <inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE  
[00:00:16.935,668] <dbg> nrf_cloud_transport: nct_connect: getaddrinfo failed -11  
[00:00:16.935,729] <dbg> nrf_cloud: nfsm_set_current_state_and_notify: state: 1  
[00:00:16.935,729] <err> nrf_cloud_integration: NRF_CLOUD_EVT_TRANSPORT_CONNECT_ERROR: -3

I think there is an issue connecting to a network with LTE? 

at AT+CEREG?
+CEREG: 5,2

I then ran Modem Shell to debug. Many of the commands, like `cloud`, simply return "Command not found". However, `location get` returns

Started to get current location...
[00:09:33.566,192] <err> nrf_cloud_jwt: Modem does not have valid date/time, JWT not generated
[00:09:33.566,253] <err> location: Failed to generate JWT, error: -62

Which made me wonder whether being unable to generate JWTs may be the problem in interacting with nRF Cloud? 

I was also curious about the modem not having a valid date/time, here I get

mosh:~$ at AT+CCLK?
ERROR

When I check available networks, I get

mosh:~$ at AT+COPS=?
+COPS: (1,"","","23410",7)
OK

Anyway, I can see that

- The SIM is active in nRF Cloud

- The ICCID is correct

- But I cannot register to O2 UK network, `at AT+CEREG?` returns +CEREG: 0,4

I am not sure why. 

Finally, the logs from Modem Shell:

[00:00:00.494,567] <inf> nrf_modem_lib_trace: Trace thread ready
[00:00:00.502,105] <inf> nrf_modem_lib_trace: Trace level override: 2
mosh:~Network registration status: searching
Currently active system mode: LTE-M
LTE cell changed: ID: 128864662, Tracking area: 4288
RRC mode: Connected
PDN event: PDP context 0 activated
PDN event: PDP context 0, PDN type IPv4 only allowed
Modem domain event: Search done
Network registration status: Connected - roaming
PDN event: PDP context 0 deactivated
Network registration status: searching
RRC mode: Idle
Modem config for system mode: LTE-M - GNSS
Modem config for LTE preference: No preference, automatically selected by the modem
Currently active system mode: LTE-M
Modem FW version:      mfw_nrf9160_1.3.5
Device ID:             nrf-350457794443174
link_api_xmonitor_read failed, result: ret -77
Currently active system mode: None
Could not parse CID, err: -22
Unable to obtain pdp context info (-22)
LTE cell changed: ID: -1, Tracking area: -1

[Hakon]

maurits said:

- But I cannot register to O2 UK network, `at AT+CEREG?` returns +CEREG: 0,4

Have you checked that iBasis is allowed on this network? You should contact the network provider first and check if they know something about it.

[maurits]

I instead tried ordering a sim from Simbase, which definitely supports O2 in the UK.

All the problems are still exactly the same. 

at AT+CEREG?
+CEREG: 5,2

It is not connecting to anything, even though there are networks detected:

mosh:~$ at AT+COPS=?
+COPS: (1,"","","23430",7),(1,"","","23410",7),(3,"","","23432",7)
OK

Notably, there are still issues with the clock, no idea how to solve those either.

mosh:~$ at AT+CCLK?
+CME ERROR: 0

It is a shame, I spent quite of lot time and money on this device and either it cannot connect at all, or maybe it can but there is no documentation to help troubleshoot.

[Hakon]

You should have a raw modem trace if you want us to investigate this further. That means a file in the .mtrace or .bin format

[maurits]

Hi Hakon,

Simbase got back to me to say they've identified the issue and I can now use the SIM. Thank you for your help.

I am currently trying to get a BLE application working, but not yet succesfully.

Best wishes,

Maurits