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: camonitor the PACT field |
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>, "Neidherr, Dennis Dr." <D.Neidherr at gsi.de> |
Date: | Thu, 15 May 2025 12:40:54 +0000 |
Hi Dennis,
The PACT field does not send monitor events, so you can read it, but not monitor it.
The old EPICS Record Reference Manual makes this clear. Note that the Rec Proc Monitor column is No for the PACT field.
Unfortunately, the new EPICS 7 Record Reference Manual does not have a column that indicates whether fields generate monitors.
For example, in the old manual it is clear that the STAT and SEVR fields generate monitors, but in the new manual that information is missing.
Mark
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Neidherr, Dennis Dr. via Tech-talk <tech-talk at aps.anl.gov>
Sent: Thursday, May 15, 2025 1:43 AM To: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov> Subject: camonitor the PACT field Dear all,
I have again a small question, this time about the reading out of the PACT field: For this test I am using a small StreamDevice record which communicates with a connected device. If I execute the processing of this record and use a python script to monitor the status of the PACT field via cagets in a loop, I receive exactly what I expected, so the value of this field changes from 0 to 1 and back to 0. But if I try this with a camonitor (or a pvmonitor) no change is recognized. This also happens in a command prompt so it is no problem of the python library I am using. Is this a normal behavior? Thanks in advance, Greetings Dennis |