Argonne National Laboratory

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  <20182019  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  <20182019 
<== Date ==> <== Thread ==>

Subject: Re: Possible duplicate writeInt32 call when using Asyn
From: "alan.greer@diamond.ac.uk" <alan.greer@diamond.ac.uk>
To: Mark Rivers <rivers@cars.uchicago.edu>, "tech-talk@aps.anl.gov" <tech-talk@aps.anl.gov>
Date: Thu, 25 Oct 2018 15:06:33 +0000
Ah OK thanks.  I'm using a DLS specific 1-6-1 so the problem could be originating from there.  I'll take a look at that newer version.


Thanks again, Alan


________________________________
From: Mark Rivers <rivers@cars.uchicago.edu>
Sent: 25 October 2018 16:00:18
To: Greer, Alan (OBS,RAL,DIA); tech-talk@aps.anl.gov
Subject: Re: Possible duplicate writeInt32 call when using Asyn

Hi Alan,


What version of the bust module are you using?  There were a number of fixes to the busy record logic in R1-7.


Mark





________________________________
From: tech-talk-bounces@aps.anl.gov <tech-talk-bounces@aps.anl.gov> on behalf of alan.greer@diamond.ac.uk <alan.greer@diamond.ac.uk>
Sent: Thursday, October 25, 2018 9:45 AM
To: tech-talk@aps.anl.gov
Subject: Possible duplicate writeInt32 call when using Asyn

Hello,


I have an IOC with a busy record connected to an asyn parameter within an area detector application.  If I perform multiple caputs to the record occasionally I appear to get two writeInt32 calls in quick succession.  I'm performing the caput calls from a script to ensure I've eliminated any involvement from a GUI.


Below shows the output from asynTrace when this occurs:


2018/10/25 15:12:52.238 ODN.OD addr 0 queueRequest priority 0 not lockHolder
2018/10/25 15:12:52.238 asynManager::portThread port=ODN.OD callback
2018/10/25 15:12:52.238 Param[ODIN_HDF5_WRITE]::put<bool>: 1
2018/10/25 15:12:52.238 Param[ODIN_HDF5_WRITE]::fetch<int>: 0
2018/10/25 15:12:52.238 Param[ODIN_HDF5_WRITE]::basePut: 'true'
2018/10/25 15:12:52.241 OdinDataDriver:writeInt32: function=100, value=1
2018/10/25 15:12:52.241 EXCALIBUR:OD:Capture devBusyAsyn::interruptCallback pr->val=1, new value=1
2018/10/25 15:12:52.241 EXCALIBUR:OD:Capture devBusyAsyn::processCallback value 1

2018/10/25 15:12:52.241 ODN.OD addr 0 queueRequest priority 0 not lockHolder
2018/10/25 15:12:52.241 asynManager::portThread port=ODN.OD callback
2018/10/25 15:12:52.241 Param[ODIN_HDF5_WRITE]::put<bool>: 1
2018/10/25 15:12:52.241 Param[ODIN_HDF5_WRITE]::fetch<int>: 0
2018/10/25 15:12:52.241 Param[ODIN_HDF5_WRITE]::basePut: 'true'
2018/10/25 15:12:52.245 OdinDataDriver:writeInt32: function=100, value=1
2018/10/25 15:12:52.245 EXCALIBUR:OD:Capture devBusyAsyn::processCallback value 1

This is intermittent and the rate of occurrence is altered by turning on the asynTrace debug.
I'm using

asyn 4-31
ADCore 2-6
EPICS R3.14.12.3
RHEL 6

Is this an issue that anyone has noticed before?  I can see that many of our detector application implementations would silently ignore this but in this application we are queueing acquisitions and so we observe in the queue a duplicate request.

Thanks, Alan



--
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom


References:
Possible duplicate writeInt32 call when using Asyn alan.greer@diamond.ac.uk
Re: Possible duplicate writeInt32 call when using Asyn Mark Rivers

Navigate by Date:
Prev: Re: Possible duplicate writeInt32 call when using Asyn Mark Rivers
Next: Re: DM recommedation. J. Lewis Muir
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  <20182019 
Navigate by Thread:
Prev: Re: Possible duplicate writeInt32 call when using Asyn Mark Rivers
Next: calling EIPCS' Raspberry Pi users Chew Eh Piew
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  <20182019 
ANJ, 25 Oct 2018 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·