more quick actions
minimize quick actions
Alarm Data mgt
3
Posts
2
Users
0
Likes
26
Views
Topic starter
Hello,
Is it possible to avoid that threshold alarms are given a new timestamp after the restart of PcVue? The alarm variables are flagged as "saved", but apparently the NS>S transition of the underlying register variable triggers the assignment of a new timestamp.
Posted : 03/05/2018 2:37 pm
Hi Armin
Sorry but it's been a while since I check the forum .
Just a quick thought. Did you try to save the register on which the threshold is based as well. With any chance the threshold will get the saved TS of the register.
Worth a try...
Posted : 09/05/2018 8:52 pm
Topic starter
Did you try to save the register on which the threshold is based as well.
It is already like that. The register variables are Modbus data points with the "Saved" option ticked. However, even though these variables are persisted they are assigned a new timestamp at startup (by the point in time they becoming significant, I guess...).
Maybe that is the actual issue here...? Is it normal that persisted Cimway variables are assigned a new timestamp at startup? The behavior of alarm variables with Cimway-source seems to differ from that.
Posted : 14/05/2018 1:33 pm