Technical Paper Abstract
A functional gap in CIP Safety is being able to change parametric data in a safety I/O class device (or get data from a safety device) on-demand (when the need arises) based on safety program execution. Today, parametric data can only be sent when the device CIP Safety connection is opened, or by embedding parametric data as part of a safety output data assembly. Sending parametric data in the Forward_Open configuration block is not suitable for program driven parametric data exchange with a safety device. In fact, for a safety device, the configuration block of the Safety Open is part of the Safety Signature and cannot be modified programmatically without violating the devices safety signature. Using the Output Assembly for on-demand parameter data transfer is both wasteful and a misuse of I/O connection’s intent, not to mention that the number and complexity of the resulting assembly structures would explode.
With no effective mechanism for on-demand programmatic data exchange, CIP Safety systems limit the flexibility customers have for advanced safety applications, especially for motion safety related functions, and looking forward for high availability (SIS) safety systems.
Paper and presentation from the 2017 Industry Conference & 18th Annual Meeting of Members
Kevin Colloton, Rockwell Automation