Re: [foxboro] AIM OPC Server
- From: "Corey R Clingo" <clingoc@xxxxxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Mon, 7 Mar 2005 15:54:44 -0500
This kind of thing is why I really would like a more open, OS- and
application-independent, closer-to-the-wire protocol (say, something more
akin to Ethernet/IP, to provide one example) to supercede OPC. I'm no OPC
expert (I dabble in it just enough to get it working), but I fail to
understand why one needs a DCOM and RPC infrastructure just to get data
from a control system when a simple TCP socket will do. And anyone who
has ever tried to make Windows boxen work through firewalls knows how
a-cough-crappy-cough-dept Microsoft is at designing network protocols
(LANMAN, Netmeeting...).
Not to mention the issue of being at Micro$oft's mercy. I read recently
some comments from a member of the OPC Foundation. He saif that .NET is
not really fast enough to do real-time data access, based on some
experiments they've done (OPC-XML I think they call it), and is hoping
that gigabit Ethernet and "faster processors" (what? 8-way? Multi-core?
"Cell"?) mitigate the problem. He also stated a desire to move OPC in a
more platform-independent direction. Hmmm....
Corey Clingo
BASF Corp.
"Ken Heywood" <kheywood@xxxxxxxxx>
Sent by: foxboro-bounce@xxxxxxxxxxxxx
03/03/2005 10:13 AM
Please respond to foxboro
To: foxboro
cc:
Subject: Re: [foxboro] AIM OPC Server
I'm always game for free advice. Application tunneling always makes life =
easier. But, it's kind of perverse when you have many workstations that =
expect to use the benefits of named OPC object access sourced from all =
kinds of devices, and you need to load the client apps for all the =
devices on every workstation. It's akin to telling Internet users that =
they can display any webpage as long as they have ActiveX loaded.
Barring any DCOM issues, 3 or 4 NIC cards shouldn't present a problem =
... I think. No?
* K
-----Original Message-----
From: Johnson, Alex (Foxboro) [mailto:ajohnson@xxxxxxxxxxx]=20
Sent: Wednesday, March 02, 2005 2:02 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] AIM OPC Server
Free advice?
Put the AIM*OPC DA Server on the client machines and use NetAIM*API to
connect to the source AW (AW70 or AW51). This is equivalent to =
Matrikon's
"OPC Tunnelling".
Why do it?
Easy - the setup is much simpler - no DCOM.
Worth the time and money, I promise.
Regards,
=20
Alex Johnson
Invensys Process Systems
Invensys Systems, Inc.
10707 Haddington
Houston, TX 77043
713.722.2859 (voice)
713.722.2700 (switchboard)
713.932.0222 (fax)
ajohnson@xxxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] =
On
Behalf Of Ken Heywood
Sent: Wednesday, March 02, 2005 12:26 PM
To: Foxboro Freelist (E-mail)
Subject: [foxboro] AIM OPC Server
Content-Type: text/plain;
charset=3D"iso-8859-1"
Content-Transfer-Encoding: quoted-printable
=3D20
I am planning an AIM OPC Server to serve data to two separate networks. =
=3D
The box will have 3 NIC cards; 1 for I/A, and one each fro each IT =3D
network. Are there any special AIM restrictions? Network addressing or =
=3D
network connection issues? Has anybody done this? Thanks.
=3D20
* K
=3D20
-- No attachments (even text) are allowed --
-- Type: image/gif
-- File: image001.gif
-- Desc: image001.gif
=20
=20
_______________________________________________________________________
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
=20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
=20
=20
_______________________________________________________________________
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
=20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
_______________________________________________________________________
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:
