[comp.os.vms] Help!! VAX/VMS Puma Robot Interface driver and DR-11c

cchang@hubcap.UUCP (Chin Hui Chang) (06/22/88)

Dear USENET readers, 

	At  our  node  at  Clemson University's Electrical and Computer
Engineering department  Computer Vision and Robotics Laboratory, we are
investigating  a  new  software  package  for our Puma 500 robots.  The
problem right now is that we do not have the document as how to install
the driver to  our dedicated VAX 11/750 VMS  system  from  the software
supplier.

	Therefore, we need you to help us to answer the following
questions:

1) We compile the device driver code, link it, and place it in the 
   sys$system directory, right?

$ MACRO PIDRIVER.MAR+SYS$LIBRARY:LIB.MLB/Library
$ CREATE PIDRIVER.OPT
base=0
[CTRL/Z]
$ LINK /NOTRACE PIDRIVER,PIDRIVER.OPT/OPTIONS,-
_$ SYS$SYSTEM:SYS.STB/SELECTIVE_SEARCH
no user transfer address

2) Then we run sys$system:sysgen, use the CONNECT subcommand to
   establish the relationship between the hardware, i.e, the Control
   status register of the DR-11c and the logical device name, in this
   case, OAA0, and the device driver name, PIDRIVER, a sample line 
   might look like this:

$ set def sys$system
$ copy dua0:[000000.rccl.rci]pidriver.exe pidriver.exe
$ run sysgen

SYSGEN> CONNECT oaa0 /adapter=ub0/csr=%0767600/drivername=pidriver-
SYSGEN> /vector=%0300  
SYSGEN> exit

   Is this procedure legitimate?
   Do we have any problems in the DDTAB which shows like:

   DDTAB DEVNAM=PI,-                         ; Generic name of device

   or should we change it to OA?
   Are there any other modifications that we should consider?

   The original software was ran at NASA on a MicroVax II running VMS.
   They're using Q22 bus(?) for interfacing the LSI-11 and in turn the 
   LSI-11 control the PUMA 's 6503 microcontrollers.

   Also, what caution do we need for this procedure?

   We asked this question just to make sure that we are right.
   Hardware difference between NASA and ours is that we use VAX 11/750
   UNIBUS.    

   Richard Critz, if you are out there, would you please answer this
   question for us?  Your help is deeply appreciated!

   Also John Llyod's original LoadLsi document talks about UNIX and
   LSI-11 interface uses the serial port to connect a VAX terminal as
   the console terminal of the LSI-11.  Then he ran a program "loadlsi"
   to cause VAL-II to exit to ODT mode (Online octal Debugging Tool) 
   and cause a bootstrap.  In turn the bootstrap loads the remaining of
   LSI-11 monitor program.  Do we do the same thing over here in VMS?

   (Please use mail)
					Sincerely,

					Joeseph Chin Hui Chang,
					John K. Sun,

					System programmer.
                                        ECE dept, Clemson Univ
                                        Clemson, SC 29634

ARPANET: cchang@hubcap.clemson.edu
         cchang@prism.clemson.edu
         cchang@eureka.clemson.edu

BITNET: JSUN@CLEMSON
UUCP:   ...!gatech!hubcap!scarle!{hazel,citron,amber}!johnksun
        (registration with NIC this summer)