I wanted a clock that never needed setting. Things escalated

There’s a time zone setting offset slider and a DST slider. I basically touch it twice a year, maybe another if I move time zones. I’ve only had to touch it for DST (never switched time zones). Takes me conservatively 10 seconds to find and flip, so it’s taken me 460 seconds or a little under 8 minutes in the past 23 years to do time adjustments.

While these efforts are definitely fun hobby projects, there are cheap reliable solutions out there with minimal intervention that consume the NIST radio signal for time.

Just for anyone interested who wasn’t aware there’s some “old school” time broadcast solutions out there too besides NTP: https://www.nist.gov/pml/time-and-frequency-division/time-di...

I have three La Crosse clocks that run off the NIST time signal out of Boulder, CO, and need their AA battery replaced maybe once a year. The real challenge is running such a thing on a small battery for a year.

I once made a small clock that displayed "A LITTLE AFTER SIX" and such, changing its text every five minutes. Needed a power connection, though.

Ok, so instead of bumping your clock +- one hour twice a year you preferred distro upgrades?

> The end result exactly matched my expectations—the best criterion for success that I can think of. With an LLM providing the heavy code lifting and the CAD work, I think I spent more time waiting on supplies to arrive than on anything else—something attributable to my lack of planning and the ease of next-day delivery.

I think the author robbed themselves of a deeper understanding.

[1] https://www.npl.co.uk/products-services/time-frequency/msf-r...

Why is it so dang impossible to find a not trash simple LED clock that's 'large print', 'the right color', and not annoyingly too bright?

A deluxe model might include a day of the week bar or dot and a month / day in month number (smaller than the time, mostly people care about the time)

Also: I reckon the closest best-value watch alternative that ticks most(?) of the author's boxes is the Casio GW-M5610-1ER, so long as you are inside a radio-controlled time area.

I made a LED matrix clock using esp32 syncing time with ntp server every hour and an external RTC to do time keeping if my network is down, and it runs perfectly for years, with accuracy +-1s to time.is. Never have to do setting except the first boot to setup wifi.

Might want to flip the clock over and check for a battery door before starting next time.

I was tempted to go the Atomic Clock route, based on actual cesium oscillators, having found a cheapish ($999) used CSAC on ebay[1]. However, once I started digging into the data sheets[2], I found something unacceptable, Pin 1, labeled "Tune", an analog tuning input.

It was then that I learned that while the Cesium vapor cells were accurate, they aged, and drifted, unlike a properly degaussed and Zeeman harmonic calibrated Cesium Beam atomic clock, which is a primary standard.

Further demotivating was learning they have a 5-10 year service life. That's a lot of money to pay for what's essentially a better OXCO.

I'll stick with GPS disciplined oscillators for now.

[1] https://www.ebay.com/itm/327134074179

[2] https://www.mouser.com/datasheet/2/523/Microsemi_CSAC_Space_...

https://en.wikipedia.org/wiki/WWV_(radio_station)

It just doesn't seem to get used that much, I suppose?

This clock still sits on my nightstand. The backlight stopped working years ago, the cheap plastic case is cracked, the numbers on the dial from 12 to 5 have crumbled away. But it keeps perfect time! It is also silent (no ticking at all, no quartz crystal) and has no battery to charge or worry about leaking

I'd pay quite a bit for a replacement, but such clocks haven't been made in over 30 years. An "atomic" clock is cool, but the signal doesn't reach where I live.

The secret to finding an inexpensive radio-controlled clock/alarm/watch of your liking it to be German. They LOVE their Funk-Uhren! Sadly they typically only support Germany's DCF77 signal. You can also trivially find DCF77 receivers as components to use in a project.

No need for me to reinvent the wheel, works a treat mounted above my monitor

Nice fun project!

Edit: Maybe you can add speaker for internet radio to wake up?

> Battery-backed self-setting “atomic” clocks that get their updates via the cosmic ether have been a thing for years and get me most of the way there, but damned if I could find one with a red seven-segment display that I liked (maybe someone else’s search kung-fu is better than mine?)

I found this with ~5 minutes of searching. I think it meets your critera: https://www.amazon.com/Sharp-Digital-Alarm-AccuSet-Automatic...

(Regardless, cool project! I think yours still looks better than this one)

No complete protocol or handshake, just grab some close-enough time.

And things can escalate from there too . . .

https://www.youtube.com/watch?v=smUwbzA9SEo

That said, why do people need clocks? I usually know the time, day or night, within 30 minutes or so, and if I need to know the exact time (which happens rarely if ever), I look at my watch. There are zero clocks in my home. I would find it quite aggressive to have a big display that tells me exactly what time it is.

Come to think of it there is one clock in the kitchen, on the oven. It's usually never correct because it resets after any power flicker and nobody takes the time to set it back properly. This is a recent oven; it's surprising kitchen appliances still are so dumb.

There are a few places to get the current time:

- on-board real-time clock (RTC) connected to a continuous power source (e.g. button battery)

- GPS

- Colorado WWVB signal (60 KHz), Frankfurt DCF-77 (77.5 KHz), Cumbria NPL (60 KHz)

- the internet (NTP, HTTPS servers, etc.)

- mobile internet (e.g. LTE)

- estimate time elapsed between power cycles by tracking and storing IEEE 802.11 timing synchronization function (TSF) timestamps from nearby wifi routers.

All of these are potentially problematic.

The best option is the RTC. Buy a DS3231, hook it up to your microcontroller and a button battery, and forget about it for a few years. The only problem with these (besides the battery) is that they can drift pretty badly. The fancy ones account for temperature fluctuations and are accurate to ~2 ppm, which is one minute per year. Aside from the drift, it sucks to need an always-on dedicated IC just to know the time, especially if you don't always need to know the time.

GPS is nice but it's hard to get a signal indoors, especially in a skyscraper far away from a window, as can happen here in New York. You also need a relatively bulky component and an antenna.

The longwave radio signals (WWVB, DCF-77, and NPL) are neat and old and what "atomic clocks" use, but the signal is tiny and you need a sensitive long-running receiver, either with a gigantic antenna or a slightly less gigantic ferrite rod. Even then, one of those cheap atomic clocks might not sync at all unless it's placed near a window. The WWVB signal is also very weak in certain parts of America and at certain times of day, so your circuit might only get a bit of signal over the noise once or twice a day, which might or might not be enough to deduce the time.

The plain old internet works fine, but then your power budget involves a wifi radio, though you only need to run it for a few hundred milliseconds per hour. You also need a wifi password, which is a pain to configure in an IoT device. Also, you wanted a clock, why does it need the internet? GTFOOH.

Mobile internet is way overkill.

The last idea is something I haven't tested fully, since my microcontroller (raspberry pi pico w) can't keep up with the "promiscuous mode" unofficially offered by its wifi chip. It's a neat idea, though: you're in an environment with wifi routers all around, and you want to guess the time elapsed since you last checked by listening, without credentials, to the chatter. With enough routers and some flash storage you can probably keep track of time, assuming the whole area doesn't get a power outage.

That's my very long way of saying that keeping time is a solved problem but all of the solutions have drawbacks and none works perfectly.

Did everyone forget that hackers and engineers like to have fun? Seriously.

Someone at Open Sauce this year made a friggin CRT-based VR headset. Why? Why not.

Did we forget where we came from? Does everything have to be optimal?

Funny but I have one which updates time "via the cosmic ether", has big red 7-seg LEDs and as cherry on top it has laser LED based projector that displays same big red 7 seg digits on whatever surface one points it to - ceiling in my case. I bought it decades ago in RadioShack

But on the other hand... gosh, this was about the simplest software engineering challenge imaginable (toggle some I/O pins) and the simplest design task imaginable (make a featureless rectangular box). And the author - a technologist! - isn't just saying "I wanted to try out some new tech". They're saying "this was too hard, I needed help from an LLM" ("would absolutely not be able to meet this challenge", "hit another wall").

And that... I mean, I just don't know what to make of this. Were we always like this? Are LLMs making us like this? Is it good? Is it bad?... and don't give me the calculator analogy...

That way all the microwaves of the world could listen in and update their clocks accordingly