Different approaches in making an asset tracker on nRF9160

RE: Different approaches in making an asset tracker on nRF9160

Simonr — Wed, 04 Jan 2023 09:15:58 GMT

There is just a "normal" and "low" accuracy specifically in the GNSS interface, that is true, but you can tweak (increase) its run time to achieve similar accuracy as to what the location library provides.

Best regards,

Simon

RE: Different approaches in making an asset tracker on nRF9160

Torje — Wed, 04 Jan 2023 07:40:00 GMT

Hi again,

I was under the impression that the accuracy from gnss interface was "normal", and a "high accuracy" was implemented in the Location lib by letting it run for longer. If this is incorrect, then I'm very happy by using the GNSS interface already.

Thank you for assisting me in this, and for clarifying on my initial request. Sometimes you can't see the wood for the trees.

Kind regards,

Torje

RE: Different approaches in making an asset tracker on nRF9160

Simonr — Wed, 04 Jan 2023 07:32:27 GMT

Using the GNSS interface library by itself would be the way to go if you don't want the location library I think, as it uses the high GNSS accuracy by default, with the option to go to low acc. if relevant. The GNSS sample project uses the GNSS interface alone, so you can look at that for reference.

Best regards,

Simon

RE: Different approaches in making an asset tracker on nRF9160

Torje — Tue, 03 Jan 2023 14:01:33 GMT

Hello Simon,

And thank you for replying, and for confirming my understanding.

Allow me to do a follow up question: Do you know of a method of choosing higher gnss accuracy without using the Location library? I've played with the though of selecting "continuous mode" and just let it run a bit after the first fix is produced, but perhaps there are some more elegant solutions to this?

Thanks again,

Torje

RE: Different approaches in making an asset tracker on nRF9160

Simonr — Tue, 03 Jan 2023 13:56:24 GMT

Hi Torje

I think you have got it correctly, as the location library provides a "full package" with a compact API and a location core that handles functionality independent of the location method used. Depending on your preference you might want a more "bare bones" library letting you decide exactly what is returned and not, and the GNSS interface API is part of the location library, so it can't be used "together" with it I'm afraid, nor is the location library designed to be combined with other approaches AFAIK.

I'm not sure I'm able to elaborate any better on the location library than what the documentation itself provides.

Best regards,

Simon