Skip to content
Snippets Groups Projects
Commit fde8da21 authored by Arthur Coolen's avatar Arthur Coolen
Browse files

Bug1365: list of datapoints will only be triggered after a change, so it won't...

Bug1365: list of datapoints will only be triggered after a change, so it won't be handed every time a station connects/disconnects, but only after a real change.  I hope this will avoid the dropping errormsg's effect
parent f004b521
No related branches found
No related tags found
No related merge requests found
......@@ -30,7 +30,7 @@
// it monitors the state changes in the database, and will update the alarms accordingly
//
bool bDebug=false;
bool bDebug=true;
bool occupied=false;
main () {
......@@ -112,9 +112,9 @@ void distSystemTriggered(string dp1, dyn_int systemList) {
// also connect to the dpResetList dp to receive lists if dp's that need to be cleared from the global list and thus from the
// datapoint in the database
if (dpExists(DPNAME_NAVIGATOR + ".alarms.dpResetList")) {
dpConnect("resetTriggered",DPNAME_NAVIGATOR + ".alarms.dpResetList",
DPNAME_NAVIGATOR + ".alarms.dpResetStates",
DPNAME_NAVIGATOR + ".alarms.dpResetMsgs");
dpConnect("resetTriggered",false,DPNAME_NAVIGATOR + ".alarms.dpResetList",
DPNAME_NAVIGATOR + ".alarms.dpResetStates",
DPNAME_NAVIGATOR + ".alarms.dpResetMsgs");
} else {
DebugTN("monitorAlarms.ctl:distSystemTriggered|Couldn't connect to"+DPNAME_NAVIGATOR + ".alarms.dpResetList");
}
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment