1
4

PS1 logo on the top screen of a white DS

Gaming on a Nintendo DS can bring back great memories of long car trips from the past. But looking back, we remember wishing to play more than the DS could ever hope to handle. [fami] looks into the SuperCard DSTWO in her recent video, a solution to our past sorrows.

Able to play anything from the very games designed for the DS to emulated PS1 games, the DSTWO is more than capable of surpassing the abilities of the DS itself. More impressively, all games are run directly from the cartridge itself rather than on the DS’s hardware. While this emulated console within a handheld is impressive, it is far from simple to get running.

The DSTWO runs with an Ingenic JZ4732 as the CPU, completely different from any native architecture of the DS. Pair this with the unhelpful SDK made for the cartridge, and the aging hardware is held together by the community development behind any improvements. This is aided by the CPU similarities of another widely modded game console, the Dingoo A320.

When not having a fit, and after going through hours of troubleshooting, you might find the DSTWO running a game of SimCity 2000 or even Spyro the Dragon inside a DS. Even with the difficulties of use, the fact that these games run at all is impressive. If you want to try the DSTWO emulation yourself, check out the forums.

This is far from the only example of extreme care going into emulation. Here at Hackaday, we have covered similarly impressive projects such as this completely DIY handheld made for any retro game emulation you throw at it.

Thanks to DjBiohazard for the tip!


From Blog – Hackaday via this RSS feed

2
2

EFI from cables is something every ham loves to hate. What if you modulated, that, though, using an ordinary cable as an antenna? If you used something ubiquitous like a video cable, you might have a very interesting exploit– which is exactly what [Xieyang Sun] and their colleagues have done with TEMPEST-LoRa, a technique to encode LoRa packages into video files

The concept is pretty simple: a specially-constructed video file contains information to be broadcast via LoRa– the graphics card and the video cable serve as the Tx, and the Rx is any LoRa module. Either VGA or HDMI cables can be used, though the images to create the LoRa signal are obviously going to differ in each case. The only restriction is that the display resolution must be 1080×1920@60Hz, and the video has to play fullscreen. Fullscreen video might make this technique easy to spot if used in an exploit, but on the other hand, the display does not have to be turned on at the time of transmission. If employed by blackhats, one imagines syncing this to power management so the video plays whenever the screen blanks. 

This image sends LoRa. Credit: TEMPEST-LoRa

According to the pre-print, a maximum transmission distance of 81.7m was achieved, and at 21.6 kbps. That’s not blazing fast, sure, but transmission out of a totally air-gapped machine even at dialup speeds is impressive.  Code is on the GitHub under an MIT license, though [Xieyang Sun] and the team are white hats, so they point out that it’s provided for academic use. There is a demo video, but as it is on bilbili we don’t have an easy way to embed it. The work has been accepted to the ACM Conference on Computer and Communications Security (2025), so if you’re at the event in Taiwan be sure to check it out. 

We’ve seen similar hacks before, like this one that uses an ethernet cable as an antenna. Getting away from RF, others have used fan noise, or even the once-ubiquitous HDD light. (And here we thought casemakers were just cheaping out when they left those off– no, it’s security!)

Thanks to [Xieyang Sun] for the tip! We’ll be checking the tips line for word from you, just as soon as we finish wrapping ferrites around all our cables.


From Blog – Hackaday via this RSS feed

3
5

Turbo engine mockup

[Ryan] of [Fat Lip Collective] has been on a streak of using 3D printing for his car mod projects. From spark plug adapters to exhaust pipes to dash panels, his CAD skills and additive manufacturing tech have played a number of roles in his process.

Most recently, [Ryan] has embarked on a mission to equip an ’80s-era Toyota KE70 Corolla with a turbo engine. The main question there being how to fit the engine back into the car once he’s inserted a salvaged turbo into the exhaust line.

There is a non-trivial amount of stuff that needs to be packed in with the rest of the engine and finding a working configuration that doesn’t get in the way of anything else requires some trial and error. Furthermore, the alignment of the many twisting and turning pieces of schedule 40 pipe that will direct gasses where they need to go needs to be pretty precise.

Juggling all of this would be tedious, time consuming, and error prone if it were not for [Ryan’s] mighty 3D printer. He printed a set of the different elbows and reducers modeled on the schedule 40 pipe that he would likely be using. He added degree markers for easy reference later and flat sections at the ends of each piece so they could be bolted to each other. With this kit of parts in hand, he was able to mock up different arrangements, re-configuring them as he considered the position of other nearby components.

The project is still ongoing. but we’re looking forward to seeing [Ryan] roaring around in his souped-up Corolla soon. In the meantime you can go deeper on ways of adding turbo to vehicles from the ’90s, the innovation of the Mercedes Formula 1 split turbo engine, and see the evolution of a 3D-printed pulsejet turbocharger.

Thanks to [Ryan Ralph] (not the same Ryan) for tipping us off.


From Blog – Hackaday via this RSS feed

4
8

Some people can’t be bothered to read the analog face of a traditional clock. Some people cannot stand the low frequency “hum” of mains current. If you are in either of those categories, you probably don’t want to make [Christian]’s handsome and well-documented electromechanical CMOS clock.

As you might guess from the name, the clock uses CMOS logic, based around a 12 bit counter, to provide the divider circuits 24 (daily) and 60 (minutes and seconds). Specifically, the circuits are based around a CD4040 twelve-bit adder. Those signals go through DAC circuits based around DAC0808 chips to drive some very nice coil meters for hours and minutes in lieu of the traditional clock face. Taking the time to make a CMOS clock circuit from adder chips is respectable enough in this era of instant-gratification through micro-controllers, and we dig the blinkenlights built into the circuits, but it’s what is being added that is where things get really interesting.

[Christian] had the bright idea that a stepper motor could be driven via the mains, simply by using a capacitor to offset the waveforms on the coils by 90 degrees. With a 200-step stepper motor, [Christian] gets one revolution per second out of the 50 Hz grid; this generates the seconds signal for his CMOS chips by the simple expedient of a 3D printed arm and a light barrier. Once per second, the light is interrupted by the spinning arm, creating a pulse for the clock circuits to add up. Check it out in action in the demo video below.

This project also seems to have the distinction of being the first project submitted to our One Hertz Challenge. It’s not just for clocks, but keep an eye on your clock because entries are only open until 9:00 AM Pacific time on August 19th.


From Blog – Hackaday via this RSS feed

5
6

Cooking is all about temperature control: too cold isn’t good enough, and too hot can ruin everything. To aid in this regard, [Printerforge] created a smart temperature alarm to keep them aware of exactly what’s going on in the pot.

The device is simple — it uses an Arduino Nano hooked up to a thermistor to measure the temperature of fluid in a pot. The microcontroller displays the current temperature and the target temperature on a simple 16×2 character LCD. Upon the fluid reaching the target temperature, the alarm is sounded, indicating that the cooking has reached a given stage or must otherwise be seen to. The whole build is wrapped up in a simple 3D printed case, along with a lithium-ion cell with charging managed via a TP4056 module.

If you’re regularly letting your pasta overcook or your stews burn in the pot, this kind of tool could be useful for you. Similarly, if you’ve ever wanted to pursue the 64-degree egg, this could be a way to do it.  The trick is to make sure you build it safely—ensuring that any parts that come into contact with the food are rated as food safe for your given application.

If this build has you contemplating the possibilities of machine-assisted cooking, you might like to go even further. How about getting involved in the world of sous vide? Meanwhile, if you’ve got any kitchen hacks of your own, don’t hesitate to let us know on the tipsline!


From Blog – Hackaday via this RSS feed

6
4

It’s Independence Day here in the USA, but if you’re not a fan of fireworks and hot dogs, Elliot and Dan’s rundown of the best hacks of the week is certainly something to celebrate. Rest easy, because nothing exploded, not even the pneumatic standing desk that [Matthias] tore into, nor the electroplated 3D prints that [H3NDRIK] took a blowtorch to. We both really loved the Ploopiest knob you’ve ever seen, which would be even Ploopier in anodized aluminum, as well as an automatic book scanner that takes its job very seriously. We looked into the mysteries of the Smith chart, another couple of fantastic student projects out of Cornell, the pros and cons of service loops, and what happened when the lights went out in Spain last Spring. And what does Janet Jackson have against laptops anyway?

Download this entirely innocent-looking MP3.

Where to Follow Hackaday Podcast

Places to follow Hackaday podcasts:

iTunesSpotifyStitcherRSSYouTubeCheck out our Libsyn landing page

Episode 327 Show Notes:

News:

Supercon CFP ExtendedAnnouncing The 2025 Hackaday One Hertz Challenge

What’s that Sound?

Fill out this form for your chance to win!

Interesting Hacks of the Week:

Open-Source Knob Packed With Precision Ploopy Open Source Trackball Keeps Rolling AlongA Ploopy Pick and PlaceStanding Desk Uses Pneumatics To Do The JobData Visualization And Aggregation: Time Series Databases, Grafana And More Howto: Docker, Databases, And Dashboards To Deal With Your DataVictoriaMetrics: Simple & Reliable Monitoring for EveryoneA Scanner For Arduino-Powered Book Archiving Page-turning Book Scanner RoundupAutomatic Book Scanner To Bring Knowledge To Ethiopian StudentsAudio Localization Gear Built On The CheapMeet Cucumber, The Robot DogBlowtorching Electroplated 3D Prints For Good Reason

Quick Hacks:

Elliot’s Picks Turbine Blower 3D Prints Every Part, Including Triple Planetary GearsWindows 95 On PlayStation 2 Works As Well As You ExpectedPhone Keyboard Reverse EngineeredDan’s Picks: Pi Networks The Smith Chart WayAre Service Loops A Good Idea?Move Over, Cybertruck: Series Hybrids From Edison Are On The Way Edison Blue Hex Code

Can’t-Miss Articles:

One Laptop Manufacturer Had To Stop Janet Jackson Crashing Laptops Shouting in the Datacenter – YouTubeThe 2025 Iberian Peninsula Blackout: From Solar Wobbles To Cascade Failures The 2003 Northeast Blackout And The Harsh Lessons Of Grid Failures


From Blog – Hackaday via this RSS feed

7
8

These days ‘AI’ is everywhere, including in software development. Coming hot on the heels of approaches like eXtreme Programming and Pair Programming, there’s now a new kind of pair programming in town in the form of an LLM that’s been digesting millions of lines of code. Purportedly designed to help developers program faster and more efficiently, these ‘AI programming assistants’ have primarily led to heated debate and some interesting studies.

In the case of [Jj], their undiluted feelings towards programming assistants like GitHub Copilot burn as brightly as the fire of a thousand Suns, and not a happy kind of fire.

Whether it’s Copilot or ChatGPT or some other chatbot that may or may not be integrated into your IDE, the frustration with what often feels like StackOverflow-powered-autocomplete is something that many of us can likely sympathize with. Although [Jj] lists a few positives of using an LLM trained on codebases and documentation, their overall view is that using Copilot degrades a programmer, mostly because of how it takes critical thinking skills out of the loop.

Regardless of whether you agree with [Jj] or not, the research so far on using LLMs with software development and other tasks strongly suggests that they’re not a net positive for one’s mental faculties. It’s also important to note that at the end of the day it’s still you, the fleshy bag of mostly salty water, who has to justify the code during code review and when something catches on fire in production. Your ‘copilot’ meanwhile gets off easy.


From Blog – Hackaday via this RSS feed

8
33

So-called artificial intelligence (AI) is all the rage right now between your grandma asking ChatGPT how to code in Python or influencers making videos without having to hire extras, but one growing concern is where the power is going to come from for the data centers. The MIT Technology Review team did a deep dive on what the current situation is and whether AI is going to kill us all (with carbon emissions).

Probably of most interest to you, dear hacker, is how they came up with their numbers. With no agreed upon methods and different companies doing different types of processing there were a number of assumptions baked into their estimates. Given the lack of information for closed-source models, Open Source models were used as the benchmark for energy usage and extrapolated for the industry as a whole. Unsurprisingly, larger models have a larger energy usage footprint.

While data center power usage remained roughly the same from 2005 to 2017 as increases in efficiency offset the increase in online services, data centers doubled their energy consumption by 2023 from those earlier numbers. The power running into those data centers is 48% more carbon intensive than the US average already, and expected to rise as new data centers push for increased fossil fuel usage, like Meta in Louisiana or the X data center found to be using methane generators in violation of the Clean Air Act.

Technology Review did find “researchers estimate that if data centers cut their electricity use by roughly half for just a few hours during the year, it will allow utilities to handle some additional 76 gigawatts of new demand.” This would mean either reallocating requests to servers in other geographic regions or just slowing down responses for the 80-90 hours a year when the grid is at its highest loads.

If you’re interested in just where a lot of the US-based data centers are, check out this map from NREL. Still not sure how these LLMs even work? Here’s an explainer for you.


From Blog – Hackaday via this RSS feed

9
7

Using an SMD capacitor as a clip for flash media on a circuit board.

Here’s a clever hack. Simple, elegant, and eminently cost-effective: using an SMD capacitor to hold your flash media in place!

This is a hack that can pretty much be summed up with just the image at the top of the page — a carefully placed SMD capacitor soldered to a routed tab makes for an extremely cost effective locking mechanism for the nearby SD card slot. There’s just enough flexibility to easily move the capacitor when its time to insert or eject your media.

It’s worth noting that the capacitor in this example doesn’t even appear to be electrically connected to anything. But there’s also no reason you couldn’t position one of the capacitors in your existing bill of materials (BOM). This form of mechanical support will be much cheaper than special purpose clips or mounts. Not a big deal for low-volume projects, but if you’re going high-volume this is definitely something to keep in mind.

If you’re just getting started with SMD capacitors then one of the first things to learn is how to solder them. Also, if you’re hoping to salvage them then try to look for newer equipment which is more likely to have SMD components than through-hole. If you’re planning to use your capacitors for… “capacitance” (how quaint), you can start by learning the basics. And if you want to know everything you can learn about the history of capacitors, too.

Thanks to [JohnU] for writing in to let us know about this one. Have your own natty hacks? Let us know on the tipsline!


From Blog – Hackaday via this RSS feed

10
6

You could use a little pocket-sized Pez dispenser if you’re a humble, reserved person. Or, you could follow the example of [Backhaul Studios], and build a dangerously powerful blaster that shoots Pez fast enough to shatter them into pieces. Just don’t aim it at your own mouth.

As the video explains, Pez is really the perfect candy for this application. It’s compact, hard, and already designed to be dispensed via a magazine. It’s thus not a big stretch to set it up to be fired out of a pistol-like blaster. The build is of the flywheel type, where a pair of counter-rotating wheels fling the candy out at great speed. The wheels themselves are spun up to high speed with a pair of small brushless motors, running off hobby speed controllers and lithium-ion batteries. A simple trigger mechanism dispenses the rectangular candies into the wheel mechanism, sending them flying out of the blaster at will. It’s all 3D-printed, designed specifically for the purpose of high-speed candy delivery.

The video goes into great detail on the design, from the development of the TPU treads on the flywheels and other details that helped improve the effectiveness of the design. The final build shoots Pez fast enough that they practically detonate upon hitting a surface.

We’ve featured some innovative work in this space from [Backhaul Studios] before—the condiment cannon was really quite something. Video after the break.


From Blog – Hackaday via this RSS feed

11
8

Mjolnir, also known as Thor’s hammer, is a discerning thing, at least if you believe the modern Marvel canon. [alemanjir] decided to build a semi-functional replica that makes judgement calls of its own, though they’re perhaps a little less thought-out than the storied hammer of legend.

The build consists of a 3D-printed hammer prop, inside of which is a Raspberry Pi Pico microcontroller running the show. It’s hooked up to a MPR121 touch sensor that detects when someone grips the handle of the hammer. At this point, the Pico makes a pseudorandom “worthiness check” as to whether the holder is righteous enough to wield the hammer. If they are pure of heart, it unlocks a magnet which frees the hammer from whatever metallic surface it might be stuck to. [alemanjir] also included a little additional functionality, with the hammer playing various sounds when swung thanks to a speaker and a ADXL345 accelerometer secreted inside.

One wonders whether the electromagnet inside is strong enough to hold out against an unworthy person lifting it from the ground. While it’s perhaps not as powerful or as decisive as the mythical object, it’s nonetheless a fun learning project that likely taught [alemanja] some useful basics of embedded development.

We’ve featured some terrifying takes of the Mjolnir prop before, too, like this shockingly high voltage version. Video after the break.


From Blog – Hackaday via this RSS feed

12
9

An aluminium frame is visible, supporting several connected pieces of chemistry equipment. At the left, there is a tube containing a clear solution, with a tube leading to a clear tube heated by a gas flame, with another tube leading to a clear bottle, which has a tube leading to a bubbling orange solution.

Modern fertilizer manufacturing uses the Haber-Bosch and Ostwald processes to fix aerial nitrogen as ammonia, then oxidize the ammonia to nitric acid. Having already created a Haber-Bosch reactor for ammonia production, [Markus Bindhammer] took the obvious next step and created an Ostwald reactor to make nitric acid.

[Markus]’s first step was to build a sturdy frame for his apparatus, since most inexpensive lab stands are light and tip over easily – not a good trait in the best of times, but particularly undesirable when working with nitrogen dioxide and nitric acid. Instead, [Markus] built a frame out of aluminium extrusion, T-nuts, threaded rods, pipe clamps, and a few cut pieces of aluminium.

Once the frame was built, [Markus] mounted a section of quartz glass tubing above a gas burner intended for camping, and connected the output of the quartz tube to a gas washing bottle. The high-temperature resistant quartz tube held a mixture of alumina and platinum wool (as we’ve seen him use before), which acted as a catalyst for the oxidation of ammonia. The input to the tube was connected to a container of ammonia solution, and the output of the gas washing bottle fed into a solution of universal pH indicator. A vacuum ejector pulled a mixture of air and ammonia vapors through the whole system, and a copper wool flashback arrestor kept that mixture from having explosive side reactions.

After [Markus] started up the ejector and lit the burner, it still took a few hours of experimentation to get the conditions right. The issue seems to be that even with catalysis, ammonia won’t oxidize to nitrogen oxides at too low a temperature, and nitrogen oxides break down to nitrogen and oxygen at too high a temperature. Eventually, though, he managed to get the flow rate right and was rewarded with the tell-tale brown fumes of nitrogen dioxide in the gas washing bottle. The universal indicator also turned red, further confirming that he had made nitric acid.

Thanks to the platinum catalyst, this reactor does have the advantage of not relying on high voltages to make nitric acid. Of course, you’ll still need get ammonia somehow.


From Blog – Hackaday via this RSS feed

13
11

If you’re a solo musician, you probably have lots of gear you’d like to control, but you don’t have enough hands. You can enlist your feet, but your gear might not have foot-suitable interfaces as standard. For situations like these, [Nerd Musician] created the OpenMIDIStomper.

The concept is simple enough—the hardy Hammond enclosure contains a bunch of foot switches and ports for external expression pedals. These are all read by an Arduino Pro Micro, which is responsible for turning these inputs into distinct MIDI outputs to control outboard gear or software. It handles this via MIDI over USB. The MIDI commands sent for each button can be configured via a webpage. Once you’ve defined all the messages you want to send, you can export your configuration from the webpage by cutting and pasting it into the Arduino IDE and flashing it to the device itself.

We’ve featured some great MIDI controllers over the years, like this impressive parts bin build.


From Blog – Hackaday via this RSS feed

14
5

Good news, procrastinators! Today was going to be the last day to throw your hat in the ring for a slot to talk at Supercon in November, but we’re extending the deadline one more week, until July 10th. We have an almost full schedule, but we’re still missing your talk.

So if the thought of having missed the deadline fills you with regret, here’s your second chance. We have spots for both 40-minute and 20-minute talks still open. We love to have a mix of newcomers as well as longtime Hackaday friends, so don’t be shy.

Supercon is a super fun time, and the crowd is full of energy and excitement for projects of all kinds. There is no better audience to present your feats of hardware derring-do, stories of reverse engineering, or other plans for world domination. Where else will you find such a density of like-minded hackers?

Don’t delay, get your talk proposal in today.


From Blog – Hackaday via this RSS feed

15
11

[juskim] wanted to build a tiny mouse, but it couldn’t just be any mouse. It had to be a high-tech gaming mouse that could compete with the best on raw performance. The results are impressive, even if the final build is perhaps less than ideal for pro-level gameplay.

The build riffs on an earlier build from [juskim] that used little more than a PCB and a 3D-printed housing to make a barebones skeleton mouse. However, this one ups the sophistication level. At the heart of the build is the nRF54L15 microcontroller, which is paired with a PAW3395 mouse sensor which is commonly used in high-end gaming mice. It offers resolution up to 26K DPI for accurate tracking, speeds up to 650 ips, and 8 kHz sampling rates. Long story short, if you want fine twitch control, this is the sensor you’re looking for. The sensor and microcontroller are laced together on a custom PCB with a couple of buttons, a battery, and a charging circuit, and installed in a barebones 3D-printed housing to make the final build as small as possible.

The only real thing letting the design down is the mouse’s key feature—the size. There’s very little body to grab on to and it’s hard to imagine being able to play most fast-paced games at a high level with such a tiny device. Nevertheless, the specs are hardcore and capable, even if the enclosure isn’t.

[juskim] loves building tiny peripherals; we’ve featured his fine work before, too. Video after the break.


From Blog – Hackaday via this RSS feed

16
10

Some time last year, a weird thing happened in the hackerspace where this is being written. The Internet was up, and was blisteringly fast as always, but only a few websites worked. What was up? Fortunately with more than one high-end networking specialist on hand it was quickly established that we had a problem with our gateway’s handling of IPv4 addresses, and normal service was restored. But what happens if you’re not a hackerspace with access to the dodgy piece of infrastructure and you’re left with only IPv6? [James McMurray] had this happen, and has written up how he fixed it.

His answer came in using a Wireguard tunnel to his VPS, and NAT mapping the IPv4 space into a section of IPv6 space. The write-up goes into extensive detail on the process should you need to follow his example, but for us there’s perhaps more interest in why here in 2025, the loss of IPv4 is still something that comes with the loss of half the Internet. As of this writing, that even includes Hackaday itself. If we had the magic means to talk to ourselves from a couple of decades ago our younger selves would probably be shocked by this.

Perhaps the answer lies in the inescapable conclusion that IPv6 answers an address space problem of concern to many in technical spaces, it neither solves anything of concern to most internet users, nor is worth the switch for so much infrastructure when mitigations such as NAT make the IPv4 address space problem less of a problem. Will we ever entirely lose IP4? We’d appreciate your views in the comments. For readers anxious for more it’s something we looked at last year.


From Blog – Hackaday via this RSS feed

17
6

The door-unlocking mechanism, featuring a 3D printed bevel gear and NEMA 17 stepper.

How many times do you have to forget your keys before you start hacking on the problem? For [Binh], the answer was 5 in the last month, and his hack was to make a gesture-based door unlocker. Which leads to the amusing image of [Binh] in a hallway throwing gang signs until he is let in.

The system itself is fairly simple in its execution: the existing deadbolt is actuated by a NEMA 17 stepper turning a 3D printed bevel gear. It runs 50 steps to lock or unlock, apparently, then the motor turns off, so it’s power-efficient and won’t burn down [Binh]’s room.

The software is equally simple; mediapipe is an ML library that can already do finger detection and be accessed via Python. Apparently gesture recognition is fairly unreliable, so [Binh] just has it counting the number of fingers flashed right now. In this case, it’s running on a Rasberry Pi 5 with a webcam for image input. The Pi connects via USB serial to an ESP32 that is connected to the stepper driver. [Binh] had another project ready to be taken apart that had the ESP32/stepper combo ready to go so this was the quickest option. As was mounting everything with double-sided tape, but that also plays into a design constraint: it’s not [Binh]’s door.

[Binh] is staying in a Hacker Hotel, and as you might imagine, there’s been more penetration testing on this than you might get elsewhere. It turns out it’s relatively straightforward to brute force (as you might expect, given it is only counting fingers), so [Binh] is planning on implementing some kind of 2FA. Perhaps a secret knock? Of course he could use his phone, but what’s the fun in that?

Whatever the second factor is, hopefully it’s something that cannot be forgotten in the room. If this project tickles your fancy, it’s open source on GitHub, and you can check it out in action and the build process in the video embedded below.

After offering thanks to [Binh] for the tip, the remaining words of this article will be spent requesting that you, the brilliant and learned hackaday audience, provide us with additional tips.


From Blog – Hackaday via this RSS feed

18
5

When it comes to text, how small is too small? The experts say a six point font is the minimum for readability, but as [James Bowman] shows us, you can get away with half of that.

The goal is to produce a 40-character display on a 24 mm x 24 mm LCD that has a resolution of 240 x 240 to show a serial terminal (or other data) on the “TermDriver2” USB-to-Serial adapter. With 24 lines, that’s a line per millimeter: very small text. Three points, to be precise, half what the experts say you need. Diving this up into 40 columns gives a character cell of six by nine pixels. Is it enough?

The raw font on the left, the subpixel rendering on the right. For once, it’s better if you don’t click to enlarge.

Not by itself, no. That’s where the hack comes in: sub-pixel rendering. After all, a “white” pixel on an LCD is actually three elements: a red, a green, and a blue subpixel, stacked side-by-each. Drive each of those subpixels independently and 240 pixels now becomes 720. That’s plenty for a 40 column terminal.

The article discusses how, in general terms, they pulled off the subpixel rendering and kept the font as legible as possible. We think it’s a good try, though the colored fringe around the characters can be uncomfortable to look at for some people — and then we can’t forget the physical size of the characters being 1 mm tall.

If this trick were being used on a larger display with a 240-wide resolution, we’d say “yes, very legible, good job!”– but at this size? We hope we can find our reading glasses. Still, it’s a neat trick to have in your back pocket for driving low-resolution LCDs.

It may not surprise you that aside from improving legibility, subpixel rendering is also used for pixel (er, sub-pixel) art.

The full set of glyphs in their subpixel-rendered glory.


From Blog – Hackaday via this RSS feed

19
3

Great Scott! If my calculations are correct, when this baby hits 88 miles per hour, you’re gonna see some serious shit. — Doc Brown

On this day, forty years ago, July 3rd, 1985 the movie Back to the Future was released. While not as fundamental as Hackers or realistic as Sneakers, this movie worked its way into our pantheon. We thought it would be appropriate to commemorate this element of hacker culture on this day, its forty year anniversary.

If you just never got around to watching it, or if it has been a few decades since you did, then you might not recall that the movie is set in two periods. It opens in 1985 and then goes back to 1955. Most of the movie is set in 1955 with Marty trying to get back to 1985 — “back to the future”. The movie celebrates the advanced technology and fashions of 1985 and is all about how silly the technology and fashions of 1955 are as compared with the advancements of 1985. But now it’s the far future, the year 2025, and we thought we might take a look at some of the technology that was enchanting in 1985 but that turned out to be obsolete in “the future”, forty years on.

As the opening credits roll there are a bunch of different ticking clocks, signaling the time motif. But they are all analog clocks, some with pendulums, and not an LED or 7-segment display in sight. The only “digital” clock is a split-flap. The signaling of the time motif by clocks is done throughout the film, from the control panel in Doc’s DeLorean time-machine to the stopped clock on the town hall. Of course these days clocks have gotten much better and now they can even set themselves.

We see a wide-angled shot of Doc's vast collection of analog clocks.

The JVC hand-held video camera recorded to VHS tape. The competing format to VHS at the time was known as Betamax which was developed by Sony. You will of course still find hand-held video cameras today but these days they are far more capable such as with 8K video cameras and you probably have one as a feature of your smartphone anyway. The tape-based VHS and Betamax media has been made obsolete mostly by flash media.

We see Doc controlling the time-machine while Marty records the event with a large video camera; Doc's truck is in the background.

The old Cathode Ray Tube (CRT) television gave way to flat-screen LCD displays and nowadays transparent OLED is state of the art. There were two competing video standards back in 1985 being NTSC which was used in North America, Japan, parts of South America, and so on; and PAL which was used in Europe, Australia, parts of Asia, and Africa.

These old standards didn’t accommodate more than 30 frames-per-second, NTSC was 29.97 Hz and PAL was 25 Hz; and long before “widescreen” 16:9 aspect ratios were released in the 90s they had resolutions of up to 720 × 480 for NTSC and 720 × 576 for PAL. That’s “up to”, there were versions with resolutions worse than this. Of course this is a long way from the 4K@60Hz you have become accustomed to! Also there were no remote controls for these old beasts, you had to get up out of your chair to adjust the volume or change the channel, oh the indignity of it all!

We see an old CRT television with manual dials; a newscaster is presenting the news.

When Marty McFly rocks out, he plugs his guitar into a vacuum tube amplifier, a piece of gear that has proven to have surprisingly long legs. You would think that it would now be an anachronism, replaced by transistor technology, but many guitarists still think that analog vacuum tube technology has a superior and warmer distortion sound. Powering the amp is another dinosaur that survived. The Variac controller shown is an autotransformer that is still made and used, although in 1985 the Variac trademark was owned by General Radio but is now owned by ISE, Inc.

We see the scene widened to include what looks like a CRO and a bench VOM with a red toolbox in the background.The Cathode-Ray Oscilloscope (CRO) on the table there is completely obsolete, but it remains customary for a hacker to get nostalgic and buy one on eBay. The analog Voltage-Ohm-Milliamp (VOM) meter is maybe only half obsolete, and as with the CRO, a nostalgic hacker will still have one. Everyone else has a Digital Multi-Meter (DMM) which can do everything a VOM could do, and much more.

The old reel-to-reel magnetic tape recorder and player gave way to miniature flash storage in the end. And also a bunch of other media formats in the interim, ranging from floppy-disks to hard-drives. Reel-to-reel magnetic tech had a number of drawbacks, not least was that rewinding and fast-forwarding to find the track you were looking for was a real hassle. (Should we say a reel hassle?) Also the signal would get weaker and more distorted the more copies were made, this was known as generation loss and isn’t relevant to digital media.

We see Marty on the old pulse-dial telephone talking to Doc; there is equipment and mess everywhere; the fallen shelving is clearly visible in the back after the incident with the amplifier.

The pulse-dial telephone gave way first to DTMF-based phones and then ultimately to cellphones and Voice over IP. People who are too young to have seen or used a rotary-dial phone won’t know how slow and annoying they were to use. To key in a number you had to rotate the dial in proportion to the number you wanted to enter, one for one, two for two, up to nine for nine and ten for zero; so if you had larger numbers in the phone number you were keying in you would have to wait for the dial to count back, which was tedious and boring. It is certainly not for practicality reasons that hackers keep trying to bring them back.

We see Marty looking exasperated as he talks to Doc on the old pulse-dial phone; various shelving, books, and crockery are seen in the background.

Like the pulse-dial and DTMF-based landline telephones the cordless telephone also gave way to cellphones and VoIP, but the old cordless telephones get a special mention because they were totally insecure. The radio signals they used were easily sniffed by anyone who knew how to operate a radio. To patch this technical vulnerability, the FCC made listening to particular frequencies illegal, and manufacturers cut out the cellphone and wireless phone bands from their scanners.

We see Marty in his double-bed on his cordless telephone.

And to wrap-up let’s give a special mention to the push-button Seeburg vinyl jukebox. These were commonplace back in the day and every good bar had a coin-operated one. These days you’re unlikely to find a jukebox at the bar, it is perhaps more likely that one of the bar staff is streaming music to the bar’s Bluetooth speakers from their smartphone.

We see Marty still on the phone to Doc, with the jukebox clearly visible to the left, and clothing draped over furniture in the back.

Thanks for coming with us on this brief journey back to 1985, it was fun to take some time to look at some of the things that have changed, and to pay our respects to this icon of hacker culture on its fortieth birthday. Don’t forget to sound-off in the comments regarding where you have seen references to the movie!


From Blog – Hackaday via this RSS feed

20
4

Like many of us of a certain vintage, [Dillan Stock] at The Stock Pot is nostalgic for VHS tapes. It’s not so much the fuzzy picture or the tracking issues we miss, but the physical experience the physical medium brought to movie night. To recreate that magic, [Dillan] made a Modern VHS with NFC and ESPHome.

NFC tags are contained in handsomely designed 3D printed cartridges. You can tell [Dillan] put quite a bit of thought into the industrial design of these: there’s something delightfully Atari-like about them, but they have the correct aspect ratio to hold a miniaturized movie poster as a label. They’re designed to print in two pieces (no plastic wasted on supports) and snap together without glue. The printed reader is equally well thought out, with print-in-place springs for that all important analog clunk.

Electronically, the reader is almost as simple as the cartridge: it holds the NFC reader board and an ESP32. This is very similar to NFC-based audio players we’ve featured before, but it differs in the programming. Here, the ESP32 does nothing related directly to playing media: it is simply programmed to forward the NFC tag id to ESPHome. Based on that tag ID, ESPHome can turn on the TV, cue the appropriate media from a Plex server (or elsewhere), or do… well, literally anything. It’s ESPHome; if you wanted to make this and have a cartridge to start your coffee maker, you could.

If this tickles your nostalgia bone, [Dillan] has links to all the code, 3D files and even the label templates on his site. If you’re not sold yet, check out the video below and you might just change your mind. We’ve seen hacks from The Stock Pot before, everything from a rebuilt lamp to an elegant downspout and a universal remote.


From Blog – Hackaday via this RSS feed

21
4

Selecting a random sample from a set is simple. But what about selecting a fair random sample from a set of unknown or indeterminate size? That’s where reservoir sampling comes in, and [Sam Rose] has a beautifully-illustrated, interactive guide to how reservoir sampling works. As far as methods go, it’s as elegant as it is simple, and particularly suited to fairly sampling dynamic datasets like sipping from a firehose of log events.

While reservoir sampling is simple in principle it’s not entirely intuitive to everyone. That’s what makes [Sam]’s interactive essay so helpful; he first articulates the problem before presenting the solution in a way that makes it almost self-evident.

[Sam] uses an imaginary deck of cards to illustrate the problem. If one is being dealt cards one at a time from a deck of unknown size (there could be ten cards, or a million), how can one choose a single card in a way that gives each an equal chance of having been selected? Without collecting them all first?

In a nutshell, the solution is to make a decision every time a new card arrives: hold onto the current card, or replace it with the new one. Each new card is given a 1/n chance of becoming held, where n is the number of cards we’ve seen so far. That’s all it takes. No matter when the dealer stops dealing, each card that has been seen will have had an equal chance of ending up the one selected.

There are a few variations which [Sam] also covers, and practical ways of applying it to log collection, so check it out for yourself.

If [Sam]’s knack for illustrating concepts in an interactive way is your jam, we have one more to point out. Our own Al Williams wrote a piece on Turing machines; the original “universal machine” being a theoretical device with a read/write head and infinite paper tape. A wonderful companion to that article is [Sam]’s piece illustrating exactly how such a Turing machines would work in an interactive way.


From Blog – Hackaday via this RSS feed

22
4

This week Jonathan chats with benny Vasquez about AlmaLinux! Why is AlmaLinux the choice for slightly older hardware? What is the deal with RISC-V? And how does EPEL fit in? Tune in to find out!

https://www.linkedin.com/in/bennyvasquez/almalinux.orghttps://almalinux.org/blog/2025-04-24-election-announcement/https://almalinux.org/blog/2025-06-26-epel-v2-now-covers-almalinux-10-stable/

Did you know you can watch the live recording of the show right on our YouTube Channel? Have someone you’d like us to interview? Let us know, or contact the guest and have them contact us! Take a look at the schedule here.

Direct Download in DRM-free MP3.

If you’d rather read along, here’s the transcript for this week’s episode.

Places to follow the FLOSS Weekly Podcast:

SpotifyRSS

Theme music: “Newer Wave” Kevin MacLeod (incompetech.com)

Licensed under Creative Commons: By Attribution 4.0 License


From Blog – Hackaday via this RSS feed

23
1

Since the earliest days of affordable, home 3D printers, the technology behind them has been continuously improving. From lowering costs, improving print quality, increasing size and detail, and diversifying the types of materials, it’s possible to get just about anything from a 3D printer today with a minimum of cost. Some of the things that printers can do now might even be surprising, like this upgrade that makes [Startup Chuck]’s 3D printer capable of printing realistic-sounding cowbells out of plastic.

The key to these metal-like prints is a filament called PPS-CF which is a carbon fiber-reinforced polyphenylene sulfide, or PPS. PPS-CF has a number of advantages over other plastics including high temperature tolerance and high dimensional stability, meaning its less likely to warp or deform even in harsh environments. But like anything with amazing upsides, there are some caveats to using this material. Not only does the carbon fiber require more durable extruder nozzles but PPS-CF also needs an extremely hot print head to extrude properly in addition to needing a heated bed. In [Startup Chuck]’s specific case he modified his print head to handle temperatures of 500°C and his print bed to around 100°C. This took a good bit of work just to supply it with enough energy to get to these temperatures and caused some other problems as well, like the magnet on the printer bed demagnetizing above around 75°C.

To get to a working cowbell took more than just printer upgrades, though. He had to go through a number of calibrations and test prints to dial in not only the ideal temperature settings of the printer but the best thicknesses for the cowbell itself so it would have that distinct metallic ring. But cowbells aren’t the only reason someone might want to print with carbon-reinforced materials. They have plenty of uses for automotive, chemical processing, high voltage, and aerospace applications and are attainable for home 3D printers. Just make sure to take some basic safety precautions first.


From Blog – Hackaday via this RSS feed

24
48

There are all manner of musical myths, covering tones and melodies that have effects ranging from the profound to the supernatural. The Pied Piper, for example, or the infamous “brown note.”

But what about a song that could crash your laptop just by playing it? Even better, a song that could crash nearby laptops in the vicinity, too? It’s not magic, and it’s not a trick—it was just a punchy pop song that Janet Jackson wrote back in 1989.

Rhythm Nation

As told by Microsoft’s Raymond Chen, the story begins in the early 2000s during the Windows XP era. Engineers at a certain OEM laptop manufacturer noticed something peculiar. Playing Janet Jackson’s song Rhythm Nation through laptop speakers would cause the machines to crash. Even more bizarrely, the song could crash nearby laptops that weren’t even playing the track themselves, and the effect was noted across laptops of multiple manufacturers.

Rhythm Nation was a popular song from Jackson’s catalog, but nothing about it immediately stands out as a laptop killer.

After extensive testing and process of elimination, the culprit was identified as the audio frequencies within the song itself. It came down to the hardware of the early 2000s laptops in question. These machines relied on good old mechanical hard drives. Specifically, they used 2.5-inch 5,400 RPM drives with spinning platters, magnetic heads, and actuator arms.

The story revolves around 5,400 RPM laptop hard drives, but the manufacturer and model are not public knowledge. No reports have been made of desktop PCs or hard disks suffering the same issue. Credit: Raimond Spekking, CC BY-SA 4.0

Unlike today’s solid-state drives, these components were particularly susceptible to physical vibration. Investigation determined that something in Rhythm Nation was hitting a resonant frequency of some component of the drive. When this occurred, the drive would be disturbed enough that read errors would stack up to the point where it would trigger a crash in the operating system. The problem wasn’t bad enough to crash the actual hard drive head into the platters themselves, which would have created major data loss. It was just bad enough to disrupt the hard drive’s ability to read properly, to the point where it could trigger a crash in the operating system.

A research paper published in 2018 investigated the vibrational characteristics of a certain model of 2.5-inch laptop hard drive. It’s not conclusive evidence, and has nothing to do with the Janet Jackson case, but it provides some potentially interesting insights as to why similar hard drives failed to read when the song was played. Credit: Research paper

There was a simple workaround for this problem, that was either ingenious or egregious depending on your point of view. Allegedly, the OEM simply whipped up a notch filter for the audio subsystem to remove the offending frequencies. The filter apparently remained in place from the then-contemporary Windows XP up until at least Windows 7. At this point, Microsoft created a new rule for “Audio Processing Objects” (APO) which included things like the special notch filter. The rule stated that all of these filters must be able to be switched off if so desired by the user. However, the story goes that the manufacturer gained a special exception for some time to leave their filter APO on at all times, to prevent users disabling it and then despairing when their laptops suddenly started crashing unexpectedly during Janet Jackson playlists.

As for what made Rhythm Nation special? YouTuber Adam Neely investigated, and came up with a compelling theory. Having read a research paper on the vibrational behavior of a 2.5-inch 5,400 RPM laptop hard disk, he found that it reported the drive to have its largest vibrational peak at approximately 87.5 Hz.  Meanwhile, he also found that Rhythm Nationhad a great deal of energy at 84.2 Hz. Apparently, the recording had been sped up a touch after the recording process, pushing the usual low E at 82 Hz up slightly higher. The theory being that the mild uptuning in Rhythm Nationpushed parts of the song close enough to the resonant frequency of some of the hard drive’s components to give them a good old shaking, causing the read errors and eventual crashes.

It’s an interesting confluence of unintended consequences. A singular pop song from 1989 ended up crashing laptops over a decade later, leading to the implementation of an obscure and little-known audio filter. The story still has holes—nobody has ever come forward to state officially which OEM was involved, and which precise laptops and hard drives suffered this problem. That stymies hopes for further research and recreation of this peculiarity. Nevertheless, it’s a fun tech tale from the days when computers were ever so slightly more mechanical than they are today.


From Blog – Hackaday via this RSS feed

25
19

It’s been awhile since we checked in with Canada’s Edison Motors, so let’s visit [DeBoss Garage] for an update video. To recap, Edison Motors is a Canadian company building diesel-electric hybrid semi-trucks and more.

Arial view of Edison's new propertyThe last interesting thing to happen in Donald, BC was when it burned down in the 1910s.

Well, they’ve thankfully moved out of the tent in their parents’ back yard where the prototype was built. They’ve bought themselves a company town: Donald, British Columbia, complete with a totally-not-controversial slogan “Make Donald Great Again”.

More interesting is that their commercial-off-the-shelf (COTS), right-to-repair centered approach isn’t just for semi-trucks: they’re now a certified OEM manufacturer of a rolling heavy truck chassis you can put your truck cab or RV body on, and they have partnered with three coach-builders for RVs and a goodly number of manufacturing partners for truck conversion kits. The kits were always in the plan, but selling the rolling chassis is new.

One amazingly honest take-away from the video is the lack of numbers for the pickups: top speed, shaft horsepower, torque? They know what all that should be, but unlike the typical vaporware startup, Edison won’t tell you the engineering numbers on the pickup truck kits until it has hit the race track and proved itself in the real world. These guys are gear-heads first and engineers second, so for once in a long time the adage “engineers hate mechanics” might not apply to a new vehicle.

The dirt track is the first thing under construction in Donald, so hopefully the next update we hear from Edison Motors will include those hard numbers, including pesky little things like MSRP and delivery dates. Stay tuned.

In our last post about an electric truck, a lot of you in the comments wanted something bigger, heavier duty, not pure battery, and made outside the USA. Well, here it is.

Thanks to [Keith Olson] for the tip. Remember, the lines are always open!


From Blog – Hackaday via this RSS feed

view more: next ›

Hackaday

316 readers
73 users here now

Fresh hacks every day

founded 11 months ago
MODERATORS