TIGER in-flight checkout procedure

Optional procedures are in italics

TIGER checkout procedure
 Commands
* Start TIGER GSE program
 gse
* Enter a mark in the datastream1 159, ####
* Do a sensor housekeeping [automatic every 4 minutes]
   (may require several times for data to go through)
   Verify temperatures (CPU at 45 degrees should be the maximum)
   Verify high-voltages are correct
   Verify current / low-voltage levels
 154, 5
* Do a misc housekeeping [automatic every 15 minutes]
   (may require several times for data to go through)
   Verify LED levels are set
   Verify threshold settings
   Verify coincidence setting (0276)
   Verify the priority cutoff (3000)
 154, 6
* Look at the scalar housekeeping [automatic every 1 minute]
   (since they are automatic every 1 minute, it is not really necessary
   to enter the command).
   Verify that the scalars are reasonable
 154, 7
* Look at the SIP fast-rate report (wait for reply in window)
 162
* Check the disk space left on the current drive partition
   (each partition has about 2.1 GB)
 164
* Switch partitions if the current one has very little space left
 165, y
* Start a new run
 Type "r" in the
storctl window
* Enter a mark in the datastream1
 159, ####
* Do 100 pedcals @ 10 ms [80 are sent automatically every 20 minutes]
 186, 2, 100, 10
* Do 100 lightcals @ 10 ms [80 are sent automatically every 20 minutes]
   Verify in the cal events window that hodoscope PHA readings look correct
 186, 3, 100, 10
* Enter a mark in the datastream1 159, ####
* Continue exercising instrument
* Enter a mark in the datastream1 159, ####

TIGER turnoff procedure
* Enter a mark in the datastream1 159, ####
* Set all EDACs to 0 179, 0
* Do a sensor housekeeping
   (may require several times for data to go through)
   Verify high-voltages are near 35		 154, 5
* Turn off 12V Vicors to HV 130, y
* Do a sensor housekeeping
   (may require several times for data to go through)
   Verify 12V Vicors are off
 154, 5
* Turn off VME racks 133, y
* Do a sensor housekeeping
   (may require several times for data to go through)
   The sensor housekeeping window should
   return garbled values.		 154, 5
* CPU may be turned off now NSBF discrete


1.  I have been entering MARKs in the datastream as timestamps.  I find that this helps me keep track of when things are done, and how long a given test has been running.  For example, if I'm doing a test in run 00101, and I decide to do 250 pedestal calibrations at 4:30 PM (St. Louis time), I put a MARK 1630 in the datastream before commencing the test.  Then at the end, say two minutes later, I put in a MARK 1632.  We should come up with a scheme for when new runs are started, say at midnight St. Louis time (at the nearest TDRSS window).  This might work well, since that is only 7:00 PM in McMurdo.  At the end of a shift, the user will do a summary of what commands were sent and what marks were made.