The South American Power Outage That Plunged 48 Million Into Blackout

A massive power outage in South America last month left most of Argentina, Uruguay, and Paraguay in the dark and may also have impacted small portions of Chile and Brazil. It’s estimated that 48 million people were affected and as of this writing there has still been no official explanation of how a blackout of this magnitude occurred.

While blackouts of some form or another are virtually guaranteed on any power grid, whether it’s from weather events, accidental damage to power lines and equipment, lightning, or equipment malfunctioning, every grid will eventually see small outages from time to time. The scope of this one, however, was much larger than it should have been, but isn’t completely out of the realm of possibility for systems that are this complex.

Initial reports on June 17th cite vague, nondescript possible causes but seem to focus on transmission lines connecting population centers with the hydroelectric power plant at Yacyretá Dam on the border of Argentina and Paraguay, as well as some ongoing issues with the power grid itself. Problems with the transmission line system caused this power generation facility to become separated from the rest of the grid, which seems to have cascaded to a massive power failure. One positive note was that the power was restored in less than a day, suggesting at least that the cause of the blackout was not physical damage to the grid. (Presumably major physical damage would take longer to repair.) Officials also downplayed the possibility of cyber attack, which is in line with the short length of time that the blackout lasted as well, although not completely out of the realm of possibility.

This incident is exceptionally interesting from a technical point-of-view as well. Once we rule out physical damage and cyber attack, what remains is a complete failure of the grid’s largely automatic protective system. This automation can be a force for good, where grid outages can be restored quickly in most cases, but it can also be a weakness when the automation is poorly understood, implemented, or maintained. A closer look at some protective devices and strategies is warranted, and will give us greater insight into this problem and grid issues in general. Join me after the break for a look at some of the grid equipment that is involved in this system.

Continue reading “The South American Power Outage That Plunged 48 Million Into Blackout”

New Space Abort Systems Go Back To The Future

Throughout the history of America’s human spaceflight program, there’s been an alternating pattern in regards to abort systems. From Alan Shepard’s first flight in 1961 on, every Mercury capsule was equipped with a Launch Escape System (LES) tower that could pull the spacecraft away from a malfunctioning rocket. But by the first operational flight of the Gemini program in 1965, the LES tower had been deleted in favor of ejection seats. Just three years later, the LES tower returned for the first manned flight of the Apollo program.

Mercury LES Tower

With the Space Shuttle, things got more complicated. There was no safe way to separate the Orbiter from the rest of the stack, so when Columbia made its first test flight in 1981, NASA returned again to ejection seats, this time pulled from an SR-71 Blackbird. But once flight tests were complete, the ejector seats were removed; leaving Columbia and all subsequent Orbiters without any form of LES. At the time, NASA believed the Space Shuttle was so reliable that there was no need for an emergency escape system.

It took the loss of Challenger and her crew in 1986 to prove NASA had made a grave error in judgment, but by then, it was too late. Changes were made to the Shuttle in the wake of the accident investigation, but escape during powered flight was still impossible. While a LES would not have saved the crew of Columbia in 2003, another seven lives lost aboard the fundamentally flawed Orbiter played a large part in President George W. Bush’s decision to begin winding down the Shuttle program.

In the post-Shuttle era, NASA has made it clear that maintaining abort capability from liftoff to orbital insertion is a critical requirement. Their own Orion spacecraft has this ability, and they demand the same from commercial partners such as SpaceX and Boeing. But while all three vehicles are absolutely bristling with high-tech wizardry, their abort systems are not far removed from what we were using in the 1960’s.

Let’s take a look at the Launch Escape Systems for America’s next three capsules, and see where historical experience helped guide the design of these state-of-the-art spacecraft.

Continue reading “New Space Abort Systems Go Back To The Future”

Robotic Dishwashers And Dishwashing As A Service

There’s a story that goes back to the 1980s or so about an engineering professor who laid down a challenge to the students of his automation class: design a robot to perform the most mundane of household tasks — washing the dishes. The students divided up into groups, batted ideas around, and presented their designs. Every group came up with something impressive, all variations on a theme with cameras and sensors and articulated arms to move the plates around. The professor watched the presentations respectfully, and when they were done he got up and said, “Nice work. But didn’t any of you idiots realize you can buy a robot that does dishes for $300 from any Sears in the country?”

The story may be apocryphal, but it’s certainly plausible, and it’s definitely instructive. The cultural impression of robotics as a field has a lot of ballast on it, thanks to decades of training that leads us to believe that robots will always be at least partially anthropomorphic. At first it was science fiction giving us Robbie the Robot and C3PO; now that we’re living in the future, Boston Dynamics and the like are doing their best to give us an updated view of what robots must be.

But all this training to expect bots built in the image of humans or animals only covers a narrow range of use cases, and leaves behind the hundreds or thousands of other applications that could prove just as interesting. One use case that appears to be coming to market hearkens back to that professor’s dishwashing throwdown, and if manufacturers have their way, robotic dishwashers might well be a thing in the near future.

Continue reading “Robotic Dishwashers And Dishwashing As A Service”

Ask Hackaday: What Are Your Apollo Memories?

This month will mark the 50th anniversary of the Apollo 11 mission that brought to a successful conclusion the challenge laid down by President Kennedy only eight years earlier. Three men went to the Moon, two walked on it, and they all came back safely, in a dramatic eight-day display of engineering and scientific prowess that was televised live to the world.

If you’ve made more than 50 trips around the sun, chances are good that you have some kind of memories of the first Moon landing. An anniversary like this is a good time to take stock of those memories, especially for something like Apollo, which very likely struck a chord in many of those that witnessed it and launched them on careers in science and engineering. We suspect that a fair number of Hackaday readers are in that group, and so we want to ask you: What are your memories of Apollo?

A Real American Hero

My memory of the Moon landing is admittedly vague. I had just turned five the month before, hadn’t even started kindergarten yet, but I had already caught the space bug in a big way. I lived and breathed the space program, and I knew everything about the Mercury missions that were over by the time I was born, and the Gemini missions that had just wrapped up. Apollo was incredibly exciting to me, and I was pumped to witness the landing in the way that only a five-year-old can be.
Continue reading “Ask Hackaday: What Are Your Apollo Memories?”

The Saga Of 32-Bit Linux: Why Going 64-Bit Raises Concerns Over Multilib

The story of Linux so far, as short as it may be in the grand scheme of things, is one of constant forward momentum. There’s always another feature to implement, an optimization to make, and of course, another device to support. With developer’s eyes always on the horizon ahead of them, it should come as no surprise to find that support for older hardware or protocols occasionally falls to the wayside. When maintaining antiquated code monopolizes developer time, or even directly conflicts with new code, a difficult decision needs to be made.

Of course, some decisions are easier to make than others. Back in 2012 when Linus Torvalds officially ended kernel support for legacy 386 processors, he famously closed the commit message with “Good riddance.” Maintaining support for such old hardware had been complicating things behind the scenes for years while offering very little practical benefit, so removing all that legacy code was like taking a weight off the developer’s shoulders.

The rationale was the same a few years ago when distributions like Arch Linux decided to drop support for 32-bit hardware entirely. Maintainers had noticed the drop-off in downloads for the 32-bit versions of their distributions and decided it didn’t make sense to keep producing them. In an era where even budget smartphones are shipping with 64-bit processors, many Linux distributions have at this point decided 32-bit CPUs weren’t worth their time.

Given this trend, you’d think Ubuntu announcing last month that they’d no longer be providing 32-bit versions of packages in their repository would hardly be newsworthy. But as it turns out, the threat of ending 32-bit packages caused the sort of uproar that we don’t traditionally see in the Linux community. But why?

Continue reading “The Saga Of 32-Bit Linux: Why Going 64-Bit Raises Concerns Over Multilib”

Ask Hackaday: How Can You Build For A Ten Millennia Lifespan?

There’s been a lot of news lately about the Long Now Foundation and Jeff Bezos spending $42 million or so on a giant mechanical clock that is supposed to run for 10,000 years. We aren’t sure we really agree that it is truly a 10,000 year clock because it draws energy — in part — from people visiting it. As far as we can tell, inventor Danny Hills has made the clock to hoard energy from several sources and occasionally chime when it has enough energy, so we aren’t sure how it truly sustains itself. However, it did lead us to an interesting question: how could you design something that really worked for 10,000 years?

Continue reading “Ask Hackaday: How Can You Build For A Ten Millennia Lifespan?”

Reverse Engineering Cyclic Redundancy Codes

Cyclic redundancy codes (CRC) are a type of checksum commonly used to detect errors in data transmission. For instance, every Ethernet packet that brought you the web page you’re reading now carried with it a frame check sequence that was calculated using a CRC algorithm. Any corrupted packets that failed the check were discarded, and the missing data was detected and re-sent by higher-level protocols. While Ethernet uses a particularly common CRC, there are many, many different possibilities. When you’re reverse-engineering a protocol that contains a CRC, although it’s not intended as a security mechanism, it can throw a wrench in your plans. Luckily, if you know the right tool, you can figure it out from just a few sample messages.

A case in point was discussed recently on the hackaday.io Hack Chat, where [Thomas Flayols] came for help reverse engineering the protocol for some RFID tags used for race timing. Let’s have a look at the CRC, how it is commonly used, and how you can reverse-engineer a protocol that includes one, using [Thomas’] application as an example.

Continue reading “Reverse Engineering Cyclic Redundancy Codes”