西门子SIMATIC NET OPC UA .NET客户端开发教程

需积分: 0 118 浏览量更新于2024-06-22 收藏 3.13MB PDF 举报

OPC UA .NET客户端开发示例文档是一份针对Siemens SIMATIC NET OPC UA服务器的编程指南，使用C#语言编写。这份文档主要针对.NET平台，旨在帮助开发者理解和实现西门子工业自动化产品的OPC Unified Architecture (OPC UA)通信。OPC UA是一种开放标准，用于设备之间交换实时和历史数据，特别是在工业自动化环境中。文档的核心内容包括以下几个关键知识点： 1. **OPC UA简介**：OPC UA提供了一种统一的访问接口，允许不同制造商的设备和服务进行互操作，确保数据的一致性和安全性。它支持多种编程语言，如C#，方便开发者在.NET环境中集成和开发客户端应用程序。 2. **C#编程示例**：文档提供了详细的C#代码示例，展示了如何创建、连接到OPC UA服务器、查询和订阅数据，以及处理事件和异常情况。这对于初学者和有经验的.NET开发者都是宝贵的实践资源。 3. **SIMATIC NET OPC UA Server**：文档链接指向Siemens官方支持文档，说明了该服务器的功能特性及其在实际应用中的角色。它可能涉及服务器的配置、安全设置以及与C#客户端的交互方法。 4. **责任与免责声明**：文档强调应用示例仅供参考，不构成完整电路设计或客户特定解决方案。开发者需自行确保正确使用产品，并遵循安全操作、安装、运行和维护规程。此外，Siemens对基于示例产生的任何损坏或索赔不承担责任，且保留随时修改示例的权利。 5. **注意事项**：开发者在使用这些示例时，应明确理解自己的责任，并认识到仅依赖示例可能存在风险，需要根据具体项目需求进行适当的定制和验证。这份文档是开发人员在.NET环境下利用OPC UA技术进行工业自动化应用开发的重要参考资料，涵盖了从理论概念到实际代码实现的方方面面，有助于提高工作效率和产品质量。

2 Automation Solution

.NET OPC UA-Client

Entry-ID: 42014088, V1.2, 12/2017

Software components

Table 2-6

Component

Qty.

Article number

Note

SIMATIC NET DVD

V14

6GK1700-0AA14-0AA0

STEP 7 Professional

V14 SP1

6ES7822-1AA04-0YA5

Microsoft Visual

Studio 2010

Alternatively, later versions

of VS are also possible.

.NET Framework 4.5

Example files and projects

The following list includes all files and projects that are used in this example.

Table 2-7

Component

Note

42014088_OPC_UAClient_DOKU_V12_en.pdf

This document.

42014088_OPC_UAClient_CODE_V12.zip

This zip file contains the OPC UA client

with sources and the related STEP 7

V14 project.

2.4 Alternative solutions

OPC Data Access on the basis of COM

Today, this automation task is typically solved with the COM based classic OPC

Data Access interface.

Advantages of the solution with COM OPC Data Access:

 Wide distribution of the interface.

 Many applications for different tasks support the interface.

 Easy access for local applications.

Disadvantages of the solution with COM OPC Data Access:

 Complicated DCOM configuration for remote access.

 No communication possible across firewall or internet boundaries.

 OPC clients can only be operated on Windows PC systems.

 Restricted security mechanisms and user authentication only within the

framework of the DCOM configuration.

 No user-defined access rights possible.

3 Basics

.NET OPC UA-Client

Entry-ID: 42014088, V1.2, 12/2017

3 Basics

3.1 Basics on OPC

Overview

In recent years, the OPC Foundation (an interest group of well-known

manufacturers for the definition of standard interfaces) has defined a large number

of software interfaces to standardize the information flow from the process level to

the management level. According to the different requirements within an industrial

application, different OPC specifications have been developed in the past: Data

Access (DA), Alarm & Events (A&E), Historical Data Access (HDA) and Data

eXchange (DX). Access to process data is described in the DA specification, A&E

describes an interface for event-based information, including acknowledgement,

HDA describes functions for archived data and DX defines a lateral server to server

communication.

Based on the experience with these classic OPC interfaces, the OPC Foundation

defined a new platform, called OPC Unified Architecture (UA). The aim of this new

standard is the generic description and uniform access to all information which is to

be exchanged between systems or applications. This includes the functionality of

all previous OPC interfaces. Furthermore, it is to generate the possibility of natively

integrating the interface in the respective system, irrespective of which operating

system the system is operated on and irrespective of the programming language in

which the system was created.

This example discusses the OPC Unified Architecture interface. A detailed

documentation is available on the SIMATIC NET CD. For more information, please

go to www.opcfoundation.org.

What is OPC?

In the past, OPC was a collection of software interfaces for data exchange between

PC applications and process devices. These software interfaces have been defined

according to the rules of Microsoft COM (Component Object Model) and can

therefore be easily integrated into Microsoft operating systems. COM or DCOM

(Distributed COM) provides the functionality of inter process communication and

organizes the information exchange between applications, even across network

boundaries (DCOM). Using mechanisms of the Microsoft operating system, an

OPC client (COM client) can use it to exchange information with an OPC server

(COM server).

The OPC server provides process information of a device at its interface. The OPC

client connects itself with the OPC server and can access the offered data.

The use of COM or DCOM causes OPC servers and clients to run only on a

Windows PC or in the local network and that the communication to the respective

automation system has to be realized mainly via proprietary protocols. Additional

tunneling tools often have to be used for the network communication between

client and server in order to get through firewalls or to avoid the complicated

DCOM configuration. The interface can furthermore only be accessed natively with

C++ applications; .NET or JAVA applications can only gain access via a wrapper

layer. In real-life situations, these restrictions lead to additional communication and

software layers which increase the configuration workload and the complexity.

Due to the widespread use OPC, the standard is increasingly used for the general

connection of automation systems and no longer only for the original application as

driver interface in HMI and SCADA systems to access process information.

3 Basics

.NET OPC UA-Client

Entry-ID: 42014088, V1.2, 12/2017

List of specifications

Table 3-1 explains the list of specifications and their contents. The currently

relevant specifications for the SIMATIC NET server are highlighted here

Table 3-1

Specification

Description

Part 1 – Concepts

This non-normative part gives an overview of the standard.

Part 2 – Security

The requirements to security and an introduction to the basics are described

in the second part, which is also non-normative.

Part 3 – Address Space

Model

This part defines the basic rules and elements for the set-up of the address

space of an OPC UA server. These rules form the basis for the information

models in part 5, 8 to 11 and the companion specifications.

Part 4 – Services

This document is the only part which defines the interface for the access to

all OPC UA information. It specifies a list of methods, the so called services.

These services are generic and form the basis for all information models.

Part 5 – Information Model

The basic information model defines the access points in the address space

and basic types such as, e.g. data types or object types. This part, together

with part 3 and 4 forms the core of OPC UA.

Part 6 – Service Mapping

The services in part 4 are independent of the defined transport mechanism

used. This part specifies the realization of the services in different ways of

serialization, security and transport protocols for messages between OPC

UA client and server. This part forms the basis for the implementation of

communication stacks and is not relevant for the users of the technology.

Part 7 – Profiles

A profile specifies a subset of OPC functionalities for different applications

which are offered by an OPC UA server or which can be used by an OPC

UA client. This part defines the list of profiles for OPC UA.

Part 8 – Data Access

This part defines the variable types, properties and quality status codes for

process data. All other necessary concepts are already contained in parts 3

to 5.

Part 9 – Alarms and

Conditions

This part defines the model for the description of condition monitoring and

process alarms and the signaling of status changes via events. All other

necessary concepts for events are already contained in parts 3 to 5.

Part 10 – Programs

This part defines how actions, which are running over a longer period of time

can be started and monitored. This is performed on the basis of state

machines whose handling is defined in part 5 in OPC UA.

Part 11 – Historical Access

Here, the access to historical data and events is defined.

Part 12 – Discovery

Defines how the OPC UA server can be found in the network.

Part 13 – Aggregates

This part defines aggregate functions for data compression such as average

or maximum value over a time range. The aggregates can be used for

current or historical data.

Devices (DI)

This companion specification defines a generic model for the configuration

and diagnostics of devices.

IEC 61131-3 (PLC)

This companion specification defines a mapping of the IEC 61131-3

software model and of the standardized control programming languages on

an OPC UA server address space.

Analyzer Device Integration

(ADI)

This companion specification defines a model for the configuration and data

linking for complex devices for process analysis based on DI

Field Device Integration

(FDI)

This companion specification defines a model for the complete engineering

of field devices on the basis of Electronic Device Description Language

(EDDL) and Field Device Tool (FDT).

剩余85页未读，继续阅读

innwpu

粉丝: 0
资源: 1

西门子SIMATIC NET OPC UA .NET客户端开发教程

OPC UA客户端例程

c# OPC UA .NET Client代码实例

OPC UA Server Client 实例源码下载

使用UA-.NETStandard库简化OPC UA开发

理解OPC UA的基本概念

深入了解OPC UA的数据模型

实现C# OPC UA服务端的访问控制

创建自定义的OPC UA对象和变量

opc ua .net client

opc ua西门子客户端开发

最新资源