Error -11 when connecting to nRF Cloud

[Tester013]

Hi

I'm just starting out to test the nRF9160 DK board and have just flashed the NB-IoT Asset Tracker as per the introductory video uploaded by Nordic here:

https://www.youtube.com/watch?v=rMvW3HXLErk&t=583s

However, I'm running into an issue with [0m<inf> app_event_manager: CLOUD_EVT_CONNECTION_TIMEOUT when setting things up. As the iBasis SIM card doesn't seem to work in my area, I have utilised by own sim card from WirelessLogic, and have confirmed with them that there is sufficient data left in the sim card.

Any help is very much appreciated, thanks!

[Albrecht Markus Schellenberger]

Hello,

I have utilised by own sim card from WirelessLogic, and have confirmed with them that there is sufficient data left in the sim card.

Can you confirm that your nRF9160 DK together with the SIM card you are currently using is able to connect to a network? 

Regards, 

Markus  

[Tester013]

Yes, it can connect to a LTE network currently and produces the MODEM_EVT_LTE_CONNECTED Message.

The following is the log file, if required:

[00:00:00.506,042] 

[0m<inf> app_event_manager: APP_EVT_START

[0m

[00:00:00.507,293] 

[0m<inf> app_event_manager: MODEM_EVT_INITIALIZED

[0m

[00:00:00.564,514] 

[0m<inf> app_event_manager: MODEM_EVT_LTE_CONNECTING

[0m

[00:00:01.525,360] 

[0m<inf> app_event_manager: DATA_EVT_CONFIG_INIT

[0m

[00:00:01.525,909] 

[0m<inf> app_event_manager: APP_EVT_ACTIVITY_DETECTION_DISABLE

[0m

%MDMEV: SEARCH STATUS 1

[00:02:01.525,939] 

[0m<inf> app_event_manager: APP_EVT_DATA_GET_ALL

[0m

[00:02:01.526,611] 

[0m<inf> app_event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, NEIGHBOR_CELLS, MOD_STAT)

[0m

[00:02:01.527,435] 

[0m<inf> app_event_manager: SENSOR_EVT_ENVIRONMENTAL_NOT_SUPPORTED

[0m

[00:02:01.530,487] 

[1;31m<err> modem_info_params: Link data not obtained: 5 -22

[0m

[00:02:01.531,127] 

[1;31m<err> modem_info_params: Link data not obtained: 8 -22

[0m

[00:02:01.531,646] 

[1;31m<err> modem_info_params: Link data not obtained: 3 -22

[0m

[00:02:01.534,240] 

[1;31m<err> modem_info_params: Link data not obtained: 21 -22

[0m

[00:02:01.535,034] 

[1;31m<err> modem_info_params: Link data not obtained: 20 -5

[0m

[00:02:01.535,034] 

[1;31m<err> modem_info_params: Network data not obtained: -93

[0m

[00:02:01.535,064] 

[1;31m<err> modem_module: modem_info_params_get, error: -11

[0m

[00:02:01.535,125] 

[0m<inf> app_event_manager: MODEM_EVT_MODEM_STATIC_DATA_NOT_READY

[0m

[00:02:01.625,396] 

[1;31m<err> modem_info_params: Link data not obtained: 5 -22

[0m

[00:02:01.625,946] 

[1;31m<err> modem_info_params: Link data not obtained: 8 -22

[0m

[00:02:01.626,556] 

[1;31m<err> modem_info_params: Link data not obtained: 3 -22

[0m

[00:02:01.628,967] 

[1;31m<err> modem_info_params: Link data not obtained: 21 -22

[0m

[00:02:01.629,425] 

[1;31m<err> modem_info_params: Link data not obtained: 20 -5

[0m

[00:02:01.629,455] 

[1;31m<err> modem_info_params: Network data not obtained: -93

[0m

[00:02:01.629,455] 

[1;31m<err> modem_module: modem_info_params_get, error: -11

[0m

[00:02:01.629,547] 

[0m<inf> app_event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_NOT_READY

[0m

[00:02:01.632,751] 

[1;31m<err> modem_info_params: Link data not obtained: 5 -22

[0m

[00:02:01.633,270] 

[1;31m<err> modem_info_params: Link data not obtained: 8 -22

[0m

[00:02:01.633,819] 

[1;31m<err> modem_info_params: Link data not obtained: 3 -22

[0m

%NCELLMEAS: 1

+CEREG: 2

[00:02:01.719,085] 

[1;31m<err> modem_info_params: Link data not obtained: 21 -22

[0m

[00:02:01.719,879] 

[1;31m<err> modem_info_params: Link data not obtained: 20 -5

[0m

[00:02:01.719,909] 

[1;31m<err> modem_info_params: Network data not obtained: -93

[0m

[00:02:01.719,909] 

[1;31m<err> modem_module: modem_info_params_get, error: -11

[0m

[00:02:01.720,001] 

[0m<inf> app_event_manager: MODEM_EVT_BATTERY_DATA_NOT_READY

[0m

[00:02:01.729,095] 

[0m<inf> app_event_manager: MODEM_EVT_NEIGHBOR_CELLS_DATA_NOT_READY

[0m

[00:02:01.729,705] 

[0m<inf> app_event_manager: MODEM_EVT_LTE_DISCONNECTED

[0m

[00:02:01.730,285] 

[0m<inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE

[0m

[00:02:01.731,140] 

[0m<inf> app_event_manager: DATA_EVT_DATA_READY

[0m

%CESQ: 67,3,22,3

+CEREG: 2,"242A","00378F15",9

+CSCON: 1

%CESQ: 68,3,27,3

[00:02:05.448,577] 

[0m<inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE

[0m

%MDMEV: SEARCH STATUS 2

+CEREG: 5,"242A","00378F15",9,,,"00001010","11000001"

%XTIME: ,"22708031347580","01"

[00:02:07.115,173] 

[0m<inf> app_event_manager: MODEM_EVT_LTE_CONNECTED

[0m

[00:02:07.115,814] 

[0m<inf> app_event_manager: MODEM_EVT_LTE_PSM_UPDATE

[0m

[00:02:07.117,156] 

[1;33m<wrn> cloud_module: Cloud connection establishment in progress

[0m

[00:02:07.117,156] 

[1;33m<wrn> cloud_module: New connection attempt in 32 seconds if not successful

[0m

[00:02:07.117,309] 

[0m<inf> app_event_manager: CLOUD_EVT_CONNECTING

[0m

[00:02:07.134,033] 

[0m<inf> app_event_manager: DATA_EVT_DATE_TIME_OBTAINED

[0m

%CESQ: 68,3,22,3

%CESQ: 68,3,27,3

+CSCON: 0

%CESQ: 68,3,21,3

%CESQ: 67,3,28,4

%CESQ: 255,0,255,0

[00:02:39.117,340] 

[0m<inf> app_event_manager: CLOUD_EVT_CONNECTION_TIMEOUT

[0m

[00:02:39.117,828] 

[1;31m<err> nrf_cloud_integration: nrf_cloud_connect, error: -11

[0m

[00:02:39.117,858] 

[1;31m<err> cloud_module: cloud_connect failed, error: -11

[0m

[00:02:39.117,858] 

[1;33m<wrn> cloud_module: Cloud connection establishment in progress

[0m

[00:02:39.117,889] 

[1;33m<wrn> cloud_module: New connection attempt in 64 seconds if not successful

[0m

[Albrecht Markus Schellenberger]

Tester013 said:

The following is the log file, if required:

Thanks for the log! 

What I can see is that during the first connection attempt, the modem is not ready as it has not been able to establish a network connection yet.  

During the second try, it seems to time out again. I’m not a 100% sure though if 

%CESQ: 255,0,255,0

is because of modem entering PSM or losing the network. 

Which modem firmware are you currently operating with and which version of the Asset Tracker firmware is running on your nRF9160 DK? 

Regards, 

Markus 

[Tester013]

Albrecht Markus Schellenberger said:

Which modem firmware are you currently operating with and which version of the Asset Tracker firmware is running on your nRF9160 DK? 

Both pieces of software were obtained from the nRF9160 DK Downloads page, inside the zip file nrf9160dk_fw_2022-06-02_880c82db.zip. I used the nbiot version of the asset_tracker with the file name "nrf9160dk_asset_tracker_v2_nbiot_2022-06-02_880c82db.hex" and version 1.3.2 of the modem firmware provided inside the same zip file.

[Albrecht Markus Schellenberger]

Tester013 said:

Both pieces of software were obtained from the nRF9160 DK Downloads page, inside the zip file nrf9160dk_fw_2022-06-02_880c82db.zip. I used the nbiot version of the asset_tracker with the file name "nrf9160dk_asset_tracker_v2_nbiot_2022-06-02_880c82db.hex" and version 1.3.2 of the modem firmware provided inside the same zip file.

Ok, that is a good starting point :-)

I’m not quite sure though what the problem is here yet but let us start with some basic network-related checks. Could you please flash the AT Client sample to your DK (available as pre-compiled image) and run through the following sequence: 

[2022-07-08 17:43:01] *** Booting Zephyr OS build v3.0.99-ncs1  ***
[2022-07-08 17:43:01] The AT host sample started
[2022-07-08 17:43:04] AT+CGMR
[2022-07-08 17:43:05] mfw_nrf9160_1.3.2
[2022-07-08 17:43:05] OK
[2022-07-08 17:43:10] AT%MDMEV=1
[2022-07-08 17:43:10] OK
[2022-07-08 17:43:14] AT%XMODEMSLEEP=1,1000,60000
[2022-07-08 17:43:14] O%XMODEMSLEEP: 4
[2022-07-08 17:43:14] K
[2022-07-08 17:43:18] AT+CEREG=5
[2022-07-08 17:43:19] OK
[2022-07-08 17:43:22] AT%CESQ=1 
[2022-07-08 17:43:23] OK
[2022-07-08 17:43:27] AT%XSYSTEMMODE?
[2022-07-08 17:43:28] %XSYSTEMMODE: 1,0,0,0
[2022-07-08 17:43:28] OK
[2022-07-08 17:43:31] AT+CFUN=1
[2022-07-08 17:43:32] %XMODEMSLEEP: 4,0
[2022-07-08 17:43:32] OK
[2022-07-08 17:43:33] %CESQ: 46,2,18,2
[2022-07-08 17:43:33] +CEREG: 2,"7AA9","01444000",7
[2022-07-08 17:43:34] %MDMEV: SEARCH STATUS 2
[2022-07-08 17:43:34] +CEREG: 1,"7AA9","01444000",7,,,"00001010","11000001"
[2022-07-08 17:43:42] %CESQ: 47,2,23,3
[2022-07-08 17:43:57] %CESQ: 46,2,18,2
[2022-07-08 17:44:08] %CESQ: 255,0,255,0
[2022-07-08 17:44:08] %XMODEMSLEEP: 1,1151979975

Please note that you need to reconfigure the modem to NB-IoT support instead before setting it to normal mode. This is done with the %XSYSTEMMODE AT command. 

Thanks & regards, 

Markus