FDT specific OPC UA ObjectTypes – OPC UA for Field Device Tool (FDT)

7 FDT specific OPC UA ObjectTypes

7.1 General

The OPC UA information model for FDT is based on OPC UA for Devices. This document defines a mapping for device-related information, services and data types.

Services which are defined in OPC UA for Devices, but for which no mapping is defined here (e.g. Locking service), have to be implemented by the OPC UA Server according to the specification in OPC UA for Devices.

7.2 FdtDeviceType

This OPC UA ObjectType is the base for a device type derived from an FDT device type definition. Any manufacturer-specific device type is derived from FdtDeviceType.

Figure 7 shows an overview for the FdtDeviceType with its Properties and related ObjectTypes. It is formally defined in Table 12.

The FdtDeviceType is formally defined in Table 12.

Table 12 – FdtDeviceType Definition

Attribute	Value
BrowseName	FdtDeviceType
IsAbstract	True

References	Node Class	BrowseName	DataType	TypeDefinition	Other
Subtype of 2:DeviceType defined in OPC UA for Devices
HasInterface	ObjectType	IFdtDeviceHealthType		Defined in 7.4
HasInterface	ObjectType	IFdtSupportInfoType		Defined in 7.5
0:HasProperty	Variable	ManufacturerId	0:String	0:PropertyType	O
0:HasProperty	Variable	DeviceTypeId	0:String	0:PropertyType	O
0:HasProperty	Variable	DeviceTag	0:String	0:PropertyType	M
Applied from 2:IFdtDeviceHealthType
0:HasComponent	Variable	2:DeviceHealth	2:DeviceHealthEnumeration	0:BaseDataVariableType	M, RO

The FdtDeviceType is an abstract type and cannot be used directly.

The definition for DeviceHealth overrides the definition of OPC UA for Devices and makes this member mandatory for FdtDeviceType.

The mapping of FDT information to FdtDeviceType is defined in 12.2.1.

7.3 FdtFunctionalGroupType

FdtFunctionalGroupType is used for representing functional grouping of methods and parameters. It is formally defined in Table 13.

Table 13 – FdtFunctionalGroupType Definition

Attribute	Value
BrowseName	FdtFunctionalGroupType
IsAbstract	False

References	Node Class	BrowseName	DataType	TypeDefinition	Other
Subtype of 2:FunctionalGroupType defined in OPC UA for Devices 5.4
0:HasProperty	Variable	ApplicationId	ApplicationIdEnumeration	0:PropertyType	O
0:HasProperty	Variable	SemanticInfo	SemanticInfoType	0:PropertyType	O

The FdtFunctionalGroupType is a concrete type and can be used directly.

7.4 IFdtDeviceHealthType Interface

IFdtDeviceHealthType defines additional requirements for the IDeviceHealthType interface, which is formally defined in Table 14.

Table 14 – IFdtDeviceHealthType Definition

Attribute	Value
BrowseName	IFdtDeviceHealthType
IsAbstract	True

References	Node Class	BrowseName	DataType	TypeDefinition	Other
Subtype of the 2:IDeviceHealthType interface defined in OPC UA for Devices 5.5.4.
0:HasComponent	Variable	2:DeviceHealth	2:DeviceHealthEnumeration	0:BaseDataVariableType	M

The definition for DeviceHealth overrides the definition of OPC UA for Devices and makes the DeviceHealth member mandatory for IFdtDeviceHealthType.

7.5 IFdtSupportInfoType Interface

7.5.1 Overview

The IFdtSupportInfoType defines additional requirements for the ISupportInfoType interface, which is formally defined in Table 15.

Table 15 – IFdtSupportInfoType Definition

Attribute	Value
BrowseName	IFdtSupportInfoType
IsAbstract	True

References	Node Class	BrowseName	DataType	TypeDefinition	Other
Subtype of the 2:ISupportInfoType interface defined in OPC UA for Devices 5.5.5.

The components of the IFdtSupportInfoType have additional references as defined in Table 16.

Table 16 – IFdtSupportInfoType Additional Subcomponents

Source Path	References	Node Class	BrowseName	Data Type	TypeDefintion	Others
2:Documentation	HasComponent	Object	<FdtDocumentIdentifier>		FdtDocumentType	MP
2:ProtocolSupport	HasComponent	Object	<FdtProtocolSupportIdentifier>		FdtDocumentType	MP

Documents provided for a device are exposed as Objects organized in the Documentation folder. In most cases they will represent a product manual, which can exist as a set of individual documents. The BrowseName of each Object in the Documentation Folder will consist of the document label that can be used to identify the document.

Protocol support files (e.g. GSD files, EDS files) provided for a device are exposed as Objects organised in the ProtocolSupport folder.

7.6 Document types

7.6.1 FdtDocumentType

This abstract type describes the information associated with a document provided by a DTM. The FdtDocumentType is formally described in Table 17.

Table 17 – FdtDocumentType Definition

Attribute	Value
BrowseName	FdtDocumentType
IsAbstract	True

References	Node Class	BrowseName	DataType	TypeDefinition	Other
Subtype of 0:BaseObjectType
0:HasProperty	Variable	Classification	DocumentClassification	0:PropertyType	M
0:HasProperty	Variable	Help	0:String	0:PropertyType	O
0:HasProperty	Variable	Language	0:String	0:PropertyType	O
0:HasProperty	Variable	MediaType	0:String	0:PropertyType	M
0:HasProperty	Variable	SemanticInfo	SemanticInfoType	0:PropertyType	O

The FdtDocumentType is an abstract type and cannot be used directly.

The MIME type of document is identified by the MediaType property of each Variable.

7.6.2 FdtDocumentFile

This is a type for representing documents, which are provided as files. It is formally defined in Table 18.

Table 18 – FdtDocumentFile Definition

Attribute	Value
BrowseName	FdtDocumentFile
IsAbstract	False

References	Node Class	BrowseName	DataType	TypeDefinition	Other
Subtype of FdtDocumentType
0:HasComponent	Object	File		0:FileType	M

The FdtDocumentFile is a concrete type and can be used directly.

The document may be retrieved from the server by using the methods related to the object of type FileType.

7.6.3 FdtDocumentUrl

This is a type for representing documents, which are provided as URL. It is formally defined in Table 19.

Table 19 – FdtDocumentUrl Definition

Attribute	Value
BrowseName	FdtDocumentUrl
IsAbstract	False

References	Node Class	BrowseName	DataType	TypeDefinition	Other
Subtype of FdtDocumentType
0:HasProperty	Variable	URL	0:String	0:PropertyType	M

The FdtDocumentUrl is a concrete type and can be used directly.

The actual document may be retrieved by the Client from the URL.

7.7 FdtProtocolType

This type is used to specify which protocols an FdtDeviceType requires or supports.

The FdtProtocolType is formally defined in Table 20.

Table 20 – FdtProtocolType Definition

Attribute	Value
BrowseName	FdtProtocolType
IsAbstract	True

References	Node Class	BrowseName	DataType	TypeDefinition	Other
Subtype of 2:ProtocolType defined in OPC UA for Devices 6.1
0:HasProperty	Variable	BusCategory	0:String	0:PropertyType	M

The FdtProtocolType is an abstract type and cannot be used directly.

The property BusCategory shall be used by any instance of FdtProtocolType or its subtypes.

7.8 FdtTransferServiceType

This type is used to specify support for transfer services.

Figure 9 – FdtTransferServiceType overview

The FdtTransferServiceType is formally defined in Table 21.

Table 21 – FdtTransferServiceType Definition

Attribute	Value
BrowseName	FdtTransferServiceType
IsAbstract	False

References	Node Class	BrowseName	DataType	TypeDefinition	Other
Subtype of 2:TransferServicesType
0:HasProperty	Variable	SupportedTransfer	SupportedTransfer	0:PropertyType	M

The FdtTransferServiceType is a concrete type and can be used directly.

The property SupportedTransfer (defined in 10.4.11) is used to indicate the services supported for the respective device.

7.9 FdtIoSignalInfoType

This type is used to provide information about the IO signals available at the device.

Figure 10 – FdtIoSignalInfoType overview

The FdtIoSignalInfoType is formally defined in Table 22.

Table 22 – FdtIoSignalInfoType Definition

Attribute	Value
BrowseName	FdtIoSignalInfoType
IsAbstract	False

References	Node Class	BrowseName	DataType	TypeDefinition	Other
Subtype of BaseObjectType
0:HasProperty	Variable	Description	0:String	0:PropertyType	O
0:HasProperty	Variable	FrameApplicationTag	0:String	0:PropertyType	M
0:HasProperty	Variable	IECDatatype	IECDatatype	0:PropertyType	M
0:HasProperty	Variable	IsLocked	0:Boolean	0:PropertyType	M
0:HasProperty	Variable	IsSafety	0:Boolean	0:PropertyType	M
0:HasProperty	Variable	RoutedIoSignalId	0:String	0:PropertyType	O
0:HasProperty	Variable	SemanticInfo	SemanticInfoType	0: PropertyType	O
0:HasProperty	Variable	SignalType	SignalTypeEnumeration	0:PropertyType	M
0:HasProperty	Variable	HasAlarmInfo	DataRefType	0:PropertyType	O
0:HasProperty	Variable	HasDeviceData	DataRefType	0:PropertyType	O
0:HasProperty	Variable	HasRange	DataRefType	0:PropertyType	O
0:HasProperty	Variable	HasSubstituteValue	DataRefType	0:PropertyType	O
0:HasProperty	Variable	HasUnit	DataRefType	0:PropertyType	O

The FdtIoSignalInfoType is a concrete type and can be used directly.