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

image014.png

Figure 10 – DeviceType

Table 35 – DeviceType definition

Attribute

Value

BrowseName

1:DeviceType

IsAbstract

True

References

NodeClass

BrowseName

DataType

TypeDefinition

Other

Subtype of the ComponentType defined in 4.5.7

HasInterface

ObjectType

1:ISupportInfoType

Defined in 4.5.3.

HasInterface

ObjectType

1:IDeviceHealthType

Defined in 4.5.3.

0:HasComponent

Object

1:<CPIdentifier>

1:ConnectionPointType

OP

0:HasProperty

Variable

1:SerialNumber

0:String

0:PropertyType

M

0:HasProperty

Variable

1:RevisionCounter

0:Int32

0:PropertyType

M

0:HasProperty

Variable

1:Manufacturer

0:LocalizedText

0:PropertyType

M

0:HasProperty

Variable

1:Model

0:LocalizedText

0:PropertyType

M

0:HasProperty

Variable

1:DeviceManual

0:String

0:PropertyType

M

0:HasProperty

Variable

1:DeviceRevision

0:String

0:PropertyType

M

0:HasProperty

Variable

1:SoftwareRevision

0:String

0:PropertyType

M

0:HasProperty

Variable

1:HardwareRevision

0:String

0:PropertyType

M

0:HasProperty

Variable

1:DeviceClass

0:String

0:PropertyType

O

0:HasProperty

Variable

1:ManufacturerUri

0:String

0:PropertyType

O

0:HasProperty

Variable

1:ProductCode

0:String

0:PropertyType

O

0:HasProperty

Variable

1:ProductInstanceUri

0:String

0:PropertyType

O

Applied from IDeviceHealthType

0:HasComponent

Variable

1:DeviceHealth

DeviceHealthEnumeration

0:BaseDataVariableType

O

0:HasComponent

Object

1:DeviceHealthAlarms

0:FolderType

O

Applied from ISupportInfoType

0:HasComponent

Object

1:DeviceTypeImage

0:FolderType

O

0:HasComponent

Object

1:Documentation

0:FolderType

O

0:HasComponent

Object

1:ProtocolSupport

0:FolderType

O

0:HasComponent

Object

1:ImageSet

0:FolderType

O

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 can 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 are not 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 required.