EPICS VXI driver support

Experimental Physics and Industrial Control System

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	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
<== Date ==>		<== Thread ==>

Subject:	VXI driver support
From:	[email protected] (John Faucett)
To:	[email protected]
Date:	Mon, 7 Jan 2002 14:49:02 -0700

I'm writing driver support for the KineticSystems V345 output register and using the V215 driver that comes with EPICS 3.13.4 as a pattern. This is my first try at a VXI module. The IOC is a KSC V150 and builds with hkbaja60 routines.

The drvVxi routine does not recognize that the V345 module is present. The vxiMemProbe call in open_vxi_device returns a status value of -1 for all logical addresses (the V345 is set to logical address 1). Therefore epvxiResourceMangerOK never becomes TRUE causing the device support to never fully initialize.

Is some sort of initialization for the V150 required before iocInit runs?

Replies:: RE: VXI driver support Jeff Hill

Navigate by Date:: Prev: Re: mbbiRecord undefined state Marty Kraimer; Next: RE: VXI driver 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
Navigate by Thread:: Prev: RE: Problems building 3.14.0beta1 Rarback, Harvey; Next: RE: VXI driver 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