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: | RE: QuadEM operation with parameters "Queued" |
From: | Iain Marcuson via Tech-talk <tech-talk at aps.anl.gov> |
To: | Mark Rivers <rivers at cars.uchicago.edu> |
Cc: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Thu, 21 Oct 2021 14:33:38 +0000 |
> asyn does queue both write and read operations if you create your driver with the ASYN_CANBLOCK flag. Did you do that? I am assuming I am not doing ASYN_CANBLOCK, as I see no references to it in the code > How does your polling record work, i.e. is it going through your quadEM driver and then the underlying drvAsynIPPort driver? The record has a SCAN field of 1 second. When it is triggered, it invoke ::writeInt32(), which sets the output buffer to the empty string and then calls the function writeReadMeter() to write
and read from the hardware. writeReadMeter() skips the write on an empty string, and then reads the input buffer until empty. > Changing parameter A and having no message sent does not make sense to me unless the asyn queueRequest is timing out. Are there any messages on the IOC console when this happens? I am having trouble reproducing the problem, but I don’t recall any messages like that. > > All writes, which includes the 1 Hz record mentioned above, write to the same shared buffer that is then sent, so might there be contention there? > Does your polling record write to a record which then results in your driver's writeOctet or similar method being called? If so, then it should be OK because if you set ASYN_CANBLOCK then both the drvAsynIPPort driver lock, and
the asynPortDriver lock for your quadEM driver will be held when writeOctet is called. If you then write to the shared buffer and immediately call the underlying drvAsynIPPort->write() function then it should not be possible for 2 threads to be trying to
use the shared buffer at the same time. The polling record writes to a member char array and ultimately invokes pasynOctetSyncIO->write() and pasynOctetSyncIO->read(). There is no writing to another record. Mark From: Tech-talk <tech-talk-bounces at aps.anl.gov>
on behalf of Iain Marcuson via Tech-talk <tech-talk at aps.anl.gov> I am working on writing a new IOC for QuadEM device, and the IOC mostly works. The IOC talks over TCP via asyn to a middle software layer that talks to the hardware. The middle
layer can send unsolicited messages to EPICS, so I implemented polling by having a record scan once a second and read the port. Sometimes, however, I get a case where EPICS seems to be queueing writes, so I would get Change parameter A -> No message send Change parameter B -> Send A Change parameter C -> Send B All writes, which includes the 1 Hz record mentioned above, write to the same shared buffer that is then sent, so might there be contention there? Thank you, Iain Marcuson Software Engineer, Sydor Technologies 585.278.1168 |
www.SydorTechnologies.com Skype:
iain.marcuson at sydorinstruments.com This message has been scanned for malware by Forcepoint.
www.forcepoint.com Click
here to report this email as spam. |