Lenze ECSCPxxx - Manual (Page 278)

Configuration
Configuring MotionBus/system bus (CAN)
Axis synchronisation (CAN synchronisation)
8
l
278 EDBCSXP064 EN 8.0
8.1.7 Axis synchronisation (CAN synchronisation)
By means of the axis synchronisation, the internal time base can be synchronised with the
instant of reception of the sync signal. By this, the start of cyclic internal processes of all
drives involved in the synchronisation is synchronous.
Sync signal source
The sync signal source is set via C1120:
Code Possible settings IMPORTANT
No. Designation Lenze/
{Appl.} Selection
C1120 Sync mode 0 Sync signal source ^ 278
0 Off Off
1 CAN sync Sync connection via interface X4
(CAN) ^ 282
2 Terminal sync Sync connection via terminal
X6/DI1 ^ 283
Synchronisation cycle
For the purpose of synchronisation the master sends a cyclic CAN sync telegram.
The controllers receive the CAN sync telegram and control the starting time of their own
program cycle in relation to the instant of reception of the CAN sync signal. The start is to
be offset by the synchronisation phase (C1122).
The synchronisation cycle set under C1121 must be set the same as the transmission cycle
of the CAN sync telegrams.
Code Possible settings IMPORTANT
No. Designation Lenze/
{Appl.} Selection
C1121 Sync cycle 2 Synchronisation cycle ^ 278
1 {1 ms} 13
Phase shift
The synchronisation phase (C1122) defines the period of time of the offset by which the
start of the controller−internal cycle lags behind the sync signal received.
)
Note!
Always set the synchronisation phase higher than the maximum possible
"jitter" of the received CAN sync telegrams!
phase shifting and thus periodic changes of signal frequencies are called
"Jitter".
Code Possible settings IMPORTANT
No. Designation Lenze/
{Appl.} Selection
C1122 Sync phase 0.460 Synchronisation phase ^ 278
0.000 {0.001 ms} 6.500