Re: [foxboro] OSI tags for Foxboro I/A
- From: "Landry, Dwayne" <rdlandry@xxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Fri, 4 Mar 2005 12:47:50 -0600
We use a 3 digit area identification followed by a dash then a letter
to indicate the unit type followed by a 4 digit loop number. In some
cases when needed we may have to have the .spt .out etc... added to=20
the end of the tag if the standard .pnt or .meas is not enough.
Example
Area is 69A, Type is Flow and P&ID is 1234
69A-F1234
This one is a manual entered value.
69A-FM1234
Thanks,
Dwayne
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Clement, Mark
(KIDDMET)
Sent: Friday, March 04, 2005 12:38 PM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: Re: [foxboro] OSI tags for Foxboro I/A
Hi All,
What does everyone use as a tag naming convention ?
Just loops numbers or combination loop# and area # or something better ?
What works best from end user perspective ?
Regards
Mark
-----Original Message-----
From: WMagda@xxxxxxx [mailto:WMagda@xxxxxxx]
Sent: Friday, March 04, 2005 1:38 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] OSI tags for Foxboro I/A
I agree with Brad, PI-SMT is the way to go using Excel. We started =
using=20
PI last September. It took us a few tries, but once you have it figured =
out, it is easy to add/delete as needed.
Wally Magda
IE&C Spec Sr
Colorado Springs Utilities
PO Box 214
660 W. Monument Creek Rd
USAF Academy, CO 80840
719.668.9502 office
wmagda@xxxxxxx
brad.s.wilson=20
Sent by: foxboro-bounce@xxxxxxxxxxxxx
03/03/2005 10:33 AM
Please respond to
foxboro@xxxxxxxxxxxxx
To
foxboro@xxxxxxxxxxxxx
cc
Subject
Re: [foxboro] OSI tags for Foxboro I/A
I remember the problems I had first setting up PI to read Foxboro ... =
but
once you know it, it's soooo easy. PI-SMT is definitely the way to go =
...
it's an Excel add-in which provides a drop-down menu on the top Excel
command line. From that drop-down menu, you can either upload PI
configuration data to the spreadsheet, or download from the spreadsheet =
to
the PI configuration. The macros that are employed are exactly the same =
as
the script files you would run if you were doing the configuration in =
DOS,
so I think it should work for older versions of PI also.
The most difficult thing, as I remember, was getting the location tags
correct ... location1 is an address that points to the source (in our =
case
101 is our AW51, when I get my other AW hooked up, that will be 102).
location2 is the collection group on the DCS (this was the most =
difficult
thing for me to understand, but I'm set up with 2 groups per CP - one =
for
analog points, one for digital points), location3 works with the type of
data (we have 3 is 32-bit floating, 5 is digital). This is explained
pretty well in the PI manuals, but those CP collection groups really had =
me
going for a while.
The pointsource parameter differentiates the type of source device (in =
our
case, F=3DFoxboro, D=3DYokagawa, C=3Dcalculated, A=3DAllen-Bradley, =
etc).
The exdesc parameter holds the DCS C:B.P reference
Using discrete inputs requires defining Digital Sets in PI which hold =
all
the potential values that the input may be. For example, you might have =
a
Digital Set called VALVESTATESET which contains the values Open, Closed,
Opening, Closing, Mismatch ... these would correspond to the various=20
values
that a GDEV.STAIND might return. That way, rather than seeing the =
STAIND
integer values in your PI archive, you'd see the text values.
Everything else I think is fairly straightforward.
Brad Wilson
ExxonMobil Chemical Co
Edison Synthetics Plant
732-321-6115
732-321-6177 fax
Brad.S.Wilson@xxxxxxxxxxxxxx
=20
=20
_______________________________________________________________________
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
=20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
=20
=20
_______________________________________________________________________
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
=20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
The Noranda/Falconbridge Anti-Virus System has scanned this
message/attachment(s) for viruses.
=20
=20
_______________________________________________________________________
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
=20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
_______________________________________________________________________
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:
