Re: [foxboro] AIM Historian BAD POINTS
- From: "Pat Martens" <fox@xxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Thu, 19 Jul 2007 19:45:29 +0200
Not the most simple solution but it works:
We read the aim historian RTP configuration into an MS-access database by
means of the AIM ODBC driver (of which, if I am correct but I could be
wrong, there is alway 1 license available).
You need a PC with the aim* tools installed which has access to your
historian AW(s) and you have to set-up the ODBC in windows.
If you have this working, then importing the RTP definition (or any other
historian data) is easy.
Next, you create a list of all your CP blocks with an ICC list script (or
something equivalent) and import this into the same MS-access database.
Now you can build a 'non-related-items' query and you find all references in
the RTP definition file for which no C:B exists.
What's missing is the check on typing mistakes in the parameter name but as
most of our RTP points are added with automated tools, this is not a problem
in our case.
A bit complicated maybe but ones you have this set-up you have made the
first step of creating your own I/A documentation tool. The next thing is
you will want to have more I/A data available in your access database and
before you know it you spend all your free evenings with visual basic
programming.
Non existing RTP points is only one thing.
Incorrect C:B.P linking, incorrect display links, incorrect sequence
references, incorrect alarm.tab files, incorrect references in whatever
other file you can think, I/O allocations, FBM counts and type, etc, etc,
can all be traced ones you have this data available in access.
I'am slightly worried though that all may effort will render useless
whenever we decide to up-grade to Infusion, or whatever the name of the
product will be at that time.
For the time being I would not know how to keep our system 'in good shape'
without such a tool.
Regards,
Patrick Martens,
Total Raff. Ned. N.V.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Gillis, Dale
Sent: maandag 16 juli 2007 17:19
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] AIM Historian BAD POINTS
Hello List.
I use IA Ver 6.5.2 and run AIM 3.2.4 Historian. The older versions of
this AIM used to give you a list of BAD Points (ie points historized but
may not exist in your CP anymore) that may be in the Historian when it
started up....in some log file under /opt/aim/inst. It doesn't seem to
do this anymore with the newer version. Can anyone help me in finding a
tool that will do this or point me in the proper direction?
Dale Gillis
_______________________________________________________________________
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:
- » Re: [foxboro] AIM Historian BAD POINTS
