ESP32 based old clock controller, with NTP sync

A very common control protocol, used more or less by IBM, Simplex, and Standard Electric, is this: a pulse delivered once per minute advances the minute hand one notch. A pulse delivered at the top of every hour (on a separate wire, I believe in the Simplex case that I am most familiar with) powers an electromagnet which "snaps" the minute hand to the 00 position, correcting any error that occurred in tracking the minute pulses over the preceding hour.

If the clock is doing a poor job of tracking the minute pulse (due to a dirty/bound up local mechanism in the case of school clocks I've messed with), it's common to see the minute hand perhaps ten minutes behind late in the hour, and then at the top of the hour it will fairly quickly "sweep" to the correct position. Of course these clocks should be serviced, but the school district I was dealing with had a paltry budget and a hard time finding companies to service the clocks so they tended to stay broken in this way for years at a time.

The big problem with this system is that it could only "correct" clocks that were a bit off at the top of the hour (if the error was too large the top-of-the-hour reset did not function correctly, and the hour hand was never corrected). This meant that in the event of a loss of power to the clock system, it was necessary to manually reset the hour hand of every clock in the building prior to restart. The convention for Simplex and I believe for other vendors as well is to set all clocks to 12:00 exactly, the master clock then has a mode in which it delivers "accelerated" minute pulses to advance all clocks to the correct time. Back when I was in middle school the controller seemed to be broken in a way where it occasionally went into this mode incorrectly (maybe a short power disruption) and sometimes all the clocks in the building would be moving at 10x speed for a few hours of the day.

DST correction needs to be handled similarly, so you will have to visit every clock in the system at least twice a year, assuming you have reliable power and aren't in Arizona or something. Or, in an underfunded school district, just apply the DST correction weeks late or not at all. It is amazing how habituated people become to the clocks being completely unreliable.

I have read that there were systems that used a third signal to reset the hour hand at 12:00, avoiding this problem, but I've never personally seen one - perhaps they weren't popular at all or perhaps they just fell into an awkward spot at the end of the period where analog systems were being installed. In modern slave clock systems, it's more common to use RS422 or 900MHz radio to directly transmit timestamps once per second. These have the major advantage of making digital displays extremely easy to implement and analog displays still fairly easy, with no need to ever manually set clocks.

In installations today though, it seems like the most popular option for schools are one of several digital (sometimes IP) paging systems that support a clock display as an add-on feature. Integrating the clocks with paging makes more sense than you might think, as the slave clock system in schools generally also controlled the bells (sometimes using the same signal wires, e.g. using opposite polarity of pulses to open a relay on the 12/24vac bells), and so now that bells are being replaced with paging it makes sense to keep clocks on the same system.

There's a subset of the curious internet community of fire alarm collectors who also collect these clock systems, since they are somewhat similar in nature to older fire alarms. I'll admit that I've considered trying to get a few old Simplex slave clocks to fix up and put in my house, probably implementing my own controller since even the later-generation digital controllers Simplex sold were large wall cabinets.

An even earlier version used an atmega and was powered from batteries [3]

Those slave-clocks are pretty loud. Both versions have a way to pause the clock.

https://gitlab.com/close2/nebenuhr https://gitlab.com/close2/nebenuhr_hardware https://github.com/close2/nebenuhr

Also, the commenter on your website is correct about fading OLED displays. The cheap 128x64 OLEDs selling on eBay for $1-$2 seem to degrade within 6 months. I hope to use an LCD for my next clock.

So one just need synthesize a perfect 60Hz ~115vac input and the clock will keep perfect time. (In theory the grid tries to keep somewhat accurate time, but in practice at least on the west coast the departures can be pretty substantial.)

I have a wall clock here that keeps coordinated Mars time, driven off a local atomic clock.

This is interesting because that's very similar to how the Swiss railway clocks synchronize their time. The second hand takes 58.5 seconds to make one full rotation, and then the clock pauses and waits for a central pulse that comes every minute.

If I'm not mistaken I believe most of their actual station clocks are made by Mobatime, although Mondaine seems to have gotten the rights for the Swiss railway's merchandise, which is kind of sad because they haven't replicated that characteristic and historic smooth second hand and pause-and-go motion on their clocks and watches, and seem to have slapped on a run-of-the-mill cheap ticking quartz mechanism.

I'd love an NTP sync'd wall clock but my time for hardware hacking is pretty limited. Are there any off the shelf wall clocks that do NTP? Bonus points for POE and no WiFi.

https://www.timeexpander.com/posts/nixie_kit_1_3/

It currently uses RPi Zero, but I think there is an ESP32 version planned.

What is the PS-1 mechanism?