REQUIRED DATA FOR SEISMIC CONTROLLER SOFTWARE		BKT  06-Dec-99

Table + actuators final assembly drawing, showing:

1)  The desired degrees of freedoms (e.g., "X", "Z", and "Pitch").

2)  Direction of positive X, Y, and Z.

3)  Actuator labels (e.g., "X1", "Y3", etc).  These should agree with
    the labels used in drawings and cable labels.
	
4)  Actuator-table attachment data:

    When all actuators are at center stroke, give the x-y-z coordinates
    of both pivot ends of each actuator relative the center top of the
    table (i.e., the "table origin"), and its pin-to-pin length.  If the
    actuator works through a strut, also give the locations of both pivot
    ends of the the strut and its pin-to-pin length.

5)  Accelerometer labels (e.g., "AX1", "AY3").    These should agree with
    the labels used in drawings and cable labels.

6)  Accelerometer attachment data:

    Give the x-y-z coordinates of each accelerometer relative the center
    top of the table (i.e., the "table origin"), and its orientation.


Individual actuator data:

1)  Dynamic stroke (not static).
2)  Piston area.
3)  Flow rating @ 1000 psi.
4)  Pressure transducer calibration, i.e., what it reads in engineering
    units when its output is 10 volts.
5)  If there is a Temposonics displacement feedback transducer, its
    calibration measured in counts per inch.


Individual accelerometer data:

1)  Accelerometer calibration, i.e., what it read in engineering units
    when its output is 10 volts.


Customer preferences for engineering units:

1)  Displacement
2)  Velocity
3)  Acceleration
4)  Force
5)  Pressure
6)  Mass


Mechanical complications:

1)  Mechanical constraints on a degree-of-freedom.
2)  Desired restrictions on the range of motion commanded by the
    controller due to clearance problems, etc.
    

Electrical input/output channel assignments:

1)  Signal conditioners.
2)  A/Ds and D/As.
3)  Digital I/O.


Miscellaneous questions:

1)  Is STEX being provided on this system?  Does it interface to the
    controller via A/Ds and D/As or by direct program-to-program
    communication?

2)  Does the user want to hook our controller up to his data acquisition
    system?  If so, what signals do we provide him (in analog, of course)?

3)  How does the controller interface to the hydraulic pumps and manifolds?
