5
5.6 Net data (PKW and PZD area)
5-255
Siemens AG 2005 All Rights Reserved
SIMODRIVE 611 universal Description of Functions (FBU) – 04.05 Edition
5.6.5 Configuring process data (from SW 3.1)
The process data structure of the telegram can be defined and configu-
red as follows:
1. By selecting a standard telegram (P0922 > 0)
Examples:
– P0922 = 1 standard telegram for n
set
interface 16 bit
– P0922 = 101 telegram is as for SW 2.4
(dependent on the operating mode)
2. By freely–configuring the telegram (P0922 = 0)
Example:
– P0922 = 0 Before SW 4.1:
PZD1 to PZD4 are defined as standard
PZD5 to PZD16 can be freely configured
From SW 4.1:
PZD1 remains defined as standard
PZD2 to PZD16 can be freely configured
Setpoint direction
(refer to the parameter overview for P0915:17)
e.g.:
P0915:5 = xxxx (required signal ID)
P0915:6 = yyyy ...
or
Actual value direction
(refer to the parameter overview for P0916:17)
e.g.:
P0916:5 = uuuu (requested signal ID)
P0916:6 = vvvv ...
Note
Standard signals, defined in the PROFIdrive Profile as well as special
signals only defined for the ”DP slave 611U” can be configured as
setpoints/actual values.
For double–word signals (32 bits) the appropriate signal ID must be
configured twice on adjacent process data.
Example:
P0916:7 = 50011 ––> G1_XIST1 is assigned to PZD7
P0916:8 = 50011 ––> G1_XIST1 is assigned to PZD8
––> as G1_XIST1 is a double word (32 bits), it must be assigned
2 PZDs.
Description
5 Communications via PROFIBUS DP
07.0108.01
To Next Page
Loading...
