OPC .NET Developer Toolkit FAQs

OPC .NET Developer Toolkit FAQs
DeltaV Whitepaper
October 2015 – Page 1
OPC .NET Toolkit FAQs
OPC .NET Developer Toolkit FAQs
This document answers questions about the OPC .NET Developer Toolkit
www.DeltaV.com
DeltaV Whitepaper
October 2015 – Page 2
OPC .NET Toolkit FAQs
Table of Contents
Introduction.............................................................................................................................. 3
Terminology ......................................................................................................................... 3
1.1. What is the OPC .NET Developer Toolkit? .................................................................... 3
1.2. Are any DeltaV licenses required to use this toolkit?..................................................... 3
1.3. Will the toolkit work with any OPC .NET server? ........................................................... 3
1.4. What do I need to start developing OPC .NET clients for DeltaV? ................................ 3
1.5. What are the “Xi DLLs” in the toolkit code? ................................................................... 4
DeltaV Whitepaper
October 2015 – Page 3
OPC .NET Toolkit FAQs
Introduction
Terminology
This whitepaper answers questions about the implementation of the OPC standard within DeltaV system. In this
document, the following terminology is used.
OPC: Open Platform Communications (OPC) is an overarching name for a series of standards and
specifications that facilitate interoperability between different vendors in industrial telecommunication
applications.
OPC Classic: The OPC specification that uses Windows COM/DCOM to exchange data between
software components, clients, and servers.
OPC .NET: The OPC specification that uses Windows WCF to exchange data between software
components, clients, and servers.
OPC UA: The OPC specification that is platform independent and uses a service-oriented architecture
between software components, clients, and servers.
OPC DA: Data Access (DA) specification defines the exchange of real-time data.
OPC HDA: Historical Data Access (HDA) specification defines the exchange of historical data.
OPC A&E: Alarms and Events (A&E) specification defines the exchange alarm and event type data.
1.1. What is the OPC .NET Developer Toolkit?
The OPC .NET Developer Toolkit is a set of simple sample code snippets written in C# that can be used to create
custom client applications to interact with a standard OPC .NET server. This toolkit is meant to be used as a
starting point for developers to create their applications for reading and writing OPC data via OPC .NET. It is
provided by Emerson and requires that users agree with the Terms and Conditions before downloading.
1.2. Are any DeltaV licenses required to use this toolkit?
Yes, the DeltaV system must be licensed to run DeltaV’s OPC server in order to allow communications with the
toolkit clients. For more information on the licensing options, refer to the DeltaV OPC .NET Product Data Sheet.
For development purposes, an OPC .NET server may be downloaded from the OPC Foundation website.
1.3. Will the toolkit work with any OPC .NET server?
The toolkit sample clients are written with standard OPC .NET interfaces and will work with any compliant OPC
.NET server. The only caveat is that the “Client Side DLLs” provided with the toolkit must conform to the
application running on the server side. The end user must verify that the client and server side DLLs are
compliant and running at the same version. For DeltaV, Emerson has already done this for this toolkit by
specifying the version of DeltaV for each sample client in the toolkit.
1.4. What do I need to start developing OPC .NET clients for DeltaV?
All you need is a properly licensed DeltaV system (refer to the DeltaV OPC .NET Product Data Sheet) and a copy
of Microsoft Visual Studio 2010 or Microsoft Visual Studio 2012. At that point it is easy to develop, deploy, and
test the OPC .NET client on your DeltaV system.
DeltaV Whitepaper
October 2015 – Page 4
OPC .NET Toolkit FAQs
1.5. What are the “Xi DLLs” in the toolkit code?
The “Xi DLLs” are referred to as the “Client Side DLLs”. Their purpose is to make the client code simpler and
easier to implement. Some functions that the “Client Side DLLs” perform for the client are: data conversions,
status update, keep-alive messages, notifications, and browsing support. These “Client Side DLLs” are updated
regularly and kept evergreen on the OPC Foundation website.
DeltaV Whitepaper
OPC .NET Toolkit FAQs
October 2015 – Page 5
This page intentionally left blank.
To locate a sales office near you, visit our website at:
www.EmersonProcess.com/DeltaV
Or call us at:
Asia Pacific: 65.6777.8211
Europe, Middle East: 41.41.768.6111
North America, Latin America:
+1 800.833.8314 or
+1 512.832.3774
For large power, water, and wastewater applications
contact Power and Water Solutions at:
www.EmersonProcess-powerwater.com
Or call us at:
Asia Pacific: 65.6777.8211
Europe, Middle East, Africa: 48.22.630.2443
North America, Latin America: +1 412.963.4000
© Emerson Process Management 2014. All rights reserved. For Emerson Process Management trademarks and service marks, go to:
http://www.emersonprocess.com/home/news/resources/marks.pdf.
The contents of this publication are presented for informational purposes only, and while every effort has been made to ensure their accuracy, they are not to be
construed as warrantees or guarantees, express or implied, regarding the products or services described herein or their use or applicability. All sales are governed
by our terms and conditions, which are available on request. We reserve the right to modify or improve the design or specification of such products at any time
without notice.
www.DeltaV.com
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising