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

image013.png

Figure 10 – DeviceType

Table 26 – DeviceType definition

Attribute

Value

BrowseName

DeviceType

IsAbstract

True

References

NodeClass

BrowseName

DataType

TypeDefinition

ModellingRule

Subtype of the ComponentType defined in 4.6

HasInterface

ObjectType

ISupportInfoType

Defined in 4.5.3.

HasInterface

ObjectType

IDeviceHealthType

Defined in 4.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

Conformance Units

DI DeviceType

DeviceType is a subtype of ComponentType which means it inherits all InstanceDeclarations.

The DeviceType ObjectType is abstract. There will be no instances of a DeviceType itself, only of concrete subtypes.

ConnectionPoints (see 5.4) represent the interface (interface card) of a DeviceType instance to a Network. Multiple ConnectionPoints may exist if multiple protocols and/or multiple Communication Profiles are supported.

The Interfaces and their members are described in 4.5. Some of the Properties inherited from the ComponentType are declared mandatory for backward compatibility.

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

Clients can ignore the Properties when they have these defaults.

When Properties are not supported, Servers should initialize the corresponding Property declaration on the DeviceType with the default value. Relevant Browse Service requests can then return a Reference to this Property on the type definition. That way, no extra Nodes are needed.