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

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

maurits — Mon, 03 Mar 2025 22:20:11 GMT

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

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

Hakon — Fri, 17 Jan 2025 14:21:50 GMT

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

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

maurits — Sat, 14 Dec 2024 19:05:26 GMT

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.

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

Hakon — Wed, 11 Dec 2024 12:04:54 GMT

[quote user="maurits"]- But I cannot register to O2 UK network, `at AT+CEREG?` returns +CEREG: 0,4[/quote]

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.

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

maurits — Fri, 29 Nov 2024 13:27:50 GMT

Yes, it's active and has 10.47 out of 10.49 MB remaining (it's the iBasis that came included)

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

Hakon — Fri, 29 Nov 2024 13:14:29 GMT

Hello,

have you checked that the SIM card has data on it?

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

maurits — Sat, 23 Nov 2024 10:53:38 GMT

Some more output from Modem Shell - it looks like it briefly connects and then disconnects. No idea whether it's a problem with the SIM. I tried setting the PDP context manually with

AT+CGDCONT=0,"IP","iBASIS.iot"which produces the below output

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
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
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-350457794443123
link_api_xmonitor_read failed, result: ret -77
Currently active system mode: None
Could not parse dns str for cid 0, err: -22
PDP context info 1:
  CID:                0
  PDN ID:             0
  PDP context active: no
  PDP type:           IP
  APN:                iBASIS.iot
  IPv4 address:       0.0.0.0
  IPv6 address:       ::
  IPv4 DNS address:   0.0.0.0, 0.0.0.0
  IPv6 DNS address:   ::, ::
LTE cell changed: ID: -1, Tracking area: -1

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

maurits — Thu, 21 Nov 2024 11:30:49 GMT

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

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

maurits — Wed, 20 Nov 2024 18:29:30 GMT

Here are the device logs:

*** Booting Zephyr OS build v3.2.99-ncs2 ***
[00:00:01.512,695] <inf> at_host: UART check failed: 12. Dropping buffer and retrying.
[00:00:01.523,284] <inf> app_event_manager: APP_EVT_START
[00:00:01.526,824] <inf> app_event_manager: MODEM_EVT_INITIALIZED
[00:00:01.600,036] <inf> app_event_manager: MODEM_EVT_LTE_CONNECTING
[00:00:02.544,372] <inf> app_event_manager: DATA_EVT_CONFIG_INIT
[00:00:04.296,966] <inf> app_event_manager: SENSOR_EVT_MOVEMENT_ACTIVITY_DETECTED
%CESQ: 52,2,4,0
+CEREG: 2,"10C0","07AE5196",7
%CESQ: 54,2,17,2
+CSCON: 1
%CESQ: 55,2,11,1
[00:00:12.157,073] <inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE
+CGEV: ME PDN ACT 0,0
+CNEC_ESM: 50,0
%MDMEV: SEARCH STATUS 2
+CEREG: 5,"10C0","07AE5196",7,,,"00001010","11000010"
+CGEV: NW DETACH
+CGEV: ME PDN DEACT 0
+CEREG: 2,"10C0","07AE5196",7
[00:00:14.731,414] <inf> app_event_manager: MODEM_EVT_LTE_CONNECTED
[00:00:14.732,574] <inf> app_event_manager: CLOUD_EVT_CONNECTING
[00:00:14.744,506] <inf> app_event_manager: MODEM_EVT_LTE_PSM_UPDATE
[00:00:14.828,155] <inf> app_event_manager: MODEM_EVT_LTE_DISCONNECTED
[00:00:14.828,918] <err> nrf_cloud_integration: nrf_cloud_disconnect, error: -13
+CSCON: 0
%CESQ: 255,0,255,0
+CEREG: 2
[00:00:16.485,229] <inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE
%CESQ: 52,2,4,0
[00:00:18.484,558] <inf> app_event_manager: CLOUD_EVT_CONNECTING
%CESQ: 53,2,12,1
%CESQ: 47,2,11,1
%CESQ: 44,2,16,2
%CESQ: 44,2,11,1
%CESQ: 255,0,255,0
%CESQ: 62,3,28,4
+CEREG: 2,"B7F3","003E8217",9
+CSCON: 1
+CEREG: 2,"B7F3","003E8217",9,0,11
+CSCON: 0
[00:01:30.250,518] <inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE
%CESQ: 61,3,34,4
%CESQ: 255,0,255,0
+CEREG: 2
%CESQ: 45,2,16,2
[00:01:46.426,483] <inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE
%CESQ: 43,2,10,1
[00:02:02.545,013] <inf> app_event_manager: APP_EVT_DATA_GET_ALL
[00:02:02.545,715] <inf> app_event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, MOD_STAT, LOCATION)
[00:02:02.646,545] <inf> app_event_manager: LOCATION_MODULE_EVT_AGPS_NEEDED
[00:02:02.646,911] <inf> app_event_manager: LOCATION_MODULE_EVT_ACTIVE
[00:02:02.647,735] <inf> app_event_manager: SENSOR_EVT_ENVIRONMENTAL_DATA_READY
[00:02:02.676,025] <err> modem_info_params: Link data not obtained: 5 -22
[00:02:02.676,055] <err> modem_module: modem_info_params_get, error: -22
[00:02:02.676,116] <inf> app_event_manager: MODEM_EVT_MODEM_STATIC_DATA_NOT_READY
[00:02:02.682,464] <err> modem_info_params: Link data not obtained: 5 -22
[00:02:02.682,495] <err> modem_module: modem_info_params_get, error: -22
[00:02:02.682,556] <inf> app_event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_NOT_READY
[00:02:02.771,942] <err> modem_info_params: Link data not obtained: 5 -22
[00:02:02.771,972] <err> modem_module: modem_info_params_get, error: -22
[00:02:02.772,064] <inf> app_event_manager: MODEM_EVT_BATTERY_DATA_NOT_READY
%CESQ: 43,2,17,2
> at AT
ERROR
%CESQ: 255,0,255,0
%NCELLMEAS: 1
[00:03:32.667,816] <wrn> location: GNSS timed out possibly due to too short GNSS time windows
[00:03:32.702,545] <wrn> location: Current cell ID not valid
[00:03:32.702,575] <wrn> location: No cellular neighbor cells or Wi-Fi access points found
[00:03:32.702,606] <err> location: Location acquisition failed and fallbacks are also done
[00:03:32.702,636] <wrn> location_module: Getting location failed
[00:03:32.702,728] <inf> app_event_manager: LOCATION_MODULE_EVT_DATA_NOT_READY
[00:03:32.703,155] <inf> app_event_manager: LOCATION_MODULE_EVT_INACTIVE
[00:03:32.703,735] <inf> app_event_manager: DATA_EVT_DATA_READY
%CESQ: 42,2,9,1
%CESQ: 44,2,16,2
[00:04:02.545,013] <inf> app_event_manager: APP_EVT_DATA_GET_ALL
[00:04:02.545,715] <inf> app_event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, MOD_STAT, LOCATION)
[00:04:02.646,575] <inf> app_event_manager: LOCATION_MODULE_EVT_AGPS_NEEDED
[00:04:02.646,942] <inf> app_event_manager: LOCATION_MODULE_EVT_ACTIVE
[00:04:02.647,674] <inf> app_event_manager: SENSOR_EVT_ENVIRONMENTAL_DATA_READY
[00:04:02.674,072] <err> modem_info_params: Link data not obtained: 5 -22
[00:04:02.674,102] <err> modem_module: modem_info_params_get, error: -22
[00:04:02.674,163] <inf> app_event_manager: MODEM_EVT_MODEM_STATIC_DATA_NOT_READY
[00:04:02.680,297] <err> modem_info_params: Link data not obtained: 5 -22
[00:04:02.680,328] <err> modem_module: modem_info_params_get, error: -22
[00:04:02.680,389] <inf> app_event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_NOT_READY
[00:04:02.769,805] <err> modem_info_params: Link data not obtained: 5 -22
[00:04:02.769,836] <err> modem_module: modem_info_params_get, error: -22
[00:04:02.769,927] <inf> app_event_manager: MODEM_EVT_BATTERY_DATA_NOT_READY
%CESQ: 44,2,11,1
%CESQ: 49,2,11,1
%CESQ: 54,2,13,1
%CESQ: 55,2,18,2
%CESQ: 53,2,12,1
%CESQ: 255,0,255,0
[00:05:32.665,832] <wrn> location: GNSS timed out possibly due to too short GNSS time windows
%NCELLMEAS: 1
[00:05:43.768,585] <wrn> location: Current cell ID not valid
[00:05:43.768,615] <err> location: Location acquisition failed and fallbacks are also done
[00:05:43.768,707] <inf> app_event_manager: LOCATION_MODULE_EVT_TIMEOUT
[00:05:43.769,165] <inf> app_event_manager: LOCATION_MODULE_EVT_INACTIVE
[00:05:43.769,683] <inf> app_event_manager: DATA_EVT_DATA_READY
%CESQ: 52,2,7,1
%CESQ: 54,2,14,2
[00:06:02.545,013] <inf> app_event_manager: APP_EVT_DATA_GET_ALL
[00:06:02.545,684] <inf> app_event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, MOD_STAT, LOCATION)
[00:06:02.646,514] <inf> app_event_manager: LOCATION_MODULE_EVT_AGPS_NEEDED
[00:06:02.646,881] <inf> app_event_manager: LOCATION_MODULE_EVT_ACTIVE
[00:06:02.647,705] <inf> app_event_manager: SENSOR_EVT_ENVIRONMENTAL_DATA_READY
[00:06:02.674,804] <err> modem_info_params: Link data not obtained: 5 -22
[00:06:02.674,835] <err> modem_module: modem_info_params_get, error: -22
[00:06:02.674,896] <inf> app_event_manager: MODEM_EVT_MODEM_STATIC_DATA_NOT_READY
[00:06:02.684,906] <err> modem_info_params: Link data not obtained: 5 -22
[00:06:02.684,906] <err> modem_module: modem_info_params_get, error: -22
[00:06:02.684,997] <inf> app_event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_NOT_READY
[00:06:02.786,407] <err> modem_info_params: Link data not obtained: 5 -22
[00:06:02.786,437] <err> modem_module: modem_info_params_get, error: -22
[00:06:02.786,529] <inf> app_event_manager: MODEM_EVT_BATTERY_DATA_NOT_READY
%CESQ: 53,2,9,1
%CESQ: 54,2,14,2
%CESQ: 255,0,255,0
[00:07:32.665,771] <wrn> location: GNSS timed out possibly due to too short GNSS time windows