- Solution Name:
- Alarm History Filter
- Software Version:
- v10
- Keywords:
- Alarms, Filters
Summary
This sample shows solution example demonstrates how to filter Alarm History AlarmHistory data using by applying start and end dates and , as well as SQL statements, as AlarmViewer filters.
The Alarm Viewer object allows to show Online Alarm, Historian Alarms or Audi Trail logs.
In order to select the historian time-frame, the Alarm Viewer object uses the fields Start and EndDateTIme.
This example shows use calendar or SQL queries to populate the Start and End fields.
Technical Information
The Alarm Viewer object allows to show Online Alarm, Historian Alarms or Audi Trail logs.
In order to select the historian time-frame, the Alarm Viewer object uses the fields Start and EndDateTIme.
This example shows use calendar or SQL queries to populate the Start and End fields.
Technical Information
By default, AlarmViewers show online Alarms – that is, Alarms that have yet to be acknowledged and normalized. To view previously active Alarms, double-click the AlarmViewer in Draw mode and change the List checkbox to AlarmHistory. By default, this will show all of the alarms from the AlarmHistorian dataset, accessible via the Datasets → DBs table.
For better visualization, you can filter the AlarmHistory by dates or SQL queries. To do so, double-click the AlarmViewer and specify values for the History Interval and Filter fields. You can also link tags to these fields, to let the user decide which filters to apply, as this solution example demonstrates.
Reference Information
→ See AlarmViewer Control to learn more about AlarmViewers and related settings.
→ For more information on the databases FrameworX uses to preserve a solution’s history, check out Datasets DBs.
In this section:
| Page Tree | ||||
|---|---|---|---|---|
|
Reference Information
See Alarms and Audit Trail for more information.