5
5.6 Net data (PKW and PZD area)
5-274
Siemens AG 2005 All Rights Reserved
SIMODRIVE 611 universal Description of Functions (FBU) – 04.05 Edition
The IDs for the task telegram (master ––> slave) should be taken from
the following table:
Table 5-29 Task IDs (master ––> slave)
Task identifica-
tion
Function Response ID (positive)
0 No task 0
1 Request parameter value 1, 2
2 Change parameter value (word) 1
3 Change parameter value (double word) 2
4, 5 – –
6 Request parameter value (array) 4, 5
7 Change parameter value (array word) 4
8 Change parameter value (array double word) 5
9 Request number of array elements 6
10 (from SW 3.5) Quickly change the parameter value (array, double
word)
5
Note:
All of the ”SIMODRIVE 611 universal” parameters can be read and written into the using the task IDs
6, 8 and 10.
The negative response ID is 7.
The IDs are defined so that they indicate which fields of the PK interface must also be evaluated.
Task 8 Data is first calculated into the control and then a response telegram is sent
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.
The IDs for the response telegram (slave ––> master) can be taken
from the following table:
Table 5-30 Response IDs (slave ––> master)
Response ID
Function
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 –
Task telegram,
IDs
Response
telegram,
IDs
5 Communications via PROFIBUS DP
07.0108.01
To Next Page
Loading...
