7 synchronisation, 1 fif-can sync response, 2 fif-can sync identifier – Lenze DDS System bus CAN for PLC User Manual
Page 67: 3 fif-can sync tx transmission cycle, Synchronisation, Fif−can sync response, Fif−can sync identifier, Fif−can sync tx transmission cycle, System bus (can) for lenze plc devices, Configuration (fif interface)
System bus (CAN) for Lenze PLC devices
Configuration (FIF interface)
5−7
l
PLC−Systembus EN 2.0
5.7
Synchronisation
Tip!
By means of the CAN_Synchronization SB, the internal time base of the PLC can be synchronised
with the arrival of the sync telegram.
Thus the internal calculating processes (e. g. control oriented processes) of the PLC can be
synchronised with the calculating processes of other nodes which can also process the sync
telegram.
Detailed information on the CAN_Synchronization SB can be found in chapter 7.7.
(
^ 7−23)
5.7.1
FIF−CAN sync response
The response to the reception of a sync telegram can be configured via C2466:
Code
LCD
Possible settings
IMPORTANT
Lenze
Selection
C2466 Sync response
1
FIF−CAN sync response
0
No response
No response
1
Response to sync
PLC responds to a sync telegram
by sending the FIF−CAN1_OUT
object.
5.7.2
FIF−CAN sync identifier
The transmission or reception identifiers of the sync telegram can be configured via C2467/C2468:
Code
LCD
Possible settings
IMPORTANT
Lenze
Selection
C2467 Sync Rx Id
128
1
{1}
256 FIF−CAN sync Rx identifier
Receive identifier for the sync
telegram
C2468 Sync Tx Id
128
1
{1}
256 FIF−CAN sync Tx identifier
Send identifier for the sync
telegram
5.7.3
FIF−CAN sync Tx transmission cycle
The cycle time within which a sync telegram with the identifier set in C2468 is transmitted can be
configured via C2469:
Code
LCD
Possible settings
IMPORTANT
Lenze
Selection
C2469 Sync Tx time
0
0
{1 ms}
65000
0 = Off
FIF−CAN sync time
Sync transmission telegram cycle