Lenze L-force CANopen EMF2178IB - Page 130

Codes
Communication−relevant Lenze codes
14
l
130
EDSMF2178IB EN 3.0
C1856/C2356:
Boot−up− and cycle times
Code Subcode Index
Possible settings
Data type
Lenze Selection
C1856
/1: Boot−up time
/2: Cycle time CAN−OUT1
/3: Cycle time CAN−OUT2
/4: Cycle time CAN−OUT3
/5: Sync Tx cycle time
22719 =
0x58BF
0 ms 0 [1 ms] 65535 FIX32
C2356 22219 =
0x56CB
In the event−controlled/cyclic operation it is possible to define the cycle times with which
the single PDOs will be sent via the CAN bus (also see code C1875/C2375, "Tx mode" for
CAN−OUT1 ... 3).
) Note!
The value "0" deactivates the cyclic sending of the PDO.
"Sync Tx cycle time" (C1856/5, C2356/5) describes the interval time (in ms) that is required
for sending a sync telegram to the CAN bus.
Relation to CANopen
ƒ The object I−1006 (communication cycle period) has a direct influence on subcode
C1856/5 or C2356/5.
– As the data processing speed of the EMF2178IB communication module amounts
to 1000 ms, the entry via the object I−1006 is rounded to an integer multiple of
1000 ms and stored under C1856/5 or C2356/5 (depending on the standard device).
– When the object I−1006 is read, the content of the corresponding subcode (in ms) is
returned as a response.
– When a value is entered under subcode C1856/5 or C2356/5, bit30 of the object
I−1005 (COB−ID SYNC message) is set automatically and the communication
module sends a sync telegram.
ƒ The objects I−1800/5 ... I−1802/5 (TPDO Event Timer) have a direct influence on the
subcodes C1856/2 ... 4 or C2356/2 ... 4. Newly entered values in the objects
I−1800/5 ... I−1802/5 are also transferred to the subcodes C1856/2 ... 4 or
C2356/2 ... 4.