Alarm sets

[otrotabi]

I´ve been working with the HistoricalTM172 alarms project Bastian shared some time ago.

The active alarms are shown only as long as a variable set by the PLC is true (or set to value = 1 in the original project).  So I´m wondering if there´s some way I can tell which alarm of the set is being shown in case there is more than one active at a given time.

My goal is to be able to show the time the alarms were active initially. So i need to identify which index is being shown on the screen. Is there anyway to programatically access the $PagIndex variable ? 

[FedericoM · Accepted solution]

Hello,

$PagIndex can be used in the HMI script.

Personally I keep on different pages active alarms and historical alarms events.

If you define an EEprom variable which define the start time of each alarm, you can create additional sets with the same visibility of the alarm one and in this way you will see the active alarms and the related start time

[otrotabi]

Thanks for your answer. I assumed this could not be done without trying, my mistake. But, from the TM172Historical project, it shows the active alarms but the $PagIndex is not related to the "position" of the alarm in the table. Just out of curiosty, I was willing to see if I could display when an active alarm started.

What I mean is this, for example: High Pressure switch alarm is active.  This is my page displaying this alarm.

If I go to the alarm log page, I can see when it started. This information is saved in EEPROM.

What "ideally" I would want to do is to show this information on the active alarms page (the date the alarm started is in red)

But there´s no (easy) way I can know which alarm is being shown at a given time. on the active alarms page, because the $PagIndex var is actually streamlined to the number of active alarms

Anyway, it works fine enough as it is, and it only takes a couple of keystrokes to find the information. I was jut hoping to make it easier for the operator to see how long the chiller or condensing unit has been stopped.

Reading your message once again, it looks like you are defining an additional EEPROM var saving the last time a specific alarm was made active.... I will explore this possibility.