Home Site Map Contact
News Technology Development Tools Certification Literature Support Organization Products
Introduction to Sercos interface
Advantages
Applications Types
Sercos III
Introduction
General Architecture
Features
Sercos III Profiles
Performance
Blended Infrastructure
Additional Resources
Sercos I and II
Sercos Standardization
  Application Layer
  I/O Profile
CIP Safety on Sercos
  Controller-to-Controller Profile
  Energy Profile
Encoder Profile
Packaging Profile


CIP Safety on Sercos

CIP Safety on Sercos is a function-specific profile (FSP Safety) used to transfer safety-related data on Sercos III. CIP Safety on Sercos is based on the ODVA (Open DeviceNet Vendors Association) CIP Safety™ safety protocol. It provides for safe data transmission over Sercos III up to SIL 3 (Safety Integrity Level) according to IEC 61508. 

No additional safety bus is required, as the safety information is sent in addition to the standard data on the Sercos network. The combination of drives, I/O, peripheral devices, safety bus and standard Ethernet in a single network simplifies handling and reduces hardware and installation costs, plus it makes it easier to deploy integrated safety controllers and homogeneous safety solutions.

With CIP Safety on Sercos, data is sent on the same medium using the same connections as standard communication. The function of the cross-media CIP Safety protocol is performed by the end units, making it possible to simultaneously operate standard and safety devices in the same network. Reliable communication can take place between all network levels, including peer-to-peer communication and cross-network communication. The master does not necessarily have to be a safety controller. It can also route data without being able to interpret it. This makes it possible for users to flexibly configure the safety network architecture for implementation of safety programmable controllers or peer-to-peer communication between sensors and actuators.

The safety protocol uses the Sercos Messaging Protocol (SMP), which enables the representation of the CIP data and services on configured, cyclic data containers in the Sercos telegram. Due to the routing capability of the CIP Safety protocol, a safety network can stretch across several diverse communication networks (e.g., DeviceNet, Ethernet/IP, Sercos III). According to the CIP Safety specification, the safe data container embedded in the Sercos frame can contain between 2 and 250 Bytes of safe user data.


In addition, when combining Sercos safety with the fault tolerance provided by the hardware redundancy of Sercos III, safe, highly dependable automation solutions can be implemented for both centralized and decentralized safety applications.

The combination of CIP Safety with Sercos III allows users and suppliers to embark on a global standard instead of supporting different safety protocols. The extensions specified by Sercos international are included in Edition 2.2. of the CIP Safety specification and will be published in the IEC 61784-3 international safety standard.   Next >>


DeviceNet, CIP and CIP Safety are trademarks of Open DeviceNet Vendor Association, Inc. (ODVA). EtherNet/IP is a trademark of ControlNet International under license by ODVA.