Replicating The World’s Oldest Stringed Instrument

Posts on Hackaday sometimes trend a little bit retro, but rarely do we cover hacks that reach back into the Bronze Age. Still, when musician [Peter Pringle] put out a video detailing how he replicated an ancient Sumerian instrument, we couldn’t wait to dig in.

The instrument in question is the “Golden Lyre of Ur”, and it was buried at the Royal Cemetery of Ur with a passel of other grave goods (including a Silver Lyre) something around 4400 to 4500 years ago. For those not in the know, Ur was an early Sumerian city in the part of Mesopotamia became modern-day Iraq. A lyre is a type of plucked stringed instrument, similar to a harp.

That anything of the instrument remains after literal millennia buried under the Mesopotamian sand is thanks to the

This representation was unearthed in the same dig as the remains of the Golden Lyre and its silver sister.

extensive ornamentation on the original lyre– the gut strings and wooden body might have rotted away, but the precious stones and metals adorning the lyre preserved the outline of the instrument until it was excavated in 1922. Reconstruction was also greatly aided by contemporary mosaics and pottery showing similar lyres.

For particular interest are the tuning pegs, which required that artistic inspiration to recreate– the original archeological dig did not find any evidence of the tuning mechanism. [Peter] spends some time justifying his reconstruction, using both practical engineering concerns (the need for tension to get good sound) and the pictographic evidence. The wide “buzzing” bridge matches the pictographic evidence as well, and gives the lyre a distinct, almost otherworldly sound to Western ears. [Peter]’s reconstruction sounds good, though we have no way of knowing if it matches what you’d have heard in the royal halls of Ur all those dusty centuries ago. (Skip to 17:38 in the video below if you just want to hear it in action.)

The closest thing to this ancient, man-sized lyre we’ve seen on Hackaday before might be one of the various laser harp projects we’ve featured over the years. If you squint a little, you can see the distant echo of the Golden Lyre of Ur in at least some of them. We also can’t help but note that the buzzing bridge gives the Sumerian lyre a certain droning quality not entirely unlike a hurdy-gurdy, because we apparently can’t have a musical post without mentioning the hurdy-gurdy.

Continue reading “Replicating The World’s Oldest Stringed Instrument”

Close up of a DIY minimalist EDC multitool, a penny, and a paperclip

This Pocket Multitool Weighs Less Than A Penny

A multitool that weighs less than a penny? Yes, it exists. This video by [ToolTechGeek] shows his titanium flat-cut design tipping the scales at only 1.9 grams—lighter than the 2.5-gram copper penny jingling in your pocket. His reasoning: where most everyday carry (EDC) tools are bulky, overpriced, or simply too much, this hack flips the equation: reduce it to the absolute minimum, yet keep it useful.

You might have seen this before. This second attempt is done by laser-cutting titanium instead of stainless steel. Thinner, tougher, and rust-proof, titanium slashes the weight dramatically, while still keeping edges functional without sharpening. Despite the size, this tool manages to pack in a Phillips and flathead screwdriver, a makeshift saw, a paint-lid opener, a wire bender (yes, tested on a paperclip), and even a 1/4″ wrench doubling as a bit driver. High-torque screwdriving by using the long edges is a clever exploit, and yes—it scrapes wood, snaps zip ties, and even forces a bottle cap open, albeit a bit roughly.

It’s not about replacing your Leatherman; it’s about carrying something instead of nothing. Ultra-minimalist, featherlight, pocket-slip friendly—bet you can’t find a reason not to just have it in your pocket.

Continue reading “This Pocket Multitool Weighs Less Than A Penny”

Pinout of 74HC595

Using The 74HC595 Shift Register To Drive 7-Segment Displays

In a recent video our hacker [Electronic Wizard] introduces the 74HC595 shift register and explains how to use it to drive 7-segment displays.

[Electronic Wizard] explains that understanding how to apply the 74HC595 can increase the quality of your projects and also help keep the demands on the number of pins from your microcontroller to manageable levels. If you’re interested in the gory details you can find a PDF datasheet for the 74HC595 such as this one from Texas Instruments.

[Electronic Wizard] explains further that a shift register is like a small one byte memory where its data is directly available on its eight output pins, no input address required. When you pulse the clock pin (CLK) each bit in the eight bit memory shifts right one bit, making room for a new bit on the left. The bits that fall off the right hand side can daisy chain into another 74HC595 going out on pin 9 and coming in on pin 14.

Continue reading “Using The 74HC595 Shift Register To Drive 7-Segment Displays”

How Intel’s 386 Protects Itself From ESD, Latch-up And Metastability

To connect the miniature world of integrated circuits like a CPU with the outside world, a number of physical connections have to be made. Although this may seem straightforward, these I/O pads form a major risk to the chip’s functioning and integrity, in the form of electrostatic discharge (ESD), a type of short-circuit called a latch-up and metastability through factors like noise. Shielding the delicate ASIC from the cruel outside world is the task of the I/O circuitry, with [Ken Shirriff] recently taking an in-depth look at this circuity in Intel’s 386 CPU.

The 386 die, zooming in on some of the bond pad circuits. (Credit: Ken Shirriff)
The 386 die, zooming in on some of the bond pad circuits. (Credit: Ken Shirriff)

The 386 has a total of 141 of these I/O pads, each connected to a pin on the packaging with a delicate golden bond wire. ESD is on the top of the list of potential risks, as a surge of high voltage can literally blow a hole in the circuitry. The protective circuit for this can be seen in the above die shot, with its clamping diodes, current-limiting resistor and a third diode.

Latch-up is the second major issue, caused by the inadvertent creation of parasitic structures underneath the P- and NMOS transistors. These parasitic transistors are normally inactive, but if activated they can cause latch-up which best case causes a momentary failure, but worst case melts a part of the chip due to high currents.

To prevent I/O pads from triggering latch-up, the 386 implements ‘guard rings’ that should block unwanted current flow. Finally there is metastability, which as the name suggests isn’t necessarily harmful, but can seriously mess with the operation of the chip which expects clean binary signals. On the 386 two flip-flops per I/O pad are used to mostly resolve this.

Although the 386’s 1985-era circuitry was very chonky by today’s standards, it was still no match for these external influences, making it clear just how important these protective measures are for today’s ASICs with much smaller feature sizes.

Linux Fu: Windows Virtualization The Hard(ware) Way

As much as I love Linux, there are always one or two apps that I simply have to run under Windows for whatever reason. Sure, you can use wine, Crossover Office, or run Windows in a virtual machine, but it’s clunky, and I’m always fiddling with it to get it working right. But I recently came across something that — when used improperly — makes life pretty easy. Instead of virtualizing Windows or emulating it, I threw hardware at it, and it works surprisingly well.

Once Upon a Time

First, a story. Someone gave me a Surface Laptop 2 that was apparently dead. It wouldn’t charge, and you can’t remove the keyboard without power. Actually, you can with a paper clip, and I suggested pulling it to see if the screen would charge by itself. They said they had already bought a new computer, so they didn’t care.

Unsurprisingly, once I popped the keyboard off, the computer charged and was fine. You just have to replace the keyboard or use another one. Or use it as a tablet, which it is set up for anyway. But I have plenty of laptops and computers of every description. What was I going to do with this nice but keyboardless computer? Continue reading “Linux Fu: Windows Virtualization The Hard(ware) Way”

Bad To The Bluetooth: You Shouldn’t Use This Jammer

Back in the day, an FM bug was a handy way to make someone’s annoying radio go away, particularly if it could be induced to feedback. But these days you’re far more likely to hear somebody’s Bluetooth device blasting than you are an unruly FM radio.

To combat this aural menace, [Tixlegeek] is here with a jammer for the 2.4 GHz spectrum to make annoying Bluetooth devices go silent. While it’s not entirely effective, it’s still of interest for its unashamed jankiness. Besides, you really shouldn’t be using one of these anyway, so it doesn’t really matter how well it works.

Raiding the AliExpress 2.4 GHz parts bin, there’s a set of NRF24L01+ modules that jump around all over the band, a couple of extremely sketchy-looking power amplifiers, and a pair of Yagi antennas. It’s not even remotely legal, and we particularly like the sentence “After running the numbers, I realized it would be cheaper and far more effective to just throw a rock at [the Bluetooth speaker]“. If there’s a lesson here, perhaps it is that effective jamming comes in disrupting the information flow rather than drowning it out.

This project may be illegal, but unlike some others we think it (probably) won’t kill you.

Ask Hackaday: Where Are All The Fuel Cells?

Given all the incredible technology developed or improved during the Apollo program, it’s impossible to pick out just one piece of hardware that made humanity’s first crewed landing on another celestial body possible. But if you had to make a list of the top ten most important pieces of gear stacked on top of the Saturn V back in 1969, the fuel cell would have to place pretty high up there.

Apollo fuel cell. Credit: James Humphreys

Smaller and lighter than batteries of the era, each of the three alkaline fuel cells (AFCs) used in the Apollo Service Module could produce up to 2,300 watts of power when fed liquid hydrogen and liquid oxygen, the latter of which the spacecraft needed to bring along anyway for its life support system. The best part was, as a byproduct of the reaction, the fuel cells produced drinkable water.

The AFC was about as perfectly suited to human spaceflight as you could get, so when NASA was designing the Space Shuttle a few years later, it’s no surprise that they decided to make them the vehicle’s primary electrical power source. While each Orbiter did have backup batteries for emergency purposes, the fuel cells were responsible for powering the vehicle from a few minutes before launch all the way to landing. There was no Plan B. If an issue came up with the fuel cells, the mission would be cut short and the crew would head back home — an event that actually did happen a few times during the Shuttle’s 30 year career.

This might seem like an incredible amount of faith for NASA to put into such a new technology, but in reality, fuel cells weren’t really all that new even then. The space agency first tested their suitability for crewed spacecraft during the later Gemini missions in 1965, and Francis Thomas Bacon developed the core technology all the way back in 1932.

So one has to ask…if fuel cell technology is nearly 100 years old, and was reliable and capable enough to send astronauts to the Moon back in 1960s, why don’t we see them used more today?

Continue reading “Ask Hackaday: Where Are All The Fuel Cells?”