Hackaday Links Column Banner

Hackaday Links: August 1, 2021

Amateur radio operators have a saying: When all else fails, there’s ham radio. And that’s true, at least to an extent — knock out the power, tear down the phone lines, and burn up all the satellites in orbit, and there will still be hams talking about politics on 40 meters. The point is, as long as the laws of physics don’t change, hams will figure out a way to send and receive messages. In honor of that fact, the police in the city of Pune in Maharashtra, India, make it a point to exchange messages with their headquarter using Morse code once a week. The idea is to maintain a backup system, in case they can’t get a message through any other way. It’s a good idea, especially since they rotate all their radio operators through the Sunday morning ritual. We can’t imagine that most emergency services dispatchers would be thrilled about learning Morse, though.

Just because you’re a billionaire with a space company doesn’t mean you’re an astronaut. At least that’s the view of the US Federal Aviation Administration, which issued guidelines pretty much while Jeff Bezos and his merry band of cohorts were floating about above the 100-km high Kármán line in a Blue Origin “New Shepard” rocket. The FAA guidelines make it clear that those making the trip need to have actually done something to qualify as an astronaut, by “demonstrated activities during flight that were essential to public safety, or contributed to human space flight safety.” That’s good news to the “Old Shepard”, who clearly was in control of “Freedom 7” during the Mercury program. But the Bezos brothers, teenager Oliver Daemen, and Wally Funk, one of the “Mercury 13” group of women who trained to be NASA astronauts but never got to fly, were really just along for the ride, as the entire flight was automated. It doesn’t take away from the fact that they’ve been to space and you haven’t, of course, but they can’t officially call themselves astronauts. This goes to show that even billionaires can just be ballast too.

Good news, everyone — if you had anything that was being transported aboard the Ever Given, your stuff is almost there. The Suez Canal-occluding container ship finally made it to its original destination in Rotterdam, approximately four months later than originally predicted.  After plugging up the vital waterway for six days last March, the ship along with her cargo and her crew were detained in Egypt’s Great Bitter Lake, perhaps the coolest sounding body of water in the world next to the Dead Sea. Legal squabbling ensued at that point, all the while rendering whatever was in the 20,000-odd containers aboard the ship pretty much pointless. We’d imagine that even with continuous power, whatever was in the refrigerated containers must be pretty nasty by now, so there’s probably a lot of logistics and clean-up left to sort out.

I have to admit that I have a weird love of explosive bolts. I don’t know what it is, but the idea of fasteners engineered to fail in a predictable way under the influence of pyrotechnic charges just tickles something in me. I mean, I even wrote a whole article on the subject once. So when I came across this video explaining how the Space Shuttles were held to the launch pad, I really had to watch it. Surprisingly, the most interesting part of this story was not the explosive aspect, but the engineering problem of supporting the massive vehicle on the launch pad. For as graceful as the Shuttles seemed once they got into orbit, they really were ungainly beasts, especially strapped to the external fuel tank and booster. The scale of the eight frangible nuts used to secure the boosters to the pad is just jaw-dropping. We also liked the idea that NASA decided to catch the debris from the explosions in a container filled with sand.

Retrotechtacular: Understanding Protein Synthesis Through Interpretive Dance

With the principles of molecular biology very much in the zeitgeist these days, we thought it would be handy to provide some sort of visual aid to help our readers understand the complex molecular machines at work deep within each cell of the body. And despite appearances, this film using interpretive dance to explain protein synthesis will teach you everything you need to know.

Now, there are those who go on and on about the weirdness of the 1960s, but as this 1971 film from Stanford shows, the 60s were just a warm-up act for the really weird stuff. The film is a study in contrasts, with the setup being provided by the decidedly un-groovy Paul Berg, a professor of biochemistry who would share the 1980 Nobel Prize in Medicine for his contributions to nucleic acid research. His short sleeves and skinny tie stand in stark contrast to the writhing mass of students capering about on a grassy field, acting out the various macromolecules involved in protein synthesis. Two groups form the subunits of the ribosome, a chain of ballon-headed students act as the messenger RNA (mRNA) that codes for a protein, and little groups standing in for the transfer RNA (tRNA) molecules that carry the amino acids float in and out of the process.

The level of detail, at least as it was understood in 1971, is impressively complete, with soloists representing things like T-factor and the energy-carrying molecule GTP. And while we especially like the puff of smoke representing GTP’s energy transfer, we strongly suspect a lot of other smoke went into this production.

Kitsch aside, and with apologies to Lewis Carroll and his Jabberwock, you’ll be hard-pressed to find a modern animation that captures the process better. True, a more traditional animation might make the mechanistic aspects of translation clearer, but the mimsy gyre and gimble of this dance really emphasize the role random Brownian motion plays in macromolecular processes. And you’ll never see the term “tRNA” and not be able to think of this film.

Continue reading “Retrotechtacular: Understanding Protein Synthesis Through Interpretive Dance”

Retrotechtacular: Mechanical TV From The People Who Made It Happen

If we have a television in 2021 the chances are that it will be a large LCD model, flat and widescreen, able to display HD images in stunning clarity. Before that we’d have had a CRT colour TV, them maybe our parents grew up with a monochrome model. Before those though came the first TVs of all, which were mechanical devices that relied on a spinning disk to both acquire and display the image. The BBC Archive recently shared a vintage clip from 1970 in which two of the assistants of [John Logie Baird], the inventor of the first demonstrable television system, demonstrated its various parts and revealed its inner workings.

We’ve covered the Nipkow scanning disk in a previous article, with its characteristic spiral of holes. We see the original Baird Televisor, but the interesting part comes as we move to the studio. Using the original equipment they show a dot of light traversing the presenter’s face to scan a picture before taking us to a mock-up of the original studio. Here there’s a surprise, because instead of the camera we’d expect today there is a Nipkow disk projector which traverses the subject sitting in the dark. A bank of photocells above the projector senses the reflected light, and returns a video signal.

The resulting low-resolution pictures had a low enough bandwidth to be broadcast over an AM radio transmitter, and for a tiny 30-line picture in the glowing pink of a neon light they provide a surprising amount of detail. With such a straightforward principle it’s not surprising that they’ve appeared in a few projects on these pages, including an Arduino driven colour video monitor, and a POV clock. Take a look at the video below the break.

Continue reading “Retrotechtacular: Mechanical TV From The People Who Made It Happen”

The Man-Machine

This week we saw a couple DIY tools for small-run manufacturing at home that help make your life easier if you’re climbing out of the happy bucket and into the pit of despair — when you’re making enough of the item that it’s not fun any more, but you still don’t have the volume to leave the manufacturing to someone else.

The first was an automatic through-hole soldering machine made from a 3D printer. This actually makes sense even if you’re getting boards assembled for you, because through-hole pads are a lot more expensive than SMT parts, and they usually charge per pin. Put a 2×20 pin header on your project, and it can end up costing a lot. Or you can robotificate the solution.

This week’s second solution really caught my eye. PnPassist is machine that turns your PCB around, locates a laser crosshair over the next SMT piece that you need to place, and even has an OLED screen that tells you what to put there. There are many great mechanical design choices here, but what really drew my attention is how well this machine fills a gap between manual and fully automatic pick-and-place.

I know you hate looking back and forth between the board and the schematic or parts list, trying to find just where Q23 is on the darn board, or looking up resistor values. With PnPassist, you still have to do the placing, but with machine guidance. If you don’t have the money or the space for a fully automatic PnP, this is an obvious win, but also for short runs when loading up the reels takes more time than populating the board, this could be a huge win.

I love this kind of human-capability-enhancing machine, and I’m always happy to see a design like this. It reminds me of the very clever Shaper Origin, or even just this handy automatic XY table for drilling many precise holes. In all these cases, there’s some part of the problem that would be hard to solve, require extremely bulky or expensive machinery, or can just be more simply accomplished by a meatbag. But combining machine precision with the human element produces something more than the sum of the parts.

What’s your favorite human-enhancing tool?

Fresh Paint Or Patina Of Ages, That’s The Antique Question

The world of antique furniture and the world of hackers rarely coincide, and perhaps the allure of the latest tech is greater for most of us than that of a Chipendale cabinet. But there are times when there are analagous situations in both worlds, so it’s worth taking a moment to consider something.

This late-17th-century dressing box would not be of such value or interest were a restoration to strip it of its patina. Daderot, CC0.
This late-17th-century dressing box would not be of such value or interest were a restoration to strip it of its patina. Daderot, CC0.

Antique furniture has survived for hundreds of years before being owned by today’s collectors. Along the way it picks up bumps and scrapes, wear, and even the occasional repair. Valuable pieces turn up all the time, having been discovered in dusty attics, cowsheds, basements, and all sorts of places where they may have been misused in ways that might horrify those who later pay big money for them. Thus there is a whole industry of craft workers in the field of furniture restoration whose speciality lies in turning the wreck of a piece of furniture into a valuable antique for the showroom.

The parallel in our community if you hadn’t already guessed, can be found in the world of retrocomputers. They are the antiques we prize, they come to us after being abused by kids and then left to languish in a box of junk somewhere. Their capacitors are leaking, their cases may be cracked or dirty, and they often possess the signature look of old ABS mouldings, their characteristic yellowing. This is caused by the gradual release of small quantities of bromine as the fire retardant contained within the plastic degrades under UV light, and causes considerable consternation among some retrocomputing enthusiasts. Considerable effort goes into mitigating it, with the favourite technique involving so-called Retr0bright recipes that use hydrogen peroxide to bleach away the colour.

Continue reading “Fresh Paint Or Patina Of Ages, That’s The Antique Question”

Hackaday Podcast 129: Super Clever 3D Printing, Jigs And Registration Things, 90s Car Audio, And Smooth LED Fades

Hackaday editors Mike Szczys and Elliot Williams have found a critical mass of projects this week that wouldn’t be possible without 3D printers. There’s an absolutely astounding model roller coaster that is true to the mechanisms and physics of the original (and beholden to hours of sanding and painting). Adding sheet material to the printing process is a novel way to build durable hinges and foldable mechanisms. Elliot picks out not one, but two quadruped robot projects that leverage 3D-printed parts in interesting ways. And for the electronics geeks there’s a server rack stuffed with Raspberry Pi, and analog electronic wizardry to improve the resolution of the WS2811 LED controller. We wrap it all up with discussions of flying boats, and adding Bluetooth audio to old car head units.

Take a look at the links below if you want to follow along, and as always, tell us what you think about this episode in the comments!

Direct download (60 MB or so.)

Places to follow Hackaday podcasts:

Continue reading “Hackaday Podcast 129: Super Clever 3D Printing, Jigs And Registration Things, 90s Car Audio, And Smooth LED Fades”

This Week In Security: Fail2RCE, TPM Sniffing, Fishy Leaks, And Decompiling

Fail2ban is a great tool for dynamically blocking IP addresses that show bad behavior, like making repeated login attempts. It was just announced that a vulnerability could allow an attacker to take over a machine by being blocked by Fail2ban. The problem is in the mail-whois action, where an email is sent to the administrator containing the whois information. Whois information is potentially attacker controlled data, and Fail2ban doesn’t properly sterilize the input before piping it into the mail binary. Mailutils has a feature that uses the tilde key as an escape sequence, allowing commands to be run while composing a message. Fail2ban doesn’t sanitize those tilde commands, so malicious whois data can trivially run commands on the system. Whois is one of the old-school unix protocols that runs in the clear, so a MItM attack makes this particularly easy. If you use Fail2ban, make sure to update to 0.10.7 or 0.11.3, or purge any use of mail-whois from your active configs. Continue reading “This Week In Security: Fail2RCE, TPM Sniffing, Fishy Leaks, And Decompiling”