This week, Jonathan Bennett talks Rocky Linux with Gregory Kurtzer and Krista Burdine! Where did the project come from, and what’s the connection with CIQ and RESF? Listen to find out!
Hackaday Columns4287 Articles
This excellent content from the Hackaday writing crew highlights recurring topics and popular series like Linux-Fu, 3D-Printering, Hackaday Links, This Week in Security, Inputs of Interest, Profiles in Science, Retrotechtacular, Ask Hackaday, Teardowns, Reviews, and many more.
Retrotechtacular: Yamming CRT Yokes
Those of us who worked in TV repair shops, back when there was such a thing, will likely remember the cardinal rule of TV repair: Never touch the yoke if you can help it. The complex arrangement of copper wire coils and ferrite beads wrapped around a plastic cone attached to the neck of the CRT was critical to picture quality, and it took very little effort to completely screw things up. Fixing it would be a time-consuming and frustrating battle with the cams, screws, and spacers that kept the coils in the right orientation, both between themselves and relative to the picture tube. It was best to leave it the way the factory set it and to look elsewhere for solutions to picture problems.
But how exactly did the factory set up a deflection yoke? We had no idea at the time, only learning just recently about the wonders of automated deflection yoke yamming. The video below was made by Thomson Consumer Electronics, once a major supplier of CRTs to the television and computer monitor industry, and appears directed to its customers as a way of showing off their automated processes. They never really define yamming, but from the context of the video, it seems to be an industry term for the initial alignment of a deflection yoke during manufacturing. The manual process would require a skilled technician to manipulate the yoke while watching a series of test patterns on the CRT, slowly tweaking the coils to bring everything into perfect alignment.
Hack On Self: One Minute Blitz
Have you yet stumbled upon the principle of “consistently applied small amounts of work can guarantee completion of large projects”? I have, and it’s worked out well for me – on days when I could pay attention to them, that is.
A couple times, I’ve successfully completed long-term projects by making sure to do only a little bit of it, but I do it every day. It helps a lot with the feeling you get when you approach a large project – say, cleaning up your desk after a few days of heavy-duty hacking. If you’re multi-discipline, and especially if you happen to use multiple desks like me, a desk can stay occupied for a while.
Can you do one minute of desk cleaning today? Sure doesn’t feel like much time, or much effort. In a week’s time, however, you might just have a clean desk. Cleaning discrete messes is where this concept applies pretty well – you couldn’t wash floors like this, but you could wipe off the dust from a few surfaces for sure.
Now, I want to make this a habit – use it on like, seven different things a day. I wrote a script to make it possible – here’s how it works for me right now.
Building Upon The Seen-Before
I relied on a few previously-discussed things for this one. Main one is the Headphone Friend project – a pocketable Linux device, streaming audio from my laptop as I walk around my room. As a reminder, the headphones also have a button that emits HID events when pressed/released, and I have a small piece of software that can map actions to combinations of short-medium-long presses of that button.
Another necessity was a bit of software – dodging my questing system “away from laptop = system breaks” mistake, I wanted to put everything into my headphones, even the task names, trying to reach a “flow” through a series of 1-minute tasks. Of course, I reused the old sound library, but I also needed TTS generation on the fly! I went for PicoTTS with a simple wrapper – it’s not the best TTS system, but it’s damn fast, and perfectly suited for a prototype.
For the button-to-action mapping script, I had to expose some sort of API, to avoid merging the button scanning code and the task switching code. After a little deliberation, I picked websockets – they work decently well, and they’re quite portable, so I could run the button monitoring itself on the Headphone Friend device, and the main software on my laptop, for prototyping purposes.
Now, the more interesting question – how do I build the algorithm?
Keebin’ With Kristina: The One With The Cutting Board Keyboard
Doesn’t this look fantastic? Hard to believe it, but the base of this keyboard began life as a cutting board, and there’s a gallery to prove it. This is actually [androidbrick]’s second foray into this type of upcycling.
This time, [androidbrick] used a FiiO KB3 and replaced the bottom half of the plastic shell with a hand-routed kitchen cutting board. The battery has been disabled and it works only in wired mode, which is fine with me, because then you get to use a curly cord if you want.
Those keycaps look even nicer from top-down, which you’ll see in the sound test video linked above. Just search ‘JCM MOA GMK’ on Ali and you’ll find them in a bunch of colorways for around $20. Apparently, [androidbrick] was saving them for months, just waiting for this build.
Via reddit
Continue reading “Keebin’ With Kristina: The One With The Cutting Board Keyboard”
Hackaday Links: February 16, 2025
Just when you thought the saga of the Bitcoin wallet lost in a Welsh landfill was over, another chapter of the story appears to be starting. Regular readers will recall the years-long efforts of Bitcoin early adopter James Howells to recover a hard drive tossed out by his ex back in 2013. The disk, which contains a wallet holding about 8,000 Bitcoin, is presumed to be in a landfill overseen by the city council of Newport, which denied every request by Howells to gain access to the dump. The matter looked well and truly settled (last item) once a High Court judge weighed in. But the announcement that the Newport Council plans to cap and close the landfill this fiscal year and turn part of it into a solar farm has rekindled his efforts.
Howells and his investment partners have expressed interest in buying the property as-is, in the hopes of recovering the $780 million-ish fortune. We don’t think much of their odds, especially given the consistently negative responses he’s gotten over the last twelve years. Howells apparently doesn’t fancy his odds much either, since the Council’s argument that closing the landfill to allow him to search would cause harm to the people of Newport was seemingly made while they were actively planning the closure. It sure seems like something foul is afoot, aside from the trove of dirty diapers Howells seeks to acquire, of course.
Valentine’s Day…Hacks?
How do you reconcile your love for hacking projects together with your love for that someone special? By making him or her a DIY masterpiece of blinking red LEDs, but in heart shape. Maybe with some custom animations, and in a nice frame with a capacitive touch sensor to turn it on or off.
Or at least, that’s what I did. The good news is that my girlfriend, now wife, understands that this sort of present comes from a place of love. And it probably didn’t hurt that I also picked up some flowers to frame it with, and cooked her favorite lunch later that afternoon.
But if I’m 100% frank with myself, I’d have to admit that this was about 50% “present” and 50% “project”. Of course it also helps that she gets me, and that she knows that I put a bunch of effort into making it look as good as it did, and maybe because of that she forgives the 50% project.
Valentine’s day projects are a high-wire balancing act. If any other project fails, you can just try again. But here, the deadline is firm. Cosmetics matter a lot more on Valentine’s day than the other 364 days of the year, too. And finally, you really have to know the gift-receiver, and be sure that you’re not falling deeper into the excuse-for-a-cool-project trap than I did. And don’t forget the flowers.
I pulled it off with this one, at least, but I do feel like it was close, even today. Have you ever made a Valentine’s hacking project? How’d it go?
(Note: Featured image isn’t my project: It’s a lot more colorful!)
Hackaday Podcast Episode 308: The Worst 1 Ever, Google’s Find My Opened, And SAR On A Drone
It’s Valentine’s Day today, and what better way to capture your beloved’s heart than by settling down together and listening to the Hackaday Podcast! Elliot Williams is joined by Jenny List for this week’s roundup of what’s cool in the world of hardware. We start by reminding listeners that Hackaday Europe is but a month away, and that a weekend immersed in both hardware hacking and the unique culture offered by the city of Berlin can be yours.
The stand-out hack of the week is introduced by Elliot, Henrik Forstén’s synthetic aperture radar system mounted on a cheap quadcopter, pushing the limits of construction, design, and computation to create landscape imagery of astounding detail. Most of us will never create our own SAR system, but we can all learn a lot about this field from his work. Meanwhile Jenny brings us Sylvain Munaut’s software defined radio made using different projects that are part of Tiny Tapeout ASICs. The SDR isn’t the best one ever, but for us it represents a major milestone in which Tiny Tapeout makes the jump from proof of concept to component. We look forward to more of this at more reasonable prices in the future. Beyond that we looked at the porting of Google Find My to the ESP32, how to repair broken zippers, and tuning in to ultrasonic sounds. Have fun listening, and come back next week for episode 309! Continue reading “Hackaday Podcast Episode 308: The Worst 1 Ever, Google’s Find My Opened, And SAR On A Drone”
