Keeps the time stable for weeks/month? #9
Replies: 3 comments 3 replies
-
(Moving discussion to AceTimeClock project, where the SystemClock classes live since v1.8) |
Beta Was this translation helpful? Give feedback.
-
How is the The only time I've had problems with clock accuracy is due to defective DS3231 chips. I get the impression that the quality of the parts coming out of China through sellers on eBay is not very good. The spec for the DS3231 says that it's supposed to be accurate to 2ppm, so 0.2 seconds per day. But I rarely see a DS3231 chip that accurate. Most of them are off by several seconds per day. The worst one would randomly lose 30-90 minutes after a few days. If you using the NtpClock, the clock should be accurate to within seconds. If you are using the internal |
Beta Was this translation helpful? Give feedback.
-
Hi Brian, my current sketch goes like this: In the setup the ESP32 tries to connect to the WLAN (router). If the connection does not work, the ESP switches to AP mode and waits for the user to connect to the AP. In any case, from then on AceTime should be responsible for obtaining the time, because it may happen that the connection to the router is lost at night (because the router is switched off, for example). Here is a shortened version of my sketch. If I am wrong here:
|
Beta Was this translation helpful? Give feedback.
-
Hi Brian, I have again a question about your library (sorry for asking so much;-)
Can it be that the time - once it is set and "kept alive" in the loop with systemClock.loop(); - is gradually adjusted (i.e. after a few days the clock is suddenly e.g. 20 minutes slow?).
Beta Was this translation helpful? Give feedback.
All reactions