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: odd ASYN behavior |
From: | Mark Rivers via Tech-talk <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>, "Runchey, John" <jrunchey at anl.gov>, Mark Rivers <rivers at cars.uchicago.edu> |
Date: | Fri, 18 Mar 2022 17:47:07 +0000 |
What versions of quadEM and asyn are you using?
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>
Sent: Friday, March 18, 2022 12:45 PM To: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>; Runchey, John <jrunchey at anl.gov> Subject: Re: odd ASYN behavior
HI John,
I just looked at the code in drvQuadEM::writeInt32 and drvTetrAMM::setAcquireMode and it looks OK. It sets the new value in the parameter library at the beginning and unconditionally does callParamCallbacks at the end. That should result in the
camonitor value being correct.
I am on vacation but will test this when I return. Meanwhile you could enable all of the asynTrace debugging to see what that shows.
Mark
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Runchey, John via Tech-talk <tech-talk at aps.anl.gov>
Sent: Monday, March 14, 2022 11:14 AM To: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov> Subject: odd ASYN behavior
I'm working with a new build of QUADEM for the tetrAMM and seeing a weird asyn issue.
Summary: When writing to the AcquireMode PV, the associated _RBV PV is 'one behind' in reporting the new value, consistently. But if I manually do a caput to the _RBV.PROC field and force it to process, the readback is then consistently correct.
camonitor of the issue:
S28IDFE-XBPM:CM3ds:AcquireMode 03/11/22 09:00:39.158459244 Single
S28IDFE-XBPM:CM3ds:AcquireMode_RBV 03/11/22 09:00:39.158436082 Multiple
S28IDFE-XBPM:CM3ds:AcquireMode_RBV 03/11/22 09:01:23.572226245 Single
S28IDFE-XBPM:CM3ds:AcquireMode 03/11/22 09:01:23.572245721 Continuous
S28IDFE-XBPM:CM3ds:AcquireMode_RBV 03/11/22 09:01:34.876944669 Continuous
S28IDFE-XBPM:CM3ds:AcquireMode 03/11/22 09:01:34.876973666 Multiple
after caput AcquireMode_RBV.PROC 1:
S28IDFE-XBPM:CM3ds:AcquireMode_RBV 03/11/22 09:06:33.097901171 Single
// caput caused _RBV to update to the (correct) value of Continuous
S28IDFE-XBPM:CM3ds:AcquireMode_RBV 03/11/22 09:06:42.683848695 Continuous
S28IDFE-XBPM:CM3ds:AcquireMode 03/11/22 09:06:42.683874661 Continuous
S28IDFE-XBPM:CM3ds:AcquireMode_RBV 03/11/22 09:06:44.284941724 Multiple
S28IDFE-XBPM:CM3ds:AcquireMode 03/11/22 09:06:44.284974097 Multiple
S28IDFE-XBPM:CM3ds:AcquireMode_RBV 03/11/22 09:06:45.876836770 Single
S28IDFE-XBPM:CM3ds:AcquireMode 03/11/22 09:06:45.876854823 SingleThis is the first time I've built this on a RHEL 8 machine for what that's worth.
Any thoughts?
Thanks,
John
|