Experimental Physics and Industrial Control System
Hi Luciano & Mark,
On 2011-11-29 Piccoli, Luciano wrote:
>
> Here is the output and the dbpr's.
> [lpiccoli@cdlx22 iocMksu]$ ./st.cmd
> #! ../../bin/linux-x86/example
> dbLoadDatabase("../../dbd/example.dbd")
> #dbLoadDatabase("HMSApp.dbd")
> example_registerRecordDeviceDriver(pdbbase)
> # Registering MKSU iocsh() functions
> drvMksu_init()
> # Registering MKSU iocsh() functions
> drvAsynIPPortConfigure("MksuServer", "194.168.0.21:56789 UDP", 0, 0, 1)
> initMksu("Mksu", "MksuServer")
> # Creating MKSU object
> asynSetTraceIOMask("MksuServer",0,4)
> asynSetTraceMask("MksuServer",0,255)
> dbLoadTemplate("mksu.substitutions")
> #dbLoadRecords("mksu.db")
> iocInit()
> Starting iocInit
> ###########################################################################
> # ## EPICS R3.14.10-lcls1 $R3-14-10$ $2008/10/27 19:39:04$
> ## EPICS Base built Jul 15 2009
> ###########################################################################
> KLYS:IN20:3130:MOD_TRIG_DELAY_READ devAsynInt32::initCommon Link must be
> INST_IO
> KLYS:IN20:3130:WF_TRIG_DELAY_READ devAsynInt32::initCommon Link must be
> INST_IO
> KLYS:IN20:3130:MOD_TRIG_DELAY_WRITE devAsynInt32::initCommon Link must be
> INST_IO
> KLYS:IN20:3130:WF_TRIG_DELAY_WRITE devAsynInt32::initCommon Link must be
> INST_IO
> iocRun: All initialization complete
Those error messages are printed by the initCommon() routine in
$(ASYN)/asyn/devEpics/devAsynInt32.c but most of the error string comes from
from the parseLinkMask() routine in asynEpicsUtils.c. However the code in
initCommon() calls the latter if it first gets an error from the call to the
parseLink() routine, and unfortunately this results in the error message from
the first call being overwritten.
I wonder if what's happening here is that the parseLink() routine is returning
an error of some kind (there are lots of "goto error" statements in the case
INST_IO: section), but the error reporting code is not telling us what the
actual problem is, and instead is giving us a secondary error. That looks to
me like a shortcoming of the code in initCommon().
- Andrew
--
Optimization is the process of taking something that works and
replacing it with something that almost works, but costs less.
-- Roger Needham
- Replies:
- RE: Asyn: "devAsynInt32::initCommon Link must be INST_IO" Mark Rivers
- References:
- Asyn: "devAsynInt32::initCommon Link must be INST_IO" Piccoli, Luciano
- RE: Asyn: "devAsynInt32::initCommon Link must be INST_IO" Mark Rivers
- RE: Asyn: "devAsynInt32::initCommon Link must be INST_IO" Piccoli, Luciano
- Navigate by Date:
- Prev:
RE: EPICS Base 3.14.12.2-rc1 available for testing Mark Rivers
- Next:
RE: Asyn: "devAsynInt32::initCommon Link must be INST_IO" Mark Rivers
- 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: Asyn: "devAsynInt32::initCommon Link must be INST_IO" Mark Rivers
- Next:
RE: Asyn: "devAsynInt32::initCommon Link must be INST_IO" Mark Rivers
- 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