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:	Disable output record using asynInt32 interface automatic read from the hardware
From:	Yann Mandza via Tech-talk <tech-talk at aps.anl.gov>
To:	"tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date:	Mon, 22 Apr 2024 17:09:10 +0000

Hi all,

I have an asyn port driver using the asynInt32 and asynFloat64 interfaces for different output record types. Am using the asynDrvUser to create the driver parameters.

I noticed that for asynFloat64 interface, there is no auto call to the ‘readFloat64’ method when DB load at ioc boot which is the behaviour am expecting. However, for asynInt32 interface, Ao records tend to make a call to the ‘readInt32’ method somehow automatically. I tried longout and bo on that interface and there are no initial calls to ‘readInt32’. Tried to follow this thread. https://epics.anl.gov/tech-talk/2019/msg01402.php, but am still puzzled on how to control this feature on AO records.

My DB looks somehow like this, am my driver has these asynflags: ASYN_CANBLOCK | ASYN_MULTIDEVICE

record( ao, "$(P)$(R):DelayedTripAction-O") {

field(DTYP,"asynInt32")

field(OUT,"@asyn($(PORT))INT_PARAM1($(ADDR))")

}

record(mbbo,"$(P)$(R):R2") {

field(DTYP,"asynInt32")

field(OUT,"@asyn($(PORT)) INT_PARAM2($(ADDR))")

}

Best Regards

Yann