%0 Generic %1 LechlerSchlechtendahlLeursEtAl2012 %A Lechler, A. %A Schlechtendahl, J. %A Leurs, L. %A Verl, A. %D 2012 %K Echtzeit ISW Kommunikation Sicherheit xsl %P -- %T Make CIP Safety Your Safety Protocol %X The use of fieldbuses in automation systems instead of hard wired interactionbetween components provides a number of well-known advantages like lowercosts, more flexibility, new functionalities and higher dynamics. Forinteractions which are needed to fulfill safety requirements, hard-wiredconnections are still being used in parallel to the fieldbus wire. In order toreap the aforementioned advantages for the case of safety connections, asafety protocol needs to be integrated into the fieldbus communication layers.The inherent failure rate of fieldbus protocols is generally much higher thanthat allowed in international standards for safety applications. This paperwill focus on the steps that are required to adapt the safety protocol CIPSafety™ to a non-CIP fieldbus. It will explain in detail which steps withrespect to specification, TÜV involvement, and conformance testing softwaremodification have to be taken to make CIP Safety the safety protocol of afieldbus. This paper will use the example of the successful CIP Safetyintegration on top of the existing sercos III communication layer.

@misc{LechlerSchlechtendahlLeursEtAl2012, __markedentry = {[xtl:6]}, abstract = {The use of fieldbuses in automation systems instead of hard wired interactionbetween components provides a number of well-known advantages like lowercosts, more flexibility, new functionalities and higher dynamics. Forinteractions which are needed to fulfill safety requirements, hard-wiredconnections are still being used in parallel to the fieldbus wire. In order toreap the aforementioned advantages for the case of safety connections, asafety protocol needs to be integrated into the fieldbus communication layers.The inherent failure rate of fieldbus protocols is generally much higher thanthat allowed in international standards for safety applications. This paperwill focus on the steps that are required to adapt the safety protocol CIPSafety™ to a non-CIP fieldbus. It will explain in detail which steps withrespect to specification, TÜV involvement, and conformance testing softwaremodification have to be taken to make CIP Safety the safety protocol of afieldbus. This paper will use the example of the successful CIP Safetyintegration on top of the existing sercos III communication layer.}, added-at = {2016-03-03T09:53:12.000+0100}, author = {Lechler, A. and Schlechtendahl, J. and Leurs, L. and Verl, A.}, biburl = {https://puma.ub.uni-stuttgart.de/bibtex/2a0a99df7f63a45ee3daf65443a5f3ba2/isw-bibliothek}, interhash = {ee3d0c0ca4802880b7d46810133355c2}, intrahash = {a0a99df7f63a45ee3daf65443a5f3ba2}, keywords = {Echtzeit ISW Kommunikation Sicherheit xsl}, pages = {--}, timestamp = {2016-03-08T15:14:12.000+0100}, title = {Make CIP Safety Your Safety Protocol}, year = 2012 }