Having issues with history sets involving DVEs.
I have history sets on a monitored table.
When I enable the DVE, the alarm moves to the new element successfully and keeps the history set. (The ‘warning’ alarm in this example)
After I disable the DVE, the alarm is recreated under the parent element with a new root alarm time.
Is this expected behavior or is there something I missed out in my implementation? Appreciate any advice, thanks!
Hello Joshua,
Are you sure the sets that are performed are sent in chronological order?
If the answer is yes, I believe it’s best to create a support ticket.
Things that we would require:
DELT package of the DVE main element (make sure alarms are checked so we have the alarm history, child will automatically be exported too) when the DVE is created and has the alarm tree exported and either simulation files or a virtualized version of the driver.
That way it can easily be simulated and checked if either we can suggest a workaround for the time being.
Regards,
Hi Davy, in the example there was only 1 set done and on a new element.
Thanks for the reply, I'll follow up with the support ticket if required.