Parameterization and commissioning
CX8095
29
Version: 1.5
6.3
Configuration
6.3.1
CCAT adaptor
The CCAT adaptor is the driver for the various interfaces of the CX809x. It is found when the CX809x is
scanned and can then be used in conjunction with the real-time capable Ethernet protocols.
No settings at the CCAT adapter are required, and it does not have to be linked with a task. It only needs to
be present in the System Manager.
Note
Search for protocol or driver
The CCAT adaptor must be selected when searching for the EtherCAT Automation Proto-
col (EAP) or the driver for the RT-Ethernet communication. See also the corresponding
sections of the documentation (only CX8090).
Using the CCAT adapter for protocols that are not real-time capable
The CCAT adapter is not required if Ethernet protocols are used, which are not real-time capable. If the
CCAT adapter is only used for protocols, which are not real-time capable (interfaces X101 and X102), we
recommend deleting the CCAT adapter from the configuration in the System Manager. This ensures that the
CCAT is optimally registered in the operating system.
Examples of protocols, which are not real-time capable, include ModbusTCP/UDP, ADS, TCP/IP, OPC UA
and HTTP (HTML). The CCAT adapter must be deleted, if only protocols of this type are used.
Examples of real-time capable protocols include PROFINET, Ethernet/IP, BACnet/IP, RT Ethernet and EAP.
These protocols require the CCAT adapter.
For configurations containing both real-time capable protocols and protocols that are not real-time capable,
we recommend setting the task time as short as possible, in order to ensure that the non-real-time capable
protocols are relayed to the operating system quickly enough. The real-time capable protocols can be set to
a higher cycle time through the data exchange "factor". In this case the CCAT is triggered via a fast task,
while the real-time capable protocols can be operated with a slower cycle time.
Sample:
The task operates with 1 ms. If the factor is set to 8, the real-time capable protocol is processed with 8 ms.
The interface itself will continue to be processed with 1 ms.
If the task is set to 2 ms and the factor is left at 8, the RT Ethernet interface is processed with 16 ms.
Make sure you monitor your system load. If the system load is too high, telegrams may be discarded or
timeouts may occur. A system load of less than 60 % is recommended.
