Re: [foxboro] PI connection type
- From: <G.Macdonald@xxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 24 Mar 2010 08:20:54 -0600
We recently went through the same issue (unix to windows AW). We decided to
stick with the PIAPI instead of the newer OPC interface option. We had no
issues with the upgrade. We have the PIAPI running on 5 separate nodes with a
mix of windows XP and Server 2003. We too used the "go script" option to start
the interface.
Currently we are trying to get Writes to work from PI to the foxboro and can't
seem to get it to work. When we add the "-write" flag to fxbais file, the
interface appears to start up correctly according to the pipc.log, but all the
points show up flat-lined in PI. Anyone have any ideas? We are at 4.3.2
FoxAPI & 8.4.2.
Thanks,
Grant
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Lowell, Timothy
Sent: March 24, 2010 7:39 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] PI connection type
Stan,
I've never used the OPC connection from I/A to PI, but I have experience with
using the Windows XP PI interface that uses FoxAPI (fxbais).
I believe the latest version of FoxAPI is 4.3.2, and that seems to work OK with
the Windows XP PI fxbais interface. We had a problem where v.4.3.2 broke the
DMC Bridge software, but Invensys has issued a quick fix for this. I believe
any version up to and including v4.3.1 had a problem on the Windows XP platform
writing points from PI back to I/A, but a quick fix was also issued for that.
There was also a quick fix issued that allowed the fxbais program to run as a
service in XP or Server 2003, but we have never gotten that to work. Even
after we applied the quick fix, we still got the same error when we tried to
start fxbais as a service. We put a "go script" for fxbais in the /usr/fox/bin
directory to start it up, which is the traditional way to do it in Unix. This
works great and there is no pressing need to change it.
Apparently, OSI has a replacement for the fxbais program that still uses
FoxAPI, but can be started and managed using the OSI Interface toolkit. One of
our sites tried this, and we weren't able to write data from PI back to I/A, so
we shut it down and went back to the old fxbais method. They are attempting to
start another small PI interface this week for an environmental project that
doesn't require any writes from PI to I/A, and they will be using this new OSI
Interface toolkit method. I'll let you know how it goes.
Tim Lowell
Tesoro Refining and Marketing Company
19100 Ridgewood Parkway
San Antonio, TX 78259
210-626-4929 (w)
210-253-0225 (c)
timothy.lowell@xxxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of stan
Sent: Wednesday, March 24, 2010 8:18 AM
To: Foxboro List
Subject: [foxboro] PI connection type
WE are preparing to design our first Windows based system, that will be
providing data to PI. We have many working instances using UNIX based
machines. These machines all connect to Pi using the FoxAPI (I think I got
the terminology right there).
According to our Pi expert, in windows, we can continue to use this
technology, or got to an OPC connections.
I am soliciting peoples experience using these two techniques. Any feedback
on this will be useful.
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
_______________________________________________________________________
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:
