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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: Differences between using disconnectOnReadTime in asynSetOption and asyn record |
From: | "Wang, Andrew via Tech-talk" <tech-talk at aps.anl.gov> |
To: | Mark Rivers <rivers at cars.uchicago.edu>, EPICS tech-talk <tech-talk at aps.anl.gov> |
Date: | Thu, 23 Mar 2023 13:55:06 +0000 |
Mark, thank you very much. From: Mark Rivers <rivers at cars.uchicago.edu> Hi Andy, > Is there a difference between the two approaches for disconnecting a port upon a read
timeout? No, there is no difference. The asynRecord simply calls the setOption() method in the
asynOption interface to the driver in this line: That is this code: case asynRecordDRTO:
status = pasynRecPvt->pasynOption->setOption(pasynRecPvt->asynOptionPvt, pasynUser, "disconnectOnReadTimeout", drto_choices[pasynRec->drto]); break; Mark From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Wang, Andrew via Tech-talk <tech-talk at aps.anl.gov> Hi all, I have a clarification question regarding setting a port to disconnect upon a read timeout. In the asynRecord documentation, there is a DRTO field in the IP Control Fields section (https://epics-modules.github.io/asyn/asynRecord.html#ip-control-fields)
for that. Meanwhile, in the asynDriver documentation (https://epics.anl.gov/modules/soft/asyn/R4-29/asynDriver.html),
the disconnectOnReadTimeout key can be used for asynSetOption. Is there a difference between the two approaches for disconnecting a port upon a read timeout? Thanks, Andy |