Principles, Standards and Implementation

Catalogs > Safety Products Catalog > Principles, Standards and Implementation > Protective Measures and Complementary Equipment

Protective Measures and Complementary Equipment

Integrated Safety Controllers

Safety control solutions now provide complete integration within a single control architecture where safety and standard control functions reside and work together. The ability to perform motion, drive, process, batch, high speed sequential, and SIL 3 safety in one controller provides significant benefits. The integration of safety and standard control provides the opportunity to utilize common tools and technologies which reduce costs associated with design, installation, commissioning and maintenance. The ability to utilize common control hardware, distributed safety I/O or devices on safety networks and common HMI devices reduce purchase and maintenance costs, and also reduce development time. All of these features improve productivity, the speed associated with troubleshooting and the lowering of training costs due to commonality.

Figure 96 shows an example of the integration of control and safety. The standard non-safety related control functions reside in the Main Task. The safety related functions reside in the Safety Task.

Figure 96: Integrated Safety and Nonsafety Tasks

All standard and safety related functions are isolated from each other. Figure 97 shows a block diagram of allowed interaction between the standard and safety portions of the application. For example, safety tags can be directly read by the standard logic. Safety tags can be exchanged between GuardLogix controllers over EtherNet, ControlNet or DeviceNet. Safety tag data can be directly read by external devices, Human Machine Interfaces (HMI), personal computers (PC) or other controllers.

Figure 97: Standard and Safety Task Interaction

1.	Standard tags and logic behave the same as ControlLogix.
2.	Standard tag data, program or controller scoped and external devices, HMI, PC’s, other controllers, etc.
3.	As an integrated controller, GuardLogix provides the ability to move (map) standard tag data into safety tags for use within the safety task. This is to provide users the ability read status information from the standard side of GuardLogix. This data must not be used to directly control a safety output.
4.	Safety tags can be directly read by standard logic.
5.	Safety tags can be read or written by safety logic.
6.	Safety tags can be exchanged between GuardLogix controllers over EtherNet.
7.	Safety tag data, program or controller scoped can be read by external devices, HMIs, PCs, other controllers, etc. Note, once this data is read, it is considered standard data, not safety data.