When implementing history sets in an existing protocol what are the pitfalls?
What is the impact when updating an existing element with a protocol that now has history sets?
Is implementing history sets on an existing protocol is that considered a major change?
The impact I have in mind
(1) from a driver-logic point of view this no problem
(2) DataMiner blocks 'going back in time' within an element-run-time, but since this update will trigger a restart of the element nothing will be blocked.
Some caveats
(1) Trend data could be overlapping if you wrote already data to the database at that timestamp. So this might result in a bit of strange behavior there. For real-time these will be 'intermingled'. For the average trend-points this could be a bit more confusing, as there could be 2 records for the same average window.
(2) If your parameter would already have an active alarm, it could be that an update you do with a history-set is 'older' than the previous alarm.