Documentation of alarm
my customer wants a documentation of all possible alarms of my Freelance-System.
He wants a list of the alarm an the possible reason for the alarm.
Maybe we have an MANA and want to detect an HIGH of pressure
Name of Alarm ; Alarm ; Value
PI10_MANA ; HIGH ; 3.0 bar
Is it possible to create this kind of list or how can I extract these information out of CBF.
Thanks for help
Voted best answer
There is no straightforward way to do this. You may still try, but this will require some engineering effort.
One way to do this is extracting this information from .csv export file. If You never done it and the project is big this can take some time and effort, so I generally don't recommend it. The other way is to export your alarms from OPC server (if Your system has one). This can be really fast. Synchronize CBF with Your own OPC server (in configuration mode choose 'System' menu, then 'OPC item list' and 'Synchronize'). Then select all alarms from right side of the window and right click them. From menu choose 'Export'.
Save export file and then either open it with notepad or even change the format to .csv and open it straight up in excel. Check, correct, delete any info You don't need, add info You do need and You should end up with a ready list/document. If You can use Your OPC server it should take less then 10 minutes.
There can be a problem with values of alarm limits. As You probably know they can be set as parameters or as inputs to function block. In the second case there is no way to know what's the current limit value. BUT if they are set as static parameters You can download them easily. Go online (commissioning mode), choose any Controller in Project Tree and then 'Parameters' from 'Load' menu. In the search menu select all parameters with name 'Gw*' (the asterix sign '*' is for 'any character'). The Gw* is a standard name for a parameter, that holds limit value. You may export this list with 'Export' button. Remember to select correct parameters in the list!
Save the export file, open with notepad and copy needed values to Your documentation. This part may take some additional time because of matching the limit value to the alarm in Your document. Then repeat it for every controller...
Well, as I said, it's not a straightforward way to do this, but it works and is still better then doing it all manually (or at least I think it is...)
Hope it helps,
I think customer is looking for logs(process alarm and event log) and you can get that printed on printer. you can do so by using SSLN or SSL1, but I suggest go through logs information and decide which logs serves your need. information about logs you can find in online help or in manual '3BDD012518 Engineering - Operator Station Configuration'. In same document you can find information about how to get it printed.
Under DigiVis resource in configuration mode try to insert next level and you will get option to insert a logs, from there switch to online help and get started....
Thanks for answer.
But my customer don't these logs.
He wants it for documentation, not the logs in DigiVis. He wants the possible alarms of the system. If he get an call of the operator because an alarm is on the system, he want to look in the list an tell him what is the reason for this alarm.