336 / 413
6/66
Functions
3
Software
3
OPC data server software
OPC Factory Server
Functions
Development of client applications
OFS software has 4 types of interface:
b
OLE Automation interface (OPC-DA)
Particularly suitable for end users, this enables the development of OPC client
applications in Visual Basic, in Visual Basic for Excel, and in C++.
b
OLE Custom interface (OPC-DA)
Used primarily by suppliers of automated control system or industrial IT products,
this interface enables the development of applications in C++ in order to access the
OFS software OPC server. It is aimed at software development experts in particular,
so that they can integrate the client application into their standard products. This is
the interface with the highest performance, in terms of access time, to data stored in
the OPC server. It requires extensive knowledge of C++ programming to set up.
b
OPC .NET API wrapper interface
The .NET Microsoft compatibility of the OFS data server gives an OPC .NET client
standard access to items on the OFS server via an Intranet network, thus ensuring
greater interoperability with standard .NET environments.
Note:
In this case, communication between the OPC .NET client and the OFS server is conducted
through the DCOM layer (or COM layer in a local configuration) via the OPC-DA protocol.
b
OPC XML-DA interface
(1)
The OPC XML-DA V1.0 specifications are designed to overcome the limitations of
the OPC-DA specification and COM/DCOM by providing:
v
An interface for Windows and non-Windows client applications
v
Remote access via the Internet through firewalls (beyond the Intranet perimeter)
The OPC XML-DA specification is based on Web Services standards such as SOAP,
XML, WSDL. ASOAP client can access data on the OFS server via Intranet or Internet
using the SOAP protocol in conformity with the OPC XML-DAV1.01 specification of
the OPC Foundation.
(1)
Only available with the Large version of OPC Factory Server V3.3.
Presentation:
pages 6/62
Setup:
page 6/65
References:
page 6/67
2
1
3
4
5
6
7
8
9
10