Google NexusOne Can Survive a Hard Vacuum
technologyreview.com
technologyreview.com
I thought that space stuff usually used ancient CPUs because they had to be rad-hard in ways that stuff beneath the ionosphere doesn't need to be, and creating a sufficently rad-hard CPU was difficult and time consuming (thus you end up with what was state of the art when you started working on it, some time ago)
we just finished a radiation susceptibility test for a commercial IC supposed to fly on a satellite in low-earth orbit (which you can find in a lot of consumer electronic products): no serious performance degeneration occured while exposed to a much higher total dose than expected during the lifetime of the satellite.
EDIT: if you're interested in the effects of radiation on electronic devices/components in low-earth orbit, check [0].
[0] http://klabs.org/DEI/References/design_guidelines/design_ser... [pdf]
- capacitors leaking.
- gas bubbles in various parts.
- heat problems due to lack of convective cooling.I can think of one reason - increases weight of the whole package - but perhaps the corresponding cost increase is not so much as buying a radiation hardened 1Ghz processor.
The "age" of rad hardened devices is pretty much limited by the processes used. Only simpler designs work well. The finer the traces, the more charge-related problems occur and the less reliable they will be. Also, there's not much interest in making it better because it works fine as it is.
If you take away the JVM, most of the OS, the graphics stack, comms layer and all the fancy abstractions from the Nexus One and Android OS, a 1MHz RCA 1802 is fine ;-)
Simple is good enough though when you read a bit of telemetry and you use low bandwidth RF comms.
Also the Nexus is a really bad idea as it contains FLASH, which if you fart any radiation near, it flips bits like crazy.
LEO has enough air that satellites experience noticeable drag and friction from it.
I wonder how they get around that.
Receivers capable of operating above 18km and 515 meters/sec are export controlled, but then, so is cryptography software.
The relevant document is available here: http://www.armscontrol.org/documents/mtcr
Note that it refers to export controls, not any blanket ban on functionality.