I have made a new release of the RT Linux TASS Driver. (RTLTD?
anyone have a better name?  I want the name to mean that it
works for all types of TASS cameras, runs under RT Linux and
handles the camera hardware, FITS files, client connections
and will driver a data reduction script.

The file is "TASS_Driver_09SEP97.tgz" and is now on both
p674p06.isc.rit.edu/pub/incoming  and storm.fnal.gov/incoming

(Hey, It's dark and my computer still works.  I real life
UPS test.  Lights on.  About a 15 sec power fail there.
Good. now I can justify the money spent on the UPS)

This is a bug fix release.  The only new feature is to allow
for an extended "clearing" mode.  The driver will now run in
"fast readout" mode for any lenght of time.  It can be told
to record data to FITS files while in this mode too.  This may
help with making flats.  e-mail for details.

Alarms and Shutdown is working now (I hope)
Type the command "status_t3_alarm_shutdown" to see a table
like the following:
 
CURRENT ALARM and SHUTDOWN SET POINTS:
   TelemetryID,    Alarm_Low,   Alarm_High, Shutdown_Low,  Shutdown_High
      CCD_TEMP,       -1E+20,        1E+20,       -1E+20,          1E+20
     COOL_TEMP,       -1E+20,        1E+20,       -1E+20,          1E+20
   TEC_CURRENT,       -1E+20,        1E+20,       -1E+20,          1E+20
    PLUS5_VOLT,       -1E+20,        1E+20,       -1E+20,          1E+20
   MINUS5_VOLT,       -1E+20,        1E+20,       -1E+20,          1E+20
        SPARE ,       -1E+20,        1E+20,       -1E+20,          1E+20

Any of the above 24 numbers can be changed at any time by using
one of the commands like "t3_alarm_tec_current <flt>  <flt>"
Where flt & flt are floating point numbers which define the
acceptable limits.  Currently everything must be expressed
in ADU numbers.

I would suggest putting the alarm/shutdown points in the start up
file along with your site's lat, long and camera aim points.

I'll do ADU --> unit conversions later once I think of a
good way to specify the conversion.  I want it to be table
driven.  I have not thought of a good way to do this yet.
Any suggestions?

Data still does not go out to clients.  I prefer to fix bugs
before adding new features.  The next realse should have the
ability to broadcast pixel data over a network.