Re: [foxboro] [I] Re: Wrting data from PI server to Foxboro IAS blocks, OPCInt <<==>> AIM OPC DA
- From: "Liptock, Sheri A" <sliptock@xxxxxxxxxxx>
- To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
- Date: Mon, 10 Oct 2011 12:00:03 -0400
Leo, I write to IA 2 ways from OPC.
1. Same as what Ted suggested: from OPC server, use OPC-DA PI interface to
send (write) the instruments' values to a PI server. Then PI server processes
(via ACE) these instruments' values. Then PI server sends (writes) newly
calculated values via fxbais (which uses foxapi) to IA blocks (Booleans,
string, etc).
2. From OPC server directly to IA RIN blocks using FDSI-FBM.
Since neither of these is exactly as you planned, do you want more info about
either? Please let me know.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Ted Jirik
Sent: Sunday, October 09, 2011 12:36 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [I] Re: [foxboro] Wrting data from PI server to Foxboro IAS blocks,
OPCInt <<==>> AIM OPC DA
Leo,
OSI has a very nice interface for IA called fxbais that does not use OPC. It
uses foxapi. It does read/write access to IA very reliably and eliminates all
the OPC configuration steps.
It is a lot easier to setup.
Ted Jirik
On Oct 9, 2011, at 3:25 AM, Leonardo Mercado wrote:
> Good morning all,
>
> I'll ask this question once again, I need to allow data write to foxboro IAS
> blocks.
> The aim is to exchange data from one PI server using PI-OPCInt to OPC DA
> Server on IAS Mesh network, then OPC DA server write those data to
> Foxboro IAS block
> Does any one have a typical configuration on all parties (PI, OPC DA
> configurator, aimapi.cfg, security issues like
> read/write permissions.......etc)
> Data flow from PI to OPC server is open, tested using apisnap utilities
>
>
> Thanks
>
> Leo
> Instrument Supevisor
>
>
>
> _______________________________________________________________________
> 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
_______________________________________________________________________
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:
