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]

Tester013 said:

If it's of any use, the log is attached below. Thanks.

Thanks a lot for the logs! Just two minor remarks: if you share logs, could you please use our Insert -> Code functionality here in DevZone as it increases readability a lot? And if you could include timestamps to the logs, they will be even easier to interpret :-) Thanks! 

Tester013 said:

I have done that and the following is the output. At the final bit the output didn't quite seem to fully match up with your provided sample but I've tried my best to run as many of hte commands as I could. Below is the output. Thanks.

Starting with the AT client log, I’m a bit confused here to be honest. You configured the system as:

AT%XSYSTEMMODE=0,1,1,2 
OK 

meaning LTE-M not supported, NB-IoT supported, GNSS supported and NB-IoT preferred. 

However, these changes appear not to have become effective, meaning that only LTE-M will be used.

 

AT%XSYSTEMMODE?  
%XSYSTEMMODE: 1,0,0,0 

OK 

But the modem actually is able to connect to an LTE-M network:

+CEREG: 5,"0421","07B56F78",7,,,"11100000","11100000"

which brings me to the next question if you are using a SIM card that supports both LTE-M & NB-IoT? 

Cheers,

Markus

[Tester013]

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 resolved the issue. In the end, there was apparently some error regarding the certificate of the device, so issuing a new one from the nRF Cloud portal and flashing it onto the board enabled me to connect to the nRF Cloud with no issues.