You can help by commenting or suggesting your edit directly into the transcript. We'll review any changes before posting them. All comments are completely anonymous. For any comments that need a reply, consider emailing email@example.com.
We are experiencing playback issues from our video hosting provider. Please check back shortly.
1:34Alarm Status Component
2:29Alarm Status – General Filtering
1:40Alarm Status – Filter on Associated Data
2:42Alarm Status – Row Styles
2:37Alarm Journal Component
2:22Alarm Journal – Filter on Date Range
2:03Alarm Journal – General Filtering
1:47Alarm Journal – Filter on Associated Data
1:27Alarm Journal – Row Styles
Take topic challenge
The Alarm Journal Table provides a built-in view to explore alarm history that has been stored in an Alarm Journal.
Video recorded using: Ignition 7.9
Transcript(open in window)
[00:00] Once we have the Alarm Journal set up in our Gateway, let's take a look at how we can visualize that data in a project. First, let's go up to the Tools menu and go to the Database Query Browser, where we can see our Alarm Events Table, an Alarm Event Data Table, in the database. If I were to query the Alarm Events Table, we can see that it's filled with a bunch of different alarm events that have happened over the past few hours. These two tables are standard database tables and can be queried directly using SQL queries. However, Ignition has a built in component to visualize this data called the Alarm Journal Table, located here in the Alarming section. Let's drag it on the window and take a look at it. You can see that it's set up like a table component but it's set to specifically query those Alarm Journal Tables. It uses color coding to help differentiate between the different types of events, although this can be customized to suit your needs. And if I put it into Preview Mode, you can see that it acts just like a power table and I can move the columns around and even select rows. I can also select the magnifying icon down in the lower right here where I can view more details about the row that I have selected. Finally, two of the most important properties of this Alarm Journal Table are the start and end date properties. By default, both the start and end date properties will be set to no date. However, what this means is that it's going to be looking at the last eight hours of alarms. Additionally, the Alarm Journal Table component does not automatically update, like the Alarm Status Table Component does. What this means is that if a new alarm event were to occur, it doesn't automatically get loaded into the table. The table first has to update to see the changes, so while my Alarm Journal Table says the most recent event was at 1:51 p.m., this is only because this was the most recent event when it last updated, which is when I first dragged it onto the screen. To get the component to update and pull in the most recent values, I would need to change the start and end date properties, typically through a binding. We will go over how to set up bindings on the start and end date properties as well as how to configure many of the other properties of the Alarm Journal Table later on in the course.