9 posts • Page 1 of 1
Hi ESP_igrr,ESP_igrr wrote:Internal RTC clock frequency error is about 5%. With external 32k XTAL the error will be determined by the XTAL, usually about 20-30ppm.
https://www.dataq.com/blog/data-logger/ ... ppm-stuff/
The de facto standard in the industry for crystal inaccuracy is 20 PPM
CheersYou can also express PPM as a percentage: ±20/1,000,000 = ±0.002%. So after 30 days (2,592,000 seconds) we can expect the clock to drift about ±52 seconds; after 60 days about ±104 seconds, and so on.
We are planning to use Internal RTC with button Cell to keep updated time once External Main power will be off. So, Will it possible to get clock properly with accuracy if we will go with Internal RTC?
Yes. We will take time from NTP if external network connectivity will be there or will set forcefully one time when board is fresh.
But our requirement is to maintain time when board is off using RTC and once there will be power applied then it will collect updated time from RTC and set into system clock.
So for that can't it be possible using internal RTC and button cell connected with VDD3.3V_RTC? what is accuracy provided if we consider 24 hours to execute RTC without external power supply?
That is our next plan if not possible to get exact accuracy with internal RTC of ESP32. Actually we don't want to extra cost overhead into our product due to lower budget.
So that my intention is to use internal RTC with just button cell holder but need to think for other option if not possible to get accuracy with internal RTC.
I have also tried to find out Internal RTC Accuracy into ESP32 Documents but didn't find it anything apart from below.
"RTC timer: Allows keeping the system time during any resets and sleep modes, only the power-up reset leads to resetting the RTC timer. The frequency deviation depends on an RTC Clock Source and affects accuracy only in sleep modes, in which case the time will be measured at 6.6667 us resolution."
Who is online
Users browsing this forum: Bing [Bot] and 56 guests