One comment. Fxbais "pushes" data into the blocks using "one-shot" calls. This is not very efficient and it is very slow if you have significant data to move. The better approach is to stage the date in OM variables local to the fxbais process (on the AW) since the "one-shot" is very fast in that case. These local OM variables should then be connected to the input parameter of the block. This makes a "read" connection from the AW to the CP and that is very fast and efficient. There are two types of "local" OM variables available to you: 1) Shared Variables 2) I/A Series Application Objects Shared Variables are free and can be created at boot-up using omcrt or ommcrt. The limitation of note is that the name is only 14 characters long and they do not have parameters. Application Objects like SVs reside in the AW's memory, but have a three part name. The advantage of this is that it is easy to create generic displays to view the data in the AOs. AOS is sold (Q0301JC). Shared Variables are included in the base software. I strongly recommend this approach if you have 100+ values to move into the CP. Regards, Alex Johnson Invensys Operations Management 10900 Equity Drive Houston, TX 77041 +1 713 329 8472 (desk) +1 713 329 1600 (operator) +1 713 329 1944 (SSC Fax) +1 713 329 1700 (Central Fax) alex.johnson@xxxxxxxxxxxx -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Liptock, Sheri A Sent: Monday, October 10, 2011 5:00 PM To: 'foxboro@xxxxxxxxxxxxx' Subject: Re: [foxboro] [I] Re: Wrting data from PI server to Foxboro IAS blocks, OPCInt <<==>> AIM OPC DA 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 *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/en/legal/default.aspx. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail reception@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: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave