nRF9160 Feather Tracker Sample + Golioth

angusa

Hi,

Hope you dont mind me digging this up but I seem to be in the same boat, im happy to start a new discussion if you would prefer.

I have been working through your Golioth tutorial and cannot get the board to sucsessfully connect and send data.

I got hung up on warnings about incorrect PSK and PSK-ID and went through a lot of iterations of checking and changing values but now suspect that this may be a red herring!

The log section of interest looks like this: (I hashed out IMEI and Cell ID)
[00:01:17.301,666] <inf> modem: Disconnected [00:01:17.301,757] <inf> modem: LTE cell changed: Cell ID: #######, Tracking area: ##### [00:01:17.301,849] <inf> app_event_manager: Evt: APP_EVENT_CELLULAR_DISCONNECT [00:01:17.345,397] <inf> modem: RRC mode: Connected [00:01:18.434,387] <inf> modem: Network registration status: Connected - roaming [00:01:18.434,783] <inf> app_event_manager: Evt: APP_EVENT_CELLULAR_CONNECTED [00:01:18.434,814] <wrn> golioth_system: Configured PSK-ID is invalid [00:01:18.434,814] <wrn> golioth_system: Configured PSK is invalid [00:01:18.434,906] <inf> golioth_system: Starting connect [00:01:18.435,150] <inf> modem: PSM parameter update: TAU: 10800, Active time: -1 [00:01:18.436,187] <inf> app: IMEI: ############ [00:01:18.436,187] <wrn> golioth_system: Configured PSK-ID is invalid [00:01:18.436,218] <wrn> golioth_system: Configured PSK is invalid [00:01:18.513,854] <inf> modem: Disconnected [00:01:18.514,007] <inf> app_event_manager: Evt: APP_EVENT_CELLULAR_DISCONNECT [00:01:19.799,285] <inf> modem: RRC mode: Idle [00:01:19.871,276] <inf> modem: LTE cell changed: Cell ID: -1, Tracking area: -1 [00:01:22.186,187] <err> golioth: Fail to get address (coap.golioth.io 5684) -11 [00:01:22.186,248] <err> golioth_system: Failed to connect: -11 [00:01:22.186,248] <wrn> golioth_system: Failed to connect: -11 [00:01:27.186,401] <inf> golioth_system: Starting connect

I am using your CircuitDojo nrf9160 board and have just updated modem firmware to 1.3.5 with no change. I used the AT Client sample to set PSK and think it should be correct. I downloaded, moved and built with SUPL and that seemed ok.

I followed above suggestions but with no success. Somewhere in my tinkering, my SIM (included hologram which seems to be sitting on Telefónica UK LTE) seems to have transmitted 20Kbs of data somewhere but nothing yet has registered in Goliath. Hologram does seem to register the SIM session connection.

Is there a way to prove that the problem lies with PSK or another connection problem?

The line:
[00:01:18.435,150] <inf> modem: PSM parameter update: TAU: 10800, Active time: -1
makes me wonder if there is a carrier issue perhaps?

The board is awesome and I am very appreciative of all the work that has gone into the software and support but there is a pretty steep learning curve with this stuff!

cheers
a

jaredwolff

Hi @angusa. Sorry I missed your post. Can you do a git describe --tags in your nfed folder? Golioth’s SDK is a bit finicky and you need a particular hash/checkout for it to work. It should be working on the v2.4.x branch as long as you followed the instructions for loading the PSK into the secure key store.

angusa

Hi Jared, no worries - cheers for the reply.

I am pretty sure I’m on v2.4 but further digging around shows that although the board is showing on the network it looks like its not not registering on the LTE network. Checking my phone shows that I don’t seem to get 4G at my desk - something I probably should have checked!

I plan on trying the board somewhere more likely to have proper coverage tomorrow and will let you know if that’s the only issue - if it is I will feel a little foolish 😉

jaredwolff

That will definitely prevent you from connecting! 🙂

angusa I plan on trying the board somewhere more likely to have proper coverage tomorrow and will let you know if that’s the only issue - if it is I will feel a little foolish 😉

Sounds good. You may need to double check to make sure that Hologram is supported in that area as well. You can double check connection status using the at_client sample and the LTE Link Monitor.