Commissioning
11.9 Identification and maintenance data
11.9.2
Record structure for I&M data
Reading I&M records via user program (centrally and distributed via PROFINET IO)
Use Read data record ("RDREC" instruction) to access specific identification data. Under the
associated record index you obtain the corresponding part of the identification data.
The records are structured as follows:
Table 11- 6
Header information
BlockType
BlockLength
BlockVersionHigh
BlockVersionLow
Identification data
Identification data
(see table below)
Table 11- 7
Record structure for I&M identification data
Identification data
Identification data 0: (record index AFF0
VendorIDHigh
VendorIDLow
Order_ID
IM_SERIAL_NUMBER
IM_HARDWARE_REVISION
IM_SOFTWARE_REVISION
SWRevisionPrefix
•
IM_SWRevision_Functional_
•
Enhancement
IM_SWRevision_Bug_Fix
•
254
Basic structure of data records with I&M identification data
Contents
2
2
1
1
I&M0/Index AFF0
I&M1/Index AFF1
I&M2/Index AFF2
I&M3/Index AFF3
Access
)
H
read (1 bytes)
0000
read (1 bytes)
002A
read (20 bytes)
6ES7516-3AN00-0AB0
read (16 bytes)
-
read (2 bytes)
1
read
Firmware version
(1 byte)
V
(1 byte)
0000
(1 byte)
0000
Length (bytes)
: 54
H
: 54
H
: 16
H
: 54
H
Example
Vendor name
H
(002A
H
Part number of the module
(e.g. CPU 1516-3 PN/DP)
Serial number (device-specific)
corresponds to hardware version
(e.g. 1)
Provides information about the firmware
version of the module (e.g. V1.0.0)
- 00FF
H
H
- 00FF
H
H
System Manual, 12/2017, A5E03461182-AE
Coding (hex)
I&M0: 0020
H
I&M1: 0021
H
I&M2: 0022
H
I&M3: 0023
H
I&M0: 0038
H
I&M1: 0038
H
I&M2: 0012
H
I&M3: 0038
H
01
00
-
-
-
-
Explanation
= SIEMENS AG)
H
Automation system