Re: [foxboro] FXBAIS vs PI OPC Interface
- From: "Johnson, Alex P (IPS)" <alex.johnson@xxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 24 Jun 2008 17:33:39 -0400
Load sharing between PI and AIM*Historian is possible. =
You need to configure AIM*API to share lists with FoxAPI. When this is
done, if the tag is in both AIM*Historian and PI and both packages are
on the same AW, the CP sees a single user.
Regards,
=
Alex Johnson
Invensys Process Systems
10900 Equity Drive
Houston, TX 77041
713 329 8472 (voice)
713 329 1600 (switchboard)
713 329 1944 (fax)
alex.johnson@xxxxxxxxxxxxxxxx
http://ips.invensys.com =
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Jack.Easley@xxxxxxxxxxxx
Sent: Tuesday, June 24, 2008 2:39 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FXBAIS vs PI OPC Interface
Yes, PI fxbais can be setup to be read-only. Sadly, in our case it is
not. So use of PI read-only from the MESH with a good Firewall is
relatively secure.
However, even if PI access is set up read-only, you should not forget
the matter of additional loading of your control system when PI tags are
added by the PI administrator. We experienced problems with this when at
Version 6.12 NODEBUS with loaded CP30/40s and Integrator 30s.
I don't think AIM is involved with the PI fxbais Interface, only FoxAPI.
Jack Easley
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Johnson, Alex P (IPS)
Sent: Tuesday, June 24, 2008 1:05 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FXBAIS vs PI OPC Interface
Re: Read-only and FoxAPI (and AIM*API for that matter)
It is possible to configure read-only access using FoxAPI. This
configuration is done in the /opt/fox/ais/bin/an_init.tcp file on the
machine running the netFoxAPI Server (an_server).
If this is set, it does not matter what PI is configured to do, the data
will not be written.
For AIM*API, the file is /opt/aim/bin/an_init.tcp.
Confidentiality Notice: This email message, including any attachments,
=3D0A=3D
contains or may contain confidential information intended only for the
=3D0A=3D
addressee. If you are not an intended recipient of this message, be =3D0A=
=3D
advised that any reading, dissemination, forwarding, printing,
copying=3D0A=3D
or other use of this message or its attachments is strictly prohibited.
If=3D
=3D0A=3D
you have received this message in error, please notify the sender =3D0A=3D
immediately by reply message and delete this email message and any=3D0A=3D
attachments from your system. =
=
=
_______________________________________________________________________
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=3Djoin
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=
* 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 legal=
ly privileged. This email is from the Invensys Process Systems business uni=
t of Invensys plc which is a company registered in England and Wales with i=
ts registered office at Portland House, Bressenden Place, London, SW1E 5BF =
(Registered number 166023). For a list of European legal entities within t=
he Invensys Process Systems business group, please click here http://www.in=
vensys.com/legal/default.asp?top_nav_id=3D77&nav_id=3D80&prev_id=3D77.
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 Help=
desk on +44 (0)20 7821 3859 / 2105 or email inet.hqhelpdesk@xxxxxxxxxxxxx T=
his e-mail and any attachments thereto may be subject to the terms of any a=
greements 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
- References:
- Re: [foxboro] FXBAIS vs PI OPC Interface
- From: Johnson, Alex P (IPS)
- Re: [foxboro] FXBAIS vs PI OPC Interface
- From: Jack.Easley
Other related posts:
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- Re: [foxboro] FXBAIS vs PI OPC Interface
- From: Johnson, Alex P (IPS)
- Re: [foxboro] FXBAIS vs PI OPC Interface
- From: Jack.Easley