Subject: |
Re: MVME162's for remote I/O |
From: |
Matthias Clausen DESY -MKV2/KRYK- <[email protected]> |
Date: |
Thu, 01 Dec 1994 20:16:58 EST |
>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
- Navigate by Date:
- Prev:
Re: MVME162's for remote I/O winans
- Next:
CA library on the PC Matt Bickley
- Index:
<1994>
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: MVME162's for remote I/O winans
- Next:
CA library on the PC Matt Bickley
- Index:
<1994>
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|