6.3.1.8 Identification
6.3.1.8.1 PnIdentificationType
Table 63 – PnIdentificationType Definition
Attribute Value
BrowseNamePnIdentificationType
IsAbstractFalse
References Node Class BrowseName DataType TypeDefinition Modelling Rule
Subtype of BaseObjectType defined in [OPC 10000-5].
HasPropertyVariableVendorIdUInt16PropertyTypeMandatory
HasPropertyVariableOrderIdStringPropertyTypeMandatory
HasPropertyVariableSerialNumberStringPropertyTypeMandatory
HasPropertyVariableSoftwareRevisionStringPropertyTypeMandatory
HasPropertyVariableHardwareRevisionStringPropertyTypeMandatory
HasPropertyVariableProfileIdUInt32PropertyTypeMandatory
HasPropertyVariableProfileSpecificTypeUInt16PropertyTypeMandatory
HasPropertyVariableVersionStringPropertyTypeMandatory
HasPropertyVariableRevisionCounterUInt16PropertyTypeOptional
HasPropertyVariableIMSupportedUInt16PropertyTypeOptional
HasPropertyVariableTagFunctionStringPropertyTypeOptional
HasPropertyVariableTagLocationStringPropertyTypeOptional
HasPropertyVariableDateDateTimePropertyTypeOptional
HasPropertyVariableDescriptorStringPropertyTypeOptional
HasPropertyVariableSignatureByteStringPropertyTypeOptional
HasPropertyVariableIM5PnIM5DataType[]PropertyTypeOptional
HasComponentMethodSetTagsSetTagsMethodOptional
HasComponentMethodSetDateSetDateMethodOptional
HasComponentMethodSetDescriptorSetDescriptorMethodOptional

Mapping to PROFINET properties:

BrowseName Method Source
VendorId ReadI&M0 | VendorID
OrderId ReadI&M0 | OrderID
SerialNumber ReadI&M0 | IM_Serial_Number
SoftwareRevision ReadI&M0 | IM_Software_Revision
HardwareRevision ReadI&M0 | IM_Hardware_Revision
ProfileId ReadI&M0 | IM_Profile_ID
ProfileSpecificType ReadI&M0 | IM_Profile_Specific_Type
Version ReadI&M0 | IM_Version
RevisionCounter ReadI&M0 | IM_Revision_Counter
IMSupported ReadI&M0 | IM_Supported
TagFunction ReadI&M1 | IM_Tag_Function
TagLocation ReadI&M1 | IM_Tag_Location
Date ReadI&M2 | IM_Date
Descriptor ReadI&M3 | IM_Descriptor
Signature ReadI&M4 | IM_Signature
IM5 Read

I&M5 | I&M5Data, see chapter 6.3.3.1.2 for details

Array size: I&M5 | NumberOfEntries

6.3.1.8.1.1 SetTags Method

This optional method writes the I&M1 fields IM_TagFunction and IM_Tag_Location remanent to the PROFINET device and sets the TagFunction and TagLocation variables accordingly.

Signature

	SetTags (
		[in] IMTagSelectorEnumeration Tag_Selector,
		[in] String Tag_Function,
		[in] String Tag_Location
		);
	
Argument Description
Tag_SelectorIf FUNCTION, Tag_Function shall be written, If LOCATION, Tag_Location shall be written, if BOTH both.
Tag_FunctionString containing the new I&M1 | IM_Tag_Function to be written remanent to the device.
Tag_LocationString containing the new I&M1 | IM_Tag_Location to be written remanent to the device.

Method Result Codes

ResultCode Description
Bad_InvalidArgumentThe Server is not able to apply an argument. The argument may be too long or may contain invalid characters.
Bad_UnexpectedErrorThe Server is not able to apply the name because an unexpected error occurred. The device might be temporarily unavailable or unreachable due to network failure.
6.3.1.8.1.2 SetDate Method

This optional method writes the I&M2 field IM_Date remanent to the PROFINET device and sets the Date variable accordingly.

Signature

	SetDate (
		[in] DateTime IM_Date
		);
	
Argument Description
IM_DateNew I&M2 | IM_Date to be written remanent to the device.

Method Result Codes

ResultCode Description
Bad_InvalidArgumentThe Server is not able to apply an argument.
Bad_UnexpectedErrorThe Server is not able to apply the name because an unexpected error occurred. The device might be temporarily unavailable or unreachable due to network failure.
6.3.1.8.1.3 SetDescriptor Method

This optional method writes the I&M3 field IM_Descriptor remanent to the PROFINET device and sets the Descriptor variable accordingly.

Signature

	SetDescriptor (
		[in] String Descriptor
		);
	
Argument Description
DescriptorNew I&M3 | IM_Descriptor to be written remanent to the device.

Method Result Codes

ResultCode Description
Bad_InvalidArgumentThe Server is not able to apply an argument. The argument may be too long or may contain invalid characters.
Bad_UnexpectedErrorThe Server is not able to apply the name because an unexpected error occurred. The device might be temporarily unavailable or unreachable due to network failure.
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”.

6.3.1.8.3 PnAssetContainerType
Table 65 – PnAssetContainerType Definition
Attribute Value
BrowseNamePnAssetContainerType
IsAbstractFalse
ReferencesNode ClassBrowseName DataTypeTypeDefinitionModelling Rule
Subtype of BaseObjectType defined in [OPC 10000-5].
HasPnAssetObject<Assets>PnAssetType

Optional

Placeholder