GPS timeout and interval (with SUPL A-GPS)

RE: GPS timeout and interval (with SUPL A-GPS)

Øyvind — Tue, 12 Oct 2021 09:32:29 GMT

Hello mbytelab, please register a new ticket with your issue. This way we can track issues regarding GPS.

Thank you.

Kind regards,
Øyvind

RE: GPS timeout and interval (with SUPL A-GPS)

mbytelab — Mon, 11 Oct 2021 14:26:33 GMT

I have same issue as pemar13.

I am using modem firmware v1.2.3 and NCS v1.6.0. Event GPS_EVT_SEARCH_TIMEOUT never occurs. I am using GPS driver (no new GNSS library). It works fine when using NCS v1.5.1.

Anyone found fix?

RE: GPS timeout and interval (with SUPL A-GPS)

Øyvind — Thu, 26 Aug 2021 20:15:30 GMT

Hi Per,

Have a look at nrfxlib\nrf_modem\include\nrf_modem_gnss.h. NRF_MODEM_GNSS_EVT_SLEEP_AFTER_TIMEOUT is only supported in modem fw 1.2.3:

/** @brief GNSS enters sleep because fix retry timeout was reached in periodic or single fix mode.
 *
 * @details This event doesn't have any payload.
 *
 * @note This event is only supported by modem firmware v1.3.0 or later.
 */
#define NRF_MODEM_GNSS_EVT_SLEEP_AFTER_TIMEOUT 8

There are several functions that only supported by v1.3.0. If the new GNSS library does not fit your needs, we will need to look into your needs in a new support ticket.

Kind regards,
Øyvind

RE: GPS timeout and interval (with SUPL A-GPS)

pemar13 — Thu, 26 Aug 2021 13:24:51 GMT

Hi again!

I have now also tested the gps sample, which uses the new GNSS library.

Also when using this sample in single-fix mode with modem FW 1.3.0, I can set the timeout AND I receive the event NRF_MODEM_GNSS_EVT_SLEEP_AFTER_TIMEOUT as expected. However, I cannot set the timeout when using modem FW v1.2.3. This is a problem.

Have I understood the following correctly:

1. For the new GNSS library, the event NRF_MODEM_GNSS_EVT_SLEEP_AFTER_TIMEOUT will NOT occur when using modem FW v1.2.3 despite that the old driver had the event GPS_EVT_SEARCH_TIMEOUT.

2. The new GNSS library has no equivalent to the old GPS_EVT_SEARCH_STARTED for single-fix mode.

3. Just as the old driver, the new GNSS library has no equivalent to the event GPS_EVT_SEARCH_STARTED for continuous mode.

For us, the GPS_EVT_SEARCH_STARTED, _STOPPED, and _TIMEOUT are very important to control the flow of events in a multithreaded application. Is there another way of knowing that these events occurred?

Best regards,
Per

RE: GPS timeout and interval (with SUPL A-GPS)

Øyvind — Wed, 25 Aug 2021 10:42:56 GMT

Hi Per,

[quote user="pemar13"]Maybe this should be rephrased using your words like "This section shows which which modem firmware versions have been tested with different versions of nRF Connect SDK",[/quote]

Noted. I will forward this feedback to the responsible person.

[quote user="pemar13"]Am I interpreting your above statements correctly in that you recommend using the methodology from the gps sample (i.e., using the new GNSS library) rather than the old GPS driver?[/quote]

Yes, that is correct, but as mentioned, the mfw 1.2.3 is not tested with NCS v1.6.1, so we cannot guarantee all functionality. As long as it works for your application, then it's OK.

Kind regards,
Øyvind

RE: GPS timeout and interval (with SUPL A-GPS)

pemar13 — Tue, 24 Aug 2021 15:57:15 GMT

Hi Öyvind!

Many thanks for the quick response!

[quote userid="77062" url="~/f/nordic-q-a/78657/gps-timeout-and-interval-with-supl-a-gps/326397#326397"]"See Modem firmware compatibility matrix for an overview of which modem firmware versions have been tested with this version of nRF Connect SDK."[/quote]

I guess I was mislead by the table's preable "This section shows compatibility between nRF9160 modem firmware and nRF Connect SDK versions", possibly overinterpreting the word "compatibility". Maybe this should be rephrased using your words like "This section shows which which modem firmware versions have been tested with different versions of nRF Connect SDK", which, to me, has a much less stringent meaning.

[quote userid="77062" url="~/f/nordic-q-a/78657/gps-timeout-and-interval-with-supl-a-gps/326397#326397"]Are you testing with the GPS sample or your application?[/quote]

I am using the nRF9160 agps sample. Am I interpreting your above statements correctly in that you recommend using the methodology from the gps sample (i.e., using the new GNSS library) rather than the old GPS driver? In that case, an upgrade of our code to ncs v1.6.1 using the GNSS library with modem 1.2.3 for B0 and 1.3.0 for B1 would seem like the best way forward for us.

Edit: This seems related to the modem FW version. With 1.3.0 the timeout works fine in single-fix mode, but not with 1.2.3.

Best regards,

Per

RE: GPS timeout and interval (with SUPL A-GPS)

Øyvind — Tue, 24 Aug 2021 14:06:40 GMT

Hi Per,

[quote user="pemar13"]I "hijack" this thread as I am becoming increasingly confused about how to update our application and custom board to achieve better GPS performance and stay up to date with Nordic's "API" development.[/quote]

I'm really sorry to hear that you are getting increasingly confused, I hope that we can clear the confusion. You can also respond to the thread/answer with me in ticket 264436.

[quote user="pemar13"]

Your compatibility matrix has now been updated, but it is not clear to me how it should be read. I read it "both ways", i.e.,

"Modem FW 1.3.0 REQUIRES 1.60 - 1.61 while Modem FW 1.2.3 REQUIRES 1.40 -1.5.1"

[/quote]

Where did you find these requirements? As it states "This section shows compatibility between nRF9160 modem firmware and nRF Connect SDK versions", and as stated in the nRF Connect SDK release notes, under supported modem firmware:

"See Modem firmware compatibility matrix for an overview of which modem firmware versions have been tested with this version of nRF Connect SDK."

We have tested the latest version of the nRF Connect SDK v1.6.0 towards modem fw 1.3.0, that does not mean it is required, it means that we have not tested latest NCS with modem fw versions below 1.3.0.

[quote user="pemar13"]This is rather crucial, since we are in production with custom boards with nRF9160 revision B0 and will start producing boards with nRF9160 revision B1, especially since your modem download page states that modem FW 1.3.0 must ONLY be used for production with revision B1.[/quote]

Yes, that is correct, the modem fw 1.3.0 is targeted nRF9160 SiP Revision 2 as per the release notes. If you have any concerns regarding this switch from B0 to B1, please do not hesitate to contact your local RSM who should be able to provide more answers.

That said, I cannot guarantee that NCS v1.3.2 will work with modem fw 1.3.0 you will need to test this yourself.

[quote user="pemar13"]2. Also, when you mention forthcoming bug fixes in the modem FW, can we expect a modem FW version 1.2.4 that works as expected using revision B0?[/quote]

I'm afraid I do not have those details. Please ask your RSM.

[quote user="pemar13"]Finally, using the "old" GPS driver with ncs 1.6.1 and modem 1.2.3, I don't get any GPS_EVT_SEARCH_TIMEOUT using single-fix or periodic mode. Is this as expected or just me (this worked fine with ncs 1.3.2)[/quote]

Are you testing with the GPS sample or your application?

Kind regards,
Øyvind

RE: GPS timeout and interval (with SUPL A-GPS)

pemar13 — Tue, 24 Aug 2021 12:29:35 GMT

Hi Öyvind,

I "hijack" this thread as I am becoming increasingly confused about how to update our application and custom board to achieve better GPS performance and stay up to date with Nordic's "API" development.

I recently had this exchange with Håkon. Your compatibility matrix has now been updated, but it is not clear to me how it should be read. I read it "both ways", i.e.,

"Modem FW 1.3.0 REQUIRES 1.60 - 1.61 while Modem FW 1.2.3 REQUIRES 1.40 -1.5.1"

but this is neither in agreement with your statement above or with the fact that we have successfully used modem FW 1.2.3 with ncs 1.3.2 (following your suggestion here).

This is rather crucial, since we are in production with custom boards with nRF9160 revision B0 and will start producing boards with nRF9160 revision B1, especially since your modem download page states that modem FW 1.3.0 must ONLY be used for production with revision B1.

1. I hope you can clarify this.

2. Also, when you mention forthcoming bug fixes in the modem FW, can we expect a modem FW version 1.2.4 that works as expected using revision B0?

3. Finally, using the "old" GPS driver with ncs 1.6.1 and modem 1.2.3, I don't get any GPS_EVT_SEARCH_TIMEOUT using single-fix or periodic mode. Is this as expected or just me (this worked fine with ncs 1.3.2)

Best regards,

Per

RE: GPS timeout and interval (with SUPL A-GPS)

anicare-tero — Fri, 20 Aug 2021 09:42:08 GMT

[quote userid="77062" url="~/f/nordic-q-a/78657/gps-timeout-and-interval-with-supl-a-gps/325887#325887"]Unfortunately, the problem is not in the GPS driver but in the modem firmware itself.[/quote]

That's good to know you have located the problem.

[quote userid="77062" url="~/f/nordic-q-a/78657/gps-timeout-and-interval-with-supl-a-gps/325887#325887"]This is a bug that our team is aware of, and are currently working on a fix.[/quote]

I heard there would be coming out some "sleep bug fix". Not sure if it repairs this issue but I hope so.

RE: GPS timeout and interval (with SUPL A-GPS)

Øyvind — Fri, 20 Aug 2021 09:30:38 GMT

Hi anicare-tero,

[quote user="ziirou"]As long as there is that "SHOULD support or SHOULD work" with the GNSS API with modem fw 1.2.3, it's not an option for us to move from GPS driver to GNSS API.[/quote]

Sorry, the correct wording is:

/** @brief GNSS woke up in periodic mode.
 *
 * @details This event is sent when GNSS receiver is turned on in periodic mode. This happens when
 *          GNSS starts acquiring the next periodic fix but also when a scheduled download starts.
 *
 * This event doesn't have any payload.
 *
 * @note This event is only supported by modem firmware v1.3.0 or later.
 */
#define NRF_MODEM_GNSS_EVT_PERIODIC_WAKEUP     7

"...only supported by modem firmware v1.3.0 or later." Meaning that it works with 1.2.3, however, some features are only available for mfw 1.3.0.

But I fully understand that you do not want to move to this yet.

[quote user="ziirou"]Is the reason of this bug known?[/quote]

Have been talking to our nRF91 team to figure out what to do. Unfortunately, the problem is not in the GPS driver but in the modem firmware itself. This is a bug that our team is aware of, and are currently working on a fix. The problem is the scheduled download logic which will perform the download regardless of the interval set. The current version of the modem fw does not allow to disable the scheduled downloads which would be the solution to use with A-GPS. This means that the periodic mode of GNSS is unfortunately not functioning as intended. Thus, we encourage customers to use GNSS in single fix or continuous mode until a fix is introduced.

RE: GPS timeout and interval (with SUPL A-GPS)

anicare-tero — Fri, 20 Aug 2021 05:30:57 GMT

Hi Øyvind,

Is there any fix for GPS driver for this issue?

Is the reason of this bug known?

As long as there is that "SHOULD support or SHOULD work" with the GNSS API with modem fw 1.2.3, it's not an option for us to move from GPS driver to GNSS API.

RE: GPS timeout and interval (with SUPL A-GPS)

Øyvind — Thu, 19 Aug 2021 12:42:26 GMT

Hi anicare-tero,

[quote user="ziirou"]Already updated that earlier.[/quote]

Yes, that is true. I forgot that detail earlier today.

[quote user="ziirou"]

So you suggest to stop using the GPS driver and to move to GNSS API? That would need a lot of work.

[/quote]

No, I'm asking if it helps to use this to test the stability of the GPS.

[quote user="ziirou"]Take the master branch of the SDK since we need a confirmed stable SDK as we are already in production.[/quote]

The link I provided to GNSS API in my last comment is from NCS v1.6.1.

[quote user="ziirou"]Use modem FW 1.3.0 since we have still B0 revisions and our devices have modem FW 1.2.3 which is not updatable to 1.3.0.[/quote]

That is OK. The new GNSS API should support mfw 1.2.3 as well. Some features are marked to work only with mfw 1.3.0, but the rest should work.

Kind regards,
Øyvind

RE: GPS timeout and interval (with SUPL A-GPS)

anicare-tero — Thu, 19 Aug 2021 09:54:31 GMT

Hi Øyvind,

[quote userid="77062" url="~/f/nordic-q-a/78657/gps-timeout-and-interval-with-supl-a-gps/325667#325667"]Also, please note that the SUPL library is now available as v 0.7.1[/quote][quote userid="83406" url="~/f/nordic-q-a/78657/gps-timeout-and-interval-with-supl-a-gps/325261#325261"]Just FYI: I updated the SUPL client library to version v0.7.1 and disabled FPU from project configuration.[/quote]

Already updated that earlier.

[quote userid="77062" url="~/f/nordic-q-a/78657/gps-timeout-and-interval-with-supl-a-gps/325667#325667"]There is a new GNSS API developed to improve usability of the GNSS, and to move away from the GPS driver.[/quote]

So you suggest to stop using the GPS driver and to move to GNSS API? That would need a lot of work.

Things I can't do now:

Take the master branch of the SDK since we need a confirmed stable SDK as we are already in production.
Use modem FW 1.3.0 since we have still B0 revisions and our devices have modem FW 1.2.3 which is not updatable to 1.3.0.

I really need this bug to be fixed and it kind of should be for the GPS driver.

Why is the A-GPS breaking those timeouts and intervals?

RE: GPS timeout and interval (with SUPL A-GPS)

Øyvind — Thu, 19 Aug 2021 09:10:18 GMT

Hi Tero,

Sorry for the delayed answer. I've talked to our development team regarding the GNSS.

[quote user="ziirou"]What those "@deprecated since v1.2.0." lines means?[/quote]

There is a new GNSS API developed to improve usability of the GNSS, and to move away from the GPS driver. This can be used with modem FW 1.2.3, but will improve usability on mfw 1.3.0. Currently, the GPS sample has been updated with this, while there is still ongoing work to introduce more imrprovement.
https://github.com/nrfconnect/sdk-nrfxlib/blob/100872a0e1052931c4bad505e709a92912d4743b/nrf_modem/include/nrf_modem_gnss.h

Also, please note that the SUPL library is now available as v 0.7.1

SUPL client library v0.7.1
Changelog:

Added soft-float build of the library.
Fixed cell ID encoding in the sent request, so that the server can determine the location of the device and send a reference location back to the device. The MCC table is used as a fall back in case no reference location is received from the server.
Reference location is now only injected if it was requested.
Fixed usage of an IPv6 address as the device ID.
Removed the dependency to the modem library (modemlib). This version works with both modem and old bsdlib (sdk-nrfxlib/bsdlib) library.

RE: GPS timeout and interval (with SUPL A-GPS)

anicare-tero — Wed, 18 Aug 2021 14:08:59 GMT

For now, I have tested these:

/* WORKING 3+3min */
		.timeout = 180,
		.interval = 180 + 180,

/* WORKING 3+5min */
		.timeout = 180,
		.interval = 180 + 300,

/* WORKING 3+7min */
		.timeout = 180,
		.interval = 180 + 420,

/* WORKING 3+8min */
		.timeout = 180,
		.interval = 180 + 480,

/* NOT WORKING 3+9min */
		.timeout = 180,
		.interval = 180 + 540,

/* NOT WORKING 3+10min */
		.timeout = 180,
		.interval = 180 + 600,

/* NOT WORKING 3+15min */
		.timeout = 180,
		.interval = 180 + 900,

/* NOT WORKING 3+20min */
		.timeout = 180,
		.interval = 180 + 1200,

I will test more tomorrow.

RE: GPS timeout and interval (with SUPL A-GPS)

anicare-tero — Wed, 18 Aug 2021 12:01:49 GMT

I'm still finding values which are working.

But I find something in nrf_socket.h:

/**@brief Defines the interval between each fix in seconds.
 * @details Allowed values are 0, 1, 10..1800, value 0 denotes single fix.
 *          Default interval is 1 second (continous mode), 0 denotes a single fix.
 * @deprecated since v1.2.0.
 */
typedef uint16_t nrf_gnss_fix_interval_t;

/**@brief Defines how long (in seconds) the receiver should try to get a fix.
 * @details The default retry wait time is 60 seconds before it gives up.
 *          0 denotes an infinite limit.
 * @deprecated since v1.2.0.
 */
typedef uint16_t nrf_gnss_fix_retry_t;

It seems that 1800 seconds should be the maximum allowed value for interval. So my value (180+1200) should be allowed there.

What those "@deprecated since v1.2.0." lines means? Those should not work anymore or? And what's that version, modem FW or SDK?

The nRF9160 GPS driver is still using that nrf_gnss_fix_interval_t on its nrf9160_gps_config structure.

I got to say I'm really confused with this issue.

RE: GPS timeout and interval (with SUPL A-GPS)

anicare-tero — Wed, 18 Aug 2021 07:46:40 GMT

Hi Øyvind,

After a short testing of the A-GPS sample, I saw the same behavior when using the same timeout and interval values as I do have in my own project. The defaults (timeout 120 and interval 240) worked properly but when I changed the timeout to 180 and the interval to 180+1200 it's failing again.

I will test that more and try to see what is the thing there that causes that unexpected behavior.

Is there any maximum values that timeout or interval could be? At least I haven't see any.

RE: GPS timeout and interval (with SUPL A-GPS)

anicare-tero — Tue, 17 Aug 2021 13:46:29 GMT

Hi Øyvind,

[quote userid="77062" url="~/f/nordic-q-a/78657/gps-timeout-and-interval-with-supl-a-gps/325325#325325"]Did your last comment make it better, worse or no change?[/quote]

There was no change.

[quote userid="77062" url="~/f/nordic-q-a/78657/gps-timeout-and-interval-with-supl-a-gps/325325#325325"]Have you tested the A-GPS sample, to verify behavior? You should look at this sample for the correct usage.[/quote]

I have tested that sample earlier. I don't see any bigger changes on the code side between the sample and our project. But I will remove the cloud stuff from the sample and then will test it again.

RE: GPS timeout and interval (with SUPL A-GPS)

Øyvind — Tue, 17 Aug 2021 13:35:26 GMT

Hi Tero,

Did your last comment make it better, worse or no change? Have you tested the A-GPS sample, to verify behavior? You should look at this sample for the correct usage.

Kind regards,
Øyvind

RE: GPS timeout and interval (with SUPL A-GPS)

anicare-tero — Tue, 17 Aug 2021 10:14:56 GMT

Just FYI: I updated the SUPL client library to version v0.7.1 and disabled FPU from project configuration.