The NASA workmanship standards are absolutely beautiful. I mean that in the fullest extent of the word. If I had any say in the art that goes up in the Louvre, I’d put them up right beside Mona. They’re a model of what a standard should be. A clear instruction for construction, design, and inspection all at once. They’re written in clear language and contain all the vernacular one needs to interpret them. They’re unassuming. The illustrations are perfectly communicative. It’s a monument to the engineer’s art.
Around five years ago I had a problem to solve. Every time a device went into the field happily transmitting magic through its myriad connectors, it would inevitably come back red tagged, dusty, and sad. It needed to stop. I dutifully traced the problem to a connector, and I found the problem. A previous engineer had informed everyone that it was perfectly okay to solder a connector after crimping. This instruction was added because, previously, the crimps were performed with a regular pair of needle nose pliers and they came undone… a lot. Needless to say, the solder also interfered with their reliable operation, though less obviously. Stress failures and intermittent contact was common.
We were initially skeptical of this article by [Aleksey Statsenko] as it read a bit conspiratorially. However, he proved the rule by citing his sources and we could easily check for ourselves and reach our own conclusions. There were fatal crashes in Toyota cars due to a sudden unexpected acceleration. The court thought that the code might be to blame, two engineers spent a long time looking at the code, and it did not meet common industry standards. Past that there’s not a definite public conclusion.
[Aleksey] has a tendency to imply that normal legal proceedings and recalls for design defects are a sign of a sinister and collaborative darker undercurrent in the world. However, this article does shine a light on an actual dark undercurrent. More and more things rely on software than ever before. Now, especially for safety critical code, there are some standards. NASA has one and in the pertinent case of cars, there is the Motor Industry Software Reliability Association C Standard (MISRA C). Are these standards any good? Are they realistic? If they are, can they even be met?
When two engineers sat down, rather dramatically in a secret hotel room, they looked through Toyota’s code and found that it didn’t even come close to meeting these standards. Toyota insisted that it met their internal standards, and further that the incidents were to be blamed on user error, not the car.
So the questions remain. If they didn’t meet the standard why didn’t Toyota get VW’d out of the market? Adherence to the MIRSA C standard entirely voluntary, but should common rules to ensure code quality be made mandatory? Is it a sign that people still don’t take software seriously? What does the future look like? Either way, browsing through [Aleksey]’s article and sources puts a fresh and very real perspective on the problem. When it’s NASA’s bajillion dollar firework exploding a satellite it’s one thing, when it’s a car any of us can own it becomes very real.
NASA has been tracking bright meteoroids (“fireballs”) using a distributed network of video cameras pointed upwards. And while we usually think of NASA in the context of multi-bazillion dollar rocket ships, but this operation is clearly shoe-string. This is a hack worthy of Hackaday.
The basic idea is that with many wide-angle video cameras capturing the night sky, and a little bit of image processing, identifying meteoroids in the night sky should be fairly easy. When enough cameras capture the same meteoroid, one can use triangulation to back out the path of the meteoroid in 3D, estimate its mass, and more. It’s surprising how many there are to see on any given night.
You can watch the videos of a meteoroid event from any camera, watch the cameras live, and even download the meteoroid’s orbital parameters. We’re bookmarking this website for the next big meteor shower.
The work is apparently based on [Rob Weryk]’s ASGARD system, for which the code is unfortunately unavailable. But it shouldn’t be all that hard to hack something together with a single-board computer, camera, and OpenCV. NASA’s project is limited to the US so far, but we wonder how much more data could be collected with a network of cameras all over the globe. So which ones of you are going to take up our challenge? Build your own version and let us know about it!
Between this project and the Radio Meteor Zoo, we’re surprised at how much public information there is out there about the rocky balls of fire that rain down on us every night, and will eventually be responsible for our extinction. At least we can be sure we’ll get it on film.
[Tony Stark Elon Musk] envisions us sending one million people to Mars in your lifetime. Put aside the huge number or challenges in that goal — we’re going to need a lot of places to live. That’s a much harder problem than colonization where mature trees were already standing, begging to become planks in your one-room hut. Nope, we need to build with what’s already up there, and preferably in a way that prepares structures before their inhabitants arrive. NASA is on it, and by on it, we mean they need you to figure it out as part of their 3D Printed Hab Challenge.
The challenge started with a concept phase last year, awarding $25k to the winning team for a plan to use Martian ice as a building material for igloo-like habs that also filter out radiation. The top 30 entries were pretty interesting so check them out. But now we’re getting down to the nitty-gritty. How would any of these ideas actually be implemented? If you can figure that out, you can score $2M.
Official rules won’t be out until Friday, but we’d love to hear some outrageous theories on how to do this in the comments below. The whole thing reminds us of one of the [Brian Herbert]/[Kevin J. Anderson] Dune prequels where swarms of robot colonists crash-land on planets throughout the universe and immediately start pooping out building materials. Is a robot vanguard the true key to planet colonization, and how soon do you think we can make that happen? We’re still waiting for robot swarms to clean up our oceans. But hey, surely we can do both concurrently.
If any of you have ever made a piece of clothing, you’ll know some of the challenges involved. Ensuring a decent and comfortable fit for the wearer, because few real people conform exactly to commercial sizes. It’s as much a matter of style as it is of practicality, because while ill-fitting clothing might be a sartorial fail, it’s hardly serious.
When the piece of clothing is a space suit though, it is a different matter. You are not so much making a piece of clothing as a habitat, and one that will operate in an environment in which a quick change to slip into something more comfortable is not possible. If you get it wrong at best your astronaut will be uncomfortable and at worst their life could be threatened.
This week, Popular Mechanics published cutaway diagrams of ships that will be seen in Star Trek: Beyond, released later this month. This is your cue for spoilers for the remainder of this paragraph. The USS Franklin looks suspiciously like – and was likely built after – the NX-01, the titular ship of Star Trek: Enterprise. The Abrams-verse Franklin was the first Warp 4 ship, yet the prime universe NX-01 was the first Warp 5 ship, with previous ships having trouble reaching Warp 2. We must now consider the Abrams-verse Trek is not a parallel universe to prime-universe Trek and should therefore be considered a completely separate canon (yes, even the destruction of Vulcan. If you see the new Star Trek movie, the NX-01 launched in 2151, and your suggested viewing beforehand is ST:ENT, S02E24, First Flight.
Walk into a dollar store, and you’ll find stupid solar powered electronic flower pots. They’re bits of plastic that shake a plastic flower back and forth when placed in the sun. They’re selling millions, and I have no idea why. [Scott] put a jolly wrencher on one of these flower pots. Really, this is just an exercise in 3D printing, but [Scott] printed the jolly wrencher. We don’t see a lot of that, due to how difficult it is to render the wrencher in OpenSCAD.
In just a few hours, Juno will perform an insertion burn around Jupiter. Does this mean pretty pictures? Not quite yet. This is the closest a spacecraft has ever gotten to Jupiter, and over thirty or forty orbits, Juno will fly between Jupiter’s massive radiation belts. Here’s the NASA trailer.
This video recently caught the Internet’s attention. It’s squares and circles that when put next to a mirror look like circles and squares. Yes, it’s weird. People have 3D printers, so of course these ambiguous objects were quickly reverse engineered and printed. Here’s how they work
The US Space Shuttle program is dead and buried. The orbiters can now be found in their permanent homes in the Air and Space Museum, Kennedy Space Center, and the California Science Center. The launch pads used by the shuttles over a career of 135 launches are being repurposed for vehicles from SpaceX and the Space Launch System. Yes, some of the hardware and technology will be reused for NASA’s next generation of heavy launch vehicles, but the orbiter – a beautiful brick of a space plane – is forever grounded.
The Space Shuttle was a product of the cold war, and although the orbiters themselves were never purely military craft, the choices made during the design of the Space Shuttle were heavily influenced by the US Air Force. The Soviet Union was keenly aware the United States was building a ‘space bomber’ and quickly began development of their own manned spaceplane.
While this Soviet Shuttle would not be as successful as its American counterpart — the single completed craft would only fly once, unmanned — the story of this spaceplane is one of the greatest tales of espionage ever told. And it ends with a spaceship that was arguably even more capable than its American twin.