6.3.1.8.2 PnAssetType
Table 64 – PnAssetType Definition
Attribute Value
BrowseNamePnAssetType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Modelling Rule
Subtype of BaseObjectType defined in [OPC 10000-5].
HasPropertyVariableUniqueIdentifierGuidPropertyTypeMandatory
HasPropertyVariableLocationStringPropertyTypeMandatory
HasPropertyVariableAnnotationStringPropertyTypeMandatory
HasPropertyVariableOrderIdStringPropertyTypeMandatory
HasPropertyVariableSoftwareRevisionStringPropertyTypeOptional
HasPropertyVariableHardwareRevisionStringPropertyTypeOptional
HasPropertyVariableSerialNumberStringPropertyTypeMandatory
HasPropertyVariableTypeIdentificationUInt16PropertyTypeMandatory
HasPropertyVariableOrganizationUInt16PropertyTypeMandatory
HasPropertyVariableVendorIdUInt16PropertyTypeMandatory
HasPropertyVariableDeviceIdUInt16PropertyTypeMandatory
HasPropertyVariableDeviceSubIdUInt16PropertyTypeMandatory
GeneratesEventObjectTypePnAssetChangedEventType

The BrowseName of an asset object instance shall be the content of the UniqueIdentifier variable in standard GUID string format.

Mapping to PROFINET properties:

BrowseName Method Source
UniqueIdentifier ReadAssetManagementData | IM_UniqueIdentifier
Location ReadAssetManagementData | AM_Location
Annotation ReadAssetManagementData | IM_Annotation
OrderId ReadAssetManagementData | IM_OrderID
SoftwareRevision ReadAssetManagementData | IM_Software_Revision or AM_SoftwareRevision
HardwareRevision ReadAssetManagementData | IM_Hardware_Revision or AM_HardwareRevision
SerialNumber ReadAssetManagementData | IM_Serial_Number
TypeIdentification ReadAssetManagementData | AM_TypeIdentification
Organization ReadAssetManagementData | AM_DeviceIdentification.Organization
VendorId ReadAssetManagementData | AM_DeviceIdentification.VendorID
DeviceId ReadAssetManagementData | AM_DeviceIdentification.DeviceID
DeviceSubId ReadAssetManagementData | AM_DeviceIdentification.DeviceSubID

If the AM_Location field is coded using the level tree format, each used level shall be encoded in the Location string with a ‘.’ followed by the value of the level bits encoded as decimal number string. According to [PN TAD] – Figure 38, the HART sensor has the Location string ”.0.4.1.1”.

If the AM_Location field is coded using the slot- and subslotnumber format, the Location string shall be encoded as ‘BeginSlotNumber/BeginSubslotNumber-EndSlotNumber/EndSubslotNumber’. BeginSlotNumber and EndSlotNumber shall be encoded as decimal number strings. BeginSubslotNumber and EndSubslotNumber shall be encoded as hexadecimal number strings (0x…) According to [PN TAD] – Figure 38, the IO-MC 1 asset has the Location string ”2/0x1-4/0x1”.