nRF Cloud - Not able to connct to it.

[dival]

Hi,

I'm currently using an nRF9160DK with an NB-IoT sim, and the problem I am currently having is that I cannot establish a connection with the nRF cloud. 

What have I tried?

1. I tried the following: https://infocenter.nordicsemi.com/pdf/nRF9160_DK_Getting_Started_Guide_v1.1.pdf section "Provisioning the nRF Connect for Cloud certificate" by opening the nRF connect, deselecting automatic requests, removed the sim card, entering AT+CFUN?4 to put the modem to offline state (and checked the state of the modem to ensure that it is off). I have loaded the JSON certificate and ensured that the security tag is set to "16842753" and then updated the certificate. The log message states "certificate updated completed.

2. Then I tried to power cycle the nRF9160DK and then inserted the SIM card to let the automatic requests run. It seems like it tries to connect to the nRF cloud but fails. I am not quite sure why this happens.

3. I also tried to add the LTE device to the nRF connection, but this was not working

The image that I have flashed to the board is nrf9160dk_asset_tracker_v2_nbiot_2022-06-02_880c82db.

Additional things that I have tried

1. The SIM card supports NB-IoT, and there is coverage within my area.

3. I have tried another NB-IoT-supported IoT device to test out the sim card by doing a ping test to ensure that the connectivity is not the problem, and this seems to work fine. 

4. It seems like the nRF9160DK is able to connect to the eNB, and connect to the network, so that is not the problem. It seems to receive an IP address successfully, so this is not a problem.

3. I have tried to re-flash the nRF9160DK 

[dival]

Hi,

I have updated the topic. I will post more screenshots when it comes to the logs.

[Øyvind]

Hello, 

The official Getting Started guide can be found here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_nrf9160_gs.html#getting-started-with-nrf9160-dk

What version of the nRF9160 Development Kit are you running? When generating new certificates, what device ID did you enter? 

You can test the connection to the LTE network by using the AT client, found in the precompiled package as well.

Please provide full log output from the application you are running on your device, as screenshots provide too little information. You can find the log output in the LTE link monitor on the bottom.

Kind regards,
Øyvind

[dival]

Hi again,

Please look at the log that I have provided above.

Regarding the JITP certificate, 

What I did was:

1) From the nRF cloud, I went to "provisioned devices" and created a JITP certificate.

2) In the link monitor I unticked the automatic update

3) In the certificate manager, when I uploaded it - I checked if it was successful, which it was.

4) I power-booted the nRF91

[dival]

Here are some more logs.

2022-11-10T17:17:06.237Z DEBUG modem << %CESQ: 87,4,20,2
2022-11-10T17:17:06.258Z DEBUG modem << +CEREG: 1,"0007","00000002",9,,,"11100000","11100000"
2022-11-10T17:17:06.266Z DEBUG modem << +CIND: "service",1
2022-11-10T17:17:06.275Z DEBUG modem >> AT+COPS=3,2
2022-11-10T17:17:06.285Z DEBUG modem << OK
2022-11-10T17:17:06.290Z DEBUG modem >> AT+COPS?
2022-11-10T17:17:06.303Z DEBUG modem << +COPS: 0,2,"99970",9
2022-11-10T17:17:06.305Z DEBUG modem << OK
2022-11-10T17:17:06.320Z DEBUG modem >> AT%XCBAND
2022-11-10T17:17:06.324Z DEBUG modem << %CESQ: 88,4,29,4
2022-11-10T17:17:06.340Z DEBUG modem << %XCBAND: 4
2022-11-10T17:17:06.342Z DEBUG modem << OK
2022-11-10T17:17:06.368Z DEBUG modem >> AT+CGDCONT?
2022-11-10T17:17:06.387Z DEBUG modem << +CGDCONT: 0,"IP","testing123","172.16.0.3",0,0
2022-11-10T17:17:06.391Z DEBUG modem << OK
2022-11-10T17:17:06.408Z DEBUG modem >> AT+CGACT?
2022-11-10T17:17:06.423Z DEBUG modem << +CGACT: 0,1
2022-11-10T17:17:06.430Z DEBUG modem << OK
2022-11-10T17:17:07.252Z DEBUG modem << [00:13:51.789,611] [0m<inf> app_event_manager: MODEM_EVT_LTE_CONNECTED[0m
2022-11-10T17:17:07.260Z DEBUG modem << [00:13:51.790,252] [0m<inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2022-11-10T17:17:07.271Z DEBUG modem << [00:13:51.791,046] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
2022-11-10T17:17:07.276Z DEBUG modem << [00:13:51.791,046] [1;33m<wrn> cloud_module: New connection attempt in 32 seconds if not successful[0m
2022-11-10T17:17:07.287Z DEBUG modem << [00:13:51.791,229] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTING[0m
2022-11-10T17:17:09.079Z DEBUG modem << +CSCON: 1
2022-11-10T17:17:10.294Z DEBUG modem << %CESQ: 89,4,34,4
2022-11-10T17:17:13.895Z DEBUG modem << %CESQ: 89,4,29,4
2022-11-10T17:17:16.014Z DEBUG modem << [00:14:01%NCELLMEAS: 0,"00000002","99970","0007",80,2391,99,89,29,831331,838215
2022-11-10T17:17:16.021Z DEBUG modem << .525,085] [0m<inf> app_event_manager: APP_EVT_DATA_GET_ALL[0m
2022-11-10T17:17:16.040Z DEBUG modem << [00:14:01.525,726] [0m<inf> app_event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, NEIGHBOR_CELLS, GNSS)[0m
2022-11-10T17:17:16.044Z DEBUG modem << [00:14:01.531,066] [0m<inf> app_event_manager: GNSS_EVT_ACTIVE[0m
2022-11-10T17:17:16.047Z DEBUG modem << [00:14:01.531,829] [0m<inf> app_event_manager: SENSOR_EVT_ENVIRONMENTAL_NOT_SUPPORTED[0m
2022-11-10T17:17:16.057Z DEBUG modem << [00:14:01.540,710] [1;31m<err> modem_info_params: Link data not obtained: 20 -5[0m
2022-11-10T17:17:16.062Z DEBUG modem << [00:14:01.540,740] [1;31m<err> modem_info_params: Network data not obtained: -5[0m
2022-11-10T17:17:16.073Z DEBUG modem << [00:14:01.540,740] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m
2022-11-10T17:17:16.078Z DEBUG modem << [00:14:01.540,832] [0m<inf> app_event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_NOT_READY[0m
2022-11-10T17:17:16.091Z DEBUG modem << [00:14:01.550,598] [1;31m<err> modem_info_params: Link data not obtained: 20 -5[0m
2022-11-10T17:17:16.093Z DEBUG modem << [00:14:01.550,628] [1;31m<err> modem_info_params: Network data not obtained: -5[0m
2022-11-10T17:17:16.108Z DEBUG modem << [00:14:01.550,659] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m
2022-11-10T17:17:16.110Z DEBUG modem << [00:14:01.550,750] [0m<inf> app_event_manager: MODEM_EVT_BATTERY_DATA_NOT_READY[0m
2022-11-10T17:17:16.124Z DEBUG modem << [00:14:01.559,539] [0m<inf> app_event_manager: MODEM_EVT_NEIGHBOR_CELLS_DATA_READY[0m
2022-11-10T17:17:19.339Z DEBUG modem << +CSCON: 0
2022-11-10T17:17:24.797Z DEBUG modem << %CESQ: 255,0,255,0
2022-11-10T17:17:24.808Z DEBUG modem << +CEREG: 2
2022-11-10T17:17:24.815Z DEBUG modem << +CIND: "service",0
2022-11-10T17:17:25.807Z DEBUG modem << [00:14:10.345,031] [0m<inf> app_event_manager: MODEM_EVT_LTE_DISCONNECTED[0m
2022-11-10T17:17:25.814Z DEBUG modem << [00:14:10.345,672] [0m<inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2022-11-10T17:17:25.831Z DEBUG modem << [00:14:10.346,496] [1;31m<err> nrf_cloud_integration: nrf_cloud_disconnect, error: -13[0m
2022-11-10T17:17:33.955Z DEBUG modem >> AT+CESQ
2022-11-10T17:17:33.968Z DEBUG modem << +CESQ: 99,99,255,255,255,255
2022-11-10T17:17:33.970Z DEBUG modem << OK
2022-11-10T17:17:36.956Z DEBUG modem << %CESQ: 87,4,22,3
2022-11-10T17:17:36.962Z DEBUG modem << +CEREG: 1,"0007","00000002",9,,,"11100000","11100000"
2022-11-10T17:17:36.989Z DEBUG modem >> AT+COPS=3,2
2022-11-10T17:17:37.001Z DEBUG modem << +CIND: "service",1
2022-11-10T17:17:37.019Z DEBUG modem << OK
2022-11-10T17:17:37.022Z DEBUG modem >> AT+COPS?
2022-11-10T17:17:37.035Z DEBUG modem << +COPS: 0,2,"99970",9
2022-11-10T17:17:37.038Z DEBUG modem << OK
2022-11-10T17:17:37.041Z DEBUG modem << %CESQ: 88,4,29,4
2022-11-10T17:17:37.054Z DEBUG modem >> AT%XCBAND
2022-11-10T17:17:37.071Z DEBUG modem << %XCBAND: 4
2022-11-10T17:17:37.073Z DEBUG modem << OK
2022-11-10T17:17:37.085Z DEBUG modem >> AT+CGDCONT?
2022-11-10T17:17:37.103Z DEBUG modem << +CGDCONT: 0,"IP","testing123","172.16.0.3",0,0
2022-11-10T17:17:37.104Z DEBUG modem << OK
2022-11-10T17:17:37.112Z DEBUG modem >> AT+CGACT?
2022-11-10T17:17:37.124Z DEBUG modem << +CGACT: 0,1
2022-11-10T17:17:37.126Z DEBUG modem << OK
2022-11-10T17:17:37.971Z DEBUG modem << [00:14:22.510,345] [0m<inf> app_event_manager: MODEM_EVT_LTE_CONNECTED[0m
2022-11-10T17:17:37.979Z DEBUG modem << [00:14:22.510,986] [0m<inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2022-11-10T17:17:37.989Z DEBUG modem << [00:14:22.511,810] [1;31m<err> nrf_cloud_integration: nrf_cloud_connect, error: -11[0m
2022-11-10T17:17:37.994Z DEBUG modem << [00:14:22.511,810] [1;31m<err> cloud_module: cloud_connect failed, error: -11[0m
2022-11-10T17:17:38.007Z DEBUG modem << [00:14:22.511,840] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
2022-11-10T17:17:38.011Z DEBUG modem << [00:14:22.511,840] [1;33m<wrn> cloud_module: New connection attempt in 32 seconds if not successful[0m
2022-11-10T17:17:39.798Z DEBUG modem << +CSCON: 1
2022-11-10T17:17:42.255Z DEBUG modem << [00:14:26.794,403] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTING[0m
2022-11-10T17:17:42.612Z DEBUG modem << %CESQ: 89,4,34,4
2022-11-10T17:18:03.959Z DEBUG modem >> AT+CESQ
2022-11-10T17:18:03.974Z DEBUG modem << +CESQ: 99,99,255,255,34,89
2022-11-10T17:18:03.978Z DEBUG modem << OK
2022-11-10T17:18:09.972Z DEBUG modem << [00:14:54.512,023] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTION_TIMEOUT[0m
2022-11-10T17:18:09.985Z DEBUG modem << [00:14:54.512,542] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
2022-11-10T17:18:10.001Z DEBUG modem << [00:14:54.512,573] [1;33m<wrn> cloud_module: New connection attempt in 64 seconds if not successful[0m
2022-11-10T17:18:10.003Z DEBUG modem << [00:14:54.512,725] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTING[0m
2022-11-10T17:18:17.257Z DEBUG modem << [00:15:01.797,882] [1;33m<wrn> date_time: getaddrinfo, error: -11[0m
2022-11-10T17:18:20.430Z DEBUG modem << %CESQ: 89,4,29,4
2022-11-10T17:18:21.030Z DEBUG modem << %CESQ: 89,4,34,4
2022-11-10T17:18:31.991Z DEBUG modem << [00:15:16.532,318] [0m<inf> app_event_manager: DATA_EVT_DATA_READY[0m
2022-11-10T17:18:33.966Z DEBUG modem >> AT+CESQ
2022-11-10T17:18:33.973Z DEBUG modem << +CESQ: 99,99,255,255,34,89
2022-11-10T17:18:33.977Z DEBUG modem << OK
2022-11-10T17:18:52.258Z DEBUG modem << [00:15:36.801,025] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTING[0m
2022-11-10T17:19:03.959Z DEBUG modem >> AT+CESQ
2022-11-10T17:19:03.977Z DEBUG modem << +CESQ: 99,99,255,255,34,87
2022-11-10T17:19:03.979Z DEBUG modem << OK
2022-11-10T17:19:13.971Z DEBUG modem << [00:15:58.512,725] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTION_TIMEOUT[0m
2022-11-10T17:19:13.988Z DEBUG modem << [00:15:58.513,244] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
2022-11-10T17:19:13.990Z DEBUG modem << [00:15:58.513,275] [1;33m<wrn> cloud_module: New connection attempt in 128 seconds if not successful[0m
2022-11-10T17:19:13.995Z DEBUG modem << [00:15:58.513,427] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTING[0m
2022-11-10T17:19:16.004Z DEBUG modem << [00:16:01.%NCELLMEAS: 0,"00000002","99970","0007",80,2391,99,88,37,960931,957598
2022-11-10T17:19:16.015Z DEBUG modem << 525,085] [0m<inf> app_event_manager: APP_EVT_DATA_GET_ALL[0m
2022-11-10T17:19:16.029Z DEBUG modem << [00:16:01.525,726] [0m<inf> app_event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, NEIGHBOR_CELLS, GNSS)[0m
2022-11-10T17:19:16.033Z DEBUG modem << [00:16:01.525,787] [1;33m<wrn> gnss_module: GNSS search already active and will not be restarted[0m
2022-11-10T17:19:16.046Z DEBUG modem << [00:16:01.525,817] [1;33m<wrn> gnss_module: Try setting a sample/publication interval greater[0m
2022-11-10T17:19:16.048Z DEBUG modem << [00:16:01.525,817] [1;33m<wrn> gnss_module: than the GNSS search timeout.[0m
2022-11-10T17:19:16.066Z DEBUG modem << [00:16:01.526,641] [0m<inf> app_event_manager: SENSOR_EVT_ENVIRONMENTAL_NOT_SUPPORTED[0m
2022-11-10T17:19:16.067Z DEBUG modem << [00:16:01.535,614] [1;31m<err> modem_info_params: Link data not obtained: 20 -5[0m
2022-11-10T17:19:16.081Z DEBUG modem << [00:16:01.535,644] [1;31m<err> modem_info_params: Network data not obtained: -5[0m
2022-11-10T17:19:16.083Z DEBUG modem << [00:16:01.535,644] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m
2022-11-10T17:19:16.087Z DEBUG modem << [00:16:01.535,736] [0m<inf> app_event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_NOT_READY[0m
2022-11-10T17:19:16.096Z DEBUG modem << [00:16:01.545,379] [1;31m<err> modem_info_params: Link data not obtained: 20 -5[0m
2022-11-10T17:19:16.102Z DEBUG modem << [00:16:01.545,440] [1;31m<err> modem_info_params: Network data not obtained: -5[0m
2022-11-10T17:19:16.112Z DEBUG modem << [00:16:01.545,440] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m
2022-11-10T17:19:16.118Z DEBUG modem << [00:16:01.545,532] [0m<inf> app_event_manager: MODEM_EVT_BATTERY_DATA_NOT_READY[0m
2022-11-10T17:19:16.129Z DEBUG modem << [00:16:01.554,473] [0m<inf> app_event_manager: MODEM_EVT_NEIGHBOR_CELLS_DATA_READY[0m
2022-11-10T17:19:27.262Z DEBUG modem << [00:16:11.804,779] [1;33m<wrn> date_time: getaddrinfo, error: -11[0m
2022-11-10T17:19:27.276Z DEBUG modem << [00:16:11.804,809] [1;33m<wrn> date_time: Did not get time from any NTP server[0m
2022-11-10T17:19:33.961Z DEBUG modem >> AT+CESQ
2022-11-10T17:19:33.977Z DEBUG modem << +CESQ: 99,99,255,255,34,90
2022-11-10T17:19:33.981Z DEBUG modem << OK
2022-11-10T17:20:02.263Z DEBUG modem << [00:16:46.807,983] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTING[0m
2022-11-10T17:20:03.957Z DEBUG modem >> AT+CESQ
2022-11-10T17:20:03.967Z DEBUG modem << +CESQ: 99,99,255,255,34,89
2022-11-10T17:20:03.970Z DEBUG modem << OK
2022-11-10T17:20:31.981Z DEBUG modem << [00:17:16.527,221] [0m<inf> app_event_manager: DATA_EVT_DATA_READY[0m
2022-11-10T17:20:33.965Z DEBUG modem >> AT+CESQ
2022-11-10T17:20:33.974Z DEBUG modem << +CESQ: 99,99,255,255,32,90
2022-11-10T17:20:33.975Z DEBUG modem << OK
2022-11-10T17:20:37.265Z DEBUG modem << [00:17:21.811,859] [1;33m<wrn> date_time: getaddrinfo, error: -11[0m
2022-11-10T17:20:49.243Z DEBUG modem << %CESQ: 90,4,29,4
2022-11-10T17:20:50.842Z DEBUG modem << %CESQ: 90,4,34,4
2022-11-10T17:21:03.957Z DEBUG modem >> AT+CESQ
2022-11-10T17:21:03.972Z DEBUG modem << +CESQ: 99,99,255,255,34,90
2022-11-10T17:21:03.974Z DEBUG modem << OK
2022-11-10T17:21:12.266Z DEBUG modem << [00:17:56.814,117] [1;33m<wrn> date_time: getaddrinfo, error: -11[0m
2022-11-10T17:21:12.278Z DEBUG modem << [00:17:56.814,147] [1;33m<wrn> date_time: Did not get time from any NTP server[0m
2022-11-10T17:21:15.998Z DEBUG modem << [00:18:01.5%NCELLMEAS: 0,"00000002","99970","0007",80,2391,99,90,36,1080931,1070878
2022-11-10T17:21:16.009Z DEBUG modem << 25,085] [0m<inf> app_event_manager: APP_EVT_DATA_GET_ALL[0m
2022-11-10T17:21:16.031Z DEBUG modem << [00:18:01.525,726] [0m<inf> app_event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, NEIGHBOR_CELLS, GNSS)[0m
2022-11-10T17:21:16.032Z DEBUG modem << [00:18:01.525,787] [1;33m<wrn> gnss_module: GNSS search already active and will not be restarted[0m
2022-11-10T17:21:16.034Z DEBUG modem << [00:18:01.525,817] [1;33m<wrn> gnss_module: Try setting a sample/publication interval greater[0m
2022-11-10T17:21:16.042Z DEBUG modem << [00:18:01.525,817] [1;33m<wrn> gnss_module: than the GNSS search timeout.[0m
2022-11-10T17:21:16.056Z DEBUG modem << [00:18:01.526,702] [0m<inf> app_event_manager: SENSOR_EVT_ENVIRONMENTAL_NOT_SUPPORTED[0m
2022-11-10T17:21:16.058Z DEBUG modem << [00:18:01.535,217] [1;31m<err> modem_info_params: Link data not obtained: 20 -5[0m
2022-11-10T17:21:16.074Z DEBUG modem << [00:18:01.535,278] [1;31m<err> modem_info_params: Network data not obtained: -5[0m
2022-11-10T17:21:16.076Z DEBUG modem << [00:18:01.535,278] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m
2022-11-10T17:21:16.091Z DEBUG modem << [00:18:01.535,339] [0m<inf> app_event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_NOT_READY[0m
2022-11-10T17:21:16.094Z DEBUG modem << [00:18:01.544,342] [1;31m<err> modem_info_params: Link data not obtained: 20 -5[0m
2022-11-10T17:21:16.105Z DEBUG modem << [00:18:01.544,403] [1;31m<err> modem_info_params: Network data not obtained: -5[0m
2022-11-10T17:21:16.107Z DEBUG modem << [00:18:01.544,433] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m
2022-11-10T17:21:16.111Z DEBUG modem << [00:18:01.544,494] [0m<inf> app_event_manager: MODEM_EVT_BATTERY_DATA_NOT_READY[0m
2022-11-10T17:21:16.123Z DEBUG modem << [00:18:01.553,558] [0m<inf> app_event_manager: MODEM_EVT_NEIGHBOR_CELLS_DATA_READY[0m
2022-11-10T17:21:21.965Z DEBUG modem << [00:18:06.513,427] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTION_TIMEOUT[0m
2022-11-10T17:21:21.974Z DEBUG modem << [00:18:06.513,946] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
2022-11-10T17:21:21.990Z DEBUG modem << [00:18:06.513,977] [1;33m<wrn> cloud_module: New connection attempt in 256 seconds if not successful[0m
2022-11-10T17:21:21.993Z DEBUG modem << [00:18:06.514,129] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTING[0m
2022-11-10T17:21:25.042Z DEBUG modem << %CESQ: 90,4,29,4
2022-11-10T17:21:26.242Z DEBUG modem << %CESQ: 90,4,34,4
2022-11-10T17:21:33.969Z DEBUG modem >> AT+CESQ
2022-11-10T17:21:33.979Z DEBUG modem << +CESQ: 99,99,255,255,33,90
2022-11-10T17:21:33.981Z DEBUG modem << OK
2022-11-10T17:21:56.968Z DEBUG modem << [00:18:41.516,906] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTING[0m
2022-11-10T17:22:03.964Z DEBUG modem >> AT+CESQ
2022-11-10T17:22:03.986Z DEBUG modem << +CESQ: 99,99,255,255,34,88
2022-11-10T17:22:03.989Z DEBUG modem << OK
2022-11-10T17:22:31.976Z DEBUG modem << [00:19:16.527,221] [0m<inf> app_event_manager: DATA_EVT_DATA_READY[0m
2022-11-10T17:22:33.972Z DEBUG modem >> AT+CESQ
2022-11-10T17:22:33.987Z DEBUG modem << +CESQ: 99,99,255,255,34,90
2022-11-10T17:22:33.989Z DEBUG modem << OK
2022-11-10T17:23:03.954Z DEBUG modem >> AT+CESQ
2022-11-10T17:23:03.971Z DEBUG modem << +CESQ: 99,99,255,255,34,91
2022-11-10T17:23:03.974Z DEBUG modem << OK
2022-11-10T17:23:15.994Z DEBUG modem << [00:20:01.5%NCELLMEAS: 0,"00000002","99970","0007",80,2391,99,91,37,1200932,1116318
2022-11-10T17:23:16.010Z DEBUG modem << 25,085] [0m<inf> app_event_manager: APP_EVT_DATA_GET_ALL[0m
2022-11-10T17:23:16.012Z DEBUG modem << [00:20:01.525,726] [0m<inf> app_event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, NEIGHBOR_CELLS, GNSS)[0m
2022-11-10T17:23:16.031Z DEBUG modem << [00:20:01.525,787] [1;33m<wrn> gnss_module: GNSS search already active and will not be restarted[0m
2022-11-10T17:23:16.034Z DEBUG modem << [00:20:01.525,817] [1;33m<wrn> gnss_module: Try setting a sample/publication interval greater[0m
2022-11-10T17:23:16.046Z DEBUG modem << [00:20:01.525,817] [1;33m<wrn> gnss_module: than the GNSS search timeout.[0m
2022-11-10T17:23:16.048Z DEBUG modem << [00:20:01.526,702] [0m<inf> app_event_manager: SENSOR_EVT_ENVIRONMENTAL_NOT_SUPPORTED[0m
2022-11-10T17:23:16.053Z DEBUG modem << [00:20:01.535,217] [1;31m<err> modem_info_params: Link data not obtained: 20 -5[0m
2022-11-10T17:23:16.066Z DEBUG modem << [00:20:01.535,247] [1;31m<err> modem_info_params: Network data not obtained: -5[0m
2022-11-10T17:23:16.068Z DEBUG modem << [00:20:01.535,247] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m
2022-11-10T17:23:16.079Z DEBUG modem << [00:20:01.535,339] [0m<inf> app_event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_NOT_READY[0m
2022-11-10T17:23:16.084Z DEBUG modem << [00:20:01.544,586] [1;31m<err> modem_info_params: Link data not obtained: 20 -5[0m
2022-11-10T17:23:16.095Z DEBUG modem << [00:20:01.544,647] [1;31m<err> modem_info_params: Network data not obtained: -5[0m
2022-11-10T17:23:16.099Z DEBUG modem << [00:20:01.544,677] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m
2022-11-10T17:23:16.112Z DEBUG modem << [00:20:01.544,738] [0m<inf> app_event_manager: MODEM_EVT_BATTERY_DATA_NOT_READY[0m
2022-11-10T17:23:16.114Z DEBUG modem << [00:20:01.553,833] [0m<inf> app_event_manager: MODEM_EVT_NEIGHBOR_CELLS_DATA_READY[0m
2022-11-10T17:23:33.957Z DEBUG modem >> AT+CESQ
2022-11-10T17:23:33.970Z DEBUG modem << +CESQ: 99,99,255,255,34,91
2022-11-10T17:23:33.972Z DEBUG modem << OK
2022-11-10T17:23:46.242Z DEBUG modem << %CESQ: 85,4,34,4
2022-11-10T17:23:51.242Z DEBUG modem << %CESQ: 90,4,34,4
2022-11-10T17:23:52.442Z DEBUG modem << %CESQ: 84,4,34,4
2022-11-10T17:23:54.442Z DEBUG modem << %CESQ: 89,4,34,4
2022-11-10T17:24:03.954Z DEBUG modem >> AT+CESQ
2022-11-10T17:24:03.959Z DEBUG modem << +CESQ: 99,99,255,255,34,88
2022-11-10T17:24:03.962Z DEBUG modem << OK

[Øyvind]

What SIM are you using? From the log there are some issues with you connection:

2022-11-10T17:19:16.067Z DEBUG modem << [00:16:01.535,614] [1;31m<err> modem_info_params: Link data not obtained: 20 -5[0m
2022-11-10T17:19:16.081Z DEBUG modem << [00:16:01.535,644] [1;31m<err> modem_info_params: Network data not obtained: -5[0m
2022-11-10T17:19:16.083Z DEBUG modem << [00:16:01.535,644] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m
2022-11-10T17:19:16.087Z DEBUG modem << [00:16:01.535,736] [0m<inf> app_event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_NOT_READY[0m
2022-11-10T17:19:16.096Z DEBUG modem << [00:16:01.545,379] [1;31m<err> modem_info_params: Link data not obtained: 20 -5[0m
2022-11-10T17:19:16.102Z DEBUG modem << [00:16:01.545,440] [1;31m<err> modem_info_params: Network data not obtained: -5[0m
2022-11-10T17:19:16.112Z DEBUG modem << [00:16:01.545,440] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m
2022-11-10T17:19:16.118Z DEBUG modem << [00:16:01.545,532] [0m<inf> app_event_manager: MODEM_EVT_BATTERY_DATA_NOT_READY[0m
2022-11-10T17:19:16.129Z DEBUG modem << [00:16:01.554,473] [0m<inf> app_event_manager: MODEM_EVT_NEIGHBOR_CELLS_DATA_READY[0m
2022-11-10T17:19:27.262Z DEBUG modem << [00:16:11.804,779] [1;33m<wrn> date_time: getaddrinfo, error: -11[0m
2022-11-10T17:19:27.276Z DEBUG modem << [00:16:11.804,809] [1;33m<wrn> date_time: Did not get time from any NTP server[0m

I see you are using a private network:

COPS: 0,2,"99970",9

Have you verified that this network is connected to the internet?

[dival]

It is a custom sim, and yes.

In terms of the verification of the network, I have tried pinging it and there doesn't seem to be an issue from that end.

I will provide more details later.

[Øyvind]

What kind of setup is this? What did you try to ping?

Could you please provide more information on what you are trying to achieve? Can you provide more information on your setup?

Using Asset Tracker for this kind of testing is not the level of testing you need to do at this point. You need to verify that the network routing from your device to the network is actually working as intended, and that your device actually gets DNS. 

To actually verify that your nRF9160 can connect to a network it would be best to use a standard SIM i.e. iBasis or a local network providers SIM. 

[dival]

Hey,

Thanks for reaching back to me.

I have attempted to ping 8.8.8.8, and it did not appear to be an issue, therefore I do not believe that connectivity is an issue. I'd also like to highlight that I have tried another microcontroller that supports NB-IoT to confirm that the setup is operating properly.

I'm currently running nrf9160dk_asset_tracker_v2_nbiot_2022-06-02_880c82db.hex which is flashed to the microcontroller. 

You also mentioned an IBasis sim card; however, there is no coverage in my city, only in another city, so I don't believe that will work. Regarding a local SIM card, I do not have one to test.

Thanks.

[Øyvind]

We will need to see a modem trace in order to verify if the issue is in the nRF9160. Can you please provide .bin file from the trace collector? 

What test setup are you connecting to? Are you working with a CMW500 or similar? Please procure a SIM from a local vendor to verify that your device is actually working. Where are you based? From the logs you provided I am assuming Norway. Please contact Telenor or Telia for an NB-IoT SIM.

From the logs e.g. 

modem_info_params: Link data not obtained: 20 -5

This indicates that there is an issue with the network connection. What other microcontroller did you test with? 

[Øyvind]

Also, please provide full .pcap along with modem trace

[dival]

I'll have to check that out. Regarding the modem trace, I am looking at the documentation right now, Is it possible to run the LTE link monitor and the modem tracer simultaneously? 

No, but it is quite similar. I'll try to see if I can get a local NB-IoT sim card for testing. In terms of the other microcontroller, it is one with a BG96 modem. (Not Nordic). 

If it is indeed the network connection, I will need to investigate further. Previously, I mentioned that when it connected to the network, attempted to establish a connection to the cloud, and then failed, it would automatically disconnect from the network.

Thanks for the help so far.

[Øyvind]

dival said:

Regarding the modem trace, I am looking at the documentation right now, Is it possible to run the LTE link monitor and the modem tracer simultaneously?

Yes, this is possible. The modem trace uses it's own UART port. You can program the nrf9160dk_asset_tracker_v2_debug_nbiot_2022-06-02_880c82db.hex, which has modem trace enabled. 

After doing that you can open Trace Collector v2 from nRF Connect for Desktop

After clicking start, make sure to reset you nRF9160DK, then you should see the size of the file increase as it tries to connect. 

dival said:

terms of the other microcontroller, it is one with a BG96 modem. (Not Nordic). 

Please note that BG96 is not the same as nRF9160 as the latter does not support EDGE and GPRS. Did you verify that you connected via NB-IoT and not EDGE or GRPS? 

dival said:

If it is indeed the network connection, I will need to investigate further. Previously, I mentioned that when it connected to the network, attempted to establish a connection to the cloud, and then failed, it would automatically disconnect from the network.

As you are on a test network, please verify your setup in the gateway.