Implemented canopen objects – Lenze EMF2178IB User Manual
Page 113

Implemented CANopen objects
Overview
I−1800 ... I−1802: Transmit PDO communication parameters
l
113
EDSMF2178IB EN 3.0
Description of subindex 1
Data telegram assignment
Byte 8
7th byte
Byte 6
Byte 5
MSB
U32
LSB
31
30
29
28
...
11
10
...
0
0/1
0/1
0
Bit value: 0
11−bit identifier
Bits
Value
Description
0 ... 10
X
11−bit identifier
11 ... 29
0
The extended identifier is not supported. Any of these bits must be "0".
30
0
RTR to TPDO possible (Lenze)
1
RTR to TPDO not possible (cannot be set)
31
0
TPDO active
1
TPDO not active
Description of subindex 2
PDO transmission
Transmission type
Description
cyclic
synchronous
event−control
led
X
X
n = 1 ... 240
By entering value n, this TPDO will be
accepted by every n−th sync.
X
n = 252
By sync, TPDO will be filled with new
data, but only sent on RTR.
X
n = 254
Manufacturer−specific,
see code C1875 / C2375
Description of subindex 3
Minimum time between two process data telegrams.
)
Note!
Subindex 3 = 0: Inhibit time deactivated.
Description of subindex 5
With event−controlled/cyclic operation, you can set the cycle time for sending PDOs via the
CAN bus.
)
Note!
Subindex 5 = 0: Cyclic PDO sending deactivated.