Re: [foxboro] Sysmon messages from AIM*
- From: "Loiselle, Marc-Andre" <marcandre.loiselle@xxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Fri, 11 May 2007 14:07:07 -0400
From B0193YJ Revision B, p. 125
"An event database contains tables each of which represents an event
message type. The table name is <message group>:<message name>, where
message group and message name together define a message type. There are
14 preconfigured message tables corresponding to the I/A Series
Historian message types (for example, <legacy:path>),"
If you are able to get sample data in a VB (or VBA) program, then you
should be able to get sysmon messages. You have to use the "Event"
database instead of the "Sample" database and the table name is
"<instance name>.legacy:sysmonmsg". hist01.legacy:sysmonmsg for example.
If you want to purchase a VBA program that is already doing what you
want, sold with a scheduler, tested, used by many customers, please
contact me off-list to learn about Foxboro Canada Alarm Extractor (Alarm
Extractor also "extracts" operator actions and sysmon messages). =
Marc-Andre Loiselle
Invensys Systems Canada
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of David Johnson
Sent: 11 mai 2007 07:37
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Sysmon messages from AIM*
1) I remember AIM (before it got splatted by Invensys or SimSci) when =
it was a Biles & Associates product.
2) I am still in search of a good way to extract sysmon messages from =
AIM*. Currently we are working on ODBC calls from VB to get these, =
but unlike the sample data (which we have working), the message data =
doesn't appear to have a table name (that we can figure out), even =
though there are messages in the historian.
I hope someone has the answer to this, because the forehead is =
begining to ache.
Thanks,
David
=
=
_______________________________________________________________________
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=3Djoin
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=
Confidentiality Notice:
The information contained in this electronic message and any attachment(s) =
to this message are intended for the exclusive use of the recipient(s) and =
may contain confidential, privileged or proprietary information. If you are=
not the intended recipient, please notify the sender immediately, delete a=
ll copies of this message and any attachment(s). Any other use of the E-Mai=
l by you is prohibited.
_______________________________________________________________________
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:
