Table of Contents
Advertisement
Table 6-62
Response for successful write operation
Value
Byte
Description
11 h
0
Slave address
06 h
1
Function code (write)
20 h
2
Number of following data bytes (20 h: 32 bytes corresponds to 16 registers)
0002 h
3,4
40601: DS47 Control = 2 (request was executed)
2F04 h
5,6
40602: Function code 2F h (47), response length 4 bytes
8002 h
7,8
40603: Request reference mirrored = 80 h,
response identifier = 2 (change parameter)
0101 h
9,10
40604: DO-ID = 1, number of parameters = 1
xx h
11
CRC "Low"
xx h
12
CRC "High"
Table 6-63
Response for unsuccessful write operation - write request still not completed
Value
Byte
Description
11 h
0
Slave address
06 h
1
Function code (write)
20 h
2
Number of following data bytes (20 h: 32 bytes corresponds to 16 registers)
0001 h
3,4
40601: DS47 Control = 1 (request is processed)
2F00 h
5,6
40602: Function 2F h(47), response length 0 (fault)
0004 h
7,8
40603: Error code:
issued)
xx h
9
CRC "Low"
xx h
10
CRC "High"
6.3.5.10
Communication procedure
Procedure for communication in a normal case
Normally, the master sends a telegram to a slave (address range 1 ... 247). The slave sends a
response telegram to the master. This response telegram mirrors the function code; the slave
enters its own address in the telegram and so the slave identifies itself with the master.
The slave only processes orders and telegrams which are directly addressed to it.
Communication error
If the slave detects a communication error on receipt (parity, CRC), it does not send a response
to the master (this can lead to "setpoint timeout").
SINAMICS G120X converter
Operating Instructions, 06/2019, FW V1.01, A5E44751209B AC
0004 Response Not Ready (response has still not been
Advanced commissioning
6.3 Drive control
259
Advertisement
Table of Contents
