2026-04-16 16:00:59
Usually, you think of bird decoys as being a tool to lure birds to an untimely encounter with a hunter. However, [Interesting Engineering] has a story about robotic bird decoys in Grand Teton National Park that are helping restore the dwindling number of sage grouse in the park.
While some decoys are static, others are motorized to replicate mating rituals. The goal: lure real birds to safer areas to breed. Particularly, they want the birds to avoid areas around the Jackson Hole Airport. The robots are built with help from local students and robotics teams. While some of the construction is made of fabric and foam, actual bird feathers are also used.
The robots mimic lekking behavior, a courtship ritual where male grouse do repetitive motions combined with recorded mating calls. This attracts other grouse and, of course, results in chicks who will be raised nearby.
Assuming the effort is successful, the same technique could help other areas where restored areas are difficult to repopulate. You can find more pictures on the Park’s Instagram, and the title picture is from that collection.
Usually, when we see something like this, the robot is trying to remove something dangerous to the endangered plant or animal, not attract them.
2026-04-16 13:00:47
Recently [Jeff Geerling] has been tinkering with FireWire in order to use some older gear, which includes the use of a Raspberry Pi HAT called the Firehat. This provides a 6-pin FireWire port courtesy of the VIA VT6315N PCIe-to-FireWire chipset. As is typical with USB gear today as well, some FireWire gear requires more power than a port can provide, requiring the use of a powered hub. Unfortunately the use of a powered FireWire hub caused a bit of a conflagration event on [Jeff]’s desk.
Part of the issue appears to be that this Firehat board was designed as a companion to the Equip-1 DV capture device, with no attention paid to the idea that someone might be backfeeding power from an attached hub. As a result the VIA chip cried uncle and let out the magic smoke.
With this Firehat board taking its name clearly a bit too literal, [Jeff] will be reporting his findings to the developers, in the hope that perhaps some diodes or another solution against backfeeding can be added to the final design. Fortunately he was sent this board for testing prior to public release, so this definitely shows a clear flaw that can now be corrected.
We hope that [Jeff] has a good HEPA air filtration setup in his office to get rid of the acrid magic smoke, as it’s not meant to be enjoyed for long periods.
2026-04-16 10:00:57
Ever since it was called OpenBeOS, Haiku has targeted the x86 platform. That makes good sense: it’s hard enough maintaining a niche system on ubiquitous hardware. But x86 isn’t the only game in town anymore. Apple’s doing very well on ARM, Linux runs on oodles of ARM SBCs, and even Windows uh, exists, on that architecture, so why not Haiku? That’s what [smrobtzz] figured, and thanks to his work you can now run Haiku on ARM, in QEMU.
There’s no image available as yet — you still need to bootstrap your own from a working system, and ironically that system cannot be Haiku. [smrobtzz] apparently used MacOS, which makes sense as his ultimate goal is apparently to go where only Aishi Linux has gone before and boot Haiku on his M1 MacBook. There had been previous efforts to get Haiku going on Raspberry Pi hardware, which seems logical considering how lightweight the operating system is, but they’re apparently nowhere near booting either. QEMU is a good start.
Interestingly, according to the ports page, Haiku is “functional” on both RISC V QEMU and the now-discontinued HiFive Unmatched SBC. We don’t seem to have covered it, but that milestone happened five year ago. Given how most RISC V boards currently available are a bit slow for modern desktop Linux, Haiku would likely be a breath of fresh air. The BeOS-descended system might be single user, but it’s snappy.
We reported a couple of years back that Haiku was daily-drivable on x86 ,it’s only gotten better since then, assuming you choose the right hardware. Hardware support is always the hard part about alternative OSes, but Haiku users are absolutely spoiled compared to fans of MorphOS, which still only runs on G4 or G5 PowerPC, and even then not only some hardware.
2026-04-16 07:00:46
MicroPython is a well-known and easy-to-use way to program microcontrollers in Python. If you’re using an Arduino Uno Q, though, you’re stuck without it. [Natasha] saves the day by bringing us a a subset reimplementation of machine for the Arduino Uno Q.
In the past, microcontrollers were primarily programmed in C, but since MicroPython’s popularity increased over the years, it has become more and more common for introductory microcontroller programming to be in Python. Python, of course, is generally considered more beginner-friendly than C. [Natasha] presumably wanted to teach this way using an Uno Q, but the usual MicroPython APIs weren’t available. And so, in true hacker fashion, they simply made their own library to implement the most important bits of the familiar API. It currently implements a subset of the machine module: Pin, PWM, ADC, I2C, SPI and UART. While not complete, this certainly has potential to make the Uno Q easier to use for those familir with MicroPython.
2026-04-16 04:00:42
Home-fermented foods are great– they’re healthier, more flavourful, and cheaper than store-bought alternatives. What they aren’t is convenient: you need to prep a big batch of veggies, let it sit, and then you have to store the excess pickles. If you’re not careful, you end up with ancient, over-fermented pickles at the bottom of the crock, or worse– run out of pickles! Surely a fate worse than death. [Cody] at Cody’s Lab has a solution: a continous-flow fermentation process that keeps just the right supply of pickles coming at all times. Our grandmothers who kept a crock for months in the cold room or root cellar might be confused, but this hack brings pickles into the Just-In-Time framework of the 21st century.
Specifically this is for lactic acid fermentation, the type that gets you kosher dills, saurkraut and kimchi along with a whole mess of other tangy, tasty vegetable treats. Vinegar pickles are a whole other thing. It’s done in a brine, as the lactic acid bacteria are salt tolerant in a way that most things that would rot your food and/or make you sick would not. You can reuse the brine over and over, which is what [Cody] is doing: he crafts a U-shaped crock out of old glass bottles and a couple of pickle jars. He cuts the jars into angled pipe segments that are held together with aquarium sealant, which is apparently food safe. It holds water and looks surprisingly good, in that it isn’t hideous.
The bioreactor gets loaded up with veggies on one end, plus lots of salt and spices to taste, plus some cultured brine from an old batch to kickstart everything. The starter isn’t necessary; it just gets things going faster. The initial packing is the hardest: after filling it the first time, one needs only press new veggies in at one end, while removing tasty treats at the other. A special packing tool [Cody]makes helps with that, but he plans on adding a larger feed side. Thanks to that kickstart, the pickles were ready to try after about a week– which means his tube is a bit long, for his desired dwell time. If you like more fermentation to your pickles, then you might like this size.
May be the first time pickles have been featured on Hackaday without turning them into LEDs. We’ve featured plenty of fermentation projects, with automation to help make the best brew or a build for better tempeh, but not a lot of vegetables.
Thanks to [cam72cam] for the tip!
2026-04-16 02:30:51
Many modern desktop 3D printers include the ability to print in multiple colors. However, this typically only works with a few colors at a time, and the more colors you can use, the higher the machine’s cost and complexity. However, a recent technique allows printers to mix new colors by overlaying thin sheets of different filaments. [YGK3D] looks at how it works in a recent video.
In the early days of 3D printing, there were several competing approaches. You could have separate extruders, each with a different color. Some designs used a single extruder and switched between different filaments on demand. Others melted different filaments together in the hot end.
One advantage of the hotends that melted different materials is that you could make different colors by adjusting the feed rates of the plastics. However, that has its own problems with maintaining flow rate, and you can’t really use multiple material types. But using single or multiple hotends that take one filament at a time means you can only handle as many colors as you have filaments. You can’t mix, say, white and black to get gray.
Using Full Spectrum, you can define virtual filaments, and the software figures out how to approximate the color you want by using thin layers of different colors. The results are amazing. While this technically could work on any printer, in reality, a filament-switching printer will create a ton of waste to mix colors, and a single-filament machine will drive you batty manually swapping filament.
So you probably really need a tool changer and translucent plastic. You can see the difference in the test article when using opaque filament vs translucent ones. At low layer heights, four filament colors can give you 39 different colors. At more common layer heights, you may have to settle for 24 different colors.
One issue is that the top and bottom surfaces don’t color well. However, a new plugin that adds texture to the surfaces may help overcome that problem.
We looked at Full Spectrum earlier, but development continues. If you are still trying to get a handle on your filament-switching printer, we can help.
