VXI gurus,
I'm starting to develop driver and device support for a bunch of in-house VXI
modules. These are register based modules which occupy space in both A16 and A24
space. Some of them have DSPs on them which will need to be loaded with code and
coefficient tables. I've been using drvAt5Vxi.c as a model. My VXI slot 0
processor is a National Instruments VXIcpu-030. There is no MXI in the system.
I'm using EPICS 3.12.2.
First off, are there any new developments that I should be aware of? Second,
documentation for VXI support seems to be rather scarce, with only Jeff Hill's
man pages to go on. Is there any other documentation around? There seems to
be a lot of stuff #if'ed out in the code, so I'm wondering if this is a finished
product.
SLAC does not appear to have a VXI manufacturer ID and so the boards are being
loaded with code 0xf00 which is defined as "user custom". Will EPICS VXI support
work with this? Does it care?
There is a non-VXI device in the crate (an Allen Bradley 6008-SV1R Scanner
module) on an HP E1407A VME-VXI adapter. How do I tell the EPICS resource
manager about it? Does it care?
drvAt5Vxi seems to require drvEpvxi (which I guess replaces epvxiLib?). It
also requires the resource manager to have run before its init routine will
complete. How is this guaranteed?
Thanks.
--
Ric Claus ([email protected], (415) 926-2697)
- Replies:
- Re: VXI support Jeff Hill
- Navigate by Date:
- Prev:
A bad thing happens when I build base/ Bill Brown
- Next:
Re: A bad thing happens when I build base/ Andrew Johnson
- 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: A bad thing happens when I build base/ Bill Brown
- Next:
Re: VXI support Jeff Hill
- 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
|