Commissioning
10.9 Identification and maintenance data
Distributed I/O system
System Manual, 12/2016, A5E03576849-AG
223
10.9.2
Data record structure for I&M data
Reading I&M data records (distributed via PROFINET IO)
You can directly access specific identification data by selecting Read data record (RDREC
instruction). You obtain the corresponding part of the identification data under the relevant
data record index.
The data records are structured as follows:
Table 10- 9 Basic structure of data records with I&M identification data
Content
Length (bytes)
Coding (hex)
Header information
BlockType
2
I&M0: 0020
H
I&M1: 0021
H
I&M2: 0022
H
I&M3: 0023
H
BlockLength
2
I&M0: 0038
H
I&M1: 0038
H
I&M2: 0012
H
I&M3: 0038
H
BlockVersionHigh
1
01
BlockVersionLow
1
00
Identification data
Identification data
(see table below)
I&M0/index AFF0
H
: 54
I&M1/index AFF1
H
: 54
I&M2/index AFF2
H
: 16
I&M3/index AFF3
H
: 54
Table 10- 10 Data record structure for I&M identification data
Identification data
Access
Default
Explanation
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).
VendorIDLow
Read (1 byte)
2 A
H
Order_ID
Read (20 bytes) 6ES7155-6AU00-0BN0
Article number of the module (e.g. of the
interface module)
IM_SERIAL_NUMBER
Read (16 bytes) -
Serial number (device-specific)
IM_HARDWARE_REVISION
Read (2 bytes)
1
Corresponding HW version
IM_SOFTWARE_REVISION
Read
Firmware 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
Summary of Contents for Simantic ET200SP
Page 1: ......