Error Provisioning Nordic Thingy91

[jake11212]

Hello

I was setting up the nordic thing 91 (1.4.0, 2020.23) using this video https://www.youtube.com/watch?v=xQ7hDzRULJQ&ab_channel=NordicSemiconductor.

Things were going fine until I got to the section on adding the LTE device around 5:20 in the video.  I was successfully able to flash the device and add the sim card, but on the LTE page I get an error that the device hasn't been provisioned.  (Error: No device found for this id. The device has not yet been provisioned. Troubleshoot nRF Code 40412).

In the description of the video is the following note:  If you have a Thingy:91 v1.4.0 or higher, you have to update the FW on the nRF52840 (connectivity_bridge) first, before following the instructions at 2:44 to update the FW on the nRF9160. Please keep in mind that the method for putting the device into serial recovery mode varies depending on which chip you are flashing to (either pushing SW3 for the nRF9160 or SW4 for the nRF52840, while turning the device on)..

This applies to my device, so to follow the note (using the download  precompiled application and modem firmware 2021-06-28_7a076c22)

1.) Turn on device with sw4 held to put into boot mode and allow flash to nrf52840

2.) Select the hex file thingy91_nrf52_connectivity_bridge_2021-06-28_7a076c22 and write (in nrf connect 3.6.1)

3) turn off device

4) boot device with sw3 held

5) update modem with mfwnrf9160120 zip file

6.)turn off device and boot again with sw3 held

7.) write thingy91_asset_tracker_ltem_2021-06-28_7a076c22 hex file 

At this point the device just flashes blue for 15+ minutes and never changes to indicate that it connected.  I am unsure if I am misunderstanding what the note is explaining to do or if there is some other issue.  What could be causing the device to fail to connect?

Also general questions: I assume that the firmware updates persist on the chip until overwritten correct?  I also noticed that if I start the device in boot mode and complete the firmware update using a zip file I cannot write after, and have to turn off and on the device in boot mode once again.  Is this the correct way to flash multiple times to the device or is something incorrect here?

Thanks

[Øyvind]

Hello, 

Good work following the exact steps. You have so far done everything correct from what I can see.

At this point the device just flashes blue for 15+ minutes and never changes to indicate that it connected.  I am unsure if I am misunderstanding what the note is explaining to do or if there is some other issue.  What could be causing the device to fail to connect?

Flashing blue I assume is flashing white (looks blue due to the plastic). This means that it is connecting. See color codes here, under User Interface of Asset Tracker. Have you registered the SIM card?

Have you tried to connect the Thingy:91 using LTE Link Monitor? What does the output say? 

Thanks.

Kind regards,
Øyvind

[jake11212]

Yes, on the nrfcloud website it says there is one sim card registered. The device seems to be alternating between flashing purple and flashing blue.  I attached the logs for a few cycles of this as well as pictures of the colors it alternates between incase that might help as well.

I also am currently in the South Eastern United States.  I checked connectivity for the ibasis sim cards and it said that there is coverage for the entire united states, but I also noticed that coverage for LTE-M for the thingy91 was only tested in the Western United States so I was wondering if this may potentially be a problem as well.

In the top right of the LTE link monitor, the UART block is red, the modem and uicc blocks are green, the lte block flashes between red and yellow, and the pdn block in green

I was also using an earlier version of the firmware that matched the tutorial when I first made the post but used the analogous files in the most recent firmware.  The files I used were:

nrf52840 - thingy91_nrf52_connectivity_bridge_2021-06-28_7a076c22

modem firmware - mfw_nrf9160_1.3.0

running file - thingy91_asset_tracker_v2_ltem_2021-06-28_7a076c22

The logs were produced running this combination of files.  I omitted the logs for the device setup because they contain the pin and imei but if you need those I could create a private ticket or send them to you in a private message.

Fullscreen thingy91 logs.txt Download

2021-07-13T16:36:51.058Z DEBUG modem << [00:01:51.231,872] [0m<inf> event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2021-07-13T16:37:00.112Z DEBUG modem << [00:02:00.286,743] [0m<inf> event_manager: APP_EVT_DATA_GET_ALL[0m
2021-07-13T16:37:00.114Z DEBUG modem << [00:02:00.293,487] [0m<inf> event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, GNSS, MOD_STAT)[0m
2021-07-13T16:37:00.148Z DEBUG modem << [00:02:00.331,939] [0m<inf> event_manager: GPS_EVT_ACTIVE[0m
2021-07-13T16:37:00.149Z DEBUG modem << [00:02:00.338,104] [0m<inf> event_manager: GPS_EVT_AGPS_NEEDED[0m
2021-07-13T16:37:00.171Z DEBUG modem << [00:02:00.348,876] [0m<inf> event_manager: SENSOR_EVT_ENVIRONMENTAL_DATA_READY[0m
2021-07-13T16:37:00.187Z DEBUG modem << [00:02:00.357,940] [1;31m<err> modem_info_params: Link data not obtained: 9 -134[0m
2021-07-13T16:37:00.189Z DEBUG modem << [00:02:00.366,607] [1;31m<err> modem_info_params: Link data not obtained: 9 -134[0m
2021-07-13T16:37:00.231Z DEBUG modem << [00:02:00.376,800] [1;31m<err> modem_info_params: Link data not obtained: 5 -22[0m
2021-07-13T16:37:00.232Z DEBUG modem << [00:02:00.385,162] [1;31m<err> modem_info_params: Link data not obtained: 5 -22[0m
2021-07-13T16:37:00.233Z DEBUG modem << [00:02:00.393,554] [1;31m<err> modem_info_params: Link data not obtained: 8 -22[0m
2021-07-13T16:37:00.234Z DEBUG modem << [00:02:00.402,069] [1;31m<err> modem_info_params: Link data not obtained: 8 -22[0m
2021-07-13T16:37:00.235Z DEBUG modem << [00:02:00.410,461] [1;31m<err> modem_info_params: Link data not obtained: 3 -22[0m
2021-07-13T16:37:00.236Z DEBUG modem << [00:02:00.418,884] [1;31m<err> modem_info_params: Link data not obtained: 3 -22[0m
2021-07-13T16:37:00.345Z DEBUG modem << [00:02:00.433,013] [1;31m<err> modem_info_params: Link data not obtained: 21 -134[0m
2021-07-13T16:37:00.346Z DEBUG modem << [00:02:00.441,772] [1;31m<err> modem_info_params: Link data not obtained: 21 -134[0m
2021-07-13T16:37:00.347Z DEBUG modem << [00:02:00.450,286] [1;31m<err> modem_info_params: Link data not obtained: 20 -22[0m
2021-07-13T16:37:00.348Z DEBUG modem << [00:02:00.457,916] [1;31m<err> modem_info_params: Network data not obtained: -356[0m
2021-07-13T16:37:00.349Z DEBUG modem << [00:02:00.465,698] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m
2021-07-13T16:37:00.351Z DEBUG modem << [00:02:00.473,297] [0m<inf> event_manager: MODEM_EVT_MODEM_STATIC_DATA_NOT_READY[0m
2021-07-13T16:37:00.352Z DEBUG modem << [00:02:00.482,238] [1;31m<err> modem_info_params: Link data not obtained: 20 -22[0m
2021-07-13T16:37:00.354Z DEBUG modem << [00:02:00.489,868] [1;31m<err> modem_info_params: Network data not obtained: -356[0m
2021-07-13T16:37:00.355Z DEBUG modem << [00:02:00.497,619] [1;31m<err> nrf_cloud_agps: Could not obtain cell information[0m
2021-07-13T16:37:00.356Z DEBUG modem << [00:02:00.505,310] [1;31m<err> nrf_cloud_agps: Failed to add modem info to A-GPS request: -11[0m
2021-07-13T16:37:00.358Z DEBUG modem << [00:02:00.514,282] [1;31m<err> agps: nRF Cloud A-GPS request failed, error: -11[0m
2021-07-13T16:37:00.359Z DEBUG modem << [00:02:00.521,850] [1;33m<wrn> cloud_module: Failed to request A-GPS data, error: -11[0m
2021-07-13T16:37:00.361Z DEBUG modem << [00:02:00.529,998] [1;33m<wrn> cloud_module: This is expected to fail if we are not in a connected state[0m
2021-07-13T16:37:00.393Z DEBUG modem << [00:02:00.542,266] [1;31m<err> modem_info_params: Link data not obtained: 9 -134[0m
2021-07-13T16:37:00.395Z DEBUG modem << [00:02:00.551,696] [1;31m<err> modem_info_params: Link data not obtained: 5 -22[0m
2021-07-13T16:37:00.396Z DEBUG modem << [00:02:00.559,997] [1;31m<err> modem_info_params: Link data not obtained: 8 -22[0m
2021-07-13T16:37:00.397Z DEBUG modem << [00:02:00.568,267] [1;31m<err> modem_info_params: Link data not obtained: 3 -22[0m
2021-07-13T16:37:00.425Z DEBUG modem << [00:02:00.579,345] [1;31m<err> modem_info_params: Link data not obtained: 21 -134[0m
2021-07-13T16:37:00.426Z DEBUG modem << [00:02:00.587,951] [1;31m<err> modem_info_params: Link data not obtained: 20 -22[0m
2021-07-13T16:37:00.428Z DEBUG modem << [00:02:00.595,581] [1;31m<err> modem_info_params: Network data not obtained: -356[0m
2021-07-13T16:37:00.430Z DEBUG modem << [00:02:00.603,332] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m
2021-07-13T16:37:00.431Z DEBUG modem << [00:02:00.610,931] [0m<inf> event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_NOT_READY[0m
2021-07-13T16:37:00.433Z DEBUG modem << [00:02:00.621,643] [1;31m<err> modem_info_params: Link data not obtained: 9 -134[0m
2021-07-13T16:37:00.459Z DEBUG modem << [00:02:00.631,103] [1;31m<err> modem_info_params: Link data not obtained: 5 -22[0m
2021-07-13T16:37:00.461Z DEBUG modem << [00:02:00.639,404] [1;31m<err> modem_info_params: Link data not obtained: 8 -22[0m
2021-07-13T16:37:00.462Z DEBUG modem << [00:02:00.647,766] [1;31m<err> modem_info_params: Link data not obtained: 3 -22[0m
2021-07-13T16:37:00.501Z DEBUG modem << [00:02:00.658,996] [1;31m<err> modem_info_params: Link data not obtained: 21 -134[0m
2021-07-13T16:37:00.502Z DEBUG modem << [00:02:00.667,449] [1;31m<err> modem_info_params: Link data not obtained: 20 -22[0m
2021-07-13T16:37:00.503Z DEBUG modem << [00:02:00.675,079] [1;31m<err> modem_info_params: Network data not obtained: -356[0m
2021-07-13T16:37:00.504Z DEBUG modem << [00:02:00.682,861] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m
2021-07-13T16:37:00.505Z DEBUG modem << [00:02:00.690,551] [0m<inf> event_manager: MODEM_EVT_BATTERY_DATA_NOT_READY[0m
2021-07-13T16:38:15.156Z DEBUG modem << [00:03:15.345,489] [0m<inf> event_manager: DATA_EVT_DATA_READY[0m
2021-07-13T16:39:00.131Z DEBUG modem << [00:04:00.286,743] [0m<inf> event_manager: APP_EVT_DATA_GET_ALL[0m
2021-07-13T16:39:00.133Z DEBUG modem << [00:04:00.293,426] [0m<inf> event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, GNSS)[0m
2021-07-13T16:39:00.134Z DEBUG modem << [00:04:00.303,741] [1;33m<wrn> gps_module: GPS search already active and will not be restarted[0m
2021-07-13T16:39:00.134Z DEBUG modem << [00:04:00.312,591] [1;33m<wrn> gps_module: Try setting a sample/publication interval greater[0m
2021-07-13T16:39:00.135Z DEBUG modem << [00:04:00.321,319] [1;33m<wrn> gps_module: than the GPS search timeout.[0m
2021-07-13T16:39:00.153Z DEBUG modem << [00:04:00.331,390] [1;31m<err> modem_info_params: Link data not obtained: 9 -134[0m
2021-07-13T16:39:00.155Z DEBUG modem << [00:04:00.340,728] [0m<inf> event_manager: SENSOR_EVT_ENVIRONMENTAL_DATA_READY[0m
2021-07-13T16:39:00.158Z DEBUG modem << [00:04:00.348,510] [1;31m<err> modem_info_params: Link data not obtained: 5 -22[0m
2021-07-13T16:39:00.204Z DEBUG modem << [00:04:00.361,450] [1;31m<err> modem_info_params: Link data not obtained: 21 -134[0m
2021-07-13T16:39:00.205Z DEBUG modem << [00:04:00.370,025] [1;31m<err> modem_info_params: Link data not obtained: 20 -22[0m
2021-07-13T16:39:00.206Z DEBUG modem << [00:04:00.377,655] [1;31m<err> modem_info_params: Network data not obtained: -312[0m
2021-07-13T16:39:00.208Z DEBUG modem << [00:04:00.385,406] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m
2021-07-13T16:39:00.210Z DEBUG modem << [00:04:00.393,005] [0m<inf> event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_NOT_READY[0m
2021-07-13T16:39:00.213Z DEBUG modem << [00:04:00.403,533] [1;31m<err> modem_info_params: Link data not obtained: 9 -134[0m
2021-07-13T16:39:00.244Z DEBUG modem << [00:04:00.412,811] [1;31m<err> modem_info_params: Link data not obtained: 5 -22[0m
2021-07-13T16:39:00.269Z DEBUG modem << [00:04:00.425,659] [1;31m<err> modem_info_params: Link data not obtained: 21 -134[0m
2021-07-13T16:39:00.270Z DEBUG modem << [00:04:00.434,143] [1;31m<err> modem_info_params: Link data not obtained: 20 -22[0m
2021-07-13T16:39:00.271Z DEBUG modem << [00:04:00.441,772] [1;31m<err> modem_info_params: Network data not obtained: -312[0m
2021-07-13T16:39:00.272Z DEBUG modem << [00:04:00.449,523] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m
2021-07-13T16:39:00.273Z DEBUG modem << [00:04:00.457,122] [0m<inf> event_manager: MODEM_EVT_BATTERY_DATA_NOT_READY[0m
2021-07-13T16:40:15.138Z DEBUG modem << [00:05:15.329,589] [0m<inf> event_manager: DATA_EVT_DATA_READY[0m
2021-07-13T16:40:54.592Z DEBUG modem << [00:05:54.772,125] [0m<inf> event_manager: GPS_EVT_TIMEOUT[0m
2021-07-13T16:40:54.594Z DEBUG modem << [00:05:54.778,137] [0m<inf> event_manager: GPS_EVT_INACTIVE[0m
2021-07-13T16:40:54.596Z DEBUG modem << [00:05:54.784,362] [0m<inf> event_manager: DATA_EVT_DATA_READY[0m
2021-07-13T16:41:00.105Z DEBUG modem << [00:06:00.286,743] [0m<inf> event_manager: APP_EVT_DATA_GET_ALL[0m
2021-07-13T16:41:00.107Z DEBUG modem << [00:06:00.293,518] [0m<inf> event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, GNSS)[0m
2021-07-13T16:41:00.163Z DEBUG modem << [00:06:00.355,865] [0m<inf> event_manager: GPS_EVT_ACTIVE[0m
2021-07-13T16:41:00.205Z DEBUG modem << [00:06:00.365,112] [1;31m<err> modem_info_params: Link data not obtained: 9 -134[0m
2021-07-13T16:41:00.208Z DEBUG modem << [00:06:00.374,359] [0m<inf> event_manager: SENSOR_EVT_ENVIRONMENTAL_DATA_READY[0m
2021-07-13T16:41:00.209Z DEBUG modem << [00:06:00.382,171] [1;31m<err> modem_info_params: Link data not obtained: 5 -22[0m
2021-07-13T16:41:00.210Z DEBUG modem << [00:06:00.390,441] [1;31m<err> modem_info_params: Link data not obtained: 8 -22[0m
2021-07-13T16:41:00.229Z DEBUG modem << [00:06:00.398,803] [1;31m<err> modem_info_params: Link data not obtained: 3 -22[0m
2021-07-13T16:41:00.255Z DEBUG modem << [00:06:00.410,064] [1;31m<err> modem_info_params: Link data not obtained: 21 -134[0m
2021-07-13T16:41:00.256Z DEBUG modem << [00:06:00.418,548] [1;31m<err> modem_info_params: Link data not obtained: 20 -22[0m
2021-07-13T16:41:00.257Z DEBUG modem << [00:06:00.426,177] [1;31m<err> modem_info_params: Network data not obtained: -356[0m
2021-07-13T16:41:00.258Z DEBUG modem << [00:06:00.434,051] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m
2021-07-13T16:41:00.260Z DEBUG modem << [00:06:00.441,619] [0m<inf> event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_NOT_READY[0m
2021-07-13T16:41:00.263Z DEBUG modem << [00:06:00.452,270] [1;31m<err> modem_info_params: Link data not obtained: 9 -134[0m
2021-07-13T16:41:00.293Z DEBUG modem << [00:06:00.461,517] [1;31m<err> modem_info_params: Link data not obtained: 5 -22[0m
2021-07-13T16:41:00.295Z DEBUG modem << [00:06:00.469,909] [1;31m<err> modem_info_params: Link data not obtained: 8 -22[0m
2021-07-13T16:41:00.296Z DEBUG modem << [00:06:00.478,271] [1;31m<err> modem_info_params: Link data not obtained: 3 -22[0m
2021-07-13T16:41:00.330Z DEBUG modem << [00:06:00.489,410] [1;31m<err> modem_info_params: Link data not obtained: 21 -134[0m
2021-07-13T16:41:00.332Z DEBUG modem << [00:06:00.497,863] [1;31m<err> modem_info_params: Link data not obtained: 20 -22[0m
2021-07-13T16:41:00.333Z DEBUG modem << [00:06:00.505,554] [1;31m<err> modem_info_params: Network data not obtained: -356[0m
2021-07-13T16:41:00.334Z DEBUG modem << [00:06:00.513,305] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m
2021-07-13T16:41:00.335Z DEBUG modem << [00:06:00.520,904] [0m<inf> event_manager: MODEM_EVT_BATTERY_DATA_NOT_READY[0m

[Øyvind]

Thanks, this all sounds correct in regards to the SW.

 

jake11212 said:

also am currently in the South Eastern United States.  I checked connectivity for the ibasis sim cards and it said that there is coverage for the entire united states, but I also noticed that coverage for LTE-M for the thingy91 was only tested in the Western United States so I was wondering if this may potentially be a problem as well.

 This is what concerns me. Are you able to test with another SIM, other than iBasis? We have seen some networks not allowing the iBasis SIM roaming permissions. 

 

jake11212 said:

running file - thingy91_asset_tracker_v2_ltem_2021-06-28_7a076c22

 Just to verify, are you using Asset Tracker v1 or v2? If you are using v2, please see user interface description here. Can you please provide a full log output.

Here is mine right after updating the certificates and added to nRF Cloud. Currently it switches between light blue and purple:

2021-07-13T19:45:52.668Z DEBUG modem >> at+cfun=1
2021-07-13T19:45:52.713Z DEBUG modem << OK
2021-07-13T19:45:53.953Z DEBUG modem << %CESQ: 53,2,3,0
2021-07-13T19:45:53.958Z DEBUG modem << +CEREG: 2,"08FF","0209E216",7
2021-07-13T19:45:53.960Z DEBUG modem << [00:02:30.483,215] [0m<inf> event_manager: MODEM_EVT_LTE_DISCONNECTED[0m
2021-07-13T19:45:53.960Z DEBUG modem << [00:02:30.490,478] [0m<inf> event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2021-07-13T19:45:53.989Z DEBUG modem << +CSCON: 1
2021-07-13T19:45:53.995Z DEBUG modem << %CESQ: 59,2,15,2
2021-07-13T19:45:55.085Z DEBUG modem << +CEREG: 5,"08FF","0209E216",7,,,"11100000","11100000"
2021-07-13T19:45:55.087Z DEBUG modem << [00:02:31.604,339] [0m<inf> event_manager: MODEM_EVT_LTE_CONNECTED[0m
2021-07-13T19:45:55.088Z DEBUG modem << [00:02:31.611,328] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
2021-07-13T19:45:55.089Z DEBUG modem << [00:02:31.619,476] [1;33m<wrn> cloud_module: New connection attempt in 32 seconds if not successful[0m
2021-07-13T19:45:55.090Z DEBUG modem >> AT+COPS=3,2
2021-07-13T19:45:55.095Z DEBUG modem << OK
2021-07-13T19:45:55.099Z DEBUG modem >> AT+COPS?
2021-07-13T19:45:55.109Z DEBUG modem << +COPS: 0,2,"24202",7
2021-07-13T19:45:55.110Z DEBUG modem << OK
2021-07-13T19:45:55.113Z DEBUG modem >> AT%XCBAND
2021-07-13T19:45:55.122Z DEBUG modem << %XCBAND: 20
2021-07-13T19:45:55.122Z DEBUG modem << OK
2021-07-13T19:45:55.124Z DEBUG modem >> AT+CGDCONT?
2021-07-13T19:45:55.139Z DEBUG modem << +CGDCONT: 0,"IP","ibasis.iot","10.160.39.153",0,0
2021-07-13T19:45:55.140Z DEBUG modem << OK
2021-07-13T19:45:55.142Z DEBUG modem >> AT+CGACT?
2021-07-13T19:45:55.149Z DEBUG modem << +CGACT: 0,1
2021-07-13T19:45:55.150Z DEBUG modem << OK
2021-07-13T19:45:58.102Z DEBUG modem << [00:02:34.638,854] [0m<inf> nrf_cloud_transport: Using socket send timeout of 60 seconds[0m
2021-07-13T19:45:58.387Z DEBUG modem << [00:02:34.926,483] [0m<inf> event_manager: CLOUD_EVT_DISCONNECTED[0m
2021-07-13T19:46:02.103Z DEBUG modem << +CSCON: 0
2021-07-13T19:46:02.246Z DEBUG modem << %CESQ: 59,2,10,1
2021-07-13T19:46:16.966Z DEBUG modem << %CESQ: 60,3,15,2
2021-07-13T19:46:27.103Z DEBUG modem << [00:03:03.628,875] [0m<inf> event_manager: CLOUD_EVT_CONNECTION_TIMEOUT[0m
2021-07-13T19:46:27.104Z DEBUG modem << [00:03:03.636,077] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
2021-07-13T19:46:27.114Z DEBUG modem << [00:03:03.644,256] [1;33m<wrn> cloud_module: New connection attempt in 64 seconds if not successful[0m
2021-07-13T19:46:27.209Z DEBUG modem << +CSCON: 1
2021-07-13T19:46:30.591Z DEBUG modem << [00:03:07.129,058] [0m<inf> nrf_cloud_transport: Using socket send timeout of 60 seconds[0m
2021-07-13T19:46:31.434Z DEBUG modem << [00:03:07.960,144] [1;33m<wrn> nrf_cloud_integration: NRF_CLOUD_EVT_USER_ASSOCIATION_REQUEST[0m
2021-07-13T19:46:31.434Z DEBUG modem << [00:03:07.968,780] [1;33m<wrn> nrf_cloud_integration: Add the device to nRF Cloud and wait for it to reconnect[0m
2021-07-13T19:46:35.644Z DEBUG modem << +CSCON: 0
2021-07-13T19:46:36.166Z DEBUG modem << %CESQ: 60,3,10,1
2021-07-13T19:46:59.206Z DEBUG modem << %CESQ: 55,2,6,0
2021-07-13T19:47:04.449Z DEBUG modem << +CSCON: 1
2021-07-13T19:47:04.457Z DEBUG modem << %CESQ: 59,2,14,2
2021-07-13T19:47:05.384Z DEBUG modem << [00:03:41.924,774] [0m<inf> event_manager: CLOUD_EVT_DISCONNECTED[0m
2021-07-13T19:47:09.895Z DEBUG modem << +CSCON: 0
2021-07-13T19:47:23.750Z DEBUG modem << [00:04:00.280,670] [0m<inf> event_manager: APP_EVT_DATA_GET_ALL[0m
2021-07-13T19:47:23.751Z DEBUG modem << [00:04:00.287,384] [0m<inf> event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, GNSS)[0m
2021-07-13T19:47:23.771Z DEBUG modem << [00:04:00.312,561] [0m<inf> event_manager: GPS_EVT_ACTIVE[0m
2021-07-13T19:47:23.781Z DEBUG modem << [00:04:00.321,197] [0m<inf> event_manager: SENSOR_EVT_ENVIRONMENTAL_DATA_READY[0m
2021-07-13T19:47:23.820Z DEBUG modem << [00:04:00.360,412] [0m<inf> event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_READY[0m
2021-07-13T19:47:23.860Z DEBUG modem << [00:04:00.401,306] [0m<inf> event_manager: MODEM_EVT_BATTERY_DATA_READY[0m
2021-07-13T19:47:31.131Z DEBUG modem << [00:04:07.653,778] [0m<inf> event_manager: CLOUD_EVT_CONNECTION_TIMEOUT[0m
2021-07-13T19:47:31.131Z DEBUG modem << [00:04:07.660,949] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
2021-07-13T19:47:31.132Z DEBUG modem << [00:04:07.669,097] [1;33m<wrn> cloud_module: New connection attempt in 128 seconds if not successful[0m
2021-07-13T19:47:31.197Z DEBUG modem << +CSCON: 1
2021-07-13T19:47:34.512Z DEBUG modem << [00:04:11.051,147] [0m<inf> nrf_cloud_transport: Using socket send timeout of 60 seconds[0m
2021-07-13T19:47:36.135Z DEBUG modem << [00:04:12.676,971] [0m<inf> event_manager: CLOUD_EVT_CONNECTED[0m
2021-07-13T19:47:36.521Z DEBUG modem << [00:04:13.027,130] [0m<inf> event_manager: DATA_EVT_DATE_TIME_OBTAINED[0m
2021-07-13T19:47:36.522Z DEBUG modem << [00:04:13.034,301] [0m<inf> event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, GNSS)[0m
2021-07-13T19:47:36.523Z DEBUG modem << [00:04:13.044,525] [1;33m<wrn> gps_module: GPS search already active and will not be restarted[0m
2021-07-13T19:47:36.523Z DEBUG modem << [00:04:13.053,283] [1;33m<wrn> gps_module: Try setting a sample/publication interval greater[0m
2021-07-13T19:47:36.523Z DEBUG modem << [00:04:13.061,920] [1;33m<wrn> gps_module: than the GPS search timeout.[0m
2021-07-13T19:47:36.533Z DEBUG modem << [00:04:13.072,509] [0m<inf> event_manager: SENSOR_EVT_ENVIRONMENTAL_DATA_READY[0m
2021-07-13T19:47:36.574Z DEBUG modem << [00:04:13.114,135] [0m<inf> event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_NOT_READY[0m
2021-07-13T19:47:36.616Z DEBUG modem << [00:04:13.157,623] [0m<inf> event_manager: MODEM_EVT_BATTERY_DATA_READY[0m
2021-07-13T19:47:40.399Z DEBUG modem << +CSCON: 0
2021-07-13T19:47:52.554Z DEBUG modem << %CESQ: 56,2,5,0
2021-07-13T19:47:52.966Z DEBUG modem << %CESQ: 61,3,18,2
2021-07-13T19:47:55.526Z DEBUG modem << %CESQ: 61,3,13,1
2021-07-13T19:48:43.790Z DEBUG modem << [00:05:20.322,265] [0m<inf> event_manager: GPS_EVT_TIMEOUT[0m
2021-07-13T19:48:43.791Z DEBUG modem << [00:05:20.328,216] [0m<inf> event_manager: GPS_EVT_INACTIVE[0m
2021-07-13T19:48:43.792Z DEBUG modem << [00:05:20.334,350] [0m<inf> event_manager: DATA_EVT_DATA_READY[0m
2021-07-13T19:48:43.802Z DEBUG modem << [00:05:20.346,954] [0m<inf> event_manager: DATA_EVT_DATA_SEND[0m
2021-07-13T19:48:43.819Z DEBUG modem << [00:05:20.362,762] [0m<inf> event_manager: DATA_EVT_DATA_SEND_BATCH[0m
2021-07-13T19:48:43.845Z DEBUG modem << [00:05:20.389,465] [0m<inf> event_manager: CLOUD_EVT_DATA_ACK[0m
2021-07-13T19:48:43.853Z DEBUG modem << [00:05:20.397,766] [0m<inf> event_manager: CLOUD_EVT_DATA_ACK[0m
2021-07-13T19:48:43.918Z DEBUG modem << +CSCON: 1
2021-07-13T19:48:49.445Z DEBUG modem << +CSCON: 0
2021-07-13T19:48:51.206Z DEBUG modem << %CESQ: 61,3,18,2
2021-07-13T19:48:53.766Z DEBUG modem << %CESQ: 61,3,13,1
2021-07-13T19:48:54.169Z DEBUG modem << +CSCON: 1
2021-07-13T19:48:59.712Z DEBUG modem << +CSCON: 0
2021-07-13T19:49:05.285Z DEBUG modem << %CESQ: 61,3,19,2
2021-07-13T19:49:07.205Z DEBUG modem << %CESQ: 62,3,14,2
2021-07-13T19:49:23.746Z DEBUG modem << [00:06:00.280,670] [0m<inf> event_manager: APP_EVT_DATA_GET_ALL[0m
2021-07-13T19:49:23.747Z DEBUG modem << [00:06:00.287,353] [0m<inf> event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, GNSS)[0m
2021-07-13T19:49:23.797Z DEBUG modem << [00:06:00.343,566] [0m<inf> event_manager: GPS_EVT_ACTIVE[0m
2021-07-13T19:49:23.809Z DEBUG modem << [00:06:00.353,271] [0m<inf> event_manager: SENSOR_EVT_ENVIRONMENTAL_DATA_READY[0m
2021-07-13T19:49:23.849Z DEBUG modem << [00:06:00.392,761] [0m<inf> event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_READY[0m
2021-07-13T19:49:23.892Z DEBUG modem << [00:06:00.437,133] [0m<inf> event_manager: MODEM_EVT_BATTERY_DATA_READY[0m

[jake11212]

Øyvind said:

 This is what concerns me. Are you able to test with another SIM, other than iBasis? We have seen some networks not allowing the iBasis SIM roaming permissions. 

I can't test another sim card for now, but in the LTE link monitor it says that verizon and AT&T are available albeit with only one bar of signal strength.  I can't test another SIM in the immediate future and if this is a likely source of the problem I'm probably better off waiting as I'm headed back to central USA in a few weeks.

Øyvind said:

Just to verify, are you using Asset Tracker v1 or v2? If you are using v2, please see user interface description here. Can you please provide a full log output.

I have tried a few different programs but am currently using asset tracker v1.  I will send you my full logs in a private message as the IMEI and SIM info are in it.

[Øyvind]

Thanks! Looking at the log I can confirm what I thought. The modem/SIM is rejected from the network.

+CEREG: 2,"7BE6","01250B01",7,0,11

+CNEC_EMM: 15

From CEREG in AT commands reference guide we see 11 in the reject cause position, from 3GPP 24.301 Annex A we find

reject cause #11 – PLMN not allowed
This EMM cause is sent to the UE if it requests service, or if the network initiates a detach request, in a PLMN
where the UE, by subscription or due to operator determined barring, is not allowed to operate.

And from Table 9.9.3.9.1: EMM cause information element 15 - No Suitable Cells In tracking area

[jake11212]

okay great, thanks for figuring it out.  Do you know of any other common sim cards that can be used with the thingy91?  Or is there a map that includes different coverage for different sim cards?