Re: [foxboro] AW: format in Alarm Manager

  • From: "Johnson, Alex (Foxboro)" <ajohnson@xxxxxxxxxxx>
  • To: foxboro@xxxxxxxxxxxxx
  • Date: Tue, 18 Feb 2003 14:33:55 -0500

Re: First question: We use the command SENDMSG(S) to MSGGR  (with S a 80
characters long string), in sequence logic. Those messages are displayed in
the Alarm Manager, however only 32 characters (default size) We would like
to see the "full" message in the Alarm History.

If the goal is to change the display in the Alarm Manager display, you can
use the DispAlarrmCfg to change some aspects of the display. To be honest,
I've never used it.

If the goal is to change the data in the Alarm History, it depends on your
historian.

If you have:
* The I/A Series Historian, a.k.a., the Data Historian or the Old Historian
- I think you are stuck. 
* FoxAMI - You should not have a problem because the message database holds
the full message.
* AIM*Historian (with AIM*Inform or AIM*AMI to view) - You should not have a
problem because the message database holds the full text. Moreover, you can
adjust the field sizes.


Re: Second question: it's not possible to acknowledge alarms within the
Alarm Manager which come from SENDMSG instructions

The reason for this is that they are not alarms. Notice that the .UNACK
parameter of the Sequence Block is not set when these messages are issued.

In fact, if you examine the message displayed on the screen it is an "INFO"
message not an alarm.



Re: Third question: how to disable the "Clear page " button in the Alarm
manager ?

Use DispAlarmCfg.


Hope this helps, but always remember free advice is worth what you paid for
it.



Regards,

Alex Johnson
Invensys Systems, Inc.
10707 Haddington
Houston, TX 77043
713.722.2859 (office)
713.722.2700 (switchboard)
713.932.0222 (fax)
ajohnson@xxxxxxxxxxx
For the latest information on ArchestrA, go to
www.invensys.com/divisions/Archestra.html

 -----Original Message-----
From:   Sascha Wildner [mailto:swildner@xxxxxxxxxx] 
Sent:   Tuesday, February 18, 2003 3:45 AM
To:     foxboro@xxxxxxxxxxxxx
Subject:        [foxboro] AW: format in Alarm Manager


> -----Ursprungliche Nachricht-----
> Von: foxboro-bounce@xxxxxxxxxxxxx
> [mailto:foxboro-bounce@xxxxxxxxxxxxx]Im Auftrag von jdesaeve@xxxxxxxxxxx
> Gesendet: Dienstag, 18. Februar 2003 10:29
> An: foxboro@xxxxxxxxxxxxx
> Betreff: [foxboro] format in Alarm Manager
>
> [First question]

I don't know.


> Second question: it's not possible to acknowledge alarms within the Alarm
> Manager which come from SENDMSG instructions

You're right.  It's not possible.

I usually build BLNALM blocks and use their alarm texts as my messages.  To
make them visible in the AM, I pulse the individual IN_x parameters from
the sequence to produce an unacknowledged alarm which will disappear when
acknowledged.


> Third question: how to disable the "Clear page " button in the Alarm
> manager ?

You do that in the DispAlarmCfg by protecting the button.  In your
environment scripts you have to do an "amcmd protect" to set the protection
class for the AM.


Regards,
Sascha

 
 
_______________________________________________________________________
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:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 
 
 
_______________________________________________________________________
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:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 

Other related posts: