Text version of the page 
Text version of the page 
Open Source OPCpipe Open Source OPCpipe Open Source OPCpipe Open Source OPCpipe Open Source OPCpipe ® ® ® ® ® INAT INAT INAT INAT INAT Network-overlapping OPC communication Network-overlapping OPC communication Network-overlapping OPC communication Network-overlapping OPC communication Network-overlapping OPC communication e e e e e r r r r r a a a a a g g g g g a a a a a for Windows and non Windows systems for Windows and non Windows systems for Windows and non Windows systems for Windows and non Windows systems for Windows and non Windows systems n n n n n e e e e e v v v v v i i i i i n n n n n Automation technology is no
longer imaginable without OPC
communication since this technology
enables simple data exchange between
automation hardware on the one side
and applications on the other – via one
standardized interface.
However, OPC has one critical
disadvantage: It is currently based
on DCOM* – a technology defi ned
by Microsoft. This means that it is not
interoperable (i.e., is only available to
Windows users). Applications written
for non Windows computers cannot
use the OPC server to access process data at the automation
level (e.g., controllers).
Furthermore, the DCOM confi guration
is anything but simple and can turn
out to be very complicated. Timeouts
cannot be confi gured with DCOM
and communication across Firewalls
is also impossible.
DCOM is frequently disabled for
security reasons and OPC clients
on Windows computers then have
no other way of accessing the OPC
servers in the network. Automation technology is no
longer imaginable without OPC
communication since this technology
enables simple data exchange between
automation hardware on the one side
and applications on the other – via one
standardized interface.
However, OPC has one critical
disadvantage: It is currently based
on DCOM* – a technology defi ned
by Microsoft. This means that it is not
interoperable (i.e., is only available to
Windows users). Applications written
for non Windows computers cannot
use the OPC server to access process data at the automation
level (e.g., controllers).
Furthermore, the DCOM confi guration
is anything but simple and can turn
out to be very complicated. Timeouts
cannot be confi gured with DCOM
and communication across Firewalls
is also impossible.
DCOM is frequently disabled for
security reasons and OPC clients
on Windows computers then have
no other way of accessing the OPC
servers in the network. Automation technology is no
longer imaginable without OPC
communication since this technology
enables simple data exchange between
automation hardware on the one side
and applications on the other – via one
standardized interface.
However, OPC has one critical
disadvantage: It is currently based
on DCOM* – a technology defi ned
by Microsoft. This means that it is not
interoperable (i.e., is only available to
Windows users). Applications written
for non Windows computers cannot
use the OPC server to access process data at the automation
level (e.g., controllers).
Furthermore, the DCOM confi guration
is anything but simple and can turn
out to be very complicated. Timeouts
cannot be confi gured with DCOM
and communication across Firewalls
is also impossible.
DCOM is frequently disabled for
security reasons and OPC clients
on Windows computers then have
no other way of accessing the OPC
servers in the network. Automation technology is no
longer imaginable without OPC
communication since this technology
enables simple data exchange between
automation hardware on the one side
and applications on the other – via one
standardized interface.
However, OPC has one critical
disadvantage: It is currently based
on DCOM* – a technology defi ned
by Microsoft. This means that it is not
interoperable (i.e., is only available to
Windows users). Applications written
for non Windows computers cannot
use the OPC server to access process data at the automation
level (e.g., controllers).
Furthermore, the DCOM confi guration
is anything but simple and can turn
out to be very complicated. Timeouts
cannot be confi gured with DCOM
and communication across Firewalls
is also impossible.
DCOM is frequently disabled for
security reasons and OPC clients
on Windows computers then have
no other way of accessing the OPC
servers in the network. Automation technology is no
longer imaginable without OPC
communication since this technology
enables simple data exchange between
automation hardware on the one side
and applications on the other – via one
standardized interface.
However, OPC has one critical
disadvantage: It is currently based
on DCOM* – a technology defi ned
by Microsoft. This means that it is not
interoperable (i.e., is only available to
Windows users). Applications written
for non Windows computers cannot
use the OPC server to access process data at the automation
level (e.g., controllers).
Furthermore, the DCOM confi guration
is anything but simple and can turn
out to be very complicated. Timeouts
cannot be confi gured with DCOM
and communication across Firewalls
is also impossible.
DCOM is frequently disabled for
security reasons and OPC clients
on Windows computers then have
no other way of accessing the OPC
servers in the network. DCOM DCOM DCOM DCOM DCOM INAT INAT INAT INAT INAT e e e e e f f f f f f f f f f e e e e e c c c c c t t t t t s s s s s INAT INAT INAT INAT INAT INAT INAT INAT INAT INAT +++ All these problems are solved with OPCpipe! +++ +++ All these problems are solved with OPCpipe! +++ +++ All these problems are solved with OPCpipe! +++ +++ All these problems are solved with OPCpipe! +++ +++ All these problems are solved with OPCpipe! +++ O O O O O P P P P P C C C C C p p p p p i i i i i p p p p p e e e e e INAT INAT INAT INAT INAT Client PCOPC Server PC Client PCOPC Server PC Client PCOPC Server PC Client PCOPC Server PC Client PCOPC Server PC OPC Server OPC Server OPC Server OPC Server OPC Server PIPECLIENTClient PIPECLIENTClient PIPECLIENTClient PIPECLIENTClient PIPECLIENTClient TCP/IP TCP/IP TCP/IP TCP/IP TCP/IP PIPESERVER PIPESERVER PIPESERVER PIPESERVER PIPESERVER INAT INAT INAT INAT INAT O O O O O P P P P P C C C C C p p p p p i i i i i p p p p p e e e e e Functionality of the OPCpipe Functionality of the OPCpipe Functionality of the OPCpipe Functionality of the OPCpipe Functionality of the OPCpipe INAT INAT INAT INAT INAT OPCpipe images the functions of the
OPC interface, thus opening OPC with
all its advantages to a world which
was unable to utilize this technology
until now. Applications which run on
non Windows systems (Linux, Solaris,
etc.) can then use a normal TCP/IP
connection to access OPCpipe servers
which in turn establish the link to the
automation components. Each pipe
connection requires only one port which
means that the connections can also be
easily used across routers or fi rewalls.
This creates a wide variety of
possibilities: Implement the OPCpipe
in your client applications such as visualizations, databases, ERP, etc. and
make direct communication possible
with OPCpipe servers across networks
without DCOM and across Firewall
boundaries. Integrate the OPCpipe
functionality in your devices which
are based on non Windows operating
systems (e.g., Industrial plcs, industrial measuring devices, data loggers, etc.) and enable
direct access to the existing system
network. Communication with OPCpipe
servers is then possible via Ethernet
(e.g., for transmitting recipes or
receiving process values). OPCpipe images the functions of the
OPC interface, thus opening OPC with
all its advantages to a world which
was unable to utilize this technology
until now. Applications which run on
non Windows systems (Linux, Solaris,
etc.) can then use a normal TCP/IP
connection to access OPCpipe servers
which in turn establish the link to the
automation components. Each pipe
connection requires only one port which
means that the connections can also be
easily used across routers or fi rewalls.
This creates a wide variety of
possibilities: Implement the OPCpipe
in your client applications such as visualizations, databases, ERP, etc. and
make direct communication possible
with OPCpipe servers across networks
without DCOM and across Firewall
boundaries. Integrate the OPCpipe
functionality in your devices which
are based on non Windows operating
systems (e.g., PLCs, measuring
devices, data loggers, etc.) and enable
direct access to the existing system
network. Communication with OPCpipe
servers is then possible via Ethernet
(e.g., for transmitting recipes or
receiving process values). OPCpipe images the functions of the
OPC interface, thus opening OPC with
all its advantages to a world which
was unable to utilize this technology
until now. Applications which run on
non Windows systems (Linux, Solaris,
etc.) can then use a normal TCP/IP
connection to access OPCpipe servers
which in turn establish the link to the
automation components. Each pipe
connection requires only one port which
means that the connections can also be
easily used across routers or fi rewalls.
This creates a wide variety of
possibilities: Implement the OPCpipe
in your client applications such as visualizations, databases, ERP, etc. and
make direct communication possible
with OPCpipe servers across networks
without DCOM and across Firewall
boundaries. Integrate the OPCpipe
functionality in your devices which
are based on non Windows operating
systems (e.g., PLCs, measuring
devices, data loggers, etc.) and enable
direct access to the existing system
network. Communication with OPCpipe
servers is then possible via Ethernet
(e.g., for transmitting recipes or
receiving process values). OPCpipe images the functions of the
OPC interface, thus opening OPC with
all its advantages to a world which
was unable to utilize this technology
until now. Applications which run on
non Windows systems (Linux, Solaris,
etc.) can then use a normal TCP/IP
connection to access OPCpipe servers
which in turn establish the link to the
automation components. Each pipe
connection requires only one port which
means that the connections can also be
easily used across routers or fi rewalls.
This creates a wide variety of
possibilities: Implement the OPCpipe
in your client applications such as visualizations, databases, ERP, etc. and
make direct communication possible
with OPCpipe servers across networks
without DCOM and across Firewall
boundaries. Integrate the OPCpipe
functionality in your devices which
are based on non Windows operating
systems (e.g., PLCs, measuring
devices, data loggers, etc.) and enable
direct access to the existing system
network. Communication with OPCpipe
servers is then possible via Ethernet
(e.g., for transmitting recipes or
receiving process values). OPCpipe images the functions of the
OPC interface, thus opening OPC with
all its advantages to a world which
was unable to utilize this technology
until now. Applications which run on
non Windows systems (Linux, Solaris,
etc.) can then use a normal TCP/IP
connection to access OPCpipe servers
which in turn establish the link to the
automation components. Each pipe
connection requires only one port which
means that the connections can also be
easily used across routers or fi rewalls.
This creates a wide variety of
possibilities: Implement the OPCpipe
in your client applications such as visualizations, databases, ERP, etc. and
make direct communication possible
with OPCpipe servers across networks
without DCOM and across Firewall
boundaries. Integrate the OPCpipe
functionality in your devices which
are based on non Windows operating
systems (e.g., PLCs, measuring
devices, data loggers, etc.) and enable
direct access to the existing system
network. Communication with OPCpipe
servers is then possible via Ethernet
(e.g., for transmitting recipes or
receiving process values). INAT GmbH INAT GmbH INAT GmbH INAT GmbH INAT GmbH Ostendstr. 50 A90482 NurembergTel: +49 911 / 544 27 -0Fax: +49 911 / 544 27 27Email: info@inat.de Ostendstr. 50 A90482 NurembergTel: +49 911 / 544 27 -0Fax: +49 911 / 544 27 27Email: info@inat.de Ostendstr. 50 A90482 NurembergTel: +49 911 / 544 27 -0Fax: +49 911 / 544 27 27Email: info@inat.de Ostendstr. 50 A90482 NurembergTel: +49 911 / 544 27 -0Fax: +49 911 / 544 27 27Email: info@inat.de Ostendstr. 50 A90482 NurembergTel: +49 911 / 544 27 -0Fax: +49 911 / 544 27 27Email: info@inat.de INAT INAT INAT INAT INAT www.inat.de www.inat.de www.inat.de www.inat.de www.inat.de NAT NAT NAT NAT NAT I I I I I INAT INAT INAT INAT INAT – Open Source OPCpipe Page 1 –
|