Re: [foxboro] Foxboro - ABB OPC tag issue
- From: "Airhart, Chad M." <Chad.Airhart@xxxxxxxxxxxxxxxxxx>
- To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 26 Mar 2013 13:44:10 -0500
We have the problem on our OPC interface to our Seimens GC's. We couldn't find
a work around and contacted Invensys and they could not help us either.
Chad M. Airhart
Principal Engineer
Instrument, Electrical and Control Systems
LyondellBasell Victoria Plant
Equistar Chemicals
P.O. Box 513
Old Bloomington Hwy
Victoria, TX 77901
Tel. +1 361.572.2568
Fax. +1 361.572.2541
Mobile: +1 361.935.3230
chad.airhart@xxxxxxxxxxxxxxxxxx
www.lyondellbasell.com
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of richard.harris@xxxxxxxxxxxxxx
Sent: Tuesday, March 26, 2013 1:25 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Foxboro - ABB OPC tag issue
Hi list,
We have a problem with a new OPC project, and I was wondering if anyone has
come across a similar problem (and hopefully solution!).
I'll briefly describe the installation first:
FCP270(FT)
FBM233(FT)
Pair of Foxboro switches
ABB servers (redundant).
Now the problem:
I have configured several test RIN and BIN blocks and these are reading Real
and Boolean OPC tags through successfully.
There is another type of tag used to show a GCC sample time (called
GCC1.STRM1.SampleTime).
I have tried unsuccessfully to connect to this type of tag using RIN, STRIN and
IIN blocks.
I am using aliases via the FDSI configurator to allow for upper/lower case
naming.
Checking the tag data type (using Matrikon OPC explorer), it is declared as
"canonical data type 7".
Looking on the web for this data type:
"It is represented as a 64-bit signed integer which represents the number of
100 nanosecond intervals since Jan 1, 1601"
Now according to the OPC client manual BO700BH : Table 3.6 data Conversions:
IIN Blocks only support 16 or 32 bit integers.
The footnote for the table states:
"64-bit signed and unsigned integers
and LBCD types are not supported."
So the question for the list is has anyone come across this and found a
workaround or solution for this data type mismatch?
Many thanks for any help!
Regards
Richard
Richard Harris,
Systems Engineer
* Dow Corning Ltd
Cardiff Road, Barry, South Wales CF63 2YL
* Voice: +44 (0)1446 723873
* Fax: +44 (0)1446 700874
* E-Mail: mailto:richard.harris@xxxxxxxxxxxxxx
_______________________________________________________________________
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
Information contained in this email is subject to the disclaimer found by
clicking on the following link: http://www.lyondellbasell.com/Footer/Disclaimer/
_______________________________________________________________________
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] Foxboro - ABB OPC tag issue - Airhart, Chad M.
