Re: [foxboro] [I] Re: FBM232 OPC to iFIX's "native" OPC server

Re: If possible could you clarify or direct to any standards/info please
how to make sense of data types? For example, with our DELTAV OPC server
then 2 of 2 (we only built 2 discrete so far to Foxboro) then what is a
DeltaV"Boolean" (an on/off pushbutton and output to valve) had to be
added as a RIN.  In one of those 2 examples the DeltaV actually showed
the datatype as floating point.

I'm sorry Sheri, but I don't understand your question. 

It is true that the data type of the DCI block (RIN, ROUT, BIN, BOUT,
etc.) must match the data type of the variable from the OPC DA Server.

A given value may be represented by an OPC DA Server using any legal
data type that makes sense, e.g., an implementation might well implement
a Boolean as a floating point value though I've never seen it.

You can use any number of OPC DA Clients to test what your server is
doing. Matrikon has a free one that you can download.

I don't know if this helps or not.


Re: When is the Foxboro OPC Server required (ie, outside of historian).
You are saying that the FBM 232 doesn't need to have a Foxboro OPC
Server to "write out" data?

All OPC DA Clients can send data and read data.

All OPC DA Servers can send data and receive data.

However, OPC DA Clients are optimized to read values from Servers and
Servers are optimized to send such data. The write capability of a
client is intended to support low volumes of data, e.g., operator
setpoints.

An OPC DA Server is best used to "serve up" large volumes of data, e.g.,
to feed a historian.



Regards,
 
Alex Johnson
Invensys Process Systems
10900 Equity Drive
Houston, TX 77041
713 329 8472 (desk)
713 329 1600 (operator)
713 329 1944 (SSC Fax)
713 329 1700 (Central Fax)
alex.johnson@xxxxxxxxxxxxxxxx

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Liptock, Sheri A
Sent: Friday, November 07, 2008 4:06 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] [I] Re: FBM232 OPC to iFIX's "native" OPC server

Thank you for your info.  Yes your assumption is correct that we will
use the ALMSTA parameter, so that will work in an OPC DA server.
Followup questions please:

1.  After you confirmed that FBM232 works to read/write to "any" OPC DA
server, then I loaded FoxOPCDiagnostic tool on the (local) iFIX pc and
OPCDiagnosticTool browsed/found the iFIX OPC DA server and CLSID (no OPC
tags built yet).  So thank you for giving me the confidence to try that.
Although ultimately the FBM232 has to connect via DCOM to iFIX.  

2.  If possible could you clarify or direct to any standards/info please
how to make sense of data types?    For example, with our DELTAV OPC
server then 2 of 2 (we only built 2 discrete so far to Foxboro) then
what is a DeltaV"Boolean" (an on/off pushbutton and output to valve) had
to be added as a RIN.  In one of those 2 examples the DeltaV actually
showed the datatype as floating point.   

3.  When is the Foxboro OPC Server required (ie, outside of historian).
You are saying that the FBM 232 doesn't need to have a Foxboro OPC
Server to "write out" data?

Thank you very much.  

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Johnson, Alex P (IPS)
Sent: Wednesday, November 05, 2008 6:39 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [I] Re: [foxboro] FBM232 OPC to iFIX's "native" OPC server

Sheri,

The FDSI OPC DA Client FBM can drive real-time values with their
associated OPC status bits and time tag into any OPC DA Server. 

Since the data that can be sent out the FDSI OPC DA Client FBM comes
from a block - ROUT or BOUT for example - in the CP owning the FBM, you
will need to arrange for it to be transferred using the peer-to-peer
capabilities of the CP if the values do not originate in the CP.

However, I'd like to pursue something that you wrote:

   I need to send Foxboro "alarms" to an iFIX PC.

By this, I assume that you want to send our Boolean alarm indicators as
opposed to our actual alarm messages. 

Is this assumption correct? 

If this assumption is correct, you might find using the ALMSTA parameter
connected to a PAKOUT block as the most efficient approach since it
includes all of the alarm status bits for a given block.

If this assumption is incorrect and you really need the alarm messages,
we will have to do something different since the FDSI OPC DA Client FBM
does not support this type of service.



Regards,
 
Alex Johnson
Invensys Process Systems
10900 Equity Drive
Houston, TX 77041
713 329 8472 (desk)
713 329 1600 (operator)
713 329 1944 (SSC Fax)
713 329 1700 (Central Fax)
alex.johnson@xxxxxxxxxxxxxxxx

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Liptock, Sheri A
Sent: Wednesday, November 05, 2008 3:35 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] FBM232 OPC to iFIX's "native" OPC server

Does anyone know if the OPC (client) FBM works to send info to
intellution's (GE Fanuc) iFIX 3.0  server?    I need to send Foxboro
"alarms" to an iFIX PC.     Can anyone explain how an OPC server is
embedded in iFIX HMI?

Sheri Liptock
Eastman Chemical Jefferson Site
West Elizabeth, PA 15088
412.384.2520.x2242 or sliptock@xxxxxxxxxxx

 
 
_______________________________________________________________________
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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 


* Confidentiality Notice:
This e-mail and any associated files are intended solely for the
individual or entity to whom they are addressed. Please do not copy it
or use it for any purposes, or disclose its contents to any other
person. Further, this e-mail and any associated files may be
confidential and further may be legally privileged. This email is from
the Invensys Process Systems business unit of Invensys plc which is a
company registered in England and Wales with its registered office at
Portland House, Bressenden Place, London, SW1E 5BF (Registered number
166023).  For a list of European legal entities within the Invensys
Process Systems business group, please click here
http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_i
d=77.

If you have received this e-mail in error, you are on notice of its
status. Please notify us immediately by reply e-mail and then delete
this message from your system. Thank you for your co-operation. You may
contact our Helpdesk on +44 (0)20 7821 3859 / 2105 or email
inet.hqhelpdesk@xxxxxxxxxxxxx This e-mail and any attachments thereto
may be subject to the terms of any agreements between Invensys (and/or
its subsidiaries and affiliates) and the recipient (and/or its
subsidiaries and affiliates).


 
 
_______________________________________________________________________
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:             http://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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 


* Confidentiality Notice:
This e-mail and any associated files are intended solely for the individual or 
entity to whom they are addressed. Please do not copy it or use it for any 
purposes, or disclose its contents to any other person. Further, this e-mail 
and any associated files may be confidential and further may be legally 
privileged. This email is from the Invensys Process Systems business unit of 
Invensys plc which is a company registered in England and Wales with its 
registered office at Portland House, Bressenden Place, London, SW1E 5BF 
(Registered number 166023).  For a list of European legal entities within the 
Invensys Process Systems business group, please click here 
http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77.

If you have received this e-mail in error, you are on notice of its status. 
Please notify us immediately by reply e-mail and then delete this message from 
your system. Thank you for your co-operation. You may contact our Helpdesk on 
+44 (0)20 7821 3859 / 2105 or email inet.hqhelpdesk@xxxxxxxxxxxxx This e-mail 
and any attachments thereto may be subject to the terms of any agreements 
between Invensys (and/or its subsidiaries and affiliates) and the recipient 
(and/or its subsidiaries and affiliates).


 
 
_______________________________________________________________________
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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 

Other related posts: