GPS issue again but different - Do I need new certificates?

SteveD0

Well I just went back to test out the GPS - outside of my house. Both the MODEM and LTE are green, the Hologram site says I’m connected, but the nRF Cloud site says “Please connect your device” and no networks appeared in the LTE link Monitor. Below is what is registering on the Terminal in the Link Manager:

I: Connected to LTE network
D: GPS socket created, fd: 1232491587
+CEDRXP: 4,“1001”,“1001”,“0001”
I: CLOUD_EVT_ERROR
E: Socket error: POLLHUP
E: Connection was closed, possibly by cloud
+CSCON: 0

I haven’t tested the GPS in a week so with all that I’ve been experimenting with I don’t know what I may have messed up. These Nordic posts indicate I might need new certificates as mentioned in these two posts:
https://devzone.nordicsemi.com/f/nordic-q-a/62990/cloud_evt_error-in-nrf_cloud_agps
https://devzone.nordicsemi.com/f/nordic-q-a/52801/nrf9160-socket-error-pollhup

What are your thoughts? And if I need new certificates, I’m not sure how to go about this? Or is there some other simple fix?

jaredwolff

SteveD0 if you blew away your certificates, this is possible. It’s also more likely that you erased your device along with any authentication keys saved for nRF Connect Cloud. I would remove the device from nRF Connect Cloud:

Then re-add it using the same PIN number as before. You may have to restart your device using the AGPS firmware and have it connect first before adding the device back with the pin. Let me know if that fixes it.

SteveD0

Finally got it working but it was not straight forward, or at least for me. I might have had some overkill due to my lack of experience, so I wanted to document this to find out what the critical path was if possible to discern from my steps below.
I removed the device from the cloud and then re-added it back. It was successfully added. Started the process over and got the same error. Then I decided to try my 2nd device which I haven’t touched since it last connected. It connected properly.
So then went back to my first device that failed and it failed again. Decided to recompile program and got a FATAL ERROR:… Looked like I was having prj.conf issues from the from the nfed/nrf path so went back to the original nrf_cloud_agps from the non-nfed ( from the original program plain nrf path you provided when we started) path and it recompiled with what seemed to be the correct KiB (if I remember correctly - 190.93). And when I went back to the LTE Link Monitor it was working and same for the nRF Cloud. Yeah! I wrote this detail to help others who might have similar issues.

jaredwolff

SteveD0 glad it’s working. Thanks for the walkthrough!