That's a really nice use of a voltmeter :-) Bookmarked for future reference, for when I have the time to do a project like this (probably never, but still).
Very nice! I like how smoothly the second gauge moves.
Question: I've been toying with the idea of building my own MCU powered clock. The gimmick with mine is I want to use an OCXO, so it's a super accurate quartz clock (as accurate as possible without GPS or rubidium). Anyway, the designs I've looked at are similar to how you've done it. They connect the oscillator to the interrupt pin. But it occurred to me the oscillator could just be the MCU's external clock signal. Then the MCU doesn't need an interrupt handler. It can just examine its own tick counter. Can you see any issues with that? Is there a reason you went the interrupt route instead? Maybe the reason is "that's what worked for the parts I had laying around" but wondering if there's a technical reason.
Postscript to some commenters on HN: the dramatic drop and bounce are intentional and make the clock a lot more fun to watch. It would be trivial to eliminate it, but why would you want to? In wristwatches, people pay extra for such theatrics (retrograde minutes / hours).
Another commenter: "I would be worried that a cheap panel voltmeter would not survive a very large number of such shocks." - the 2019 clock has been running non-stop for 7 years and is working just fine.
I mean, if you're being serious, it's a losing game. It's labor-intensive to make, people are accustomed to electronic gadgets of this sort costing less than takeout, and then if you're even modestly successful, someone in China will undercut you.
I could do a $100k Kickstarter and then disappear, though...
That's a really nice use of a voltmeter :-) Bookmarked for future reference, for when I have the time to do a project like this (probably never, but still).
Cool project! For anyone interested in the square meters just search for “62C voltmeter”
Very nice! I like how smoothly the second gauge moves.
Question: I've been toying with the idea of building my own MCU powered clock. The gimmick with mine is I want to use an OCXO, so it's a super accurate quartz clock (as accurate as possible without GPS or rubidium). Anyway, the designs I've looked at are similar to how you've done it. They connect the oscillator to the interrupt pin. But it occurred to me the oscillator could just be the MCU's external clock signal. Then the MCU doesn't need an interrupt handler. It can just examine its own tick counter. Can you see any issues with that? Is there a reason you went the interrupt route instead? Maybe the reason is "that's what worked for the parts I had laying around" but wondering if there's a technical reason.
Oh wait! Looking at the code, this is what you did, I think. Ok well glad to see I wasn't totally off base with my planned design.
Really nice.
Postscript to some commenters on HN: the dramatic drop and bounce are intentional and make the clock a lot more fun to watch. It would be trivial to eliminate it, but why would you want to? In wristwatches, people pay extra for such theatrics (retrograde minutes / hours).
Another commenter: "I would be worried that a cheap panel voltmeter would not survive a very large number of such shocks." - the 2019 clock has been running non-stop for 7 years and is working just fine.
It's honestly magical to watch. Kudos!
Sooo do you sell them?
I wouldnt personally sell them; but there are people who love this kind of special item. Engineers, mechanics, etc is all
I mean, if you're being serious, it's a losing game. It's labor-intensive to make, people are accustomed to electronic gadgets of this sort costing less than takeout, and then if you're even modestly successful, someone in China will undercut you.
I could do a $100k Kickstarter and then disappear, though...
Still more circuitry than my feeble skills could manage, but very nice work
Lovely work.