NA HMI Alarm Viewer

[kckku 9]

How can I increase the number of logged alarms in alarm viewer when using historical mode? The number of alarms seem to restart on its own and doesn't log alarms back far enough for me to get any useful information about machine stoppages. I seem to be only getting about an hour's worth of alarms.

[BE 15]

I don't know if the qty of alarms can be increased, but there is another thread about saving the log to a file. If you aren't able to see what you need, maybe saving the log to a file at intervals would allow you to at least review what was happening at the time (even if it is a bit more stuffing around to get the information)

When you say an hours worth of alarms, roughly how many alarms are we talking about? Is it 100ish, or more like 1000 etc.

 

[kckku 9]

On 7/29/2024 at 5:14 PM, BE said:

I don't know if the qty of alarms can be increased, but there is another thread about saving the log to a file. If you aren't able to see what you need, maybe saving the log to a file at intervals would allow you to at least review what was happening at the time (even if it is a bit more stuffing around to get the information)

When you say an hours worth of alarms, roughly how many alarms are we talking about? Is it 100ish, or more like 1000 etc.

 

I checked the HMI and it's only showing 50 alarms in the alarm viewer. So not really useful at all right now.

It looks like I will need to use the save to the log file option. I remember doing this for another project.

I had our intern ftp the files out daily so we can see what happened overnight. It would be nicer if we can look at the screen with more alarms (like 8 hours for a shift's worth).

Edited 31 July by kckku

[BE 15]

13 hours ago, kckku said:

it's only showing 50 alarms in the alarm viewer.

Is it set up to show all the alarms or only alarms above a certain priority? I am sure I used to have multiple screens full of alarms in my NA screens (tended to get lot of faults when the PLC fired up before healthy contacts closed........), but the history logs were configured to show everything. I have never played around with the setting to only show certain alarms, but I would assume the alarms not shown would still be in the memory, and therefore taking up 'spots' on the alarm viewer history log. Never tested it though, so only guessing at this point.

[kckku 9]

11 hours ago, BE said:

Is it set up to show all the alarms or only alarms above a certain priority? I am sure I used to have multiple screens full of alarms in my NA screens (tended to get lot of faults when the PLC fired up before healthy contacts closed........), but the history logs were configured to show everything. I have never played around with the setting to only show certain alarms, but I would assume the alarms not shown would still be in the memory, and therefore taking up 'spots' on the alarm viewer history log. Never tested it though, so only guessing at this point.

 

All of the user alarms are configured as level 1. The alarm viewer in historical mode is set to show only level 1 alarms.

I really thought it would be easier than this to set the number of alarms that is shown.

Edited 1 August by kckku
deleting unnecessary text

[BE 15]

Silly question, do you have scroll bar on the right side of your Alarm Viewer? When I had more than one page of alarms, it showed a scroll bar on the right so I could see the older alarms

[kckku 9]

On 8/5/2024 at 8:25 PM, BE said:

Silly question, do you have scroll bar on the right side of your Alarm Viewer? When I had more than one page of alarms, it showed a scroll bar on the right so I could see the older alarms

I do see a scroll bar but no luck. Even when I scroll, it's only showing around 50 alarms.

[Str8jCkt 14]

@kckku

I have not had an issue with number of retained user alarms but there is a way to check your system to see what it "thinks" it can display.

HMI Setting >> Maximum Number of User Alarm Logs

This is what you set but may not be what it is capable of depending on several things you do in your program.  There may not be enough resources left on your HMI to actually hold this set limit. So go to Project >> Resource Usage and check to see what the HMI estimates it can do.

 

If your estimated number is low then your project is using too much of the system resources that could be used for the Log history.

 

See from the manual.

Edited 9 August by Str8jCkt

[kckku 9]

I think I know what's going on. I checked the maximum number of user alarm logs and it's set to 2000. 

I looked at the alarm file that I got over ftp and it does in fact have 2000 entries. However, the log file contains all the alarms and some of them I don't care about. For example, it's logging the operator alarms like (load parts, remove parts, scan new box, etc.). About 1800 out of the 2000 entries are these sort of 'alarms'. 

This is why I am only seeing about an hour's worth of actual 'errors' where the machine stops. The rest of the buffer is filled with 'warnings'.

I don't think there's a way to define what actually gets logged. Not sure if there's another way.

 

 

[kckku 9]

I think I know what's going on. I checked the maximum number of user alarm logs and it's set to 2000. 

I looked at the alarm file that I got over ftp and it does in fact have 2000 entries. However, the log file contains all the alarms and some of them I don't care about. For example, it's logging the operator alarms like (load parts, remove parts, scan new box, etc.). About 1800 out of the 2000 entries are these sort of 'alarms'. 

This is why I am only seeing about an hour's worth of actual 'errors' where the machine stops. The rest of the buffer is filled with 'warnings'.

I don't think there's a way to define what actually gets logged. Not sure if there's another way.