Commissioning
8.3 Identification and maintenance data
Distributed I/O system
System Manual, 02/2018, A5E31861578-AF
77
The following table shows the structure of data records for I&M identification data.
Table 8- 4 Data record structure for I&M identification data
Identification data 0: (data record index AFF0 hex)
VendorIDHigh read (1 byte) 00
H
This is where the name of the manufac-
turer is stored (42
D
= SIEMENS AG).
H
Order_ID read (20 bytes) 6ES7157-1AB00-0AB0 Order number of the module (e.g. of
PROFINET interface module)
Serial number (device-specific)
Corresponding hardware version
Provides information about the firmware
version of the module
• SWRevisionPrefix
(1 byte) V
• IM_SWRevision_Functional_
Enhancement
(1 byte) 00 - FF
H
• IM_SWRevision_Bug_Fix
(1 byte) 00 - FF
H
• IM_SWRevision_Internal_Ch
ange
(1 byte) 00 - FF
H
IM_REVISION_COUNTER read (2 bytes) 0000
H
provides information about configured
changes on the module
H
0101
H
provides information about the version of
the identification data
(0101
H
= Version 1.1)
• IM_Version_Major
(1 byte)
• IM_Version_Minor
(1 byte)
IM_SUPPORTED read (2 bytes) 001E
H
provides information about the existing
identification data (I&M1 though I&M4)
Maintenance data 1: (data record index AFF1 hex)
IM_TAG_FUNCTION Read/write
- Enter an identifier for the module here,
that is unique plant-wide.
IM_TAG_LOCATION Read/write
(22 bytes)
- Enter the installation location of the mod-
ule here.
Maintenance data 2: (data record index AFF2 hex)
IM_DATE Read/write
(16 bytes)
YYYY-MM-DD HH:MM Enter the installation date of the module
here.
Maintenance data 3: (data record index AFF3 hex)
IM_DESCRIPTOR Read/write
- Enter a comment describing the module.
Reading I&M data records with data record 255 (distributed via PROFIBUS DP)
The modules support standardized access to identification data using DR 255 (index 65000
to 65003). For additional information on the DR 255 data structure, refer to the specifications
of the Profile Guideline - Order No. 3.502.