nRF9160 DK Connecting problems with nRF Cloud

[Bergmann]

Hello, I tried to set up my nRF9160 with this tutorial and there is a problem:

https://www.youtube.com/watch?v=jZQcmU3KIMY&t=216s

According to the tutorial, LED 3 and the LED 4 should be blinking after 3 minutes, what means that the board is connected to the nRF Cloud.
However on my nRF9160, the LED 4  never starts blinking, even if I wait 10 minutes longer than required.
I tried to push the reset button a few times, I turned the nRF9160 on and off a few times and I also started the "Add LTE Device" on nRF Cloud a few times.

But LED 4 still remains dark.

There were 2 things different compared to the tutorial video:

1) The Sim Card Registration worked fine, but when I came to the window in the picture below, I had an IMEI, but I found no PIN. So, I tried the option without a pin (Red mark in the picture).

Maybe I need a PIN, but where do I get it? I tried to insert every possible number I found on my nRF9160, but none of them worked. 

I have already installed the latest firmware update for the nRF9160 successfully. So what did I do wrong? Or how can I finally connect the nRF9160 to the nRF Cloud?

- Thanks for your answers

- Bergmann

[Terje K Wahl]

Hi, this thread has been very useful for me to get past several problems getting the asset tracker example to work. I connect successfully to a NB-IoT network here in Norway now, thanks to (as explained in other posts here) setting modem mode to NB-IoT, using legacy PCO mode and using a static IP address since DNS is not supported.

Finally, the problem I am left with is "cloud_connect failed: -111". I had high hopes that a certificate update would solve this, but after successfully updating my certificates the same problem still persists. 

Here is my output from the terminal:

**** Booting Zephyr OS build v1.14.99-ncs3-snapshot2-2647-gd6e67554cfeb *****
[00:00:00.378,173] 
[0m<dbg> nrf9160_gps.init: MAGPIO set: AT%XMAGPIO=1,0,0,1,1,1574,1577
Asset tracker started
[00:00:00.389,282] 
[0m<dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100223414
[00:00:00.398,498] 
[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100223414/shadow
[00:00:00.410,156] 
[0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: nrf-352656100223414/shadow/get/accepted
[00:00:00.421,661] 
[0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100223414/shadow/get/rejected
[00:00:00.434,204] 
[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100223414/shadow/update/delta
[00:00:00.447,082] 
[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100223414/shadow/update
[00:00:00.458,923] 
[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100223414/shadow/get
Connecting to LTE network. This may take several minutes.
[00:00:00.477,172] 
[0m<inf> lte_lc: Using legacy LTE PCO mode...
[00:00:00.483,428] 
[0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=0,1,1,0
[00:00:04.653,717] 
[0m<dbg> lte_lc.at_handler: recv: +CEREG: 2,"0CEB","0202791C",9,0,0,"11100000","11100000"
[00:00:04.664,123] 
[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2
[00:00:05.574,218] 
[0m<dbg> lte_lc.at_handler: recv: +CEREG: 1,"0CEB","0202791C",9,,,"11100000","11100000
[00:00:05.584,472] 
[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 1
Connected to LTE network
[00:00:05.595,123] 
[0m<dbg> nrf_cloud_transport.nct_connect: IPv4 Address 52.54.149.10
cloud_connect failed: -111
LTE link disconnect
Shutdown modem
***** Booting Zephyr OS build v1.14.99-ncs3-snapshot2-2647-gd6e67554cfeb *****

Kind regards,

Terje

[Heidi-Irene Harvey Sollie]

Hi Terje!

Could you please make a new ticket with your issue? This makes the site much more searchable for our users.

Side note: all networks in Norway support DNS lookup, so I don't think that is your issue.

Best regards,

Heidi

[Terje K Wahl]

New thread created: https://devzone.nordicsemi.com/f/nordic-q-a/53152/cloud_connect-failed--111

There you can also read that I've re-tested without static IP, and then DNS lookup fails.