RTC not keeping time #50

New Issue

2023-09-17T16:32:12-05:00

W1CDN commented

2023-09-17 16:32:12 -05:00

Not quite the same as #27.

On reboot, the time reported on the serial connection is sometimes out of date.

I spent a bunch of time on this at #24 (comment) and prior comments. It may be time to buy a better RTC and try that.

Ugh, this important if you want to run more than one transmitter at once.

Not quite the same as #27. On reboot, the time reported on the serial connection is sometimes out of date. I spent a bunch of time on this at https://amiok.net/gitea/W1CDN/vulpes/pulls/24#issuecomment-1240 and prior comments. It may be time to buy a better RTC and try that. Ugh, this important if you want to run more than one transmitter at once.

W1CDN added the bug hardware labels 2023-09-17 16:32:13 -05:00

W1CDN commented

2023-09-18 15:10:16 -05:00

"Sometimes" being the word. I can refresh the date using the webform, unplug the device for a few minutes, plug it back in, reboot on serial connection, and the time will be right (i.e., it will match the time it was rebooted, not the last time that was set using the webform).

Is the webform ever giving an old time? But still, it should keep counting. Maybe it keeps counting from an old time?

"Sometimes" being the word. I can refresh the date using the webform, unplug the device for a few minutes, plug it back in, reboot on serial connection, and the time will be right (i.e., it will match the time it was rebooted, not the last time that was set using the webform). Is the webform ever giving an old time? But still, it should keep counting. Maybe it keeps counting from an old time?

W1CDN commented

2023-09-18 15:19:01 -05:00

These seem interesting:

These seem interesting: - https://forum.arduino.cc/t/ds3231-time-not-increasing/459796/2 - https://forum.arduino.cc/t/ds3231-time-not-increasing/459796/12

W1CDN commented

2023-09-18 16:06:15 -05:00

Still counting time.

W1CDN commented

2023-09-18 18:18:55 -05:00

Still counting time...

I've been plugging in to serial monitor but not refreshing web page, to check the RTC time on boot.

Still counting time... I've been plugging in to serial monitor but not refreshing web page, to check the RTC time on boot.

W1CDN commented

2023-09-19 08:57:10 -05:00

Still counting time, made it overnight.

One thought I had is that I don't know if shorting any of the pins (if board powered off and RTC on battery) causes anything weird to happen. I've set this board on my metal MBP lid before without insulation.

Still counting time, made it overnight. One thought I had is that I don't know if shorting any of the pins (if board powered off and RTC on battery) causes anything weird to happen. I've set this board on my metal MBP lid before without insulation.

W1CDN commented

2023-09-19 09:53:24 -05:00

Hey, this is interesting, but does it apply here?

The datasheet reccomends a delay before setting: “Communication with the I²C should be held off at least for the first 2 seconds after a valid power source has been established. It is during the first 2 seconds after power is established that the accurate RTC starts its oscillator, recalls calibration codes, initiates a temperature sensor read, and applies a frequency correction.” https://thecavepearlproject.org/2014/05/21/using-a-cheap-3-ds3231-rtc-at24c32-eeprom-from-ebay/

Hey, this is interesting, but does it apply here? > The datasheet reccomends a delay before setting: “Communication with the I²C should be held off at least for the first 2 seconds after a valid power source has been established. It is during the first 2 seconds after power is established that the accurate RTC starts its oscillator, recalls calibration codes, initiates a temperature sensor read, and applies a frequency correction.” https://thecavepearlproject.org/2014/05/21/using-a-cheap-3-ds3231-rtc-at24c32-eeprom-from-ebay/

W1CDN referenced a pull request that will close this issue

2023-09-19 11:12:55 -05:00

Make sure RTC is counting time on battery #51

W1CDN commented

2023-09-19 11:13:24 -05:00

Added delay(2000); before reporting RTC time on boot.

Added `delay(2000);` before reporting RTC time on boot.

W1CDN commented

2023-09-19 15:32:12 -05:00

Set this for 20:30 CDT (should be 01:30 UTC), it came on at 15:30 CDT.

Checked the time with serial on reboot, it is correct: 20:30 UTC (15:30 CDT).

Does this mean I added a timezone problem somewhere?

The 20:30 CDT entered on the webform should have translated to 1:30 UTC (the next day), but serial reports that the alarm was set for 20:30.

Set this for 20:30 CDT (should be 01:30 UTC), it came on at 15:30 CDT. ![image](/attachments/36733b4d-5319-4d99-b873-d72f905ba48b) Checked the time with serial on reboot, it is correct: 20:30 UTC (15:30 CDT). Does this mean I added a timezone problem somewhere? The 20:30 CDT entered on the webform should have translated to 1:30 UTC (the next day), but serial reports that the alarm was set for 20:30.

image.png

4.1 KiB

W1CDN commented

2023-09-19 16:02:36 -05:00

Alarm 1 set for at 21:05:00 Fri, 19 May 2000 (only HH:MM:SS day-of-month are accurate)

This started up on schedule.

Maybe something weird if you go over the UTC day?

![image](/attachments/54029555-229b-408f-ab4e-321e2ebb3ce5) `Alarm 1 set for at 21:05:00 Fri, 19 May 2000 (only HH:MM:SS day-of-month are accurate)` This started up on schedule. Maybe something weird if you go over the UTC day?

image.png

24 KiB

W1CDN commented

2023-09-19 16:06:59 -05:00

Alarm 1 set for at 02:10:00 Sat, 20 May 2000 (only HH:MM:SS day-of-month are accurate)

It did not start at 16:10 CDT. This is correct, but also confusing.

Noting that only HH:MM:SS and day-of-month are used by the RTC alarm might still be important.

![image](/attachments/bcd98a6f-c4d8-4631-a0c1-935b41f1e269) `Alarm 1 set for at 02:10:00 Sat, 20 May 2000 (only HH:MM:SS day-of-month are accurate)` It did *not* start at 16:10 CDT. This is correct, but also confusing. Noting that only HH:MM:SS and day-of-month are used by the RTC alarm might still be important.

image.png

24 KiB

W1CDN commented

2023-09-20 15:09:10 -05:00

There it is. I put this handy thing at the top, and it's showing UTC, not local time:

EDIT: But only on Windows! This is what I see on macOS:

This is the same thing I see on Node-RED with a time-series plot. On macOS and Android, the time is local, but on Windows (checked two machines) it is UTC.

All Firefox.

There it is. I put this handy thing at the top, and it's showing UTC, not local time: ![image](/attachments/fde1cc4a-4302-4b4a-9918-1d64a2d36ad6) EDIT: But only on Windows! This is what I see on macOS: ![image](/attachments/1996bf30-1b85-4b00-a548-924e147d0bb2) This is the same thing I see on Node-RED with a time-series plot. On macOS and Android, the time is local, but on Windows (checked two machines) it is UTC. All Firefox.

image.png

1.9 KiB

image.png

13 KiB

W1CDN commented

2023-09-20 15:38:58 -05:00

I think it is this: https://superuser.com/a/1777971

One setting you can check in about:config does affect the time zone which gets reported to web sites: if privacy.resistfingerprinting is set to true, then Firefox will always report UTC to avoid leaking information about you that could be used to generate a unique fingerprint and let web sites track you even without cookies.

If I switch it to false on Windows, it shows local time.

If I switch it to true on Mac, it shows UTC.

I think it is this: https://superuser.com/a/1777971 > One setting you can check in about:config does affect the time zone which gets reported to web sites: if privacy.resistfingerprinting is set to true, then Firefox will always report UTC to avoid leaking information about you that could be used to generate a unique fingerprint and let web sites track you even without cookies. If I switch it to `false` on Windows, it shows local time. If I switch it to `true` on Mac, it shows UTC.

mattbk commented

2023-09-22 17:06:10 -05:00

It's been unplugged for over a day, plugged in and the time is correct.

W1CDN closed this issue

2023-09-25 21:14:58 -05:00

W1CDN commented

2023-10-01 11:24:23 -05:00