Mysterious Files PH

The age of steam is long gone, but there are few railfans who don’t have a soft spot for the old rolling kettles. So you’d best believe when [AeroKoi] talks about 3D printed train whistles, that’s steam whistles. Generally speaking, Diesels have horns.

You would not expect printed plastic to hold up to live steam– but that’s why [AeroKoi] uses compressed air. Besides, it’s a lot easier to both justify and maintain an air compressor than a boiler in the shop. At least some hobbyists say it doesn’t make a huge difference with brass whistles, so it should be good enough for plastic. What’s interesting is that even with 120 PSI blasting through them, these multi-part prints held together and sounded amazing.

[AeroKoi] does demonstrate there was a learning curve to climb before he had a good whistle design, and shows you what features worked best. He shared two successes on Thingiverse: A 6-Chime whistle from the Sante Fe Railroad, and a Northern Pacific 5-chime whistle, both 4″ in diameter and printed in vertically sectioned parts. The Northern Pacific is not to be confused with the totally different Union Pacific Railroad, whose famous “Big Boy” also had a whistle feature in the video — though evidently he’s not as happy with it, since he did not share the design.

Those are all North American designs, but there’s no reason this technique wouldn’t work to replicate a more European sound; one of his early experiments was kind of going in that direction already. Of course if you want a perfect replica, the old ways are the best ways: cast brass and live steam. We’ve had a few articles about train whistles in the past, one of which was a doorbell. 

For this challenge, we asked you to show off your hacks that power themselves sustainably from the environment around them. After all, nobody likes wires, and changing batteries is just a hassle. What’s better than an autonomous gizmo? Nothing.

Because this is Hackaday, we expected to see some finished-looking projects, some absolutely zany concepts, and basically everything in-between, and you did not disappoint! So without further ado, let’s have a look at the 2026 Green Powered Challenge winners, each of whom will be going on a $150 shopping spree at DigiKey, our contest’s sponsor.

LightInk Solar Watch

LightInk is a beautiful wristwatch, and e-ink is a natural companion to the small power budget that you get with a wrist-mounted solar panel. But don’t be fooled by its good looks! The real beauty of this hack is the way that [Daniel Ansorregui] crammed the screen-updating routine into the wakeup stub in the RTC peripheral. This means that the ESP32 doesn’t have to access the SPI flash every time it wakes up, saving precious milliseconds of wake time, and cutting average power in half. This is a trick you’ll want to know even if you don’t need a sexy e-ink wristwatch. (Which you do.)

Supercapacitor Solar IoT

[Nelectra]’s “Heliotrax” solar supercapacitor charger stores up the sun’s power in low-maintenance supercapacitors until it’s time to wake up your device. But supercaps have an output voltage that depends dramatically on their state of charge, so [Nelectra] added a high-efficiency and low-leakage boost converter to get a nice constant voltage out. Depending on your current needs, it can charge up in the sun and run for a few dark days without any problems. It’s a one-stop shop for solar-powered IoT devices, and it should make a whole range of projects easier to realize.

powerTimer

[Juan Flores]’s powerTimer is another module that enables your small off-grid hacks. In this case, it’s a simple latching electronic switch, designed for ultra-low quiescent power. Maybe your project has a microcontroller with a good sleep mode, but the peripherals are leaky hogs? Put the powerTimer in the middle and get your whole system’s power budget down without much extra thought. And if you don’t want to wake the microcontroller, it’s got a low-power RTC on board that can handle periodic wakeups. It’s a sweet, simple design that solves a real problem, and our judges loved that.

Honorable Mentions

• Solar: We knew there would be some great solar-powered projects here, and [Jake Wachlin]’s Ultra Low Power Feather Development Board is a great example. He pairs a low-power accelerometer and barometer with a power-sipping microcontroller to almost achieve ambient-room-lighting capability. [Jake] says you have to put it directly under a light, or in indirect sunlight. But if you have full sun at your disposal, [Arnov Sharma]’s SolMate is a lovely DIY solar power bank that we’d love to bring to the park with us.
• Anything But PV: OK, enough solar. [Ethan]’s Gravity-Powered Digital Clock is exactly the sort of out-of-the-box idea we were hoping to see. He pairs a Casio F91W with an insane gear train, a homebrew electrical generator, and a dumbbell to gather up all of the gravity that makes it work. Or should do so. The gear train ended up having so many stages that it wouldn’t turn under its own magnified friction, and the project doesn’t quite spin. But we love the idea of a wind-up electrical clock, and we hope [Ethan] doesn’t give up!
• Least Power: [caspar]’s Harvesting NFC Energy to Transmit Commands includes a stock Pi Pico dev board and some AA batteries, so you might be thinking “where is the low power element?” It’s the NFC wakeup circuit that reads in some data and writes it directly to the Pico’s EEPROM, before it wakes the chip up, which then reads the command out of EEPROM and does whatever it does under normal battery power, and then shuts itself down again. We love the idea of surreptitious NFC-powered data insertion while the microcontroller is still sleeping.
• Most Power: We initially expected this honorable mention to go to an over-sized solar install, but in the end [alnwlsn]’s Practical Power Cycling won over our judges with an unbeatable display of human determination: over five years, [alnwlsn] has generated 38 kWh on his generator bike, has powered a 3D printer through a Benchy, and even toasted a piece of toast. Maybe the real power here is the human spirit? Check out [alnwlsn]’s great build logs and diary.

Thanks to All!

Much thanks to everyone who entered into this challenge. We had more great entries than we have space to feature, so be sure to check them all out on Hackaday.io. And of course, thanks again to DigiKey for sponsoring the contest, and for providing our three finalists with the parts they need!

A pinhole camera is almost a rite of passage in photography, given that you can make one so easily with little more than a cardboard box and enough tape to keep the light from coming through the cracks. [Socialmocracy] has made one that’s 3D printed, and it’s a nice design that takes 4″ by 5″ photographic paper. The shutter is held on with magnets, and the lid is attached with thumbscrews.

As neat as printed pinhole cameras are, it’s not as though they’re particularly uncommon. What makes this one stand out from the rest is that it’s actually two cameras in one. One box, two cameras, side by side. Landscape format and it’s a pair of panoramic cameras, while in portrait mode it’s a stereo camera. Even the simplest of cameras can do wigglegrams!

We like this camera, because it manages to add something to such a simple formula.. He’s taking comments on whether to release the STLs, so drop in your two cents.

The idea of FDM 3D printing using granules rather than filament is an appealing one: rather than having to wrangle spools of filament that need to adhere to strict dimensions and cannot be too flexible, you can instead just keep topping up a big hopper with fresh granules. This is what [HomoFaciens] has been tinkering with for a while now, with their Direct Granules Extruder V7.0 showing significant improvements.

There’s also an accompanying article, with details of previous granule extruder attempts detailed on the same site. Many of the improvements here focus on making sure the granules melt properly before they reach the end of the extruder, with the auger screw helping to push things along. While this seems straightforward, there are many details to get right, with the previous v6.2 version having issues like the hot plastic backing up into the cold section and clogging things up.

For the test bench a Prusa Mk4 FDM printer is used, with the standard extruder swapped for the experimental extruder. On the extruder the cold, top part is water cooled to ensure it stays cold, with each turn of the wood-screw-turned-auger providing the right extrusion speed. As can be seen with the print tests, the results look pretty good despite the extruder not having been tuned yet.

If you want to give it a shot yourself, the article page provides files for download.

There are all manner of musical synthesis techniques, from the early electromechanical instruments through analogue tape systhesis, the all-electronic waveform synthesisers of the 1960s onwards, and Yamaha’s FM systhesis of the 1980s, to name but a few. One of the attributes of such a machine lies in how many voices it has, or in simple terms, how many notes it can play simultaneously. Electronic complexity limited those early synths, but what happens on an FPGA where vast numbers of circuits can be made with little extra cost? [Tsuneo.Ohnaka] is pushing the envelope a little, by cramming 10240 individually controllable oscillators onto a Terasic DE10-nano FPGA board.

While this thing can in theory generate 10240 different notes at once, in practice that doesn’t mean it has 10240 voices. Instead he calls it a spectrum engine, in that with such a large number of oscillators all with individually controllable frequency, phase, and amplitude, he’s made the part of all those Fourier transform maths where all the different frequencies are combined, in hardware. It’s as though you had a sound card which wasn’t based around a DAC fed with samples, instead all those spectrum points you’d derive from a Fourier transform. Because it’s a massive parallel array of real oscillators it all happens concurrently, instantaneously in real time, and is not held back by the processing constraints of a microprocessor. Think of it as something akin to a software defined radio transmitter, but for the world of audio synthesis.

In that light, it can emulate all those other forms of audio synthesis driven by software, but without the software overhead of generating the waveforms. It’s certainly a different approach to generating audio from a computer, and he’s posted a cacophonic demo video below of it as an 80-voice polyphonic synthesiser. We like it.

It’s been a story of the last week or so if you follow the kind of news channels a Hackaday scribe does, that Google have quietly installed an LLM as part of the Chrome browser. Reports vary as to when they did this because there’s a lot of confusion online with their online Gemini features also present in the browser, but it seems Chrome users are noticing its effect through slower performance and hefty disk access. Given that Chrome is by far the most popular web browser, this means that billions of users will have downloaded the four gigabyte Gemini Nano model, and now have an LLM they didn’t know about. It will be used to provide advanced auto-correct and other text suggestion features that their online version of Gemini would presumably be overburdened with, and since it’s available through a set of in-browser APIs we expect that it will find its way into a lot of websites, online applications, and plugins.

It’s caused a bit of a fuss in some circles, and we think, with some justification. When billions of computers unwittingly install an extremely energy intensive software component the effect on global power consumption will be significant, with a consequent uptick in the carbon footprint of computing. It’s not a phenomenon restricted to Chrome, as an example Siri has used a local LLM on Apple devices for a while now. We’ve seen rumblings of discontent and talk of getting European climate regulators involved, but perhaps instead it’s time to have a conversation about local AI models. The key is not whether or not they are a good thing to have, but when and how they operate.

While many of us are sick to death of AI slop and have not been lured into AI psychosis by an over-reinforcing chatbot, the fact remains that LLMs can do some useful things, they’re here to stay whether we like it or not, and having one under your control on your own computer doesn’t have to be a bad thing. Install Llama.cpp on your machine, and you’ve got an LLM of your very own, upon which your usage data isn’t going to be sold, and your content isn’t going to reinforce the finest plagiarism device the world has ever seen.

Opt-In and Opt-Out

The concerning development with the Chrome LLM is that not only has it been installed without the user’s consent, it runs without their consent too, and they can’t use it for anything except what Google Chrome wants it to be used for. Unlike the Llama.cpp mentioned above, it’s not under their control, instead it’s a compute-hungry monster ultimately controlled by Google. The prospect of a future in which multiple pieces of everyday software install their own similarly out-of-control multi-gigabyte CPU-munchers is a concerning one. Anyone who remembers Microsoft’s Clippy grabbing all the resources in a 1990s desktop as its stuttering animation played its course will know where this is going.

If local LLMs are an inevitability, what’s needed is a way to make them like any other application, one that the user chooses and installs themselves. Such an LLM could make its services available to applications such as a web browser if the user allows it to, but not run unless asked. It’s fairly obvious that installing Llama.cpp or similar is beyond many users, but it shouldn’t lie beyond the bounds of possibility to package something like it as an application they can install.

We know that the previous paragraph is pie-in-the-sky wishful thinking, and that as the person who knows computers in your family your next few Christmases will be spent wrestling with six different LLMs running on some elderly family member’s PC. But perhaps in Clippy lies the answer. If the consumer can learn to associate built-in AI features with their computer grinding to a halt just as they did with an office assistant thirty years ago, then perhaps they’ll demand change. We can hope.

Converting the ignition of a fuel-air mixture into usable mechanical energy lies at the core of a dizzying number of internal combustion engines developed over the course of more than century. Although typical piston engines with a cylinder head and valve-train are the most common by far, and even rotary engines are quite well-known, the opposed-piston engine design is significantly more obscure. In a recent video by [driving 4 answers], this type of engine is covered and why it’s actually a pretty nifty ICE design with many benefits.

Above all, the design is mechanically far more simple, as it omits all the valves and timing-related hardware of the typical four-stroke ICE. Each ignition event pushes against two pistons at the same time, allowing for more of the kinetic energy to be converted into usable power, as well as enabling largely vibration-free operation in a more compact package, especially in the case of the Asender design that eliminates the second crankshaft of the Achates design. This makes the Asender rather similar to the 1914 Simpson’s design.

Despite these many advantages, opposed-piston engines have mostly led a quiet life in industrial and military applications, including tanks, submarines and airplanes. This is where the video also sees their continued use, but as a 2021 article in Autoweek suggests, we might be seeing more of these engines in everywhere from trucks to cars as well. Even if it’s only in hybrid cars where it would be in a generator role, there are many reasons why this ICE design would fit right into certain roles.