Re: Differences between using disconnectOnReadTime in asynSetOption and asyn record

[Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>]

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:

https://github.com/epics-modules/asyn/blob/974d36c6c55e02f6b7c4818429017e3ed8c2b3b5/asyn/asynRecord/asynRecord.c#L1819

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>
Sent: Thursday, March 23, 2023 7:47 AM
To: EPICS tech-talk <tech-talk at aps.anl.gov>
Subject: Differences between using disconnectOnReadTime in asynSetOption and asyn record

 

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

 

Purple ribbon awareness