Is there a way to track the status of each of the analogue value ranges on a multi range analogue alert handle? I thought I can do a dpConnect on the _act_state, but those don't seem to change at all for any of the configured ranges. For example, with three ranges configured, if I do the following:
dpConnect("callbackfct", "tag.value:_alert_hdl.1._act_state", "tag.value:_alert_hdl.2._act_state", "tag.value:_alert_hdl.3._act_state");
The dpConnect callback function "callbackfct" only triggers once during initialisation and then never fires, regardless of which of the ranges are actually triggered. If I add "tag.value:_alert_hdl.._act_state" to the above to also track the status of the overall alert handle act state, then I can see that this changes, but all of the 1/2/3 _act_state values remain at zero. Tried it with a dpQueryConnectSingle and also with _act_state_color and those also don't work.
What I wanted to do is track which of the ranges is triggered, so that I can show the correct status on a popup which shows all the ranges configured for a particular analogue value.
status of analogue value ranges - no _act_status change?
- tpjctrl
- Posts:145
- Joined: Tue May 08, 2018 10:30 am
status of analogue value ranges - no _act_status change?
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: status of analogue value ranges - no _act_status change?
In the documentation it is written that the attribute _act_state gives the state for the alarm of the highest range.
It looks like you can only do a connect to _act_state without detail number.
Best Regards
Leopold Knipp
Senior Support Specialist
It looks like you can only do a connect to _act_state without detail number.
Best Regards
Leopold Knipp
Senior Support Specialist