Lenze 931K - Manual (Page 24)

CANopen over EtherCAT (CoE)
New communication objects
New and changed CANopen communication objects under CoE
8
l
24 KHB 13.0005−EN 1.0
Object 0x1C10 − Sync Manager Channel 0 (Mailbox Receive)
Via this object a PDO for sync channel 0 can be configured. Since sync channel 0 is always
assigned by the mailbox telegram protocol, this object cannot be changed by the user. Thus
the object always has the following values:
Sync Manager Channel 0 (Mailbox Receive)
Index 0x1C10
Name Sync Manager Channel 0 (Mailbox Receive)
Object code Array
Data type UINT8
Sync Manager Channel 0 (Mailbox Receive)
Subindex 0
Description Number of assigned PDOs
Access ro
PDO Mapping no
Value Range 0 (no PDO assigned to this channel)
Default Value 0 (no PDO assigned to this channel)
)
Note!
The name "Number of assigned PDOs that is defined for subindex 0 of these
objects by the EtherCAT specification is misleading here, as the sync manager
channels 0 and 1 are always assigned by the mailbox telegram. In this
telegram type SDOs are always transmitted under EtherCAT CoE. Subindex 0 of
these objects thus remains unused.
Object 0x1C11 − Sync Manager Channel 1 (Mailbox Send)
Via this object a PDO for sync channel 1 can be configured. Since sync channel 1 is always
assigned by the mailbox telegram protocol, this object cannot be changed by the user. Thus
the object always has the following values:
Sync Manager Channel 1 (Mailbox Send)
Index 0x1C11
Name Sync Manager Channel 1 (Mailbox Send)
Object code Array
Data type UINT8
Sync Manager Channel 1 (Mailbox Send)
Subindex 0
Description Number of assigned PDOs
Access ro
PDO Mapping no
Value Range 0 (no PDO assigned to this channel)
Default Value 0 (no PDO assigned to this channel)