'Curiosity' - NASA Mars Rover - Due to land 5th Aug 2012
Discussion
Bedazzled said:
Curiosity computer glitch puts it in safe mode here. They think files in the computer flash memory may have been corrupted by cosmic rays!
Interesting update. I hope it can all be fixed and they can carry on. From what I remember reading about the computer on board it's very customisable - so they can make 'workarounds' for a great number of unforeseen problems.Here's The Register's article on it. (Usually it's more techy that the BBC, but also a bit more flippant in headlines!)
http://www.theregister.co.uk/2013/03/03/curiosity_...
ElReg said:
Nuclear-powered, laser-armed space tank Curiosity is currently working in safe mode, after one of the craft's onboard computers developed a memory glitch.
NASA has switched the craft to its “B” computer, a device identical to the problematic “A” unit, and says “a glitch in flash memory” is the source of the problem.
Curiosity carries two computers, Rover Compute Element-A and the spare Rover Compute Element-B. As we've reported previously, both are powered by a hardened 200MHz PowerPC 750 CPU. Each is equipped with 256MB of RAM, 250KB of read-only memory (in an EEPROM that can be wiped if required) and 2GB of flash storage.
While NASA has not revealed the exact nature of RCE-A's problems but says before it was shut down it “did not send recorded data”. As our previous report states the 2GB of Flash memory is where the rover stores data before beaming it home, it seems highly likely, based on NASA's statement, that it is that 2GB of flash and not the EEPROM that is the source of the problem.
Other reports suggest the rover continuously rebooted due to the flash glitch.
Whatever the source of the problem, Curiosity is now running on RCE-B, which is behaving as its makers intended, but NASA is keeping things simple by doing no science until it can figure out what's wrong.
Magdy Bareh, leader of the mission's anomaly resolution team has said, in a canned statement, that “While we are resuming operations on the B-side, we are also working to determine the best way to restore the A-side as a viable backup.
NASA has switched the craft to its “B” computer, a device identical to the problematic “A” unit, and says “a glitch in flash memory” is the source of the problem.
Curiosity carries two computers, Rover Compute Element-A and the spare Rover Compute Element-B. As we've reported previously, both are powered by a hardened 200MHz PowerPC 750 CPU. Each is equipped with 256MB of RAM, 250KB of read-only memory (in an EEPROM that can be wiped if required) and 2GB of flash storage.
While NASA has not revealed the exact nature of RCE-A's problems but says before it was shut down it “did not send recorded data”. As our previous report states the 2GB of Flash memory is where the rover stores data before beaming it home, it seems highly likely, based on NASA's statement, that it is that 2GB of flash and not the EEPROM that is the source of the problem.
Other reports suggest the rover continuously rebooted due to the flash glitch.
Whatever the source of the problem, Curiosity is now running on RCE-B, which is behaving as its makers intended, but NASA is keeping things simple by doing no science until it can figure out what's wrong.
Magdy Bareh, leader of the mission's anomaly resolution team has said, in a canned statement, that “While we are resuming operations on the B-side, we are also working to determine the best way to restore the A-side as a viable backup.
Curiosity's been busy in the 9mth's it's been up there. Here's a timelapse video to show you what it's been doing. Lots of science!!
https://www.youtube.com/watch?v=wkmDM376-nE
https://www.youtube.com/watch?v=wkmDM376-nE
Latest Rover Report. Includes a good summary of where they've been so far. Apparently, they're done with Gleneg now and are now on their way to Mt Sharp!
https://www.youtube.com/watch?v=GH56wMh3FZg
https://www.youtube.com/watch?v=GH56wMh3FZg
Gassing Station | Science! | Top of Page | What's New | My Stuff