Mars Express observations temporarily suspended

Nov 02, 2011
Mars Express lifted off from Baikonur Cosmodrome aboard a Soyuz/Fregat launcher on 2 June 2003. It entered orbit around Mars on 25 December that year and reached its operational orbit in January 2004. The nominal mission duration was one Martian year (687 Earth days) and was completed in September 2005. The mission has since been extended five times; the current extension is until 31 December 2014, subject to a mid-term review in 2012. Credit: ESA / Alex Lutkus

( -- Anomalies in the operation of the solid-state mass memory system on board Mars Express have caused science observations to be temporarily halted. A technical work-around is being investigated that will enable the resumption of a number of observations and should evolve into a long-term solution.

In mid-August, autonomously entered safe mode, an operational mode designed to safeguard both the spacecraft itself and its in the event of faults or errors.

The cause of entering the safe mode was a complex combination of events relating to reading from and writing to in the Solid-State Mass Memory (SSMM) system. This is used to store data acquired by the instruments and housekeeping data from the spacecraft's subsystems, prior to its transmission to Earth, and is also used to store commands for the spacecraft that have been received from the ground stations, while awaiting execution.

Switch to spare memory controller

As the previous safe mode was three years ago and the current event looked like a 'normal' transition to safe mode, the flight control team executed the standard recovery procedure and restarted observations. A few days later, another fairly similar set of SSMM problems occurred. The decision was then taken to switch over to the cold-redundant spare, or 'B-side', SSMM controller, as this was virtually the only subsystem common to the two events. The decision to act was triggered by both the need to achieve stable science performance and the need to reduce the consumption of fuel caused by transitions to safe mode.

An important element in trying to reduce the number of safe mode transitions, besides the science observing time being lost, is the amount of fuel used when entering safe mode, which is approximately equal to the amount of fuel required for six months of nominal operations. The reason for this fuel consumption when entering safe mode is the 'Sun acquisition' process, which requires a significant amount of spacecraft manoeuvring.

Full were resumed on 15 September, using the B-side SSMM controller. Eight days later, the spacecraft again entered safe mode. The cause was a checksum error during communication between two subsystems within the SSMM. As this event exhibited no similarities with the two events in August, it was decided to treat this as an isolated incident and return to nominal operations; this took place on 29 September.

On 11 October, a similar problem occurred, but no safe mode transition was triggered. As all operations continued normally, it was decided to take no action, but to find a slot to execute a warm reset of the SSMM at the earliest opportunity.

Mars Express mass memory anomaly – event timeline
13 August 2011 Safe mode transition following SSMM read/write error
18 August 2011Observations restarted
23 August 2011 Re-occurrence of SSMM read/write error – without safe mode transition
24 August 2011Decision to switch to B-side SSMM controller
15 September 2011Observations restarted using B-side SSMM controller
23 September 2011Safe mode transition following SSMM internal communications error
29 September 2011 Return to nominal operations
11 October 2011SSMM internal communications error – without safe mode transition
16 October 2011 Safe mode transition following SSMM internal communications error
Observations temporarily suspended

Observations halted

On Sunday, 16 October, Mars Express again entered safe mode. The cause was a sequence of events very similar to the one that triggered the safe mode transition on 23 September, following an internal communication error.

Resuming use of the A-side SSMM controller is not considered a viable option; it would most probably lead to further transitions caused by memory module read/write errors and the additional caused by these events cannot be sustained. Faced with these circumstances, the Mission Manager decided to halt science observations.

Possible work-around

The SSMM is a critical subsystem on board Mars Express, central to all platform and instrument operations. The ESOC flight control team is preparing a work-around to address the current problems and allow at least partial resumption of science observations.

During normal operations, telecommands for the platform and instrument payload that have been received from the ground stations are stored in the Long Mission TimeLine (L-MTL), a special file in the SSMM that is used to fill the platform's command cache. In order to cope with anomalous operation scenarios, a hardware-based timeline store – the Short Mission TimeLine (S-MTL) – is available outside the SSMM subsystem.

The work-around now being investigated uses the S-MTL to store telecommands before they are executed.

Good progress is being made with the implementation of this alternative approach to commanding the Mars Express platform and its payload. A full test on the spacecraft will be executed in the near future.

ESA's mission control team and other experts are working closely with the designers and manufacturers of the SSMM subsystem to investigate the cause of the read/write anomalies and to attempt to find a solution that will enable a return to normal operations.

Explore further: NOAA's DSCOVR going to a 'far out' orbit

add to favorites email to friend print save as pdf

Related Stories

Kepler returns after safe mode event

Mar 23, 2011

After a safe mode event that lasted 144 hours, NASA’s Kepler spacecraft returned to science data collection at 2:45 p.m. EDT Sunday, March 20.

Team restoring Mars orbiter after reboot

Sep 20, 2010

( -- NASA's Mars Reconnaissance Orbiter put itself into a precautionary standby mode after experiencing a spontaneous computer reboot on Sept. 15. The mission's ground team has begun restoring ...

Kepler experienced 'safe mode' event

Dec 23, 2010

On Dec. 22, 2010, Kepler experienced a safe mode event. A safe mode is a self-protective measure that the spacecraft takes when something unexpected occurs. During safe mode, the spacecraft points the solar ...

Recommended for you

Dawn spacecraft captures best-ever view of dwarf planet

3 hours ago

NASA's Dawn spacecraft has returned the sharpest images ever seen of the dwarf planet Ceres. The images were taken 147,000 miles (237,000 kilometers) from Ceres on Jan. 25, and represent a new milestone for ...

Image: Striking lightning from space

7 hours ago

Lightning illuminates the area it strikes on Earth but the flash can be seen from space, too. This image was taken from 400 km above Earth in 2012 by an astronaut on the International Space Station travelling ...

Are asteroids the future of planetary science?

7 hours ago

I don't think I ever learned one of those little rhymes – My Very Educated Mother Just Served Us Nine Pizzas – to memorize the order of the planets, but if I had, it would've painted for me a minimalist ...

Earth's moon may not be critical to life

9 hours ago

The Moon has long been viewed as a crucial component in creating an environment suitable for the evolution of complex life on Earth, but a number of scientific results in recent years have shown that perhaps our ...

User comments : 1

Adjust slider to filter visible comments by rank

Display comments: newest first

not rated yet Nov 02, 2011
The events seem to take place on five day intervals or multiples of 5 days. A clue here for what is causing the problems??
Art L

Please sign in to add a comment. Registration is free, and takes less than a minute. Read more

Click here to reset your password.
Sign in to get notified via email when new comments are made.