Re: [foxboro] AIM* Alarm Retrieval

  • From: "Lowell, Timothy" <TLowell@xxxxxxxxxxx>
  • To: <foxboro@xxxxxxxxxxxxx>
  • Date: Wed, 3 Sep 2008 13:39:23 -0500

Jason,

This can be found in HH1000.  I'll post it here so it can show up in the
Cassandra list archives.

HH1000 deals with sysmon messages only, but you can adapt it for alarm
messages, which I have done below.

*****************************Start HH1000
Copy*****************************
1. Open a Command Prompt window and change to korn shell (d:, ncenv and
sh) or a 
VT100 window.
 
2. Change to the /opt/aim/bin directory.
        Example:
        $ cd /opt/aim/bin
 
3. Run apitst
        Example:
        $ apitst
 
4. From the Main Menu, select the "700 -(Menu 7) AIM*Historian" option.
 
        Example:
 
Foxboro AIM*API Test Program
 
-------------------------------------------------------------------
Menu (1)      AIM*API Test Program    Hostid = 64884966 System Type = 71
 
Test Program        Quick Tests            Sub Menus
-1 Exit          10-AIM*API Status   100 -(Menu 1)  Main Menu
 0-Repeat Last   11-Block Info       200 -(Menu 2)  Block Info
 1-Help          12-Objects          300 -(Menu 3)  Objects
 2-Menu On/Off   13-CDX              400 -(Menu 4)  CDX
 3-Echo On/Off   14-File             500 -(Menu 5)  File
 3-Echo On/Off   15-Historian        600 -(Menu 6)  Historian
 4-Save Settings 16-AIM*Historian    700 -(Menu 7)  AIM*Historian
 5-an_error      17-Counters         800 -(Menu 8)  Counters
                 18-Trouble Shooting 900 -(Menu 9)  Trouble Shooting
                 19-OM               1000-(Menu 10) OM Functions
                                     1100-(Menu 11) Old Functions
 
function[ 0]: 700
 
 
4. From Menu (7), select the "11-fh_FdbMsgQuery" option
 
-------------------------------------------------------------------
Menu (7)      Historian Access     Hostid = 64884966 System Type = 71
Test Program      Functions
-1 Main Menu      10-fh_FdbPutMsg       20-fh_RTPDef
 0-Repeat Last    11-fh_FdbMsgQuery     21-fh_RTPIndex
 1-Help           12-fh_FdbPutValue     22-fh_RTPName
 2-Menu On/Off    13-fh_FdbGetValues    23-fh_MsgNr
 3-Echo On/Off    14-fh_FdbReduction    24-fh_MsgName
 4-Save Settings  15-fh_FdbRedArray     25-fh_RTPControl
                  16-fh_FdbBlkInsert    26-fh_MsgControl
                                        27-fh_GroupControl
                                        28-fh_Cfg
function[ 0]: 11
 
Note: Step 3 and 4 can be executed at the same time if you type 711 from
the 
Main Menu.
 
5. Enter the information requested, the example below will give you an
idea what 
type of information you need to type.
 
Example:
 
Bulk output to file?   [ N]: y
Historian              [ hist01     ]: hist01
Output File            [ msg.txt]: alarms.txt
 
  Start time {04/17/02_06:14:13}=[1019024053]
    Date? 04/16/02
    Time? 12:00:00
  Start time {04/16/02_12:00:00}=[1018958400]
  Accept Date & Time [Y]y
 
 
  End time {04/17/02_08:15:14}=[1019031314]
    Enter "Now" for the current time!
    Date? now
  End time {04/17/02_08:15:51}=[1019031351]
  Accept Date & Time [Y]y
filter                        [ *]: *
ok to add?                    [  ]: y
 
6. APITST will provide the number of messages captures.
 
Historian  = hist01
Start Time = 04/16/02_12:00:00 (1018958400)
End Time   = 04/17/02_08:15:51 (1019031351)
Filter     = *
 Msg 1     iaalarm:alarmmesg                04/16/02_15:28:34  to
alarms.txt
 Msg 2     legacy:sysmonmsg               04/16/02_15:28:53  to
alarms.txt
 Msg 3     legacy:opraction               04/16/02_15:29:07  to
alarms.txt
 Msg 4     iaalarm:statemsg               04/16/02_15:43:07  to
alarms.txt

 4 messages printed into the alarms.txt file.
 
 
Note:
The alarms.txt file can be created in the /opt/aim/bin or
/opt/aim/inst/histname 
directory.  Where histname is the name of the instance 
 
7. Do more on the alarms.txt file.
        Example:
        $ more alarms.txt
 

****************************End HH1000
Copy*********************************

Using the "*" option for the filter gets you every message, including
process alarm messages, operator actions, and sysmon messages (assuming
you are recording these messages in AIM*).  You can try to filter
specific process alarms by using iaalarm:alarmmesg, iaalarm:statemsg,
iaalarm:alackmsg, and iaalarm:disablmsg.  There are more alarm tables,
but I don't have a listing of every single one handy.  Using "*" as the
filter makes sure you get everything.

Tim Lowell
Control Systems Engineer
Tesoro Petroleum Company
210-283-2929 (w)
210-253-0225 (c)
tlowell@xxxxxxxxxxx

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of SLADE Jason -NANTICOKE
Sent: Wednesday, September 03, 2008 12:51 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] AIM* Alarm Retrieval

Does anyone know how to retrieve alarm messages from the AIM* (v3.1)
alarm history archive files?  The AIM*API SPY tool doesn't get us to the
data we're looking for, which seems to be in the middle of the file.

Thanks,

Jason Slade
ONTARIO POWER GENERATION  
Nanticoke GS 
 
Control Technologist
Engineering / Control Systems


 
 
_______________________________________________________________________
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: