Wine In Beverage Cans Had A Rotten Egg Problem, Until Now

Aluminum beverage cans are used for all kinds of drinks, but when it comes to wine there are some glitches. Chief among them is the fact that canned wine occasionally smelled like rotten eggs. Thankfully, researchers have figured out why that happens, and how to stop it. How was this determined? As the image above hints at, lots and lots of samples and testing.

What causes this, and why don’t other beverages have this problem? Testing revealed that the single most important factor was the presence of molecular sulfur dioxide (SO2), a compound commonly used in winemaking as an antioxidant and antimicrobial.

It turns out that the thin plastic lining on the inside of beverage cans doesn’t fully stop molecular SO2 from reacting with the surrounding aluminum, creating hydrogen sulfide (H2S) in the process. H2S has a very noticeable rotten egg smell, even in low concentrations.

Researchers discovered that if a canned beverage contained more than 0.5 ppm of molecular SO2, a noticeable increase in hydrogen sulfide was likely to be present within four to eight months. The problem is that since most wines aim for around 0.5 ppm of SO2, the average can on wine sitting on a shelf will have a problem sooner rather than later. The more SO2 in the wine (reds tend to contain less, whites more), the worse the problem.

Simply increasing the thickness of the plastic liner is an imperfect solution since it increases manufacturing costs as well as waste. So, researchers believe the right move is to use a more durable liner formulation combined with a lower SO2 concentration than winemakers are usually comfortable with. Unlike bottles, cans can be hermetically sealed which should offset the increased oxidation risk of using a lower concentration of SO2. The result should be wine as a canned beverage, with a shelf life of at least 8 months.

The research is published here and gives a great look at just how one approaches this kind of scientific problem, as well as highlighting just how interesting the humble aluminum beverage can really is.

An RGB LED clock that resembles a color blindness test.

RGB LED HexaClock Doesn’t Actually Light Up The Night

Who says a clock can’t be both useful and beautiful? That seems to be the big idea behind the lovely little HexaClock from [Bulduper]. And boy, is it both.

Probably the most important part of this well-illuminated clock is the light sensor, which allows it to adjust the brightness automatically. If you’re not into that, well, there’s a really nice web app that’ll let you program the dickens out of it.

The brains of this thing is an ESP8266 on a custom PCB which controls the 127 individually addressable RGB LEDs. The clock may look large, but the big printed parts just fit on the bed of a Prusa i3. [Bulduper] used ABS because the LED strip and the PCB might get a little warm; they didn’t want to risk using PLA and having it turn into a Salvador Dali clock (although that could be cool).

Speaking of heat, make sure to use 18 AWG or thicker wires as [Bulduper] advises. LEDs may be efficient, but this clock uses lots of them! If you want to build one of these to bathe your wall in useful light, everything you need is available on GitHub. Watch HexaClock do its thing in the brief demo and walk-through video after the break.

If this is a little too bright for your tastes, check out this synesthesia clock.

Continue reading “RGB LED HexaClock Doesn’t Actually Light Up The Night”

3D Printed Adapter Helps You Eat Chicken Nuggets On The Highway

So often, we see 3D printers used to create some nifty little tool for a tricky little job. Maybe it’s to lock cams together for a timing belt change, or to work as a jig for soldering some complex device. However, some hacks are even simpler than that. [maker_guy] realized that eating nuggets in the car could be easier than ever with a little printed adapter.

The print is simple. It’s a round caddy for the nugget sauces given out by Chick-fil-A restaurants. Why round? Because it lets the nugget sauce sit neatly in your car’s cupholder at an accessible height. Put the sauce tub in the adapter, peel it open, and you can dip to your heart’s content.

So simple, yet a game changer all the same.

No more delicately balancing Zesty Buffalo by the gearstick while you try and chow down. Nor will your seat covers be tainted with Honey Mustard!

“Not a hack!” you scream. “It’s frivolous nonsense!” To that I say, are you a nugget eater or not? I myself partake, and I can absolutely see the value in this. You see, us journalists work hard. We’re often stuck eating substandard food in our cars on the way from one thing to another, like so many others in busy professions. If a smart little 3D-printed adapter can make mealtime easier and save some mess, I’m calling that a win.

You should never be afraid to use your creativity to make tools to improve your life. Parts are on Thingiverse if you need to print your own. Mod it to suit McDonald’s product if you need. Heck, print in black and it’d look like a stock part of the car!

You don’t have to like this simple adapter, but you can’t deny its utility! Share your own nifty little adapter ideas in the comments.

Welcome Back, Voyager

In what is probably the longest-distance tech support operation in history, the Voyager mission team succeeded in hacking their way around some defective memory and convincing their space probe to send sensor data back to earth again. And for the record, Voyager is a 46-year old system at a distance of now 24 billion kilometers, 22.5 light-hours, from the earth.

While the time delay that distance implies must have made for quite a tense couple days of waiting between sending the patch and finding out if it worked, the age of the computers onboard probably actually helped, in a strange way. Because the code is old-school machine language, one absolutely has to know all the memory addresses where each subroutine starts and ends. You don’t call a function like do_something(); but rather by loading an address in memory and jumping to it.

This means that the ground crew, in principle, knows where every instruction lives. If they also knew where all of the busted memory cells were, it would be a “simple” programming exercise to jump around the bad bits, and re-write all of the subroutine calls accordingly if larger chunks had to be moved. By “simple”, I of course mean “incredibly high stakes, and you’d better make sure you’ve got it right the first time.”

In a way, it’s a fantastic testament to simpler systems that they were able to patch their code around the memory holes. Think about trying to do this with a modern operating system that uses address space layout randomization, for instance. Of course, the purpose there is to make hacking directly on the memory harder, and that’s the opposite of what you’d want in a space probe.

Nonetheless, it’s a testament to careful work and clever software hacking that they managed to get Voyager back online. May she send for another 46 years!

Photo Shows Real Spiders From Mars

A cornerstone of early 1970s rock music culture was the British singer David Bowie in his Ziggy Stardust persona, along with his backing band the Spiders from Mars. You can tell that the PR department at the European Space Agency were beside themselves with glee at the opportunity to reference them when their Mars Express spacecraft snapped a picture of some of the planets surface structures which bear a passing resemblance to Earth-bound spiders. We can’t blame them, we’d have done the same.

While these spiders are definitely not arachnid in origin, they are no less interesting. Over the Martian winter there form layers of carbon dioxide ice, which turn to gas under the influence of the Sun. This gas becomes trapped underneath layers of ice, until it forms sufficient pressure to burst through and escape. In doing so it brings up dark dust which settles along fissures in the ice, leading to the spider-like patterns when viewed from orbit.

So no life on Mars then, at least as yet. But it’s an interesting observation, and another little piece in the puzzle of understanding our planetary neighbor, as well as an excuse for a classic rock earworm. Meanwhile, this isn’t the first time we’ve reported on the ESA Mars probes.

How Additional Aerodynamic Drag Helped Make GTA III Work On PS2

The PlayStation 2 was a revelation when it hit the market in 2000, and yet by modern standards, it’s almost hopelessly weak. In fact, it’s so under-powered, Rockstar developers had to pull every trick in the book to make Grand Theft Auto III even work on the platform.

The story comes to us from developer [Obbe Vermeij]. He explains that the PlayStation 2 couldn’t keep the entire open-world game map in its tiny 32 MB of RAM. Instead, models had to be streamed from the DVD drive as the player moved around the world. However, even the DVD drive wasn’t fast enough. If the player moved too quickly, they would outpace the system’s ability to load new assets, and the world would fall apart. Roads would vanish, buildings simply wouldn’t appear before the player passed by them.

According to [Obbe], getting around this challenge was the job of one [Adam Fowler]. He notes that even optimizing the layout of data on the DVD wasn’t enough to help. Nifty hacks had to be employed to slow the player down. Road networks were changed to stop the player speeding towards areas that needed lots of new models. In other areas, vehicles in the game would experience a nearly-imperceptible 5% increase in air drag to dull their speed. This was chosen as a more invisible solution; cutting engine power directly was audible to players as the audio changed.

It shows you just how hard developers had to work back when resources were far more constrained than they are today!

Nearly-Destroyed Commodore Gets New Life

We all have our shiny, modern computers for interacting with the modern world, but at times they can seem a little monochromatic. Even the differences between something like macOS and Windows for the average user often boil down to which operating system loads an Internet browser. There are obviously more differences than that, but back in the 80s it was much more extreme with interoperability a pipe dream in most cases. What keeps drawing people to maintaining and using computers from that chaotic era is more tangible compared to modern machines, and that is meant quite literally; computers from this era can be saved from an extreme amount of degradation like this Commodore that was nearly completely destroyed before it was re-discovered.

The first step was to restore the case of this Commodore PC20-III, but the restoration of the computer’s internals took a bit more time. First, the entire board was de-soldered, with any rare chips being set aside for future use. Unfortunately the board itself was too corroded and otherwise damaged to be used, but since these were just two-layer boards it could be photographed and then re-created in CAD software to make a near-perfect duplicate of the original. The team at [The Cave] took the opportunity to add patch wires which would have been present in the original machine into the PCB, and made some other upgrades as well like adding sockets to various chips that would have been originally soldered to the board.

The passive components, especially capacitors, were brand new as well and some period-correct components such as a monitor and keyboard finish out the build. The computer boots on the first try, and is quickly put through its paces testing the hard disk drive, using the old floppy drive, and even playing a few video games from the era. The fact that retrocomputers like these are easy (by modern standards) to reverse engineer and restore surely leads to their continued popularity, and we’ve seen everything from C64s to this 128DCR get a similar full restoration.

Continue reading “Nearly-Destroyed Commodore Gets New Life”