Re: MVME162's for remote I/O

[Matthias Clausen DESY -MKV2/KRYK- <claus@heracc.desy.de>]

>For your I/O you would (obviously) want to use some IP boards.  There
>are not any official EPICS drivers for them as far as I know.  DESY
>has been doing work in that area.  And there is always talk of them in
>the c.o.v group on usenet.

We (DESY) use the 162's as EPICS IOCs as well as intelligent I/O 
controllers. In the first case EPICS; VXWorks(full function) and the driver 
for the mounted IP-board are running on the same 162. In the second case 
the 162 is an intelligent I/O controller running a reduced VxWorks kernel 
and the driver to the IP-board. 
All the software is the same in both cases. There's only a config file 
which defines where the driver for the I/O is located on/off board.
The link between EPICS device support and the driver itself is performad by 
the 'common driver interface' written by Gabor.
If the 162 is a slave you can use the smallest one available.
512kB will do but 1MB is better...
Currently the 162 slaves a booted through the VME backplane and the master 
(167) from the SUN. We (Gabor) are working on a prommed version in which 
case the board can run together with any other operating system in the same 
VME crate.

Matthias
	----------------------------------------------------------------
	Matthias Clausen		Deutsches Elektronen Synchrotron
	Gruppe: MKV2/KRYK		       DESY/Hamburg, Germany