<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://test-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>Deviation of nRF9160DK GNSS measurement result</title><link>https://test-devzone.nordicsemi.com/f/nordic-q-a/89003/deviation-of-nrf9160dk-gnss-measurement-result</link><description>When using the distance measurement function newly added to the reference point by THE GNSS routine of NCS V2.0.0, it is found that each measurement has a deviation of 30 ~ 60m. What is the cause of the deviation and how to solve it</description><dc:language>en-US</dc:language><generator>Telligent Community 13 Non-Production</generator><lastBuildDate>Thu, 16 Jun 2022 08:32:54 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://test-devzone.nordicsemi.com/f/nordic-q-a/89003/deviation-of-nrf9160dk-gnss-measurement-result" /><item><title>RE: Deviation of nRF9160DK GNSS measurement result</title><link>https://test-devzone.nordicsemi.com/thread/372735?ContentTypeID=1</link><pubDate>Thu, 16 Jun 2022 08:32:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f08602a3-2ed2-4532-92ea-c0e8f0e733f5</guid><dc:creator>user2115</dc:creator><description>&lt;p&gt;No problem, happy to help!&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Deviation of nRF9160DK GNSS measurement result</title><link>https://test-devzone.nordicsemi.com/thread/372682?ContentTypeID=1</link><pubDate>Thu, 16 Jun 2022 01:08:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:950d71ff-32f1-4ed7-8862-ea978ac772f7</guid><dc:creator>user116982</dc:creator><description>&lt;p&gt;thx&lt;span class="emoticon" data-url="https://test-devzone.nordicsemi.com/cfs-file/__key/system/emoji/1f604.svg" title="Smile"&gt;&amp;#x1f604;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Deviation of nRF9160DK GNSS measurement result</title><link>https://test-devzone.nordicsemi.com/thread/372633?ContentTypeID=1</link><pubDate>Wed, 15 Jun 2022 15:12:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9c646d07-9e16-41fc-8215-484b4398866e</guid><dc:creator>user2115</dc:creator><description>&lt;p&gt;If you are only tracking the bare minimum amount of satellites to obtain a fix, then yes.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Deviation of nRF9160DK GNSS measurement result</title><link>https://test-devzone.nordicsemi.com/thread/372627?ContentTypeID=1</link><pubDate>Wed, 15 Jun 2022 14:55:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9679e595-5f64-439b-a837-826aad0d6e8c</guid><dc:creator>user116982</dc:creator><description>&lt;p&gt;&lt;span&gt;Is the range of deviations reasonable&lt;span class="emoticon" data-url="https://test-devzone.nordicsemi.com/cfs-file/__key/system/emoji/1f615.svg" title="Confused"&gt;&amp;#x1f615;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Deviation of nRF9160DK GNSS measurement result</title><link>https://test-devzone.nordicsemi.com/thread/372613?ContentTypeID=1</link><pubDate>Wed, 15 Jun 2022 14:24:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:eba29250-87ee-48b0-b37c-10bfbcaec0a8</guid><dc:creator>user2115</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;A deviation is to be expected, especially if the dilution of precision is high in the initial fix.&lt;/p&gt;
&lt;p&gt;You can calculate the GDOP (by squaring tdop+pdop) as described here:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://en.wikipedia.org/wiki/Dilution_of_precision_(navigation)"&gt;https://en.wikipedia.org/wiki/Dilution_of_precision_(navigation)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Here&amp;#39;s the *dop members in the pvt frame:&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.0.0/nrfxlib/nrf_modem/doc/api.html#c.nrf_modem_gnss_pvt_data_frame.pdop"&gt;https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.0.0/nrfxlib/nrf_modem/doc/api.html#c.nrf_modem_gnss_pvt_data_frame.pdop&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;And then add a limit for your wanted total DOP in your own application.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Easier alternative: You can let the GNSS run for a longer time period after getting a fix, by for instance filtering on the&amp;nbsp;.accuracy field:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.0.0/nrfxlib/nrf_modem/doc/api.html#c.nrf_modem_gnss_pvt_data_frame.accuracy"&gt;https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.0.0/nrfxlib/nrf_modem/doc/api.html#c.nrf_modem_gnss_pvt_data_frame.accuracy&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;PS: also make sure you&amp;#39;re not in low accuracy mode:&amp;nbsp;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.0.0/nrfxlib/nrf_modem/doc/gnss_interface.html#low-accuracy-mode"&gt;https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.0.0/nrfxlib/nrf_modem/doc/gnss_interface.html#low-accuracy-mode&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>