I’m surprised that they chose to add a bunch of components to feed the AC line frequency to the microcontroller instead of just using a 32.768 kHz crystal. A single crystal oscillator seems like both the cheaper and more accurate option
The power line frequency is carefully monitored and adjusted to ensure that deviations from the ideal (60 Hz in OP's case) are smoothed out [0]. Even a single ppm deviation equates to 2.6 seconds per month, and your cheap 32.768 kHz crystal is going to be orders of magnitude worse than that.
My microwave seems to gain minutes per month, my assumption was that it's due to incompetency of Eskom, the essentially sole producer of South African electricity. With the government and parastatals here incompetency is very common.
However, out of interest I just pulled yesterday's stats from my inverter on Sunsynk's website. It has the frequency of the grid at 5-minute intervals and the average over the whole day was 49.975Hz which doesn't strike me as particularly bad, so I have to wonder if the Microwave itself has an issue. It's a Samsung which is now 13 years old.
> the average over the whole day was 49.975Hz which doesn't strike me as particularly bad.
A day, having 86_400 seconds in it, is equivalent to 4_320_000 pulses at 50 Hz. At 49.975 Hz, it's only 4_317_840 pulses which is 2_160 pulses too few. Which, at assumption of 50 Hz, translates into discrepancy of 43.2 seconds, in this one day.
So, no, it's a pretty big discrepancy actually, over here anything over 0.2 Hz is legally declared to be "degraded quality", and it's been debated for years that this is actually a way too wide margin but the electricity providers/grid operators managed to successfully argue that they can't afford upgrades.
Moral of the story: don't get cute when designing electronics, just use AC/DC power supply and put a damn crystal oscillator as every other reasonable person.
I'm guessing you're being downvoted largely due to the "don't be snarky" rules.
You're right (by my maths too, which I only did now) about it being a discrepancy of 43.2 seconds per day, which as you say is quite high.
However, it is my understanding that most grid operators are actually very good about maintaining a 50Hz average over a day specifically for devices doing time keeping based their frequency, I've heard they intentionally run the generators faster or slower at certain points in the day in response to needing to get the average right over a day.
I used to have no issues with time drift on my microwave, only started in the last few years.
this prints my Ethernet interface as expected. It doesn't make any requests, it just figures out where to route a packet. I guess it interfaces with the OS routing table.
Thanks for sharing! This is definitely something I will look into, I am all in favor to simplify the current implementation of finding the "default" OS network interface.
That has nothing to do with the UI framework. The X11 dependency comes as part of the clipboard integration (which I'd argue should be optional or even removed). Still, I wouldn't call it modern if Wayland is outright not supported.
I hesitated a bit bringing in this feature. On one hand, I really like to have clipboard support, on the other hand, I don't like that it requires you to change from static to dynamic linking (and have the x11 dependency).
Maybe I could write an install.sh script for installation that detects the OS and fetches the correct version/tarball from the Github release.
Thanks a lot for your contribution, this is something I will look into in the upcoming days. I totally agree that CGO isn't ideal, I had to make the build/release process also a lot more complicated purely for that clipboard requirement (see GHAs and the different goreleaser files).
On the other hand, I also don't want whosthere to be depended on a fork that isn't maintained anymore. I will think about this trade-off, but I am also interested how others look at this problem.
Cool project. Tip: acetone will readily dissolve the plastic parts of the card leaving the antenna(s) and chip intact. I believe a few other people have made drop-in PCBs with NFC antennas. Here’s one: https://n-o-d-e.net/datarunner.html
Also, no F-91W thread would be complete without a mention of the sensorwatch project: https://www.sensorwatch.net/
The dissolution in acetone is nicely demonstrated here https://youtu.be/NF4VJJKTjy8?t=835
The guy does it in order to be able to pay with a prosthetic eye.
For anybody wondering wth is with a guy sculpting dioramas about obscure celebrity misadventures - he was formerly half of the Hip-Hop Comedy Duo, Sketch Artists, and behemoth Irish podcasters 'The Rubberbandits'. Probably one of the greatest neo-dadaists and proponents of Aestheticism in Europe today.
Some might even know them without realising it - their incredibly provocative Richard D. James-esque 'Dad's Best Friend', a sonic assault about isolation and toxic masculinity, was featured prominently in the Trainspotting Sequel, "T2"
Most services just include cleaning and relubrication. Parts don’t wear out that quickly.
Most watches from before the quartz crisis (pre ‘70s) used standard off-the-shelf Swiss movements for which spare parts are still readily available. It can get tricky with expensive or rare in-house stuff like Omega and Rolex though.
The minute hand is set to 43-ish minutes past the hour while the hour hand is showing 15-ish minutes past noon/midnight. If you’re used to reading analog watches it’s jarring.
Watch a few hours of watch repair on YouTube. If you're still intrigued, I highly recommend Mark Lovick's course over at https://www.watchfix.com/. You'll learn all you need to know about tools, lubricants and techniques to service most watch movements.
It is remarkable indeed! When not ruining watches with resin I enjoy servicing them, and I'm planning to learn how chronographs work next. The ST19 movement is on its way now, another very reasonably priced, reliable and fully mechanical chronograph with a column wheel. Hats off to the Chinese.
[0] https://en.wikipedia.org/wiki/Utility_frequency#Stability
reply