Home Site Map Contact
News Technology Development Tools Certification Literature Support Organization Products
Introduction to Sercos
Three Generations
Implementation of Sercos
Certification of Sercos Devices
Worldwide Availability
Applications Types
Sercos III
Sercos I and II
Sercos Standardization
Implementation of Sercos

Manufacturers can easily integrate Sercos into their own systems. Sercos II hardware is based on the SERCON816 ASIC which can be used to implement master and slave devices. It simplifies the task of the designer by automatically handling most Sercos interface communication functions.

Various hardware and software options are available for Sercos III. Connectivity is provided by a communication controller based on an FPGA logic chip, a general-purpose multiprotocol Ethernet controller, or a standard Ethernet controller (soft master). The Sercos III IP core is licensed from Sercos international and is provided either as a bitstream or as a netlist. The latter option allows the combination of the Sercos III IP core with other IPs (e.g., CPU core, PCI core) to realize SoPC (System on a Programmable Chip) solutions.

Hilscherís netX multi-protocol Ethernet controller supports Sercos III master and slave connectivity. The netX controllers are available in a number of versions which cover the performance spectrum from simple I/O controllers and drives to master controllers and control systems.

Fully assembled hardware boards can be used to connect standard PCs to a Sercos network. Versions are available with a dedicated CPU (active boards) and without a CPU (passive boards). Cards are integrated via common bus systems such as PCI or SPI. Several companies offer drivers or protocol stack software for master and slave implementations on different operating systems. Furthermore, training, consulting and support are offered. 

Using a soft master, a Sercos III master can be implemented without any special hardware. Standard Ethernet controllers are used instead of specific Sercos III hardware. Sercos-specific hardware functions are moved to the hardware-related and real-time-capable part of the master driver. Thus, a master can be fully implemented in software. Such a concept is useful for PC-based control platforms that have an onboard Ethernet interface.