Error -11 when connecting to nRF Cloud

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!

Top Replies

Tester013 over 3 years ago in reply to Albrecht Markus Schellenberger +1 verified

Hmm..that's indeed odd, as supposedly, my SIM card should be operating on the NB-IoT network but I suppose that LTE-M works as well? In any case, thank you very much for your time but I seem to have…

Parents

0 Albrecht Markus Schellenberger over 3 years ago

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

Reply