Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set PCF85063A after ntptime.settime() #44

Merged
merged 1 commit into from
Oct 11, 2023

Conversation

sinofp
Copy link
Contributor

@sinofp sinofp commented Aug 17, 2023

My Badger 2040 W always shows the clock as 2000-01-01 00:00:00, even though I can access the Internet. This issue arises from badger2040.pcf_to_pico_rtc(), which overwrites Pico's RTC using PCF85063A, after ntptime.settime() is called. However, PCF85063A is never set before.

This commit sets the PCF85063A using the freshly synced time obtained from pool.ntp.org.

My Badger 2040 W always shows the clock as 2000-01-01 00:00:00, even though I can access the Internet. This issue arises from `badger2040.pcf_to_pico_rtc()`, which overwrites Pico's RTC using PCF85063A, after `ntptime.settime()` is called. However, PCF85063A is never set before.

This commit sets the PCF85063A using the freshly synced time obtained from pool.ntp.org.
@Gadgetoid Gadgetoid merged commit a8552a5 into pimoroni:main Oct 11, 2023
@Gadgetoid
Copy link
Member

Good catch, thank you, I think we'll need to add some kind of offset to the WIFI config since mine now shows 15:58 instead of 16:58, doh!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants