Re: [foxboro] Re[2]: Alarms to Remote Stations

You would need one AM for each remote workstation on which you want to view
the alarms simultaneously since they are controlled by the same host.  For
example:

*       If you only need to view the alarms at one workstation, one AM is
sufficient with a bunch of filters.
*       If you have five workstations and want to view the alarms on all
workstations at the same time you would need five AMs.
*       If you have one workstation but want to be able to view alarms using
two different filters (at the same time) you would need two AMs.

Regards,
Kathy

-----Original Message-----
From: Chris Browder [mailto:chris_browder@xxxxxxxxx]
Sent: Wednesday, December 05, 2001 3:10 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Re[2]: Alarms to Remote Stations 



Hmm... I don't think you need two alarm managers. One
that "gets" some and one that "gets" all.

Sations (ie WPs and AWs) _get_ alarms.  Alarm managers
_view_ the alarms.  You just need to change from one
filter to another to see different alarms. Or remove
the filter to see all.  A combination of menus/buttons
for environments for alarm managers can prevent a user
from choosing a filter or see different things.

am I wrong?

--- Daren Bishop <dbisho@xxxxxxxxxxxx> wrote:
> 
>      Remote Stations are clarified as Linux boxes
> doing X-draws driven by a 
>      WP51 and an AW51 on the same node. Mirror DM's
> are assigned on each 51 
>      station for reduncancy.
>      
>      Your explanation, in addition to Alex's
> response, seem to be the way I 
>      need to go.
>      
>      I will need to flash the Alarm button on
> individual stations based on 
>      the match list too.
>      
>      I need to have a "hidden" alarm manager on each
> WP/AW that gets all 
>      alarms, and one that has "assigned alarms" that
> pertain to particular 
>      process units local to each box and remote
> alarm managers also 
>      "assigned" by process unit. 
>      
>      I think this has steered me in the right
> direction! 
>      
>      Thanks!!!
>      
>      Daren
>      
>      
>      
>      
> 
> 
> ______________________________ Reply Separator
> _________________________________
> Subject: Re: [foxboro] Alarms to Remote Stations 
> Author:  <foxboro@xxxxxxxxxxxxx> at INTERNET-MAIL
> Date:    12/5/01 1:50 PM
> 
> 
>      
> Mr. Bishop,
>      
> Pls clarify  "Remote Draw Stations"
>      
> Is this:  
> - X terminals driven by 51 series station ? 
> - Standard 51 or 70 WP ?
> - Terminals off the AW70 terminal server thing ?
>      
> (I bet you allready know most of this, but ...)
> As a general rule, alarms are routed to Printers,
> Workstations, 
> and Historians either using the Group/Device
> specifications in the 
> compound parameters, or those in the CP's Station
> block.
>      
> Dispensing with the Historians and Printers,...
>      
> The Workstation keeps a single alarm queue which
> serves all 
> the alarm managers that it runs.  In addition, there
> is no 
> way to filter what turns on the the Alarm light on
> Display 
> Manager or Foxview, and the New Alarm light on the
> Alarm Manager 
> page.
>      
> You can filter which alarms show up on a specific
> Alarm Manager
> by using the alarm matching function.  An alarm
> match specification 
> can be saved in a file on disk, and by setting the
> ALMP variable
> in 'init.user' you can invoke the match when the
> Alarm or Proc 
> button is hit in DM or FoxView. This can be used to
> present the 
> operator with 'his' subset of the alarms, but the
> Workstation 
> still has them all.
>      
> The reason you want to separate out alarms by alarm
> manager is 
> also important.  If it is too avoid alarm queue
> overflows, there 
> is a variable which can be set in the 'init.user'
> file to make 
> the queue larger.  If it is for alarm horn sounding,
> or to affect 
> the Alarm or Proc button lite, things get a bit more
> complex.  
>      
>      
> W C Ricker
> FeedForward, Inc.
>      
>      
>      
>      
>      
>
___________________________________________________________________
> 
> This list is neither sponsored nor endorsed by The
> Foxboro Company. 
> Use the information obtained here at your own risk.
> For disclaimer, 
> see
>
http://www.thecassandraproject.org/disclaimer.html#maillist
>      
> list info:   http://www.freelists.org/list/foxboro
> subscribe:  
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=join 
> unsubscribe:
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>      
>      
> 
>  
>  
>
___________________________________________________________________
> This list is neither sponsored nor endorsed by The
> Foxboro Company.
> Use the information obtained here at your own risk.
> For disclaimer,
> see
>
http://www.thecassandraproject.org/disclaimer.html#maillist
> 
> list info:   http://www.freelists.org/list/foxboro
> subscribe:  
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> unsubscribe:
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
> 


__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com
 
 
___________________________________________________________________
This list is neither sponsored nor endorsed by The Foxboro Company.
Use the information obtained here at your own risk. For disclaimer,
see http://www.thecassandraproject.org/disclaimer.html#maillist

list info:   http://www.freelists.org/list/foxboro
subscribe:   mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 
 
___________________________________________________________________
This list is neither sponsored nor endorsed by The Foxboro Company.
Use the information obtained here at your own risk. For disclaimer,
see http://www.thecassandraproject.org/disclaimer.html#maillist

list info:   http://www.freelists.org/list/foxboro
subscribe:   mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: