IEC 62769-1-2021 Field device integration (FDI) – Part 1: Overview.
3.2 IEC TR 62541-1 terms (OPC UA)
For the purposes of this document, the following terms and definitions given in IEC TR 62541 -1 apply.
AddressSpace
Attribute
Client
Method
Node
NodeClass
Notification
Object
ObjectType
Reference
ReferenceType
Server
Service Set
Session
Subscription
Variable
3.3 IEC 62541 -3 (OPC UA) terms
For the purposes of this document, the following terms and definitions given in IEC 62541 -3 apply.
Aggregates
ArrayDimensions
AuditEvent
AuditUpdateMethodEvent
BrowseName
ByteString
DataType
DataVariable
Folder
HasComponent
HasProperty
HasSubType
HasTypeDefinition
ModellingRule
NodeId
Property
UserAccessLevel
UserExecutable
Value
ValueRank
3.4 IEC 62541-4 (OPC UA) terms
For the purposes of this document, the following terms and definitions given in IEC 62541 -4 apply.
AddReferences
Browse
BrowseNext
Call
CreateSession
NodeManagement
Read
Request Header
Response Header
StatusCode
TranslateBrowsePathsToNodeIds
UserIdentityToken
Write
3.5 IEC 62541-5 (OPC UA) terms
For the purposes of this document, the following terms and definitions given in IEC 62541 -5
apply.
BaseObjectType
PropertyType
3.6 IEC 62541 -100 (OPC UA for Devices) terms
For the purposes of this document, the following terms and definitions given in IEC 62541 -1 00 apply.
Block
Device
DeviceType
Parameter
4 Background
4.1 Motivation
In today’s automation systems, field devices from many different suppliers have to be integrated into the system, which results in additional effort for installation, version management and operation of these devices. This challenge is best met with an open and standardized device integration solution.
Two different device integration technologies exist: the Electronic Device Description Language (EDDL) in accordance with IEC 61 804 and the Field Device Tool (FDT ® ) in accordance with IEC 62453. While these technologies take different approaches to solve the problem, there is a lot of overlap between them. This has led to a situation where the technologies compete instead of complementing each other. As a result, system suppliers have taken their positions, device suppliers have had to double their efforts in order to support EDDL and FDT ® , and the end users have become frustrated because they want the best of both technologies.
For all parties involved, the ideal solution looks different. System suppliers want to achieve robustness while assuring a high level of technology and platform independence. Device suppliers want to support only one technology instead of two in order to reduce cost and effort, and they want to provide the optimal means for operating their devices. End users want to avoid false investments and therefore demand only one future-proof solution that offers all the advantages of the competing technologies.
4.2 Electronic Device Description Language (EDDL) The Electronic Device Description Language (EDDL) is a language for describing the behavior of field devices. It enables systems to configure, calibrate, troubleshoot, and operate a field device without any prior knowledge of the device. Device descriptions written in EDDL describe the capabilities of the field device; it is up to the system to determine how to utilize these capabilities. These device descriptions enable systems to access all the data and properties of all devices, which simplifies the maintenance, support, and operation of the devices. It works well for small handheld applications and large integrated automation systems. It works well for embedded systems and systems running on commercial operating systems. With EDDL, the device supplier can organize the device’s data, properties, and procedures for access by the end user. This provides the system guidance in dynamically creating a user interface for the device. The capabilities of this user interface can vary significantly for different classes of devices, and it can be as simple or complex as the device being described.IEC 62769-1 pdf download.