Improving Aluminium Anodes For Lithium Batteries With Magnesium

Generally lithium-ion cells feature graphite anodes, but their chemical stability comes with the trade-off of poor capacity. Metal alloy anodes such as aluminium, silver and magnesium provide many advantages here, especially in terms of much higher capacity and higher charge/discharge rates. the formation of an LinM (lithium-metal) compound does however pose durability challenges due to volumetric expansion. This is a problem that [Yuki Nakata] et al. in an article in Communications Materials claim to have addressed for aluminium anodes.

A good overview of the advantages and challenges of various anode materials can be found in this 2026 overview article by [Serban] et al. in Coatings. In the research by [Nakata] et al. the issues with base aluminium (Al) foil anode material are further expanded upon, along with the benefits of alloying Al with magnesium (Mn).

The central problem with Al anodes is the phenomenon of Li remaining trapped in the anode below a Li-depleted Al surface, forcing delithiation through crack and pore formation in the Al. By alloying the Al with Mn the formation of these Li-depleted regions, as well as mitigating other potentially destructive mechanisms.

Although not a perfect solution, with surface degradation still clear after dozens of cycles, the authors reckon that surface coatings could address the stress from volumetric changes, potentially clearing the way for Al-Mn anode-based Li-ion cells.

Decapitation Seems Like A Great Way To Start X-Mas Decorating

American cultural osmosis being what it is, it’s likely more people know the story of Frosty the Snowman than have ever actually had the chance to build a snowman. What if you want a dancing holiday buddy of your own, but lack the key ingrediants of (a) Snow, and (b) a magic hat? Well, [Dr Jon EA] figured he could make do with a felt puppet and bunch of servos, and we say he pulled it off, as you can see in the video embedded below.

There are four servos driving the animatronic functions of this snomwan: one for each arm, and two to pan/tilt the head. Those are driven from a Pico 2W that gets its input from a 24 GHz radar module so it can interact with people around it. [Jon] has the snowman waving at people, watching them, and if you stand in front of it it nods and gestures as though the two of you are having a conversation. The personality is written as a state machine in about 300 lines of C code– which is on GitHub— and he’s incorporated servo easing into his driving code so the machine looks more lifelike instead of just jerking into position as servos are wont to do. He’s released the servo library in its own repo, if you’re interested in that.

Our favourite part of the build is, of course, the decapitation: [Jon] couldn’t get all the bits of his 3D printed frame up into the felt snowman puppet he started with from the base, so the head had to come off. There’s just something delightful about kicking off the holiday season with Mme Guillotine.

Animatronics tend to be more of a Halloween thing around here, but we’ve got robot Santas (Santii?) going back two decades now, so this is hardly out of place.

Thanks to [Dr Jon] for the tip! If you, too, are feeling the Christmas Spirit early this year, send us a tip with whatever you and your elves have cooked up.

Continue reading “Decapitation Seems Like A Great Way To Start X-Mas Decorating” →

Old FireWire Audio Interface Gets USB C Upgrade

[bonsembiante] had a PreSonus Firestudio Project on hand. It’s a very capable audio interface with 8 inputs and 8 outputs, along with MIDI to boot. However, it’s got one problem—it runs on FireWire. To bring it into modernity, the device would need an upgrade to USB operation.

This would be no mean feat. [bonsembiante] decided to remove the original FireWire controller hardware entirely, replacing it with an XMOS-based USB audio setup while reusing the existing audio circuitry in the interface. The trick was figuring out where all the digital audio signals were on the original board, and wiring them into the XMOS board with an interleaved ground-signal pattern with equal length conductors to avoid issues with interference and jitter. With the modern XMOS board hacked into the older hardware, all that was then required were the right drivers to get modern machines accessing all 8 ins and outs via a USB C connection. Files are on Github for the curious.

The hope is to turn this into a broader project that can be used on a range of older FireWire-based audio interfaces. To that end, [bonsembiante] has an explainer page on the goals and purpose of the fuegocable effort. The next interfaces targeted by the project are the Presonus FP10 and Focusrite Saffire.

We’ve featured [bonsembiante’s] work before, too, like this ADSL modem repurposed as a guitar effects pedal. Video after the break.

Continue reading “Old FireWire Audio Interface Gets USB C Upgrade” →

A test print being struck with a comically large hammer. It did not break.

How Would You Break This Flexible PETG?

Polymaker has a new PETG formulation they bill as “unbreakable”, sold as G-Flex. Aside from the questionable choice of name, it certainly looks like good stuff in a recent video review by [3D Printing Nerd].

A little flex can go a long way to increasing durability — which PETG already has over PLA — but too much flex and you get into difficulty printing, which apparently this filament doesn’t have. It’ll go through a multi-material system like Bambu’s AMS without trouble, for instance, as [3D Printing Nerd] demonstrates with a multi-color figurine, which he also fails to break. Now, just because it didn’t get destroyed in one YouTube video doesn’t mean we’re willing to swallow the “unbreakable” marketing, and to his credit, the [3D Printing Nerd] isn’t either.

One big advantage of this slightly-flexible filament over a comparable TPU is its bridging ability: it bridges like PETG. It prints like PETG, it can even use the same G-code as a PETG print you already prepared. Except it’s shore 95A hardness, which does put it into the flex category.

We’re big fans of PETG, and there’s probably going to be rolls of flexy PETG in Hackaday printers at some point. But for now we leave it to you: how do you propose to break the “unbreakable” filament?

Continue reading “How Would You Break This Flexible PETG?” →

Hackaday Podcast Episode 395: Pancake Slicer, RGB LED Origami, And Farting Synthesizers

This week, Elliot Williams and Kristina Panos met up in the super-secret studio to bring you some Hackaday news, a ‘lil something from the Mailbag, and wax nerdily about a whole lot of hacks.

In the news, we’re hiring, so come join us! If you’re reading this, chances are good that you know the format, and you’re ready to get your hands on the tips line. Just do what it says in the post, and we’ll get back to you.

Elliot dumped out the Mailbag and a single letter fluttered down to the table. It was from [iPod enjoyer], who is still using an iPod in 2026 and seems to appreciate the embedded art that ships with this here Podcast.

Then, it was on to the hacks, as you’ve come to expect. There’s something for everyone!

Check out the links below if you want to follow along, and as always, tell us what you think about this episode in the comments!

Download in lovely MP3.

Continue reading “Hackaday Podcast Episode 395: Pancake Slicer, RGB LED Origami, And Farting Synthesizers” →

E-Paper Price Tags Become Picture Frames

E-paper has lots of applications, though it’s found a particularly solid market penetration as a replacement for simple paper price tags. Because why have a cheap slip of paper for a fraction of a cent when you could have a complicated piece of electronics displaying a price? In any case, some of these price tags can be repurposed for more interesting uses, as this work from [steanlab] demonstrates.

pin16 is an open firmware for Solum EFR32BG22 e-paper price tags. Or, as the industry calls them, Electronic Shelf Labels (ESL). It covers the El016 (200×200) and EL022 (160×296) models, both of which have four colors—black, white, red, and yellow. The firmware allows uploading images over Bluetooth from a browser, turning the humble price tag into a picture frame. Pictures are converted within the browser into a format suitable for display on the tags, and are then shown as a slideshow on a timer.

Updates to firmware can be made over Bluetooth once the pin16 firmware is installed, however, it’s worth noting that initial install requires using SWD to reprogram. There’s no way to backup the factory firmware either, so don’t do this on tags that don’t belong to you.

They may not be the highest-resolution or prettiest digital picture frames out there, but nevertheless, it’s fun to see these tags opened up for other uses. Of course, you’re not limited to just using them as picture frames, either—you can use the firmware to upload your own tag graphics if you still want to use them as labels. We’ve seen other similar hacks before, too, and we’d love to see more—so light up the tipsline if you’ve got ’em!

This Week In Security: Java4Shell, Optimizely Malware, Shrinking Disclosure Deadlines, Unpatchable Freezers

Last month, the details of PHP2Shell leaked before the embargo lifted, and PHP had to scramble its release out early. This week, the same research firm, Calif, had it happen again, this time with Java. Java4Shell (CVE-2026-114938) is a heap overflow in OpenJDK’s hardware-accelerated Base64 decoder, and on November 17, Calif said it was going public early because the vulnerability had leaked. Oracle and OpenJDK pushed fixes that afternoon, and Calif followed with its write-up.

Java normally runs virtual bytecode inside the Java virtual machine, but when a function gets called often enough, the HotSpot JIT compiler turns it into native code. For some common operations it goes a step further, and swaps in hand-tuned machine code which uses special CPU instructions. On x86-64 CPUs with AVX-512 instructions, Base64 decoding is one of those, chewing through 64 bytes at a time with a mask that decides which output bytes actually get written. When the last chunk of input is a short, malformed tail with “=” padding, the calculated output length underflows below zero, the mask ends up with every bit set, and the decoder writes 64 bytes where it should have written at most two. Java then correctly throws an exception for the bad input, but by then, 62 bytes past the end of the output buffer have already been overwritten.

The overwritten bytes are fixed; the attacker controls when and where the write happens, but not what is written. Calif turned that into a working exploit anyhow. The overflow overwrites the length field of a nearby array, which allows for overwriting more of the heap with chosen values, and then into a way to read heap memory back in a response, which may hold keys, tokens, and other secrets. From there, Calif escalated to code execution, grooming the heap remotely by carefully timing the pieces of the HTTP request. Calif is holding back the exploits for specific applications for now, and points out that every target needs its own custom setup.

Not every Java server is vulnerable. The bug needs OpenJDK 17.0.6 or newer, and an x86-64 processor with AVX-512 VBMI, which in practice means Intel Ice Lake or newer server chips, or AMD Zen 4 or newer; ARM servers are safe. The decoder also has to be JIT compiled first, which Upwind found took about 10,000 decodes, so a busy server qualifies and an idle one may not. Unfortunately, Base64 shows up everywhere attacker input arrives. i’IUpwind found that the standard HTTP Basic authentication handling in Spring Security, Tomcat, and Jetty, as well as Auth0’s java-jwt library, feed attacker-supplied data to the vulnerable decoder before checking any credentials. If you can’t update yet, starting Java with “-XX:-UseBASE64Intrinsics” disables the vulnerable code. Unlike Log4Shell, this is a bug in the Java runtime itself, not in a library, so dependency scanners won’t find it, and the fix means replacing the runtime everywhere it lives, including inside every container image.

Continue reading “This Week In Security: Java4Shell, Optimizely Malware, Shrinking Disclosure Deadlines, Unpatchable Freezers” →