[comp.os.vms] custom sequential access SCSI device for ds3100 SCSI

johns@calvin.spp.cornell.edu (John Sahr) (01/17/90)

We are building a data acquisition device that will use the SCSI
interface to transfer its data out (and operating parameters in).
This device can be implemented as a sequential access device (like a
tape), as opposed to a random access device, making its design simpler
than a disk interface.

Our question: The SCSI standard does not require that a sequential
access device support disconnect/reselect (and related commands such
as save and restore data pointer).  Our largest data transfer block
will be about 64kbytes (adjustable downward to a minimum of 16kbyte if
need be); at the top speed we envision, we could be generating
200byte/sec, thus up to 3 blocks per second may need to be
transferred.  We will support synchronous operation.  Because the
disconnect/reselect adds some complexity to our design, we would like
to avoid it, if possible.  Is this reasonable or possible for the
ds3100?  In particular, for the purposes of the ds3100, must we
support disconnect/reselect?

(in case you wondered: this is not a commercial product.  We are
building a timing generator and digitizer for a small atmospheric
radar used by the Space Plasma Physics Group at Cornell University).

praises, flames, info, and inquiries by email (please) to
johns@alfven.ee.cornell.edu  607 255 8298
-- 
John Sahr,                   | Electrical Engineering - Space Plasma Physics
johns@alfven.spp.cornell.edu | Cornell University,         Ithaca, NY  14853