Alarm monitoring of non-val fields

Bug #1185928 reported by Andrew Johnson
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
EPICS Base
Confirmed
Medium
Andrew Johnson

Bug Description

http://www.aps.anl.gov/epics/core-talk/2013/msg00038.php

Kay pointed out that an alarm monitor on a non-VAL field (such as ai.LOW) never receives updates when the record's alarm status or severity changes. There is provision in the code for db_post_events() to allow callers to specify NULL for the pField pointer to send such updates, but none of the standard record types currently make use of that.

Note, the fix for this is *not* to just add another call to db_post_events(prec, NULL, monitor_mask), that results in multiple monitor events from a single record processing. Fixing this will take thought and understanding of each record type, and will increase the CA traffic from each IOC because we're generating more monitors than we used to.

Tags: codeathon rec
Changed in epics-base:
assignee: nobody → Andrew Johnson (anj)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.