New 'Safe Mode' Status of Curiosity Expected to be Brief
Mission Status Report
NASA's Mars rover Curiosity is expected to resume science investigations in a few days, as engineers quickly diagnosed a software issue that prompted the rover to put itself into a precautionary standby status over the weekend.
Commercial Satellite Imaging Market - Global Industry Analysis, Size, Share, Growth, Trends, and For...
Curiosity initiated this automated fault-protection action, entering "safe mode" at about 8 p.m. PDT (11 p.m. EDT) on March 16, while operating on the B-side computer, one of its two main computers that are redundant to each other. It did not switch to the A-side computer, which was restored last week and is available as a back-up if needed. The rover is stable, healthy and in communication with engineers.
The safe-mode entry was triggered when a command file failed a size-check by the rover's protective software. Engineers diagnosed a software bug that appended an unrelated file to the file being checked, causing the size mismatch.
"This is a very straightforward matter to deal with," said the project manager for Curiosity, Richard Cook of NASA's Jet Propulsion Laboratory, Pasadena, Calif. "We can just delete that file, which we don't need any more, and we know how to keep this from occurring in the future."
The mission's science observations have been on hold since a memory glitch on the A-side computer on Feb. 27, which prompted controllers to command a swap from the A-side computer to the B-side computer. That operator-commanded swap put Curiosity into safe mode for two days. The rover team restored the availability of the A-side as a backup and prepared the B-side to resume full operations.
Cautiously bringing Curiosity out of safe mode status on the B-side is expected to take a couple of days. A four-week moratorium on sending commands to the rover will begin April 4 due to solar system geometry of Mars passing nearly directly behind the sun from Earth's perspective. The moratorium is a precaution against interference by the sun corrupting a command sent to the rover.
Source : NASA