800xA Event List not showing events more than 2 to 4 hours
Hi
we have installed 800xA system version 6.0.3.1. All services related to system are running but we have problem when we open event list that not show events more then 2 to 4 hours. even we tired to increase alarm manager capacity from 10K to 50K but we observe same results afetr change.
System event & process alarms are ok and showing older record but only events have issue.
we tired to do cold restart of event storage service by deleting and recreating but that not work for us.
Any suggestion and support will be highly appreciated.
we have installed 800xA system version 6.0.3.1. All services related to system are running but we have problem when we open event list that not show events more then 2 to 4 hours. even we tired to increase alarm manager capacity from 10K to 50K but we observe same results afetr change.
System event & process alarms are ok and showing older record but only events have issue.
we tired to do cold restart of event storage service by deleting and recreating but that not work for us.
Any suggestion and support will be highly appreciated.
Asked 6 months ago
Answers
0
50K / 5 categories = 10K per categories.
If you have a digital alarm every second, you have 3 hours on digital.
If the alarms on Analog are every minute, you have 180 hours on analog
If you have a digital alarm every second, you have 3 hours on digital.
If the alarms on Analog are every minute, you have 180 hours on analog
Answered 6 months ago
1
Leave Alarm Manager storage at 10K.
Increase the storage settings for desired categories at the Event Storage service. If you 5x the number of events, 5x the file size too (leave number of files at default).
Next year, v6.1.1 will likely bring us a much more capable event historian, part of 800xA Base.
Increase the storage settings for desired categories at the Event Storage service. If you 5x the number of events, 5x the file size too (leave number of files at default).
Next year, v6.1.1 will likely bring us a much more capable event historian, part of 800xA Base.
1
I also had issues with too short event histories. This are my experiences:
- Increasing the capacity of some alarm category helps, I have weak memories about having troubles to finally apply changed settings.
- The history length was still not satisfying with moderate increased category capacity, we tried higher values
- Higher values failed due disk space limitations. The alarm files become crazy huge! I had to enable disk compression. xxxx ABB default disk partition scheme!
- The alarm system become very slow (not only due the disk compression, I assume)
- We changed everything back to the original values and developed a different solution:
External event storage using the 800xA Alarm Printer
800xA Alarm Printer --> Windows virtual line text printer --> TCP connection --> Event-Line-to-SQL-Program (my creation) --> MySQL Database --> small PHP webpage --> 800xA Web View Aspect
Works like a charm! I can provide details if you like.
- Increasing the capacity of some alarm category helps, I have weak memories about having troubles to finally apply changed settings.
- The history length was still not satisfying with moderate increased category capacity, we tried higher values
- Higher values failed due disk space limitations. The alarm files become crazy huge! I had to enable disk compression. xxxx ABB default disk partition scheme!
- The alarm system become very slow (not only due the disk compression, I assume)
- We changed everything back to the original values and developed a different solution:
External event storage using the 800xA Alarm Printer
800xA Alarm Printer --> Windows virtual line text printer --> TCP connection --> Event-Line-to-SQL-Program (my creation) --> MySQL Database --> small PHP webpage --> 800xA Web View Aspect
Works like a charm! I can provide details if you like.
Answered 6 months ago
2
I feel the thread is not converging enough to what need to be done...
In system 800xA, alarm and events are two entirely separate functions. For every OPC condition event, simple event or tracking event received by the array of Event Collectors and forwarded to the Alarm Manager, a copy will be sent to Event Storage.
Alarms "evaporate" from the Alarm Manager RAM memory as they return to normal and become acknowledged.
Events "wraps" from the Event Storage disk based storage as the the files become saturated (each category store 10K events per default).
- An alarm list may never* display an event.
- An event list may never display an alarm.
- Never look for alarm history in alarm lists, use event lists.
*) I am not including the "Show events" function that basically turns an alarm list into an equally filtered event list.
To see more "event history", increase the category setting on the Event Storage service.
Do NOT extend the main storage in the Alarm Manager service, keep it at 10K. Do not enable "Make new alarm each time a condition gets active". The Alarm Manager default storage setting is 10K FIFO shared across all categories; this is not good as it may prematurely expire important process related categories if there is noise from others. Therefore, it is recommended to move "noisy" system event categories from the main storage into separate and smaller "storage bins". The capacity will slightly go beyond 10K by doing so, stay below 20K.
Below, the Process Condition Event (process alarm) category of AC 800M after upsizing to 50K in Event Storage.
In system 800xA, alarm and events are two entirely separate functions. For every OPC condition event, simple event or tracking event received by the array of Event Collectors and forwarded to the Alarm Manager, a copy will be sent to Event Storage.
Alarms "evaporate" from the Alarm Manager RAM memory as they return to normal and become acknowledged.
Events "wraps" from the Event Storage disk based storage as the the files become saturated (each category store 10K events per default).
- An alarm list may never* display an event.
- An event list may never display an alarm.
- Never look for alarm history in alarm lists, use event lists.
*) I am not including the "Show events" function that basically turns an alarm list into an equally filtered event list.
To see more "event history", increase the category setting on the Event Storage service.
Do NOT extend the main storage in the Alarm Manager service, keep it at 10K. Do not enable "Make new alarm each time a condition gets active". The Alarm Manager default storage setting is 10K FIFO shared across all categories; this is not good as it may prematurely expire important process related categories if there is noise from others. Therefore, it is recommended to move "noisy" system event categories from the main storage into separate and smaller "storage bins". The capacity will slightly go beyond 10K by doing so, stay below 20K.
Below, the Process Condition Event (process alarm) category of AC 800M after upsizing to 50K in Event Storage.
Add new comment