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

image013.png

Figure 10– DeviceType

Table 29– DeviceType definition

Attribute

Value

BrowseName

DeviceType

IsAbstract

True

References

NodeClass

BrowseName

DataType

TypeDefinition

Other

Subtype of the ComponentTypedefined in 4.6

HasInterface

ObjectType

ISupportInfoType

Defined in 4.5.3.

HasInterface

ObjectType

IDeviceHealthType

Defined in 4.5.3.

0:HasComponent

Object

<CPIdentifier>

ConnectionPointType

OP

0:HasProperty

Variable

SerialNumber

0:String

0:PropertyType

M

0:HasProperty

Variable

RevisionCounter

0:Int32

0:PropertyType

M

0:HasProperty

Variable

Manufacturer

0:LocalizedText

0:PropertyType

M

0:HasProperty

Variable

Model

0:LocalizedText

0:PropertyType

M

0:HasProperty

Variable

DeviceManual

0:String

0:PropertyType

M

0:HasProperty

Variable

DeviceRevision

0:String

0:PropertyType

M

0:HasProperty

Variable

SoftwareRevision

0:String

0:PropertyType

M

0:HasProperty

Variable

HardwareRevision

0:String

0:PropertyType

M

0:HasProperty

Variable

DeviceClass

0:String

0:PropertyType

O

0:HasProperty

Variable

ManufacturerUri

0:String

0:PropertyType

O

0:HasProperty

Variable

ProductCode

0:String

0:PropertyType

O

0:HasProperty

Variable

ProductInstanceUri

0:String

0:PropertyType

O

Applied from IDeviceHealthType

0:HasComponent

Variable

DeviceHealth

DeviceHealthEnumeration

0:BaseDataVariableType

O

0:HasComponent

Object

DeviceHealthAlarms

0:FolderType

O

Applied from ISupportInfoType

0:HasComponent

Object

DeviceTypeImage

0:FolderType

O

0:HasComponent

Object

Documentation

0:FolderType

O

0:HasComponent

Object

ProtocolSupport

0:FolderType

O

0:HasComponent

Object

ImageSet

0:FolderType

O

Conformance Units

DI DeviceType

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 5.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 4.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.