| 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: seq and synchronous writes |
| From: | "Konrad, Martin" <[email protected]> |
| To: | "[email protected]" <[email protected]> |
| Date: | Thu, 5 Sep 2013 22:30:44 +0000 |
Hi Mark, > Event flags are very useful for detecting changes that may be too > quick to catch by looking at the value. I looked into them as well but the sequencer documentation says: "Neither testing the value of a monitored channel in a when clause nor associating the channel with an event flag and then testing the event flag can guarantee that the sequence is aware of all monitors posted on the channel." But going through the documentation again revealed that this issue can be fixed using queuing monitors: http://www-csr.bessy.de/control/SoftDist/sequencer/Tutorial.html#queuing-monitors However the easiest way seems to be using asychronous pvPuts together with pvPutComplete. Unfortunately all these solutions require an additional state. But I think I can live with that... Thank you! Martin