<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>nrf9160 gnss power saving mode</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/115402/nrf9160-gnss-power-saving-mode</link><description>Hi all, 
 I am trying to develop an application that frequently gets location info using gnss and also needs to work with battery. 
 In the Product Specification v2.2 I found that in continuous mode and power saving enabled - the average current consumption</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 30 Oct 2024 09:23:39 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/115402/nrf9160-gnss-power-saving-mode" /><item><title>RE: nrf9160 gnss power saving mode</title><link>https://devzone.nordicsemi.com/thread/508473?ContentTypeID=1</link><pubDate>Wed, 30 Oct 2024 09:23:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1f3b2106-3168-4175-beee-6e70da51b119</guid><dc:creator>Michal</dc:creator><description>&lt;p&gt;I can now confirm that yes, functionality like that requires development on your side. In power saving mode the GNSS only enters duty cycling, when it has a good enough fix.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Michal&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf9160 gnss power saving mode</title><link>https://devzone.nordicsemi.com/thread/507829?ContentTypeID=1</link><pubDate>Thu, 24 Oct 2024 21:56:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e87c2d68-e254-4a47-8f3e-0c2ac3b8f306</guid><dc:creator>Michal</dc:creator><description>&lt;p&gt;Thank you for the answers Vasil.&lt;/p&gt;
&lt;p&gt;I will have to look more into it and check how exactly it is implemented. Worst case there may be some development needed.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Michal&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf9160 gnss power saving mode</title><link>https://devzone.nordicsemi.com/thread/507513?ContentTypeID=1</link><pubDate>Wed, 23 Oct 2024 08:01:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cf424ddf-2d3f-4dfb-aae8-2f4d0c57bcb9</guid><dc:creator>ncvasil</dc:creator><description>[quote userid="114944" url="~/f/nordic-q-a/115402/nrf9160-gnss-power-saving-mode/507431"]&lt;p&gt;So the desired result is for the duty-cycling to timeout after the first fix, right?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;[/quote]
&lt;p&gt;Yes&lt;/p&gt;
[quote userid="114944" url="~/f/nordic-q-a/115402/nrf9160-gnss-power-saving-mode/507431"]But then, should it always timeout if it cannot get the fix in time (and risk potentially never getting a fix), or maybe every nth try it should still try for longer time?[/quote]
&lt;p&gt;The second approach sounds like a better trade-off: we accept getting a fix less frequently and have lower power consumption.&lt;/p&gt;
&lt;p&gt;If that frequency of getting a fix gets too low (like you said - after nth try we fail) - then it is ok to go back to normal continuous mode with higher power consumption.&lt;/p&gt;
&lt;p&gt;That was my understanding while I read this:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/nrfxlib/nrf_modem/doc/gnss_interface.html#power_saving_mode"&gt;https://docs.nordicsemi.com/bundle/ncs-latest/page/nrfxlib/nrf_modem/doc/gnss_interface.html#power_saving_mode&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I could be wrong.&lt;/p&gt;
&lt;p&gt;It would fit very well in my application. because in case there are no healthy satellites (even on cold start, before first fix) for a certain period of time - I will stop the gnss for a while and not waste any energy while the conditions for a fix are not good.&lt;/p&gt;
&lt;p&gt;Hope there is some approach I can use constant (forced) duty-cycling after first fix. Thanks.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vasil&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf9160 gnss power saving mode</title><link>https://devzone.nordicsemi.com/thread/507431?ContentTypeID=1</link><pubDate>Tue, 22 Oct 2024 16:42:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:52e57b03-2be7-461f-ad4c-309ae0d1970c</guid><dc:creator>Michal</dc:creator><description>[quote user="ncvasil"]&lt;span&gt;My question is: is there a way to constantly force the duty-cycling that will give me ~10 mA (after firs fix)? That will probably come at a cost - lowered accuracy I guess, but still it would be acceptable in my case.&lt;/span&gt;[/quote]
&lt;p&gt;So the desired result is for the duty-cycling to timeout after the first fix, right?&lt;/p&gt;
&lt;p&gt;But then, should it always timeout if it cannot get the fix in time (and risk potentially never getting a fix), or maybe every nth try it should still try for longer time?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf9160 gnss power saving mode</title><link>https://devzone.nordicsemi.com/thread/507147?ContentTypeID=1</link><pubDate>Mon, 21 Oct 2024 13:06:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:15c8a468-3921-4edf-aeb8-db781efdd30b</guid><dc:creator>ncvasil</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;span&gt;Michal,&lt;/span&gt;&lt;/p&gt;
[quote userid="114944" url="~/f/nordic-q-a/115402/nrf9160-gnss-power-saving-mode/506765"]I assume that you are only testing this inside? What happens if you would for example put the device outside (for example outside the window)?[/quote]
&lt;p&gt;&lt;span&gt;The nRF9160dk is indoors, but right by the window.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;After the application &amp;quot;cellular/gnss&amp;quot; boots up (continuous mode and&amp;nbsp;power saving enabled as described above) the average consumption hovers around 40mA - I guess it is due to the constant listening and downloading the necessary data from the satellites.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Since the dk board is close to a window - it has little trouble getting first fix - a few seconds to a minute.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Observing the uart output I get a fix every second from this moment on (still indoors, close to window) and the current consumption is 40mA on average, and very rarely dropping down to 1-2 mA (when this happens, the uart log also displays &amp;quot;Sleep period(s) between PVT notifications&amp;quot; as expected)&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;However, if I handle the dk board and move it no more than 1 meter, slightly outside the window - then it gets the best &amp;#39;view&amp;#39; of the satellites and the consumption drops as expected (5-6 seconds it is 1-2 mA, 1-2 seconds it goes back to 40 mA, around 10 mA on average) which is great.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;In both cases I get a fix. And only when the conditions are perfect - I also get the desired ~10 mA consumption.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;My question is: is there a way to constantly force the duty-cycling that will give me ~10 mA (after firs fix)? That will probably come at a cost - lowered accuracy I guess, but still it would be acceptable in my case.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;NOTE: I also tried to use &amp;quot;A-GNSS&amp;quot; in order to minimize the satellite communication but the result was the same.&lt;/span&gt;&lt;/p&gt;
[quote userid="114944" url="~/f/nordic-q-a/115402/nrf9160-gnss-power-saving-mode/506765"]I wonder if it&amp;#39;s behaving like this, because it takes so long to get a GNSS fix while inside.[/quote]
&lt;p&gt;&lt;span&gt;After the device obtains first fix - the consumption remains high ~40 mA - I get a fix every second, but the consumption is ~40 mA. Only in perfect conditions the consumption drops down - but I am ok to have &amp;#39;close to perfect&amp;#39; conditions and get a lower accuracy fix, as long as the current consumption is low.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vasil&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf9160 gnss power saving mode</title><link>https://devzone.nordicsemi.com/thread/506765?ContentTypeID=1</link><pubDate>Thu, 17 Oct 2024 15:34:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5012eeef-01e2-41e0-9f85-84c517dd09ee</guid><dc:creator>Michal</dc:creator><description>&lt;p&gt;Hello Vasil,&lt;/p&gt;
&lt;p&gt;I took over the case from my colleague Simon.&lt;/p&gt;
&lt;p&gt;I assume that you are only testing this inside? What happens if you would for example put the device outside (for example outside the window)?&lt;/p&gt;
&lt;p&gt;I wonder if it&amp;#39;s behaving like this, because it takes so long to get a GNSS fix while inside.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Michal&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf9160 gnss power saving mode</title><link>https://devzone.nordicsemi.com/thread/505894?ContentTypeID=1</link><pubDate>Fri, 11 Oct 2024 13:03:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:aadbc0f4-013b-4538-a474-55e939fc3b03</guid><dc:creator>ncvasil</dc:creator><description>&lt;p&gt;Hi, Simon,&lt;/p&gt;
&lt;p&gt;Yes, I made sure that the changes from the Kconfig are saved to prj.conf and then rebuild. The&amp;nbsp;&lt;/p&gt;
&lt;div&gt;
&lt;div&gt;&lt;span&gt;&lt;span&gt;nrf_modem_gnss_power_mode_set(...) gets called with parameter&amp;nbsp;&lt;/span&gt;&lt;/span&gt;
&lt;div&gt;
&lt;div&gt;&lt;span&gt;NRF_MODEM_GNSS_PSM_DUTY_CYCLING_POWER.&lt;/span&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;p&gt;I tried that on &lt;span&gt;nRF Connect SDK&lt;/span&gt; v2.5.0 and v2.6.2 - same result: current consumption is around 40mA before first fix and remains the same after the first fix - no change. I left it like that for a few minutes - no change (while it keeps getting more fixes from satellites).&lt;/p&gt;
&lt;p&gt;The LTE is not used, only GNSS, so I can&amp;#39;t see what else can draw current.&lt;br /&gt;&lt;br /&gt;EDIT: After leaving it on for a while, I noticed that very rarely the consumption drops to 1-2 mA and in the serial terminal I see the message &amp;quot;Sleep period(s) between PVT notifications&amp;quot; which means that indeed the duty-cycling is engaged, but it happens very rarely. For example the consumption stays around 40 mA for 20-30 seconds, then drops below 10mA for 3-4 seconds and so on. But definitely the average consumption for the whole period is closer to 40mA.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vasil&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf9160 gnss power saving mode</title><link>https://devzone.nordicsemi.com/thread/505870?ContentTypeID=1</link><pubDate>Fri, 11 Oct 2024 11:11:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4725a904-333e-4c26-8175-d3296356cda2</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Did you make sure to do a pristine build after enabling the power saving mode? Also, what nRF Connect SDK version are you using here, so I can do a test on my end? Is the initial fix completed or do you just measure the current consumption initially? As i think the current consumption here refers to the tracking after an initial fix has been established.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>