PDS_VERSION_ID       = PDS3
RECORD_TYPE          = STREAM
OBJECT               = TEXT
PUBLICATION_DATE     = 2006-11-20
NOTE                 = "MGS RST Instrument Health Report HEAG324A.TXT"
END_OBJECT           = TEXT
END


Miscellaneous
=============

     Due to the weekend, this is the first health report since HEAG321A.TXT.

     Kyle Martin of LMA provided the following (slightly edited) summary of
MGS status:

  No signal was seen from MGS over the weekend.  Commands were sent last
  Thursday to swap to BUS-B.  Hardware and software commands to perform
  this task were sent on 2 consecutive orbits - with no observed results.
  Two groups of Telecom commands were then radiated over the weekend per
  Telecom's direction of alternating between the two groups for 5 orbits.
  The Telecom commanding basically consisted of first connecting the LGA
  to TWTA1 in command group 1 and then next connecting the LGA to TWTA2 in
  command group 2.  Again, no signal was seen as a result of this commanding.
  A command file to turn off heaters was also interleaved with the other
  commanding.

  Upcoming Events/Items of Note:
  1. MRO will attempt to image MGS with both the CTX and HiRise.  The
     images are scheduled to be on the ground shortly after 12:00 MST.
  2. MGS TAGUP at 15:00 MST today to discuss the images.
  3. MR commands are being built to enable, turn on and command MR to
     mode 1 in preparation for a MER overflight in the Tuesday/Wednesday
     time frame.
  4. Fault tree work continues.


Engineering Data
================

     We were unable to obtain spacecraft engineering data for 2006/320-322
(2006-11-16 to 2006-11-18) due to the ongoing spacecraft emergency.


Open Loop Data
==============

  Data Collection
  ---------------

     No data collected.


Closed Loop Data
================

  Data Collection
  ---------------

     We have obtained the following files from OSCARX:

        Collect   By Type    File Name            Original File Name
          DOY                  (SOPC)
       --------  --- ----  ------------  -------------------------------------
       2006-324  JDT  EOP  2020H039.EOP  061117_165957-eop.long
       2006-324  JDT  EOP  G038H039.EOP  061117_165957-eop.short
       2006-324  JDT  ION  G305335F.ION  gimcal_94_0611_dopr.csp
       2006-324  JDT  TNF  G317H54A.TNF  20063170720_54.tnf
       2006-324  JDT  TNF  G317O14A.TNF  20063171430_14.tnf
       2006-324  JDT  TNF  G317T43A.TNF  20063171925_43.tnf
       2006-324  JDT  TNF  G318E45A.TNF  20063180440_45.tnf
       2006-324  JDT  TNF  G318H65A.TNF  20063180715_65.tnf
       2006-324  JDT  TNF  G318O14A.TNF  20063181430_14.tnf
       2006-324  JDT  TNF  G318T43A.TNF  20063181940_43.tnf
       2006-324  JDT  TNF  G319H54A.TNF  20063190720_54.tnf
       2006-324  JDT  TNF  G319O14A.TNF  20063191430_14.tnf
       2006-324  JDT  TRO  G305326A.TRO  ATC06nov.csp

  Anomalies
  ---------

     The have been no confirmed detections of the MGS signal since 2006/307
and no likely detections since 2006/310; so the "data" in the ODF and TNF's
listed above should be considered suspect.


Ancillary Data
==============

  Data Collection
  ---------------

     We have obtained the following files from the DOM:

        Collect   By Type    File Name            Original File Name
          DOY                  (SOPC)
       --------  --- ----  ------------  -------------------------------------
       2006-324  JDT  OPT  G306335A.OPT  optg_m_061102-061201_mro-img_061117
       2006-324  JDT  SPK  G306335A.SPK  spk_m_061102-061201_mro-img_061117