Last revision January 9, 1996

TJD 10069-10070 = December 18-19, 1995

The MQT for LA detector 4 turned off (first time ever) after
   TJD/sec = 10069/02219.6976 (time of last good packet based on CONT data).

It was initially thought that the later resulting AGCOUT messages were
due to detector 3 as had happened several times in the past.
Therefore, detector module 3 was turned off by command after
   TJD/sec = 10069/19025.5856 (time of last good packet based on DISCLA data) 
and turned on by command before
   TJD/sec = 10069/19105.4576 (time of first good packet based on DISCLA data)
although this may be contaminated by a spike so that the first good packet is
   TJD/sec = 10069/19107.5056 

When it was realized that the problem was in detector 4,
detector module 4 was turned off by command after
   TJD/sec = 10070/82643.6336 (time of last good packet based on DISCLA data) 
and turned on by command before
   TJD/sec = 10070/82713.2656 (time of first good packet based on DISCLA data).

Therefore, the MQT for LA detector 4 (affects CONT and HER data) was out
   between  10069/02220  and  10070/82712
and
the entire module 3 (also affects DISCLA, DISCSP, and SHER data) was out
   between  10069/19026  and  10069/19106  (flag 73; also flag 50 for CDFITS)
and
the entire module 4 (also affects DISCLA, DISCSP, and SHER data) was out
   between  10070/82644  and  10070/82712  (flag 74; also flag 50 for CDFITS).


The gain for LA detector 3 was out of balance (no flag was set)
   between  10069/19100  and  10069/29000  (ramp back to normal)

The gain for LA detector 4 was out of balance (no flag was set)
   between  10069/02219.6976  and  10071/02???  (set by command).