Table of Contents
Advertisement
5 Communications via PROFIBUS DP
5.6
Net data (PKW and PZD area)
Task telegram,
IDs
Table 5-29
Task IDs (master ––> slave)
Task identifica-
tion
0
No task
1
Request parameter value
2
Change parameter value (word)
3
Change parameter value (double word)
4, 5
–
6
Request parameter value (array)
7
Change parameter value (array word)
8
Change parameter value (array double word)
9
Request number of array elements
10 (from SW 3.5)
Quickly change the parameter value (array, double
word)
Note:
S
All of the "SIMODRIVE 611 universal" parameters can be read and written into the using the task IDs
6, 8 and 10.
S
The negative response ID is 7.
S
The IDs are defined so that they indicate which fields of the PK interface must also be evaluated.
S
Task 8
Data is first calculated into the control and then a response telegram is sent
S
Task 10
Data is calculated into the control and a response telegram is sent at the same time
For example, in order to be able to issue a start task immediately after a traversing block has been
completely transferred, the last write task should have the ID 8.
Response
telegram,
IDs
5-274
The IDs for the task telegram (master ––> slave) should be taken from
the following table:
Function
The IDs for the response telegram (slave ––> master) can be taken
from the following table:
Table 5-30
Response IDs (slave ––> master)
Response ID
0
No response
1
Transfer parameter value (word)
2
Transfer parameter value (double word)
3
–
4
Transfer parameter value (array word)
5
Transfer parameter value (array double word)
6
Transfer number of array elements
7
Task cannot be executed (with error number)
8, 9 and 10
–
SIMODRIVE 611 universal Description of Functions (FBU) – 04.05 Edition
Response ID (positive)
0
1, 2
1
2
–
4, 5
4
5
6
5
Function
E Siemens AG 2005 All Rights Reserved
07.01
08.01
08.99
Advertisement
Chapters
Table of Contents
