Go Down

Topic: RTCZero and running past 24 hours (Read 614 times) previous topic - next topic


I have scoured the Internet and I don't see anyone having this problem.  I have seen past issues where the library was giving strange results and jumping around.  My issue:  I may be missing something here, but doesn't MKR1000 have a built-in RTC?  Using latest RTCZero library and running sample sketch (simpleRTC.ino) has the clock running/reporting past 24 hours!  Isn't there something in the library which says 'if past 24 hours to start again at 1'?  Am I supposed to do that in my code (like I hear I am supposed to add my own 12 hour formatting code because that was dropped from the library)?

Example from monitor:

08/07/18 24:59:44
08/07/18 24:59:46
08/07/18 24:59:48
08/07/18 24:59:50
08/07/18 24:59:52
08/07/18 24:59:54
08/07/18 24:59:57
08/07/18 24:59:59
08/07/18 25:00:01
08/07/18 25:00:03
08/07/18 25:00:05
08/07/18 25:00:07
08/07/18 25:00:09
08/07/18 25:00:11
08/07/18 25:00:13
08/07/18 25:00:15
I have it skipping 2 seconds (delay(2000)).  This seems to be acting more like a timer rather reporting time.


Aug 04, 2018, 01:29 pm Last Edit: Aug 04, 2018, 01:31 pm by ballscrewbob
Seeing the same bug here on CREATE with carry over rather than increment the date and resetting the clock.

It does appear to be a bug.

Opened an issue for it HERE

It may not be the answer you were looking for but its the one I am giving based on either experience, educated guess, google or the fact that you gave nothing to go with in the first place so I used my wonky crystal ball.

Go Up