Space Forum / Shuttle / January 2004

If it is just software, they already have a work-around.  Opportunity could
begin work without using that section of flash ram.

____________________________________________________________________________

One problem seems to have been memory filling up with logs extending
back during the inbound flight. Opportunity has been told to delete
most, if not all of them, to reduce the chance of having the same
trouble that we saw with Spirit.

"Brian Gaff"  does this in fact mean the other Rover will not be allowed to
do what

When the troubleshooters were trying to solve the problem of the frequent
reboots, they found one program that was slowing down the computer, and the
computer in the simulator would reset when the app was run.  So I figure
they are going to do some changes there.

The determination of the nature of a possible hardware fault is in work.
There are one or two main working groups and a couple of sub-teams.  One
sub-team is looking at the question of a cosmic ray strike during a
read/write operation.  The other sub-team is looking at a possible fault in
the transistor amplifier board that sits between the computer and the
electrical devices on the Spirit.

If the fault is determined to be one of the execution of the design, there
may not be a need to change operating procedures.  If the analysis finds a
design fault, then Opportunity may want to avoid using those circuits.  It
is a little early to tell.  One of those cases where you would rather be
lucky than good.

Someone was wondering how much redundancy there is in the hardware.  It just
ocurred to me that in addition to redundancy you would also like to have
data.  Does the Spirit have the ability to report current and voltage levels
going to each of the cameras and motors?