The Ancient Computers Powering the Space Race

An anonymous reader writes "Think that the exploration of space is a high tech business? Technology dating back to the Apollo moon landings is still used by Nasa mission control for comms and the 1980s 386 processors that keep the International Space Station aloft."

Comments

This is news?

[Anonymous Coward]

I thought everyone was aware of this by now. :-/

Re:This is news?

[TheRaven64]

It's slightly different in space, because radiation hardening is also an important factor. ESA uses a lot of SPARC32 chips, in the form of the (GPL'd) LEON, which was designed to be able to be created in rad-hardened versions by anyone, cheaply. Intel periodically produces rad-hardened versions of their chips, but they certainly don't do it for the latest versions (the transistor density for the hardened process isn't has high as for the consumer-grade process), so you have longer upgrade cycles, and you also need rad-hardened versions of all of the support chips, so it's worth skipping a few generations if something works.

And, really, there's nothing wrong with using a 386, if it's fast enough. Upgrading from a chip that is twice as fast as you need to one that is a hundred times as fast as you need is not an easy decision to make.

The military was still buying Z80s until a few years ago for a lot of things. They had Z80 code that worked, and had been very well tested. Hopefully everyone involved in space learned from Arianne that upgrading something requires (expensive) revalidation and testing of everything that interfaces with it.

Makes sense

[Pojut]

Given how wonky IT and communication upgrades can be, it makes sense to keep these systems the same for as long as possible. I imagine that after the Shuttle is fully and completely retired, NASA will begin to take a serious look at their aging hardware.

Part of the Problem

[Sonny Yatsen]

It's not that simple to just update NASA's technology. Yes, a lot of NASA's computer systems are antiquated, but they've also been vetted and engineered so that all the bugs and kinks have been worked out. They can update the technology, but they'll have to go through the whole process of figuring out where all the bugs are all over again. Unlike buying a buggy desktop application, though, when NASA has a bug, lives and millions of dollars are at stake.

If it's not broke...

[g0bshiTe]

Don't fuck with it.

Re:B-2 Stealth

[OzPeter]

What is the point of this article?

I think the point of this article is to show the disconnect between the "oh-look-new-shiny-shiny" crowd who have to download and install their latest favorite application from nightly builds vs the "if-it-fucks-up-someone-gets-hurt" crowd who actually have a clue about reliability.

Not surprised

[JLangbridge]

I'm not surprised, not at all. The A320 ELAC uses 3 68k chips, and the A320 SEC uses an 80186 and even an 8086 chip. Why? For lots of reasons. Basically, it doesn't require billions of instructions per second, it doesn't need to access gigabytes of memory, and most importantly, they are proven chips that have gone through years of testing, and they are relatively simple. At the time they were complicated, granted, but they were still within reach of severe quality control. Remember the problems Intel had with the Pentium and floating point calculations? Nothing serious, but still... The chip was so complex that problems crept into the design phase, and at 38000 feet, you do not want problems. To cite a fellow Slashdotter above, (thanks tekrat), Critical systems require reliable, proven, hardened hardware, not flakey netbooks. Enough design faults have crept into aeronautical design, so I can only imagine the space sector. NASA used to program everything in 68k because they were reliable, simple, fast enough, and because they had lots of really, really good engineers that knew every single aspect of the chips. Don't get me wrong, I love todays chips, and i7s look sexy, but with a TDP of 130W for the Extreme Edition chips, they just add problems. Running at 3.2GHz, with over a billion transistors, you are just asking for trouble. At those speeds and heat, problems do happen, the system will crash. Ok, not often, but with mission critical systems, just once is enough. Did anyone seriously expect the shuttle to run quad-cores with terabytes of RAM?

Re:286's

[ThatOtherGuy435]

I'm not sure if it is still the case but for a LONG time 286 processors were the only ones available that had been hardened against cosmic radiation and were rated for space. When you're lobbing people into space, it matters most what works and is proven, not what is fastest or the newest technology.

Yes but the other priority concern for space travel is size. Every square inch of space is critical. Space agencies must balance old-but-proven technology with newer but way smaller technology. My cell phone contains more processing power, memory, and data storage space than the entirety of 1960's era Mission Control.

Don't forget about heat, either. Heat dissipation in space is a pain in the ass, and throwing a few hundred extra watts of heat at every data problem is a lot less viable than it is under your desk.

Re:Virii

[gblackwo]

If we had as many dedicated virus writers coding viruses specifically for NASA, as we do coding viruses for windows, this would not likely hold true. Viruses affect only systems they were DESIGNED for. On the other hand, the BSG fan in me wants to wholeheartedly agree.