I am trying to understand why there is a vast difference with alarms when you apply history tracking and with history tracking enabled, it condenses the alarms down to just 4 per instance?
If it is the same alarm that is coming and going (due to rain fade in this case) there were some 67 alarms. Once history tracking was applied as a filter, the alarm count had reduced to just 16.
This has caused some confusion and misdiagnosis of faults as there were clearly more alarms to indicate there was an issue onsite.
Does anyone else experience the same kind of filtering in Cube?
I'm asking this because we still have users on System Display (Plan is to migrate them over very soon and upgrade) who have been interpreting alarms a particular way in System Display and moving over to Cube is displaying or highlighting alarms very differently which is probably why the current operators a hesitant to move over.
To remove the 5 alarms per parameter limitation, please adjust the MaintenanceSettings.xml > AlarmSettings > AlarmsPerParameter from a value of 5 to a value of 100 (default). This will allow Cube to display up to 100 alarm updates per parameter. As an example, I have already implemented this change on the T01 server pair.
Thanks Michiel and Michaël!