Nrf_cloud_connect failed: 60

[rkguy]

I am getting this message with constant reboots. 

Nrf_cloud_connect failed: 60

Used tracker application. My device doesn't even show up in nrfcloud.

The at client application does connect eventually with all green but takes a while.

[Markus Tacker (he/him)]

rkguy said:

The at client application does connect eventually with all green but takes a while.

Once it is connected you need to associated it in order for the device to show up on nRF Connect for Cloud, did you do that?

[rkguy]

Hmm. I can try that but how? I can't connect unless I am using the at client application. How do I found the switches to associate? 

[Markus Tacker (he/him)]

Check out the "Get your nRF9160 DK online" guide here: https://www.nordicsemi.com/Software-and-Tools/Development-Kits/nRF9160-DK/GetStarted#infotabs

[rkguy]

Correct me if I am wrong but this requires me to run the asset tracker app to do so and the asset tracker app simply will not connect ever, I mean that it will not connect and I've tried for hours.

[Markus Tacker (he/him)]

You wrote that it connects eventually ...

Yes, the device needs to be connected in order for the demo to work.

It could be that you are in an area with limited coverage. Try moving to the device to a location with better coverage. 

iBasis has a FAQ on the areas where you have good coverage here: https://devzone.nordicsemi.com/b/nrf9160-development-status/posts/ibasis-global-access-for-things-frequently-asked-questions-faq

[rkguy]

I wrote that the at client does connect eventually but this is after repeated attempts by me to connect to the network. This is different than the asset tracker app which is giving me the error in the title of this post, constantly.

So, what do I do next? You will find this odd. My other nrf9160dk has no problem connecting and associating using the asset tracker app. They are right next to each other.

[Markus Tacker (he/him)]

So, since you have two identical 9160DKs but only one works there seems to be a hardware issue. And here Øyvind has more experience to figure out what is wrong.