simple tracker nrf9160 COAP connection error

[kevin22319]

Hello,

I am currently going through the simple tracker solution on the Nordic cellular training and getting a bit stuck on the application.

Could you assist me on the below issue?

I am getting GNSS data and sending it to a COAP server without issues.

I can see that the network is attaching and the messages are sent to the server as well.

However, when I try to access the gps data on the simple tracker page I get a COAP connection error. 

I’m not too sure why I’m getting the error. I also tried to change up the URL but no luck.

The server details should be directed to the host site “californium.eclipseprojects.io” with the device name being "cali.all.nrftest".

I am using the Onomondo SIM if it makes any difference.

Also, I want to see if I could add an external GNSS antenna, is there a way I can set the device so that it uses the external GNSS antenna rather than the internal one?

I have connected an external antenna to the UFL connector, but it looks to be using an internal antenna rather than the external one.

I was just wondering if there is anything I would have to do to change the software to use the external antenna.

 

Any help would be appreciated and please let me know if you need any other information from me.

Screenshots:

the screenshot is done without the GPS fix but I have tested with the same result after fixing GPSnrf91_simple_tracker.zip

[Amanda Hsieh]

Hi, 

However, when I try to access the gps data on the simple tracker page I get a COAP connection error. 

I am checking with the team for your issue and will reply later. 

I want to see if I could add an external GNSS antenna, is there a way I can set the device so that it uses the external GNSS antenna rather than the internal one?

If you want to  use an external GNSS antenna, please add the following configuration: CONFIG_MODEM_ANTENNA_GNSS_EXTERNAL to select an external GNSS antenna.

Regards,
Amanda H.

[Achim Kraus]

> The server details should be directed to the host site “californium.eclipseprojects.io” with the device name being "cali.all.nrftest".

Does your "cali.all.nrftest" device send the data to that server? Your data is there.

</echo/cali.all.nrftest>
    ct:    0
    obs:    
    scheme:    coaps
    time:    21.Jun-05:05:55


0.000000,0.000000
0.0 m
0000-00-00 00:00:00

> However, when I try to access the gps data on the simple tracker page I get a COAP connection error. 

I don't know this "nRF91 Simple Tracker". Please provide me link, then I will check what happens on “californium.eclipseprojects.io” when using that tool.

[Achim Kraus]

I found the https://az-app-nordicacademy-nonprod.azurewebsites.net/ service.

Testing with your device "cali.all.nrftest" fails, but if you use a device with GPS positions, it's succeeds.

I guess, only the error text "CoAP Connection Error" is wrong, it should be more something as "No valid position".

cali.all.nrftest.pcap.gz

The capture also shows, that the GET is successful, but returns an invalid position.

[Amanda Hsieh]

Hi kevin22319, 

Does this issue get solved? When we input your resource URI (coaps://californium.eclipseprojects.io/echo/cali.all.nrftest) on the website, we can get the location without error now. so it looks like this issue was solved. Please help confirm it. Thanks. 

-Amanda H.

[Achim Kraus]

> we can get the location without error now.

Yes, because now the device reports a position

-36.750813,174.713177
11.2 m
2023-06-26 01:59:48

Anyway, I'm not sure, if this is worth to be fixed, but reporting a "CoAP Connection Error" in the case the GPS position is missing is at least irritating.

AFAIK Nordic launched a own service support for CoAP. If so, I guess, this usage of the Californium sandbox will change. If it's not considered to change, I miss at least a simple statement, that the data sent to "californium.eclipseprojects.io" is public to all users. That protocol sandbox is intended to run 

"the test specification for the ETSI IoT CoAP Plugtests, London, UK, 7--9 Mar 2014."

and usually "Hello world" is sent. If something else, e.g. a GPS position, is sent, I think, it's worth to mention, that everyone can read that position.