Hi Mark,
I’m sorry to trouble you again, on a different subject.
I refer to
http://www.aps.anl.gov/epics/tech-talk/2012/msg00924.php.
I’m using setParamStatus, for an I/O Intr driven ‘Fault’ value, in my application, to signal alarm status.
There seems to have been a behaviour change between Asyn 4-26 and Asyn 4-27.
When using 4-27, the alarm status on ‘Fault.SEVR’ field is set to INVALID, but the ‘Fault.VAL’ field is not updated with the (non-zero) value that indicates the fault condition.
But if I comment out the setParamStatus call, then Fault.VAL is set to the correct value.
Both values were set as expected, while using 4-26.
Many thanks,
Peter.