A Space & astronomy forum. SpaceBanter.com

Go Back   Home » SpaceBanter.com forum » Space Science » Policy
Site Map Home Authors List Search Today's Posts Mark Forums Read Web Partners

Details on Spirit Breakdown



 
 
Thread Tools Display Modes
  #1  
Old February 8th 04, 06:47 PM
John Schutkeker
external usenet poster
 
Posts: n/a
Default Details on Spirit Breakdown


The following message was sent to me by a buddy who works closely with
VXWorks, a commercial RTOS that's used on Spirit. Unfortunately he
couldn't identify the original poster, but it has loads of good technical
details regarding why Spirit broke down. Unfortunately, the OP's English
needs a little work, but the details are decipherable.

Incidentally, the message also says something about opportunity having a
"stuck heater" on its instrumentation arm. I hadn't heard about that.
Does anybody have any more details about it or a link describing the
situation? Is it fixed, or are they still working on it?


--------------------------------------------------------------------------

The long and short of the Spirit debacle: Test what you intend to
do, and Do what you tested for. In the lab, they tested for 9 days
at a time, then cleaned things up, and ran again.

On Mars, they ran for over 18 days without doing any housecleaning.
You can get away with that on earth, you just have to vacuum twice...

As has been noted, Spirit has relatively little RAM for applications
and the OS - very little margin of error. The FLASH directory structure
and file structure required enough RAM for the dosFs cache that one last
malloc() was all it took to go over the top (malloc() puts the fat in the
FAT file system). The last malloc() failed, the task is suspended, the
dosvd semaphore never released, a high-prio task waiting on an "open"
causes a prio-inversion, another high priority task needs to write to a
heath monitor board (the RTI clock) but is block from running in time.

The RTI clock resets the system.

The system then re-initializes, rebuilds the dosFs cache... and the whole
thing happens all over again.

Current status:

They've sent commands to removed a coupld of directories of files from
the system and rebooted. They'll bring back files we're interested in,
then send another script command to reformat TFFS, and reboot. In other
words... we're back in business, Spirit is up and running, and we're
ready to finish cleaning house and start doing science again.

The heater on Opportunity that is stuck on is in the arm that holds the
RAT and two of the spectrometers. It's a very minor concern at this point,
and should not cause any operational constraints.

Opportunity had sent status early-on that the Mossbauer spectrometer had
been damaged on launch. After landing the spectrometer was checked again,
and it is working fine. It won't be long untill all 12 wheels are rolling
towards objectives!
  #2  
Old February 8th 04, 10:14 PM
Bruce Palmer
external usenet poster
 
Posts: n/a
Default Details on Spirit Breakdown

John Schutkeker wrote:
... Incidentally, the message also says something about opportunity having a
"stuck heater" on its instrumentation arm. I hadn't heard about that.
Does anybody have any more details about it or a link describing the
situation? Is it fixed, or are they still working on it?


Check the status page at http://www.spaceflightnow.com/mars/mera/status.html

Search the page for "heater" and you will find the section. It's near
the bottom of the page.

--
bp
Proud Member of the Human O-Ring Society Since 2003

  #3  
Old February 8th 04, 10:29 PM
John Schutkeker
external usenet poster
 
Posts: n/a
Default Details on Spirit Breakdown

Bruce Palmer wrote in
. net:

Check the status page at
http://www.spaceflightnow.com/mars/mera/status.html
Search the page for "heater" and you will find the section. It's near
the bottom of the page.


Thanks. These problems always make me very nervous, because my initial
feeling is that they sound like hardware problems. In this case, it sounds
like a short circuit that bypasses the switch (or just a broken switch)
upstream of the heater load. Of course, that's just my gut feeling, and
I've never seen the schematics. But if the only repair option we have is
to remotely reprogram the rovers, the only thing you can do is to stop
using the parts that had the hardware failures.

Yes, I know I'm just being paranoid, and the Spirit team really did a bang
up job getting that breakdown fixed. I hope that they can do as well with
this one. Three cheers for the software guys! Hip, hip...
  #4  
Old February 9th 04, 10:17 AM
Kaido Kert
external usenet poster
 
Posts: n/a
Default Details on Spirit Breakdown

John Schutkeker wrote in message . 93...
The following message was sent to me by a buddy who works closely with
VXWorks, a commercial RTOS that's used on Spirit. Unfortunately he

.....
As has been noted, Spirit has relatively little RAM for applications
and the OS - very little margin of error. The FLASH directory structure
and file structure required enough RAM for the dosFs cache that one last
malloc() was all it took to go over the top (malloc() puts the fat in the
FAT file system).


Quota management, anyone ? So it actually ran out of RAM, not flash
space, due to large fat ?
In any case, i woulda thought that it would have given a low memory or
low disk warning beforehand ...

-kert
  #7  
Old February 12th 04, 08:54 PM
Eric Chomko
external usenet poster
 
Posts: n/a
Default Details on Spirit Breakdown

Kaido Kert ) wrote:
: John Schutkeker wrote in message . 93...
: The following message was sent to me by a buddy who works closely with
: VXWorks, a commercial RTOS that's used on Spirit. Unfortunately he
: ....
: As has been noted, Spirit has relatively little RAM for applications
: and the OS - very little margin of error. The FLASH directory structure
: and file structure required enough RAM for the dosFs cache that one last
: malloc() was all it took to go over the top (malloc() puts the fat in the
: FAT file system).

: Quota management, anyone ? So it actually ran out of RAM, not flash
: space, due to large fat ?
: In any case, i woulda thought that it would have given a low memory or
: low disk warning beforehand ...

My immediate thought was a memory leak problem (too many mallocs as
compared to the number of free statements). Disk? I would have thought the
computer system to be radiation shielded CMOS (or modern variant)
throughout. Cripes, I get disk problems first and foremost on the systems
I use.

Eric

: -kert
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Hematite Caused Spirit Breakdown? John Schutkeker Policy 4 January 29th 04 08:17 AM
Spirit has a mind of its own? Jon Berndt Space Shuttle 33 January 28th 04 05:48 AM
Schematics +Architectural details harshit Technology 0 January 24th 04 11:17 AM
"Spirit" and "Opportunity" Brian Thorn Policy 1 July 8th 03 01:36 AM


All times are GMT +1. The time now is 03:20 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 SpaceBanter.com.
The comments are property of their posters.