Re: [foxboro] Alarm envrionments

This may not be the solution for the original question, but I do want to 
comment on the script method of switching alarm destinations.  We have 
switched the alarm groups in each block using a script, as is mentioned 
below, and it works OK but is cumbersome to set up and maintain. 

However, we have discovered that a much easier method is to have all of 
the alarm groups of the blocks of interest set to one of the station 
groups, say group 4, and then use a script (omset or omsetimp) to simply 
change the hex parameter for that group (i.e. CP0001_STA:STATION.GR4) to 
include the destinations you want at the time.  Also, as long as any new 
alarm blocks are given group 4, they are automatically included in the 
switching. 

As mentioned elsewhere, we also use the script to set a block parameter 
which is used to display to the operator that the alarms are redirected.

Rich Bakke
Longview Fibre Co.


Kevin FitzGerrell wrote:

>One other approach that hasn't been mentioned yet is to actually redirect the 
>alarms -- using a setpars (fast) or omsetimp (slower) script, or a sequence 
>block (very slow) to change the alarm groups of the blocks with alarms 
>configured in Unit 1.  If this approach is used, consider having the backup 
>group direct alarms to both Unit 1 and Unit 2 -- this preserves CAD and AHD 
>for Unit 1 when alarms are redirected, ie Group 4 -> Unit 1, Group 8 -> Units 
>1 & 2.
>
>Advantages:
>* Alarms are redirected from Unit 1 to Unit 2 even if the Unit 1 workstation 
>is down.
>* Alarms from Unit 1 do not affect Unit 2's CAD and AHD when not redirected.
>* Can be done from either Unit 1 or Unit 2 workstation.
>
>Disadvantages:
>* Transition period issues, ie - if an alarm is received on one workstation, 
>but the return to normal is received on the other unit, gcio LED may not show 
>appropriately on one workstation, and alarm may have to be cleared from one 
>CAD, rather than just acknowledged.
>* Because alarm groups are settable, if an upload is done while alarms are re-
>directed, the alarm groups in the station work files will be changed.
>* Script or program needs to be updated when new alarms are configured in Unit 
>1.
>
>Regards,
>
>Kevin FitzGerrell
>Senior Control Engineer
>Kinleith Pulp & Paper
>Carter Holt Harvey Ltd.
>+64 27 460 9994
>
>Quoting stan <stanb@xxxxxxxxx>:
>
>  
>
>>We have a single node that serves as the control system for 2 "units".
>>At
>>present we have the alarms for, say, unit 1, directed to on WP, and the
>>alarms for say, unit 2, directed to 2 other WP's. 
>>
>>I'd like for the unit 2 operator to be able to "back up" the unit 1
>>operator
>>on handling alarms, Unit1 has an audible alarm that the unit 2 operator
>>can
>>hear.
>>
>>I was poking around in the alarm manager screens, and I found under
>>Display
>>-> Operations, that I can bring up a new window, that has "environments"
>>as
>>one of it's choices. Is there some way I can configure this so that the
>>WP's for unit2 can "switch environments" and see the unit1 alarms?
>>
>>
>>-- 
>>U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite
>>Vietcong Terror 
>>- New York Times 9/3/1967
>>    
>>
>  
>
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: