Series of purple and red mechanisms are stretched from left to right. Almost like arrows pointing right.

Compliant Mechanism Shrinks Instead Of Stretching

May 16, 2025 by Ian Bos 16 Comments

Intuitively, you think that everything that you stretch will pull back, but you wouldn’t expect a couple of pieces of plastic to win. Yet, researchers over at [AMOLF] have figured out a way to make a mechanism that will eventually shrink once you pull it enough.

Named “Counter-snapping instabilities”, the mechanism is made out of the main sub-components that act together to stretch a certain amount until a threshold is met. Then the units work together and contract until they’re shorter than their initial length. This is possible by using compliant joints that make up each of the units. We’ve seen a similar concept in robotics.

Potentially this may be used as a unidirectional actuator, allowing movement inch by inch. In addition, one application mentioned may be somewhat surprising: damping. If a structure or body is oscillating through a positive feedback loop it may continue till it becomes uncontrollable. If these units are used, after a certain threshold of oscillation the units will lock and retract, therefore stopping further escalation.

Made possible by the wonders of compliant mechanics, these shrinking instabilities show a clever solution to some potential niche applications. If you want to explore the exciting world of compliance further, don’t be scared to check out this easy to print blaster design!

Continue reading “Compliant Mechanism Shrinks Instead Of Stretching” →

This Week In Security: Lingering Spectre, Deep Fakes, And CoreAudio

May 16, 2025 by Jonathan Bennett 5 Comments

Spectre lives. We’ve got two separate pieces of research, each finding new processor primitives that allow Spectre-style memory leaks. Before we dive into the details of the new techniques, let’s quickly remind ourselves what Spectre is. Modern CPUs use a variety of clever tricks to execute code faster, and one of the stumbling blocks is memory latency. When a program reaches a branch in execution, the program will proceed in one of two possible directions, and it’s often a value from memory that determines which branch is taken. Rather than wait for the memory to be fetched, modern CPUs will predict which branch execution will take, and speculatively execute the code down that branch. Once the memory is fetched and the branch is properly evaluated, the speculatively executed code is rewound if the guess was wrong, or made authoritative if the guess was correct. Spectre is the realization that incorrect branch prediction can change the contents of the CPU cache, and those changes can be detected through cache timing measurements. The end result is that arbitrary system memory can be leaked from a low privileged or even sandboxed user process.

In response to Spectre, OS developers and CPU designers have added domain isolation protections, that prevent branch prediction poisoning in an attack process from affecting the branch prediction in the kernel or another process. Training Solo is the clever idea from VUSec that branch prediction poisoning could just be done from within the kernel space, and avoid any domain switching at all. That can be done through cBPF, the classic Berkeley Packet Filter (BPF) kernel VM. By default, all users on a Linux system can run cBPF code, throwing the doors back open for Spectre shenanigans. There’s also an address collision attack where an unrelated branch can be used to train a target branch. Researchers also discovered a pair of CVEs in Intel’s CPUs, where prediction training was broken in specific cases, allowing for a wild 17 kB/sec memory leak.

Continue reading “This Week In Security: Lingering Spectre, Deep Fakes, And CoreAudio” →

There are a number of metal cylinders displayed in a line. Each cylinder has a rectangular brass plate mounted to each end, and these brass plates stand upright, with the metal cylinders held horizontally between them.

Home-casting Thermoelectric Alloys

May 16, 2025 by Aaron Beckendorf 4 Comments

If you want to convert heat into electrical power, it’s hard to find a simpler method than a thermoelectric generator. The Seebeck effect means that the junction of two dissimilar conductors will produce a voltage potential when heated, but the same effect also applies to certain alloys, even without a junction. [Simplifier] has been trying to find the best maker-friendly thermoelectric alloys, and recently shared the results of some extensive experimentation.

The experiments investigated a variety of bismuth alloys, and tried to determine the effects of adding lead, antimony, tin, and zinc. [Simplifier] mixed together each alloy in an electric furnace, cast it into a cylindrical mold, machined the resulting rod to a uniform length, and used tin-bismuth solder to connect each end to a brass electrode. To test each composition, one end of the cylinder was cooled with ice while the other was held in boiling water, then resistance was measured under this known temperature gradient. According to the Wiedemann-Franz law, this was enough information to approximate the metal’s thermal conductivity.

Armed with the necessary data, [Simplifier] was able to calculate each alloy’s thermoelectric efficiency coefficient. The results showed some useful information: antimony is a useful additive at about 5% by weight, tin and lead created relatively good thermoelectric materials with opposite polarities, and zinc was useful only to improve the mechanical properties at the expense of efficiency. Even in the best case, the thermoelectric efficiency didn’t exceed 6.9%, which is nonetheless quite respectable for a homemade material.

This project is a great deal more accessible for an amateur than previous thermoelectric material research we’ve covered, and a bit more efficient than another home project we’ve seen. If you just want to get straight to power generation, check out this project.

Wireless Doorbell Extension Features Home-Wound Coil

May 16, 2025 by John Elliot V 12 Comments

Today in the it’s-surprising-that-it-works department we have a ding dong doorbell extension from [Ajoy Raman].

What [Ajoy] wanted to do was to extend the range of his existing doorbell so that he could hear it in his workshop. His plan of attack was to buy a new wireless doorbell and then interface its transmitter with his existing doorbell. But his approach is something others might not have considered if they had have been tasked with this job, and it’s surprising to learn that it works!

What he’s done is wrap a new coil around the ding dong doorbell’s solenoid. When the solenoid activates, a small voltage is induced into the coil. This then gets run into the wireless doorbell transmitter power supply (instead of its battery) via a rectifier diode and a filter capacitor. The wireless doorbell transmitter — having also had its push-button shorted out — operates for long enough from this induced electrical pulse to transmit the signal to the receiver. To be clear: the wireless transmitter is fully powered by the pulse from the coil around the solenoid. Brilliant! Nice hack!

We weren’t sure how reliable the transmitter would be when taken out of the lab and installed in the house so we checked in with [Ajoy] to find out. It’s in production now and operating well at a distance of around 50 feet!

Of course we’ve published heaps of doorbell hacks here on Hackaday before, such as this Bluetooth Low Energy (BLE) doorbell and this light-flashing doorbell. Have you hacked your own doorbell? Let us know on the tips line!

Continue reading “Wireless Doorbell Extension Features Home-Wound Coil” →