Undefined ao record wrongly resets UDF when processed
Bug #1722540 reported by
Ralph Lange
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
EPICS Base |
Confirmed
|
Undecided
|
Ralph Lange |
Bug Description
An unset ao record, that is correctly UDF/INVALID after IOC reboot, wrongly resets UDF to false when it is processed.
Processing an undefined output record does not define its value.
Test DB:
record(ao, "ao") {
field(PINI, "YES")
}
record(bo, "bo") {
field(PINI, "YES")
}
... ad lib
After IOC boot (and PINI processing), the ao seems defined with NO_ALARM, while all other records are correctly showing UDF.
Changed in epics-base: | |
assignee: | nobody → Ralph Lange (ralph-lange) |
To post a comment you must log in.
I'm not sure I agree. Processing w/ VAL=0 (the default) should clear UDF. I know I created DBs which depend on this.