| 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: [EXTERNAL] Difference between caput/caget and PVwrite |
| From: | "Kasemir, Kay via Tech-talk" <tech-talk at aps.anl.gov> |
| To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>, Pilar Gil <pilar.gil at sevensols.com> |
| Date: | Tue, 26 Jan 2021 17:31:30 +0000 |
|
> ..everything goes well if I set a value using CSS-BOY, but the system runs into a segmentation fault if I use two consecutive times the same variable using caput...
>Which step is CSS-BOY carrying out that caput does not include?
caput roughly does this:
connect, caget (old value), caput (desired value), caget (new value), disconnect
A display tool like CS-Studio tends to do this:
connect, subscribe to changes (monitor).
When you write, it performs a caput over that standing connection.
No active 'caget', simply relying on the monitor to report the value change that was caused by the 'caput'.
disconnect when you close the display.
So if you experience a problem when calling the command-line caput, maybe it's related to caput calling caget right after writing?
-Kay
|