Re: aCalcout AVAL monitors

[Bruno Martins <brunoseivam@gmail.com>]

Hi Tim,

Sounds like the perfect solution! Would you want me to open a pull request?

Thanks,

Bruno

On Mon, Dec 18, 2017 at 3:34 PM, Mooney, Tim M. <mooney@aps.anl.gov> wrote:

Hi Bruno,

This seems a good improvement.  How about this: if any array element has changed by MDEL or larger, the array is posted with DBE_VALUE, and

if any array element has changed by ADEL or larger, the array is posted with DBE_LOG.

Tim Mooney (mooney@aps.anl.gov) (630)252-5417
Beamline Controls Group (www.aps.anl.gov)
Advanced Photon Source, Argonne National Lab

---

From: tech-talk-bounces@aps.anl.gov <tech-talk-bounces@aps.anl.gov> on behalf of Bruno Martins <brunoseivam@gmail.com>
Sent: Monday, December 18, 2017 2:24:00 PM
To: tech-talk@aps.anl.gov
Subject: aCalcout AVAL monitors

 

Hi everyone,

If VAL doesn't change between processings, acalcout doesn't post a monitor event to it, unless MDEL is set to -1 (as expected).

However, the same is not true for AVAL. Even with MDEL set to -1, if AVAL doesn't change I get no new monitor events. Here's the relevant code in the calc module:

https://github.com/epics-modules/calc/blob/master/calcApp/src/aCalcoutRecord.c#L983

This has come up before, and Tim Mooney explained it here:

http://www.aps.anl.gov/epics/tech-talk/2013/msg00069.php

So my question is: shouldn't AVAL's behavior follow VAL's? Or at the very least, shouldn't there be a mechanism to force AVAL to update?

Bruno