		Front End Support for 265 Ramp Cards

     Front end support is almost identical as for 165 cards.  The only
differences are: the length of the sub-code 1 buffer, the omission of
sub-code 4, and the code in the SSDN.  You have to refer to the writeup
for 165 card support. 

     The SSDNs for the 265 will look like corresponding SSDNs for 165s
except that the code is 2D instead of 1C (hex).  To summarize: 

		+-------------------------------+
		|	       0		|
		+-------------------------------+
		|     0        | OID = 2D (hex) |
		+-------------------------------+
		|  crate       |  slot		|
		+-------------------------------+
		|      0       |  sub code	|
		+-------------------------------+

     The "sub codes", used to define 4 devices per card, are as follows.
They work just like their 165 counterparts which you know and, er, love:

	Code 1 --  S.F. 1 (Reading and setting only one word), or
		   parameter buffer (more than one word).
		   The basic control property controls the power supply.
	Code 2 --  S.F. 2 (Reading and setting).  The basic control
		   property also controls the power supply.
	Code 3 --  Ramp enable and disable, card reset.  Basic control
		   property only.
	Code 4 --  (Omitted for 265s.)
	Code 5 --  Ramp memory.

     The sub-code 1 buffer looks like this for both flavors of card. 
Note that for the 265 card you can specify 24 clock events, so the
buffer is actually 33 words (66 bytes) long. 

	   +-----------------------+
   +0	   | SCALE FACTOR 1	   |  READ: F(1)A(1)   SET: F(17)A(1)
	   +-----------------------+
   +2	   | RAMP NUMBER EXECUTING |  READ: F(1)A(5)   SET: F(16)A(5)
	   +-----------------------+
   +4	   | S.F. SWITCH TIME      |  READ: F(1)A(6)   SET: F(17)A(6)
	   +-----------------------+
   +6	   | FIRMWARE VERSION #    |  READ: F(6)A(1)   SET: IGNORED
	   +-----------------------+
   +8 - 64 | CLOCK		   |  READ: F(17)A(14) FOLLOWED BY
	   ~    EVENT		   ~         24 F(0)A(14) COMMANDS.
	   |	ASSIGNMENTS        |  SET: 24 F(16)A(6) COMMANDS.
	   +-----------------------+

     Again, it is possible to read or write any slice out of this buffer
by specifying an appropriate length and offset. 
