Number of Alarms is wrong in AML screen if alarms from sub projects are included

• Related Articles

• opening AML screen with many alarms (including subprojects) causes a freeze

  Description When opening an AML screen with very many entries, the system freezes. Cause: In this case, the alarm ring buffer contains a very large number of alarms (several tens of thousands). If they are no longer active when the Service Engine is ...

• API method UnloadedProjects() doesn't return unloaded sub projects

  Summary When the API method UnloadedProjects() is used to return all unloaded projects from the workspace, unloaded projects that are included in a different project are not returned by the method. Description When the API method UnloadedProjects() ...

• License Only one single process screen": Integration projects start screen disappears after reloading sub project "

  Summary with license "Only one single process screen" after reload of a project open screens from other projects aren't restored Description with license "Only one single process screen" after reload of a project open screens from other projects ...

• In integration project when opening an AML screen from a subproject the filter acts on wrong default project

  Summary In an integration project when opening an AML screen (or faceplate) from a subproject the filter behaves incorrectly: it can display alarms from another subprojects or not display alarms when it should. Description In an integration project ...

• Alarm areas: wrong value of status variables of linked Alarm Classes when number of alarms exceeds the size of ring buffer

  Summary If the number of alarms exceeds the size of the ring buffer, the status variables of linked Classes in Alarm areas are calculated wrong. Description If the number of alarms exceeds the size of the ring buffer, the status variables of linked ...