SERVO, TM41 VECTOR CU_S A_INF, B_INF,
S_INF
TB30, TM31,
TM15DI_DO,
TM120,
TM150
ENCODER
Free connector-
binector convert‐
er
p2099[0 ... 1] / r2094.0 ... 15, r2095.0 ... 15
Send process data
DWORD connec‐
tor input
p2061[0 ... 26] p2061[0 ... 30] - - - p2061[0 ...
10]
WORD connec‐
tor input
p2051[0 ... 27] p2051[0 ... 31] p2051[0 ... 24] p2051[0 ... 9] p2051[0 ... 4] p2051[0 ...
11]
Free binector-
connector con‐
verter
p2080[0 ... 15], p2081[0 ... 15], p2082[0 ... 15], p2083[0 ... 15], p2084[0...15] / r2089[0 ... 4]
Telegram interconnections
● The telegram interconnection is made automatically and blocked.
Exceptions to this are the telegrams 20, 220, and 352. There, in addition to the fixed
interconnections, selected process data (PZD) can be interconnected as required in the
send/receive telegram.
● When you change p0922 ≠ 999 to p0922 = 999, the previous telegram interconnection is
retained and can now be changed.
● If p0922 = 999, a telegram can be selected in p2079. A telegram interconnection is
automatically made and blocked. The telegram can also be extended.
This is an easy method for creating extended telegram interconnections on the basis of
existing telegrams.
The telegram structure
● Parameter p0978 contains the drive objects that use a cyclic PZD exchange. All drive
objects after the first zero do not participate in the cyclic exchange.
● If the value 255 is written to p0978, this drive object is visible to the PROFIdrive controller
and empty (without the actual process data exchange). This permits cyclic communication
of a PROFIdrive controller in the following cases:
– with unchanged configuration to drive units that have a different number of drive objects.
– with deactivated drive objects, without having to change the project
● One PZD = one word.
Communication
A.1 Communication
Industrial Security
88 Configuration Manual, 08/2017, A5E36912609A
To Next Page
Loading...
