Structure Of Request/Response Telegrams - Siemens 6RA7086-6KS22 Operating Instructions Manual

6ra70 series, microprocessor-based converters from 6kw to 2500kw for variable-speed dc drives, simoreg dc master

Table of Contents

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:

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.

Task/ response

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:

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.

6RX1700-0AD76

SIMOREG DC Master

Operating Instructions

Parameter identifier

Parameter identifier

Parameter number (PNU)

Input on OP1S

Parameter value

Parameter value

PNU in parameter

Page Select Bit

(index bit 15)

Show Quick Links

Table of Contents