I have set up an alarm journal profile to a database that has a valid connection.
I have triggered alarms that show up in the alarm status table. However, I am not getting any alarms in the alarm journal table component in perspective.
What steps am I missing to be able to display historic alarms in the alarm journal table? in the videos the alarm journal table is already populated with alarms when the instructor imports the component. Is there a step to link the alarm journal table to an alarm journal profile I am missing?
I have tried enabling all filters and setting the timedate range to multiple years, but there is nothing. I have tried enabling history for the tag itself, but that does not change anything.
The database looks empty to me. That might be the issue.
I have tried to re-trigger alarms be disabling and enabling them, also by changing the trigger event.
Are there any steps required to enable the storing of alarms in the database other than creating the alarm journal profile? We have not had any issues using the SQL databases for storing historic values. I did not specify any filters when creating the alarm journal profile so in my mind all alarm should be stored there. However, I did specify a name for the alarm journal profile which i noted was not necessary when only having one alarm journal profile.
F.x. do i need to set up anything when configuring the alarm on a tag?
It seems like more than once, I've seen this question come up on a new test system, and the following day, it works, but I'm afraid that I'm just not sure what the problem is. Perhaps somebody else will have an intuition as to what is causing this.
I ran into a similar problem, getting my Alarm Journal Table to populate. My journal name was right, my DB connection was good, and I haven't seen the problem/solution I stumbled across described anywhere. I thought I would share it here for the benefit of any future searchers. On the Alarm Journal Table component properties under filter/events, if enabled or disabled is checked here and logging enabled or disabled events is not enabled on the gateway, nothing at all will be returned for the other event types whether they're selected or not. Simple fix, but it wasn't obvious (not to me anyway).