undefined | Better HN

0 pointsssl-32mo ago0 comments

Both of the WWVB clocks I've owned have been very fickle about how they're placed because RF be that way sometimes, and Colorado isn't exactly nearby to my location in Ohio.

The first manufactured GPS clock I owned (as in: switch it on and time is shown on a dedicated display) was in a 2007 Honda.

But a firmware bug ruined that clock: https://didhondafixtheclocks.com/

And even after it began displaying the right time again, it had the wrong date. It was offset by years and years, which was OK-ish, but also by several months.

Having the date offset by months caused the HVAC to behave in strange incurable ways because it expected the sun to be in positions where it was not.

But NTP? NTP has never been fickle for me, even in the intermittently-connected dialup days I experienced ~30 years ago: If I can get to the network occasionally, then I can connect to a few NTP servers and keep a local clock reasonably-accurate.

NTP has been resolutely awesome for me.

0 comments

otterley2mo ago

The WWVB clocks are around the AM band, which means they carry a great distance despite their lower transmission power, but only at nighttime. Ohio is nothing; the signal needs to make it to the southern reaches of Florida.

ssl-3OP2mo ago

Yeah, I "know" how it is supposed to work. I "knew" that back then when I bought my first WWVB-receiving clock, too.

And the placement was still fickle.

It's simple to observe:

A) Purchase and install clock. Wait (days). Observe failure to chooch.

B) Move clock. Wait (hours). Observe correct operation.

My world is ultimately bounded by reality, not theory: When it works in one position but not another, then that's the only reality I have to work with.

Dylan168072mo ago

On the one hand, some sloppy GPS units fail on a 20 year schedule. On the other hand, a bunch of things using NTP are going to fail in about ten years. (2036 rather than 2038 because reasons)

ssl-3OP2mo ago

Yeah, good point.

If I ever get the chance, I'll try to remember to tell the 1995 version of me to watch out for that pesky overflow bug that they might experience with NTP -- two score and 1 year in their future.

j / k navigate · click thread line to collapse

0 pointsssl-32mo ago0 comments

Both of the WWVB clocks I've owned have been very fickle about how they're placed because RF be that way sometimes, and Colorado isn't exactly nearby to my location in Ohio.

The first manufactured GPS clock I owned (as in: switch it on and time is shown on a dedicated display) was in a 2007 Honda.

But a firmware bug ruined that clock: https://didhondafixtheclocks.com/

And even after it began displaying the right time again, it had the wrong date. It was offset by years and years, which was OK-ish, but also by several months.

Having the date offset by months caused the HVAC to behave in strange incurable ways because it expected the sun to be in positions where it was not.

NTP has been resolutely awesome for me.

0 comments

otterley2mo ago

ssl-3OP2mo ago

Yeah, I "know" how it is supposed to work. I "knew" that back then when I bought my first WWVB-receiving clock, too.

And the placement was still fickle.

It's simple to observe:

A) Purchase and install clock. Wait (days). Observe failure to chooch.

B) Move clock. Wait (hours). Observe correct operation.

My world is ultimately bounded by reality, not theory: When it works in one position but not another, then that's the only reality I have to work with.

Dylan168072mo ago

On the one hand, some sloppy GPS units fail on a 20 year schedule. On the other hand, a bunch of things using NTP are going to fail in about ten years. (2036 rather than 2038 because reasons)

ssl-3OP2mo ago

Yeah, good point.

If I ever get the chance, I'll try to remember to tell the 1995 version of me to watch out for that pesky overflow bug that they might experience with NTP -- two score and 1 year in their future.

j / k navigate · click thread line to collapse