cdzombak / atomclock Goto Github PK

The millis() counter driven by whatever's on the Wemos ESP8266 isn't very accurate, but it certainly doesn't lose that much per second.

So:

• Note millis() each time we process a tick (in loop, not the ISR)
• When we receive a tick, check that it's not within ~100 millis of the last tick; otherwise move to an error state
• When looping in the normal operation state, if millis is now more than ~1200ms since the last tick, move to an error state

I'm undecided whether the error state should be displayed, or if we should just move back to the wifi connect -> time sync flow (resetting upAt and other critical time vars). That would be seamless, but I probably want to know if this happened.

Should reset upAt and oscTime. oscTime will get reset soon enough anyway, but I want upAt to count how long the clock has been up since the last time sync.