Prioritize sending data when trying to get a fix with GNSS

Hi! I am using nrf connect sdk 2.6.1 and modem firmware 1.3.7 on a nrf9160.

I have an application where i need to try to get a fix on a set interval and also sometimes transmit sensor data over LTE.
I want LTE operations to be prioritized so that if i need to send the sensor data it happens as quickly as possible.
I have noticed that it can take up to 13 seconds before the data is actually sent, is there anyway to make it faster? 

Parents
  • I have managed to send the data much faster by calling:

    nrf_modem_gnss_stop();

    before publishing the data, and then after waiting for 2 seconds i call:
    nrf_modem_gnss_start();

    Which restarts the searching for fix.

    But perhaps there is a better way to do it without having to stop and restart the seach from scratch?

  • Hi,

    Unfortunately, there isn't a way mentioned in our docs to  "pause" GNSS and later resume without restarting it. The GNSS API only has start and stop. To minimize the impact of stopping, you can use A-GNSS or P-GNSS in order to ensure faster restarts. To make sure that GNSS is not running more than needed between your send windows, you can select an operation mode (fix interval/ retry) which matches your pattern. 

    Best Regards,

    Samruddhi

Reply
  • Hi,

    Unfortunately, there isn't a way mentioned in our docs to  "pause" GNSS and later resume without restarting it. The GNSS API only has start and stop. To minimize the impact of stopping, you can use A-GNSS or P-GNSS in order to ensure faster restarts. To make sure that GNSS is not running more than needed between your send windows, you can select an operation mode (fix interval/ retry) which matches your pattern. 

    Best Regards,

    Samruddhi

Children
No Data
Related