Sercos telegrams in the real-time channel are processed on the fly via individual network devices during the cycle. The telegrams are therefore only delayed by a few nanoseconds because the whole protocol process is carried out in hardware. In this way, network performance is independent of protocol stack, CPU performance or software implementation transmission times.
Given that additional network infrastructure components (such as hubs or switches) are avoided, transmission times are reduced to a minimum throughout the network.
Subsequent communication mechanisms are available in the real-time channel:
- M/S (Master/Slave): Exchange of functional data between masters and slaves in an M/S connection.
- DCC (Direct Cross Communication): direct cross communication between devices in a DCC connection, either between control systems or between any periphery slaves (e.g. drive, I/O, camera, gateway).
- SVC (Service Channel): Exchange of service data that is based on demand in a SVC channel as a component in real-time communication.
- SMP (Sercos Messaging Protocol): Transmitting functional data from several devices in one time slot by using a multiplex process configured in an M/S or DCC connection.
- Sercos safety: Exchange of safety-related data in a M/S or DCC connection, e.g. disabling or approval signals or other set values.
Years of positive experience using Sercos control systems and drives led us to install Sercos as a system bus for our machines and plants. Thanks to Sercos’ real-time performance for motion, safety, vision and I/O as well as the possibility of integrating TCP/IP services easily, cabling and engineering was made considerably easier.