<?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>RTC precision problem</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/104091/rtc-precision-problem</link><description>In order to perform some application every 1 hour at nRF52832, I set the app_timer(RTC) pre-scaler to be 31. 
 I also use RTC for 3s and 5ms time keeping, but the actual intervals are sometimes lower than 3s and 5ms(for example 2.7s and 4.6ms) 
 Is the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 25 Sep 2023 11:49:29 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/104091/rtc-precision-problem" /><item><title>RE: RTC precision problem</title><link>https://devzone.nordicsemi.com/thread/447458?ContentTypeID=1</link><pubDate>Mon, 25 Sep 2023 11:49:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3a41df3c-e198-429c-bd4f-5d526131fd4a</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The&amp;nbsp;prescaler&amp;nbsp;setting will affect the resolution, but not the accuracy. The accuracy only depends on the LF clock source. If you are using the LFRC, that will be 500 ppm, if calibrated (which happens automatically if you are using the SoftDevice). If you need a better accuracy then that, you will need an 32.768 kHz crystal, and configure that as a clock source. In that case, the accuracy of the RTC and app_timer, will be equal to the accuracy of the crystal.&lt;/p&gt;
&lt;p&gt;Note that the above assumes that you do not introduce any delays in&amp;nbsp; your firmware. For instance, make sure to use &amp;quot;repeated&amp;quot; app timer, and not to re-start a timer in the timeout handler. If you do, you will introduce delays that are not compensated for, that will accumulate over time. If you use a repeated timer, that will not happen as it is handled internally in the library.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>