nrf9160dk device not showing

[AndrewR]

Hello, I have been trying to get the nrf9160DK PCA10090 version 0.8.2 to connect to your nrf cloud. I initially tried with the provided ibasis sim. I was able to get it registered and add but the connection mus have been bad here in Florida because it rarely gets to both LED3 and LED4 blinking. It has a couple times and I submitted the sequence to pair but the device never gets added. I switch over to a hologram Sim that I already had. It connects (both LED3 and LED4 blinking) very quickly. After I submit the pairing sequence it then goes to LED4 Blinking and after a little while it goes to LED4 solid. I understand this to mean the pairing is complete but I still don't see the device in the menu. Any Advice?

I did this straight out of the box. I didn't update any code on the board yet.

Also I do see the compiled source code for the asset tracker in the SDK but I don't see the raw editable code anywhere like you had in other SDKs. Is that not available yet?

[Carl Richard]

Hello, AndrewR!

Just to clarify: you can't find the device under the "devices" tab on your nRF cloud console? 

For your second question: raw editable code is available. For the asset_tracker it's located at the location: 

.../ncs/nrf/applications/asset_tracker/src

Though I assume you are using SES(Segger Embedded studio) and from what I've heard the source code is a bit more hidden there. Take a look at the image below. It shows the location of the source file for the at_client, it will be similar for the asset_tracker.

[AndrewR]

Carl, Thank you for your response. I see the c file and am able to review the code thank you. There is no Segger project files here correct I will have to build that on my end?.

For the no device. Yes it doesn't appear in the devices tab. Any thoughts?

[Carl Richard]

Great that you found the source files! 

The "Getting started guide" in nRF Connect describes how you create and build your own projects in SES.

Have you tried to look at the serial output from the DK? You can for example use the "LTE Link monitor" in nRF Connect. That could give us some idea of what's wrong here :) 

PS: I assume that you've already downloaded nRF Connect, if you haven't you can find it here.