Home

NASA Curiosity Rover Hit By Software Snafu

Comments | John Foley, InformationWeek | March 19, 2013 01:00 PM


NASA Mars Mission: No Little Green Men -- Yet
NASA Mars Mission: No Little Green Men -- Yet
(click image for larger view and for slideshow)
NASA's Curiosity rover has suffered a second on-board computer problem on Mars, causing the vehicle to go into safe mode for the second time in three weeks.

NASA said Monday that the rover had switched itself into safe mode two days earlier when a command file running on its backup, or "B-side," computer failed a size-check by protective software. The agency determined that a software bug had attached an unrelated file to the one being checked, causing a file size mismatch.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

The SUV-like rover is being operated by its B-side computer because its primary, A-side computer suffered a memory glitch on Feb. 27, causing the Curiosity project team at NASA's Jet Propulsion Laboratory to switch to the backup system and put the vehicle into safe mode for two days.

NASA is still working to determine the cause of the A-side computer problem. "We still don't know exactly what that is yet, whether it's a hardware issue or was a radiation event," said John Grotzinger, Mars Science Lab project scientist, speaking from the Lunar and Planetary Science Conference in The Woodlands, Texas.

[ Rock testing from the Curiosity rover shows elements on Mars consistent with life. Read more at NASA Curiosity Rover Finds Life-Enabling Basics On Mars. ]

For the time being, the A-side computer is operating as a backup to the B-side computer. Grotzinger said the Curiosity project team has uploaded software patches to the B-side computer to protect it from the problems that disabled the A-side computer.

NASA officials downplayed the seriousness of Curiosity's latest software glitch, saying that the rover is stable, healthy and communicating with JPL engineers. "This is a very straightforward matter to deal with," said project manager Richard Cook. "We know how to keep this from occurring in the future."

However, the snafus have put Curiosity's scientific observations on hold for nearly three weeks and counting. Those observations have been suspended since the February 27 shut down, and NASA said it will take a "couple of days" more to bring the rover out of safe mode after the latest setback.

In the near term, NASA researchers have a narrowing window of opportunity for experimentation. From Earth's perspective, Mars is about to pass behind the sun, raising the potential for interference in communications between Curiosity and mission control. As a precaution, NASA won't send commands to the rover for four weeks beginning on April 4.

The technical complications come on the heels of NASA's recent announcement that Curiosity's first rock samples revealed evidence that life-enabling conditions -- including the presence of carbon, hydrogen, nitrogen, oxygen, phosphorus and sulfur -- once existed on the Red Planet.

Attend Interop Las Vegas May 6-10 and learn the emerging trends in information risk management and security. Use Priority Code MPIWK by March 22 to save an additional $200 off the early bird discount on All Access and Conference Passes. Join us in Las Vegas for access to 125+ workshops and conference classes, 300+ exhibiting companies, and the latest technology. Register today!

John Foley is editor of InformationWeek Government.



Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

COMMENTS

Tune In to BYTE
Facebook Twitter LinkedIn Newsletter RSS
Whitepapers
whitepaper
In this paper you will learn the five trends shaping the future of enterprise mobility. Learn how the rise of social media as a business application, the lurring between work and home, the emergence of new mobile devices, the demand for tech savvy employees and changing expectations of corporate IT will fundamentally change the workplace.
whitepaper
In a survey of more than 1,700 information workers (iWorkers) in North America, notebooks, desktops, and smartphones were found to be “must-have” devices, while tablets, slates, and netbooks were relegated to “nice-to-have” status, according to a commissioned study conducted by Forrester Consulting on behalf of Dell and Intel.
Sponsored by: Dell
Upcoming Events