Kunbus PROFINET IRT Slave, User Manual

Page: 22 / 40

Gateway PROFINET IRT Slave 22
All records are addressed via API 0, Slot 0, Subslot 1. The data is transferred in Big Endian format.
In the Big Endian format, the higher-value bytes are transmitted first and stored at the memory
locations with the lowest addresses.
Two bytes are always addressed per index:
Offset 0 + Offset 1 → Record 0
Offset 510 + Offset 511 → Record 255 (0x00ff)
Index 0x0000 - 0x00ff contains the input data sent by the partner gateway component.
Index 0x1000 - 0x10ff contains the output data sent to the partner gateway component.
State of the Partner Gateway Component
You can read information about the state of the partner gateway component via API 0, Slot 0,
Subslot 1, Index 0x2000 :
Offset Length Element Comment
0 4 Serial number
4 2 Module type KUNBUS internal module type
6 2 Hardware revision
8 2 Major software version
10 2 Minor software version
12 4 Subversion revision Source code versioning
16 2 Fieldbus input length
18 2 Fieldbus output length
20 1 Bus state
20 2 Feature descriptor Supported features of the gateway com-
ponent
5.4.1 I&M Data
Identification & Maintenance Data
I&M data are data structures that are used to uniquely identify the gateway component in the
PROFINET network.
The gateway component supports the I&M data 0-4. This I&M data is available in Slot 0, Subslot 1.
The data can be read and if necessary written by the PROFINET controller via the data index
0xaff0-0xaff4.
I&M 0 Data
I&M 0 data contains information about the gateway component. They can be read by the
PROFINET controller via Record Read with Api 0, Slot 0, Subslot 1, Index 0xaff0.
You can find the following information on the gateway component via the I&M 0 data:
– Vendor ID
– Order ID
– Serial Number
– Hardware Revision
– Software Revision
– Revision Counter
– Profile ID
Configuration