Implementation options
The following technical variants are possible for external TwinCAT synchronization (as of 2022-08)
Consecutive no. | Name | Evaluation | Example illustration |
|---|---|---|---|
1 | EtherCAT data exchange device (EL6692/6695 bridge terminal, FC11xx EtherCAT slave card) 2 EtherCAT systems are directly coupled for data exchange and DC time synchronization | Best possible time (DC) coupling; master IPC sets the absolute time; only 2 partners possible (if more then linking necessary) |
|
2 | PTP IEE1588 n EtherCAT systems are coupled to a PTP network via EL6688; an EL6688 may also be the time master | Good time coupling; complex network technology required for best results; n devices possible |
|
3 | TF6225 and EL1252 n EtherCAT systems are coupled via a wire connection | Best possible time (DC) coupling; if absolute time needs to be transferred, this must be done via secondary communication, e.g. via NMEA0183 via serial RS line |
|
4 | CU2508 2 EtherCAT systems are coupled directly via one CU2508 each, for DC time synchronization
| Best possible time (DC) coupling; master IPC sets the absolute time; |
|
5 | NTP n controllers are synchronized with each other in an NTP network | Moderately good time coupling; no tracking of TwinCAT Realtime! Only the absolute time is available in the IPC for further application-side use in the PLC |
|
