Hi,
I am creating the NTP server synchronized 'zero error clock' using Raspberry Pi Pico W and Micropython now.
I noticed that:
1) Micropython library 'ntptime.py' sets millisecond field to zero in ntptime.settime() as follows:
--- ntptime.py ---
def settime():
t = time()
import machine
tm = utime.gmtime(t)
machine.RTC().datetime((tm[0], tm[1], tm[2], tm[6] + 1, tm[3], tm[4], tm[5], 0)) # last field is millisecond
2) RP2040 datasheet says 'RTC has no millisecond filed'.
Hence,
Q1) Does RP2040 RTC support millisecond accuracy ?
Q2) How can I treat 'millisecond accuracy' for 'zero error clock' fully synchronized with the accurate NTP time (without error within 1 sec) ?
Thanks,
I am creating the NTP server synchronized 'zero error clock' using Raspberry Pi Pico W and Micropython now.
I noticed that:
1) Micropython library 'ntptime.py' sets millisecond field to zero in ntptime.settime() as follows:
--- ntptime.py ---
def settime():
t = time()
import machine
tm = utime.gmtime(t)
machine.RTC().datetime((tm[0], tm[1], tm[2], tm[6] + 1, tm[3], tm[4], tm[5], 0)) # last field is millisecond
2) RP2040 datasheet says 'RTC has no millisecond filed'.
Hence,
Q1) Does RP2040 RTC support millisecond accuracy ?
Q2) How can I treat 'millisecond accuracy' for 'zero error clock' fully synchronized with the accurate NTP time (without error within 1 sec) ?
Thanks,
Statistics: Posted by koby — Mon Apr 01, 2024 2:06 am — Replies 0 — Views 20