RE: camonitor the PACT field

["Neidherr, Dennis Dr. via Tech-talk" <tech-talk at aps.anl.gov>]

Hi Marc,

 

ahh, thanks. Good to know that there is a difference also for other fields.

 

Greetings Dennis

 

From: Mark Rivers <rivers at cars.uchicago.edu>
Sent: Donnerstag, 15. Mai 2025 14:41
To: tech-talk at aps.anl.gov; Neidherr, Dennis Dr. <D.Neidherr at gsi.de>
Subject: Re: camonitor the PACT field

 

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.

https://epics.anl.gov/EpicsDocumentation/AppDevManuals/RecordRef/Recordref-6.html

 

Unfortunately, the new EPICS 7 Record Reference Manual does not have a column that indicates whether fields generate monitors.

https://epics.anl.gov/EpicsDocumentation/AppDevManuals/RecordRef/Recordref-6.html

 

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