1769-L27ERM-QBFC1B

During development, safety and standard have the same rules. The following are allowed: • Multiple programmers • Online editing • Forcing Once the project is tested and ready for final validation, apply the safety application signature and safety-lock the application. This process sets the safety task to a SIL 3 integrity level. The Compact GuardLogix controller enforces the SIL 3 integrity level. When safety memory is locked and protected, the safety logic can’t be modified and all safety functions operate with SIL 3 integrity. On the standard side of the Compact GuardLogix controller, all functions operate like a regular Logix controller. Thus online editing, forcing, and other activities are all allowed. Standard logic and external devices, like HMIs or other controllers, can read safety memory with this level of integration. This level of integration removes the need to condition safety memory for use elsewhere. The result is easy systemwide integration and the ability to display safety status on displays or marquees. Use Guard I/O™ modules for field device connectivity. For safety interlocking between Compact GuardLogix controllers, use Ethernet or ControlNet® networks. Multiple Compact GuardLogix controllers can share safety data for zone to zone interlocking, or one Compact GuardLogix controller can use remote distributed safety I/O between different cells/areas.

Topic Page Summary of Changes 2 Catalog Numbers 2 CompactLogix 5370 Controllers 3 Armor CompactLogix and Armor Compact GuardLogix Controllers 25 1769 Packaged CompactLogix Controllers with Embedded I/O 29 1769 Modular CompactLogix Controllers 35 1768 CompactLogix Controllers 38 Controller Memory Use 41 Controller Compatibility 41 Controller Connections 43 CompactLogix Controller Accessories 45 Additional Resources 47