This ObjectTypecan be used to define the structure of a Device. Figure 13shows the DeviceType. It is formally defined in Table 26.

image016.png

Figure 13– DeviceType

Table 26– DeviceType definition

Attribute

Value

BrowseName

DeviceType

IsAbstract

True

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the ComponentTypedefined in 5.6

HasInterface

ObjectType

ISupportInfoType

Defined in 5.5.3.

HasInterface

ObjectType

IDeviceHealthType

Defined in 5.5.3.

HasComponent

Object

<CPIdentifier>

ConnectionPointType

OptionalPlaceholder

HasProperty

Variable

SerialNumber

String

PropertyType

Mandatory

HasProperty

Variable

RevisionCounter

Int32

PropertyType

Mandatory

HasProperty

Variable

Manufacturer

LocalizedText

PropertyType

Mandatory

HasProperty

Variable

Model

LocalizedText

PropertyType

Mandatory

HasProperty

Variable

DeviceManual

String

PropertyType

Mandatory

HasProperty

Variable

DeviceRevision

String

PropertyType

Mandatory

HasProperty

Variable

SoftwareRevision

String

PropertyType

Mandatory

HasProperty

Variable

HardwareRevision

String

PropertyType

Mandatory

HasProperty

Variable

DeviceClass

String

PropertyType

Optional

HasProperty

Variable

ManufacturerUri

String

PropertyType

Optional

HasProperty

Variable

ProductCode

String

PropertyType

Optional

HasProperty

Variable

ProductInstanceUri

String

PropertyType

Optional

Applied from IDeviceHealthType

HasComponent

Variable

DeviceHealth

DeviceHealthEnumeration

BaseDataVariableType

Optional

HasComponent

Object

DeviceHealthAlarms

FolderType

Optional

Applied from ISupportInfoType

HasComponent

Object

DeviceTypeImage

FolderType

Optional

HasComponent

Object

Documentation

FolderType

Optional

HasComponent

Object

ProtocolSupport

FolderType

Optional

HasComponent

Object

ImageSet

FolderType

Optional

DeviceTypeis a subtype of ComponentTypewhich means it inherits all InstanceDeclarations.

The DeviceType ObjectTypeis abstract. There will be no instances of a DeviceTypeitself, only of concrete subtypes.

ConnectionPoints(see 6.4) represent the interface (interface card) of a DeviceTypeinstance to a Network. Multiple ConnectionPointsmay exist if multiple protocols and/or multiple Communication Profilesare supported.

The Interfacesand their members are described in 5.5. Some of the Propertiesinherited from the ComponentTypeare declared mandatory for backward compatibility.

Although mandatory, some of the Propertiesmay not be supported for certain types of Devices. In this case vendors shall provide the following defaults:

Clientscan ignore the Propertieswhen they have these defaults.

When Propertiesare not supported, Serversshould initialize the corresponding Propertydeclaration on the DeviceTypewith the default value. Relevant Browse Servicerequests can then return a Referenceto this Propertyon the type definition. That way, no extra Nodesare needed.