Annex B Usage with OPC UA for Devices (Informative)

This chapter shows an example of the extensions to the base model which are needed to use the base model together with OPC UA DI.

The following figure shows as an example how the objects are referred by the standard DI entry points “DeviceSet” and “NetworkSet”.

B.1 OPC UA Object Types

To use the base information model together with OPC UA DI some object types are defined which implement the interfaces defined in the base information model.

The following figure illustrates the additional object types used to extend the base information model for the use with OPC UA DI.

B.1.1 PnDIDeviceType

Although mandatory, some of the properties inherited from DeviceType may not be supported. In this case Vendors shall provide an empty string for properties with DataType String, an empty text field for properties with DataType LocalizedText and -1 for the RevisionCounter property (see [OPC 10000-100] - DeviceType also).

The following PROFINET properties are equal to their counterparts of PnIdentificationType an shall have the same content:

B.1.2 PnDIControllerType

B.1.3 PnDIRealModuleType

B.1.4 PnDIExpectedModuleType

B.1.5 PnDIRealSubmoduleType

B.1.6 PnDIExpectedSubmoduleType

B.1.7 PnDIDomainType

The standard OPC UA DI object NetworkSet (defined in [OPC 10000-100]) has hierarchical references to all NetworkType (PnDIDomainType) object instances.

The Network Object (PnDIDomainType) has a ConnectsTo reference to the ConnectionPoint (PnDIInterfaceType).

B.1.8 PnDIInterfaceType

The mandatory NetworkAddress FunctionalGroup of the ConnectionPointType has an Organizes reference to the EthernetInterface object representing the Ethernet address information of the interface.

B.1.9 PnDIPROFINETProtocolType