12.2.1.2 Mapping for DeviceType (“Types” standard Object)

All device types provided by DTMs in IDtmInformation shall be represented as subtypes of FdtDeviceType in the “Types” standard Object (see Table 58).

Table 58 – DeviceType mapping
OPCFDT
AttributeInterfaceMethodData memberDescription
BrowseName IDtmInformation<>GetSupported­TypesDeviceTypeInfo.Name
DisplayNameIDtmInformation<>GetSupported­TypesDeviceTypeInfo.Name
BrowseNameInterfaceMethodData memberDescription
2:SerialNumberMapping for online device only, see Table 61
2:RevisionCounterNot supported. Value is always set to -1
2:ManufacturerIDtmInformation<>GetSupported­TypesDeviceTypeInfo.ProductManufacturerName
ManufacturerIdIDtmInformationGetDeviceIdentInfoDeviceIdentInfo.ManufacturerId
2:ModelIDtmInformation<>GetSupported­TypesDeviceTypeInfo.ProductName
2:DeviceManualAll documents will be provided in folder Documentation
2:DeviceRevisionIDtmInformation<>GetSupported­TypesDeviceTypeInfo.ProductRevision
2:SoftwareRevisionIDtmInformationGetDeviceIdentInfoDeviceIdentInfo.SoftwareRevision
2:HardwareRevisionIDtmInformationGetDeviceIdentInfoDeviceIdentInfo.HardwareRevision
2:DeviceClass(O)IDtmInformation<>GetSupported­TypesDeviceTypeInfo.DeviceClassifications[0].DomainId + “:” + DeviceTypeInfo.DeviceClassifications[0].IdThe value is a concatenation of the enumeration member names for DomainId and Id.
DeviceTypeIdIDtmInformation<>GetSupported­TypesDeviceTypeInfo.Id
2:ManufacturerUri(O)Not supported.
2:ProductCode(O)Not supported.
2:ProductInstanceUri(O)Not supported.
<CP_Identifier>(O)IDtmInformation<>GetSupported­Types

TypeInfo.BusCategories[].Category¬Type == required

<Identifier> = TypeInfo.BusCategories[].Protocol¬Name

HasComponent-reference of type RequiredProtocol.

IDtmInformation

IChannels

<>GetSupported­Types

IChannels.CommunicationChannels

TypeInfo.BusCategories[].Category¬Type == supported

<Identifier> = CommunicationChannelItem.Id

HasComponent-reference of type SupportedProtocol.

If one Channel requires multiple protocols, multiple connection points are provided, an additional number is concatenated to the channel id.

0:IconIDtmInformationGetFdtIcon()Iconsee explanation below the table
Applied from IFdtDeviceHealthType
2:DeviceHealthMapping for online device only, see Table 61
2:DeviceHealthAlarms(O)---No mapping defined.
OPCFDT
BrowseNameInterfaceMethodData memberDescription
Applied from IFdtSupportInfoType
2:DeviceTypeImage(O)This folder will contain items as defined in 12.2.8.1.
2:Documentation
(O)		IDtmInformation<>GetSupported­TypesDeviceTypeInfo.DocumentsThis folder will contain items that represent the shown FDT data member as defined in 7.3
2:ProtocolSupport (O)INetworkDataGetNetworkDataInfoNetworkData.
DeviceInformationDocuments		This folder will be provided as defined in 12.2.8.2.
2:ImageSet(O)Not supported.

A DTM can provide several icons (list of icons). The rule for selection of the icon and extraction of an image (a specific resolution) from the icon is frame application specific. The selection of the image format in general is implementation specific, all types are allowed that are defined in OPC UA 10000-3.