Siemens 6RA7086-6KS22

05.05 Start-Up
SIEMENS AG 6RX1700-0AD76 7-57
SIMOREG DC Master Operating Instructions
7.7.9 Structure of request/response telegrams
There is no basic difference between the useful data area in the request and response telegrams
for PROFIBUS and CAN Bus. There are differences, for example, in the protocol frame and in the
sequence in which H and L bytes are transmitted. The structures shown here are those of a
SIMOREG DC Master, i.e. the values are displayed in the same way as they would be for
parameters n733 and n735, for example. The structure of the protocol frame and the transmission
sequence of bytes are therefore described where necessary in the sections containing the start-up
description for the appropriate board.
Each request and each response basically comprises three areas apart from the telegram frame
with header and trailer:
Header
Trailer
Index
IND
Parameter value
PWE
Parameter identifier
PKE
The parameter identifier (PKE) contains a request or response identifier (i.e. type of request or
response) and the number of the addressed parameter. The spontaneous signaling bit SPM (bit11)
is not used on the SIMOREG DC master.
Header Trailer
Index
IND
SPM
Parameter value
PWE
Parameter identifier
PKE
Task/ response
identifier
Parameter number (PNU)
Bits 0 to 10 contain the number of the parameter specified in the request.
Owing to the length restriction of the bit field (11 bits), a parameter number (PNU) higher than
1999 must be converted to another code for use in the parameter identifier; the Page Select Bit in
the index is used for this purpose:
Parameter
area
Displayed
number
Input on OP1S PNU in parameter
identifier
Page Select Bit
(index bit 15)
Pxxx, rxxx
0 - 999 0 - 999 0
Basic unit
Uxxx, nxxx
2000 - 2999 0 - 999 1
Hxxx, dxxx
1000 - 1999 1000 - 1999 0
Technology
board
Lxxx, cxxx
3000 - 3999 1000 - 1999 1
In the case of a request, for example, which specifies parameter U280 (2280), therefore, PNU =
280 must be entered in the parameter identifier and bit 15 set in the index.