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: Understand put requests |
From: | Mark Rivers via Tech-talk <tech-talk at aps.anl.gov> |
To: | "Liu, Wanming" <wmliu at anl.gov>, "Zhang, Tong" <ZhangT at frib.msu.edu> |
Cc: | EPICS tech-talk <tech-talk at aps.anl.gov> |
Date: | Fri, 30 May 2025 13:49:23 +0000 |
The details of what happens when you write a new request before the previous one is complete can depend on the record type and device/driver support. But in general I think it will queue at most one new request if the record is currently processing a previous
request.
Your client can use ca_put_callback to ensure that a previous request is complete before issuing another one.
Mark
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Zhang, Tong via Tech-talk <tech-talk at aps.anl.gov>
Sent: Friday, May 30, 2025 8:03 AM To: Liu, Wanming <wmliu at anl.gov> Cc: EPICS tech-talk <tech-talk at aps.anl.gov> Subject: RE: Understand put requests Hi Wanming,
Normally, the device is working well with caput under human interaction, but just sometimes does not respond (got stuck on the last setpoint) to the optimization algorithms issued put requests.
Cheers, Tong
From: Liu, Wanming <wmliu at anl.gov>
[EXTERNAL] This email originated from outside of FRIB I would try to use caput or pvput in a terminal to make sure it response before try to do it with a script or whatever. From: Tech-talk <tech-talk-bounces at aps.anl.gov>
on behalf of Zhang, Tong via Tech-talk <tech-talk at aps.anl.gov>
Dear Colleague, |