Hi,
We have been using the csi3HistoryExt for years (AX and N4) but have run into a problem that seems to be limited to N4, we are currently running on 4.2.36.34 with the current N4 version of the csi3HistoryExt from your downloads page.
We generally configure all the historyExts the same with 15min interval and COV increment of 0.05 (5%) and min cov time of 0sec (data centre project wanted to catch short evernts) and this is generally working.
When we have a history and alarm extension on a point we start to run into trouble, i’ll detail an example in a attempt to describe the problem;
BacnetBooleanPoint with csi3HistoryExt and a BooleanChangeOfStateAlarmExt.
The alarmValue of the alarmExt is set for “true” and time delays of 1min ON, 1min OFF
When the point value is false, history records are recorded as you would expect (every 15mins) however, once the point value goes to “true” a history record is recorded (once for the change of value as expected) and then again every 3-5seconds but but the record value and status are the same for each record. After the 1minute delay, the alarm status bit comes ON (expected history record is recorded) and then the records keep being recorded every 3-5 seconds while the alarm persists. Once the point value goes back to false (expected record recorded) the 3-5s recording continues, then after 1 minute delay, the alarm status bit turns off but the 3-5s records continue. At this point the status is {unackedAlarm}, the 3-5s records continue until the alarm is acknowledged in the alarm console - once acknowledged, the history returns to what we would expect, a record every 15mins until the point value changes again.
Ultimately the result is histories with millions of records that have the same value every few seconds.
Any insight would be great
Thanks in advance
Dane