You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bool Stream::process() initializes the status to NO_ALARM, then calls startProtocol, and if that fails sets recGblSetSevr(record, status, INVALID_ALARM). This means the record will have STAT=NO_ALARM and SEVR=INVALID which is a bit confusing.
Here is a fix, using the COMM_ALARM status instead.
diff --git a/src/StreamEpics.cc b/src/StreamEpics.cc
index 9117fd9..1f16e2d 100644
--- a/src/StreamEpics.cc
+++ b/src/StreamEpics.cc
@@ -732,7 +732,7 @@ process()
return false;
}
debug("Stream::process(%s) start\n", name());
- status = NO_ALARM;
+ status = COMM_ALARM;
convert = OK;
record->pact = true;
if (!startProtocol(StreamCore::StartNormal))
The text was updated successfully, but these errors were encountered:
A short comment: this will be a problem on disconnects, which can easily be simulated by setting of autoconnect and disconnect through CNCT field of the asyn record.
bool Stream::process()
initializes the status toNO_ALARM
, then callsstartProtocol
, and if that fails setsrecGblSetSevr(record, status, INVALID_ALARM)
. This means the record will haveSTAT=NO_ALARM
andSEVR=INVALID
which is a bit confusing.Here is a fix, using the
COMM_ALARM
status instead.The text was updated successfully, but these errors were encountered: