Thingi:91 : CLOUD_EVT_CONNECTION_TIMEOUT

[beshan]

Hello

Using a Thingi91 with latest firmware and Asset Tracker v2. Connects to the tower, but cant seem to connect to the NRF Cloud. How can I check if it can reach any other server (Ping possible? ) ?  What else can I check to see what's wrong. The mobile operator is saying that the sim is enabled for data and has credit. Please help

Log file attached 

Fullscreen 2022-01-26T15_10_53.266Z-log-send.txt Download

2022-01-26T15:10:54.684Z INFO Application data folder: C:\Users\Beshan\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
2022-01-26T15:10:54.763Z DEBUG App pc-nrfconnect-linkmonitor v2.0.0 official
2022-01-26T15:10:54.763Z DEBUG App path: C:\Users\Beshan\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2022-01-26T15:10:54.763Z DEBUG nRFConnect 3.9.3, required by the app is (^3.8.0)
2022-01-26T15:10:54.763Z DEBUG nRFConnect path: C:\Users\Beshan\AppData\Local\Programs\nrfconnect\resources\app.asar
2022-01-26T15:10:54.763Z DEBUG HomeDir: C:\Users\Beshan
2022-01-26T15:10:54.763Z DEBUG TmpDir: C:\Users\Beshan\AppData\Local\Temp
2022-01-26T15:10:57.976Z INFO Modem port is opened
2022-01-26T15:10:57.992Z DEBUG modem >> AT+CFUN?
2022-01-26T15:10:58.002Z DEBUG modem << +CFUN: 1
2022-01-26T15:10:58.005Z DEBUG modem << OK
2022-01-26T15:10:58.032Z DEBUG modem >> AT+CGSN=1
2022-01-26T15:10:58.041Z DEBUG modem << +CGSN: "35xxxxxxxxxxxxxx"
2022-01-26T15:10:58.045Z DEBUG modem << OK
2022-01-26T15:10:58.048Z DEBUG modem >> AT+CGMI
2022-01-26T15:10:58.059Z DEBUG modem << Nordic Semiconductor ASA
2022-01-26T15:10:58.062Z DEBUG modem << OK
2022-01-26T15:10:58.065Z DEBUG modem >> AT+CGMM
2022-01-26T15:10:58.079Z DEBUG modem << nRF9160-SICA
2022-01-26T15:10:58.081Z DEBUG modem << OK
2022-01-26T15:10:58.084Z DEBUG modem >> AT+CGMR
2022-01-26T15:10:58.092Z DEBUG modem << mfw_nrf9160_1.3.1
2022-01-26T15:10:58.094Z DEBUG modem << OK
2022-01-26T15:10:58.095Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.3.1] SerNr: 352656xxxxxxxxx
2022-01-26T15:10:58.098Z DEBUG modem >> AT+CEMODE?
2022-01-26T15:10:58.112Z DEBUG modem << +CEMODE: 0
2022-01-26T15:10:58.115Z DEBUG modem << OK
2022-01-26T15:10:58.133Z DEBUG modem >> AT%XCBAND=?
2022-01-26T15:10:58.146Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,17,19,20,25,26,28,66)
2022-01-26T15:10:58.148Z DEBUG modem << OK
2022-01-26T15:10:58.163Z DEBUG modem >> AT+CMEE?
2022-01-26T15:10:58.178Z DEBUG modem << +CMEE: 1
2022-01-26T15:10:58.181Z DEBUG modem << OK
2022-01-26T15:10:58.186Z DEBUG modem >> AT+CNEC?
2022-01-26T15:10:58.197Z DEBUG modem << +CNEC: 24
2022-01-26T15:10:58.198Z DEBUG modem << OK
2022-01-26T15:10:58.201Z DEBUG modem >> AT+CGEREP?
2022-01-26T15:10:58.211Z DEBUG modem << +CGEREP: 1,0
2022-01-26T15:10:58.213Z DEBUG modem << OK
2022-01-26T15:10:58.217Z DEBUG modem >> AT+CIND=1,1,1
2022-01-26T15:10:58.226Z DEBUG modem << OK
2022-01-26T15:10:58.231Z DEBUG modem >> AT+CEREG=5
2022-01-26T15:10:58.243Z DEBUG modem << OK
2022-01-26T15:10:58.248Z DEBUG modem >> AT+CEREG?
2022-01-26T15:10:58.260Z DEBUG modem << +CEREG: 5,1,"3573","000B1E29",9,,,"00100011","11100000"
2022-01-26T15:10:58.262Z DEBUG modem << OK
2022-01-26T15:10:58.266Z DEBUG modem >> AT+COPS=3,2
2022-01-26T15:10:58.277Z DEBUG modem << OK
2022-01-26T15:10:58.280Z DEBUG modem >> AT+COPS?
2022-01-26T15:10:58.295Z DEBUG modem << +COPS: 0,2,"41301",9
2022-01-26T15:10:58.297Z DEBUG modem << OK
2022-01-26T15:10:58.311Z DEBUG modem >> AT%XCBAND
2022-01-26T15:10:58.318Z DEBUG modem << %XCBAND: 8
2022-01-26T15:10:58.321Z DEBUG modem << OK
2022-01-26T15:10:58.332Z DEBUG modem >> AT+CGDCONT?
2022-01-26T15:10:58.344Z DEBUG modem << +CGDCONT: 0,"IP","Nbiot","10.106.222.211",0,0
2022-01-26T15:10:58.345Z DEBUG modem << OK
2022-01-26T15:10:58.349Z DEBUG modem >> AT+CGACT?
2022-01-26T15:10:58.361Z DEBUG modem << +CGACT: 0,1
2022-01-26T15:10:58.363Z DEBUG modem << OK
2022-01-26T15:10:58.366Z DEBUG modem >> AT%CESQ=1
2022-01-26T15:10:58.376Z DEBUG modem << OK
2022-01-26T15:10:58.379Z DEBUG modem << %CESQ: 64,3,27,3
2022-01-26T15:10:58.383Z DEBUG modem >> AT+CESQ
2022-01-26T15:10:58.393Z DEBUG modem << +CESQ: 99,99,255,255,27,64
2022-01-26T15:10:58.395Z DEBUG modem << OK
2022-01-26T15:10:58.398Z DEBUG modem >> AT%XSIM=1
2022-01-26T15:10:58.403Z DEBUG modem << OK
2022-01-26T15:10:58.411Z DEBUG modem >> AT%XSIM?
2022-01-26T15:10:58.418Z DEBUG modem << %XSIM: 1
2022-01-26T15:10:58.419Z DEBUG modem << OK
2022-01-26T15:10:58.433Z DEBUG modem >> AT+CPIN?
2022-01-26T15:10:58.443Z DEBUG modem << +CPIN: READY
2022-01-26T15:10:58.446Z DEBUG modem << OK
2022-01-26T15:10:58.450Z DEBUG modem >> AT+CPINR="SIM PIN"
2022-01-26T15:10:58.466Z DEBUG modem << +CPINR: "SIM PIN",3
2022-01-26T15:10:58.467Z DEBUG modem << OK
2022-01-26T15:10:58.470Z DEBUG modem >> AT+CIMI
2022-01-26T15:10:58.479Z DEBUG modem << 413012680206386
2022-01-26T15:10:58.480Z DEBUG modem << OK
2022-01-26T15:10:58.481Z INFO IMSIdentity: 413012680206386
2022-01-26T15:11:00.749Z DEBUG modem << %CESQ: 64,3,34,4
2022-01-26T15:11:03.310Z DEBUG modem << %CESQ: 64,3,21,3
2022-01-26T15:11:05.870Z DEBUG modem << %CESQ: 64,3,34,4
2022-01-26T15:11:08.431Z DEBUG modem << %CESQ: 64,3,21,3
2022-01-26T15:11:10.691Z DEBUG modem << [00:00:42.408,752] [0m<inf> event_manager: CLOUD_EVT_CONNECTION_TIMEOUT[0m
2022-01-26T15:11:10.693Z DEBUG modem << [00:00:42.415,954] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
2022-01-26T15:11:10.745Z DEBUG modem << [00:00:42.424,072] [1;33m<wrn> cloud_module: New connection attempt in 64 seconds if not successful[0m
2022-01-26T15:11:10.990Z DEBUG modem << %CESQ: 65,3,34,4
2022-01-26T15:11:13.551Z DEBUG modem << %CESQ: 65,3,21,3
2022-01-26T15:11:16.110Z DEBUG modem << %CESQ: 64,3,34,4
2022-01-26T15:11:18.671Z DEBUG modem << %CESQ: 65,3,21,3
2022-01-26T15:11:21.230Z DEBUG modem << %CESQ: 66,3,34,4
2022-01-26T15:11:23.791Z DEBUG modem << %CESQ: 65,3,20,2
2022-01-26T15:11:26.350Z DEBUG modem << %CESQ: 66,3,34,4
2022-01-26T15:11:28.912Z DEBUG modem << %CESQ: 65,3,21,3
2022-01-26T15:11:31.470Z DEBUG modem << %CESQ: 65,3,34,4
2022-01-26T15:11:34.031Z DEBUG modem << %CESQ: 65,3,20,2
2022-01-26T15:11:36.590Z DEBUG modem << %CESQ: 65,3,34,4
2022-01-26T15:11:39.150Z DEBUG modem << %CESQ: 65,3,21,3
2022-01-26T15:11:41.709Z DEBUG modem << %CESQ: 64,3,33,4
2022-01-26T15:11:44.271Z DEBUG modem << %CESQ: 64,3,21,3
2022-01-26T15:11:46.830Z DEBUG modem << %CESQ: 64,3,34,4
2022-01-26T15:11:49.390Z DEBUG modem << %CESQ: 64,3,21,3
2022-01-26T15:11:51.949Z DEBUG modem << %CESQ: 65,3,34,4
2022-01-26T15:11:54.510Z DEBUG modem << %CESQ: 64,3,21,3
2022-01-26T15:11:57.070Z DEBUG modem << %CESQ: 64,3,34,4
2022-01-26T15:11:59.630Z DEBUG modem << %CESQ: 63,3,19,2
2022-01-26T15:12:02.189Z DEBUG modem << %CESQ: 64,3,34,4
2022-01-26T15:12:04.751Z DEBUG modem << %CESQ: 64,3,21,3
2022-01-26T15:12:07.309Z DEBUG modem << %CESQ: 65,3,34,4
2022-01-26T15:12:09.871Z DEBUG modem << %CESQ: 64,3,19,2
2022-01-26T15:12:12.429Z DEBUG modem << %CESQ: 65,3,34,4
2022-01-26T15:12:14.713Z DEBUG modem << [00:01:46.433,471] [0m<inf> event_manager: CLOUD_EVT_CONNECTION_TIMEOUT[0m
2022-01-26T15:12:14.714Z DEBUG modem << [00:01:46.440,673] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
2022-01-26T15:12:14.723Z DEBUG modem << [00:01:46.448,791] [1;33m<wrn> cloud_module: New connection attempt in 128 seconds if not successful[0m
2022-01-26T15:12:14.990Z DEBUG modem << %CESQ: 65,3,21,3
2022-01-26T15:12:17.549Z DEBUG modem << %CESQ: 65,3,34,4
2022-01-26T15:12:20.110Z DEBUG modem << %CESQ: 64,3,21,3
2022-01-26T15:12:22.671Z DEBUG modem << %CESQ: 64,3,34,4
2022-01-26T15:12:25.230Z DEBUG modem << %CESQ: 64,3,21,3
2022-01-26T15:12:27.789Z DEBUG modem << %CESQ: 65,3,34,4
2022-01-26T15:12:28.526Z DEBUG modem << [00:02:00.252,868] [0m<inf> event_manager: APP_EVT_DATA_GET_ALL[0m
2022-01-26T15:12:28.532Z DEBUG modem << [00:02:00.259,643] [0m<inf> event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, NEIGHBOR_CELLS, GNSS, MOD_STAT)[0m
2022-01-26T15:12:28.556Z DEBUG modem << [00:02:00.292,785] [0m<inf> event_manager: GPS_EVT_ACTIVE[0m
2022-01-26T15:12:28.566Z DEBUG modem << [00:02:00.298,919] [0m<inf> event_manager: GPS_EVT_AGPS_NEEDED[0m
2022-01-26T15:12:28.581Z DEBUG modem << [00:02:00.306,182] [1;33m<wrn> data_module: Failed to request A-GPS data, error: -13[0m
2022-01-26T15:12:28.583Z DEBUG modem << [00:02:00.313,995] [1;33m<wrn> data_module: This is expected to fail if we are not in a connected state[0m
2022-01-26T15:12:28.596Z DEBUG modem << [00:02:00.326,538] [0m<inf> event_manager: SENSOR_EVT_ENVIRONMENTAL_DATA_READY[0m
2022-01-26T15:12:28.650Z DEBUG modem << [00:02:00.388,366] [0m<inf> event_manager: MODEM_EVT_MODEM_STATIC_DATA_READY[0m
2022-01-26T15:12:28.715Z DEBUG modem << [00:02:00.452,789] [0m<inf> event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_READY[0m
2022-01-26T15:12:28.778Z DEBUG modem << [00:02:00.517,486] [0m<inf> event_manager: MODEM_EVT_BATTERY_DATA_READY[0m
2022-01-26T15:12:28.792Z DEBUG modem << [00:02:00.530,029] [0m<inf> event_manager: MODEM_EVT_NEIGHBOR_CELLS_DATA_READY[0m
2022-01-26T15:12:30.349Z DEBUG modem << %CESQ: 65,3,20,2
2022-01-26T15:12:32.909Z DEBUG modem << %CESQ: 65,3,34,4
2022-01-26T15:12:35.470Z DEBUG modem << %CESQ: 65,3,21,3
2022-01-26T15:12:38.029Z DEBUG modem << %CESQ: 64,3,34,4

thanks

Beshan

[beshan]

Also if this was a certificate/provisions issues, I would see a different error ? Appreciate the community feedback !

[Øyvind]

Hi Beshan,

beshan said:

Also if this was a certificate/provisions issues, I would see a different error ? Appreciate the community feedback !

Yes, that is correct. What kind of SIM are you using? I see you have latest modem FW, and it does connect to NB-IoT network. We might need a modem trace of this.

Kind regards,
Øyvind

[beshan]

How do I get a modem trace ?  I tried to complile the Asset Tracker v2 using the tool chain/SE studio , but that merged hex file does not show any output from the LTE monitor. 

[Øyvind]

Hello

beshan said:

I tried to complile the Asset Tracker v2 using the tool chain/SE studio , but that merged hex file does not show any output from the LTE monitor.

Did you do this after you registered the ticket? There was no need to reprogram the device. To fix the issue we have a precompiled application package that you can download, and then program the Asset Tracker v2.
https://www.nordicsemi.com/Products/Development-hardware/Nordic-Thingy-91/Download#infotabs

beshan said:

How do I get a modem trace ?

You can follow the guide we have in our documentation: https://infocenter.nordicsemi.com/topic/ug_trace_collector/UG/trace_collector/collect_modem_trace_thingy.html

Kind regards,
Øyvind

[beshan]

This is now fixed. The NRF9160 works on Sri Lankan network, the issue was that the firmware (or the network) couldn't translate the DNS. When I use a IP address, it connects using MQTT.