<?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 Time drift on NRF9151 chip set.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/125061/rtc-time-drift-on-nrf9151-chip-set</link><description>Hello, 
 My name is Jeon. I am using the RTC function on a custom board that utilizes the same chipset as the nRF9151. I have configured the RTC to trigger an alarm every 20 minutes in order to send MQTT messages to my database. Under normal conditions</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sun, 19 Oct 2025 14:09:55 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/125061/rtc-time-drift-on-nrf9151-chip-set" /><item><title>RE: RTC Time drift on NRF9151 chip set.</title><link>https://devzone.nordicsemi.com/thread/551875?ContentTypeID=1</link><pubDate>Sun, 19 Oct 2025 14:09:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fa587cf9-854a-4c00-83a7-31a207ffc8c4</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I went through your attached project for second pair of eyes and I am confused the way you are using different clock features.&lt;/p&gt;
&lt;p&gt;When you print timestamps&amp;nbsp;using the library functions like date_time_now() or time(), you are actually showing wall-clock time, not RTC time. Wall clock is different than the RTC counter time. So if the modem receives a more accurate time fix (for example, after being offline or in PSM), your log shows a sudden shift.&amp;nbsp;When logging, it is best to print both values (RTC ticks or k_uptime_get() and date_time_now()) to clearly&amp;nbsp;see whether this is the confusion where the alarms are drifting or not. Even after printing these two separately and if you still see drift in both date time and RTC time, then the source is that RTC is drifting. So it is the clock that is sourced to RTC that should be drifting then.&lt;/p&gt;
&lt;p&gt;Are you sure that you have configured RTC to use XTAL and not the internal RC? Assuming that you have XTAL LFCLK on your board. Else you probably can use SYNTH derived from HFCLK to source it. Check your hardware to see if it has XTAL and check the device tree node&amp;nbsp;&amp;amp;lfclk to see if it is using the XTAL if you have it on the hardware. An example of how these configurations are set can be seen in this d&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/116605/nrf5340-external-high-speed-clock-source-lowpower"&gt;evzone thread.&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>