30/6/23, 11:04 Safety FAQ - GuardLogix 5560 and GuardLogix 5570 Controllers

ID: IN5219 | Access Levels: Everyone

Safety FAQ - GuardLogix 5560 and

GuardLogix 5570 Controllers

Document ID IN5219

Published Date 10/02/2020

Summary
Safety FAQ - GuardLogix 5560 and GuardLogix 5570 Controllers

Content

Question
Where can I get some basic information on GuardLogix controllers?
What is GuardLogix?
Do I need to purchase the GuardLogix and Safety Partner modules separately?

Environment
1756-L71S
1756-L72S
1756-L73S
1756-L61S
ACEPTAR
1756-L62S
Al hacer clic en “Aceptar todas las cookies”, usted acepta que las
TODAS LAS
cookies se guarden en su dispositivo para mejorar la navegación del
1756-L63S COOKIES
sitio, analizar el uso del mismo, y colaborar con nuestros estudios para
marketing.

https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/44566 1/8
30/6/23, 11:04 Safety FAQ - GuardLogix 5560 and GuardLogix 5570 Controllers

Answer
Following is a list of Frequently Asked Questions, and their respective answers, for the GuardLogix line of safety
controllers.

NOTE: All 5560 (1756-L6xS) controllers have been discontinued, starting 1/June/2017

Q: What is the difference between GuardLogix and ControlLogix?

A: GuardLogix is ControlLogix with Safety added to it. ControlLogix Redundancy (high-availability) is NOT
supported with safety GuardLogix controllers. Besides the redundancy caveat, anything ControlLogix can do,
GuardLogix can do, with the addition of a Safety Task, Safety Instruction Set, and the ability to address Safety
I/O.

All other ControlLogix basics: instructions, motion (v17 only), tasks, non-safety I/O, etc. are the same and
function similarly. The only other exception to this statement is addressed in the next question.

Q: Does GuardLogix support CompactFLASH or other non-volatile memory?

A: Non-volatile memory is not supported in L6xS GuardLogix for application save/restore or transport prior to
v18. If using GuardLogix v16 or v17, you can still use the CompactFLASH to write/retrieve tag data using the
sample application installed with RSLogix 5000 v16.

Beginning with v18, L6xS GuardLogix CompactFLASH support is identical to ControlLogix, and allows for
application storage/retrieval and firmware supervisor.

Also see 39370 - Can the GuardLogix use a compactflash card?

Beginning with v20, L7xS controllers do NOT support CompactFLASH, but do support SD cards for program
storage and transport. Both L7xS processor and it’s partner L7SP have a SD slot. Only the L7xS processor ships
with a 1784-SD card.

Q: What SIL level can GuardLogix meet?

A: GuardLogix can be used in Safety Related applications up to and including SIL 3 (61508, 62061) and PLe (13849)
provided you have an independent safety risk assessment certify compliance and also adhere to the GuardLogix
Al hacer Systems
Controller clic en “Aceptar todas las cookies”,
Safety Reference usted acepta
Manual, publication que las
1756-rm093.
cookies se guarden en su dispositivo para mejorar la navegación del
sitio, analizar el uso del mismo, y colaborar con nuestros estudios para
Q:marketing.
Can the 1756-L6xS / L7xS be used without the Safety Partner (1756-LSP / L7SP)?

A: No. The GuardLogix controllers will not function without the Safety Partner present. If either one is powered
up in a rack without the other one, it will experience a major fault and be non-functional.
https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/44566 2/8
30/6/23, 11:04 Safety FAQ - GuardLogix 5560 and GuardLogix 5570 Controllers

Q: Which Safety Partner should I select / use with my GuardLogix controller?

A: The 1756-L6xS safety controllers only work with the 1756-LSP Safety Partner. 1756-L7xS safety controllers only
with the 1756-L7SP Safety Partner.

Q: So the GuardLogix controller and Safety Partner are a matched set?

A: In terms of hardware, no. They are purchased separately, so any L6xS controller and LSP Partner will work
together. In terms of firmware they can be considered a "matched set" as they must be at the exact same
revision.

Q: Is the LSP / L7SP a redundant processor that takes over when the Safety Controller faults or fails?

A: Absolutely NOT. The LSP / L7SP is a redundant processor to the safety controller, but not in the sense that it is
a high-availability system that tries to keep running in the event of a hardware failure.

Rather, the purpose of the LSP / L7SP is to execute the Safety Task in parallel with the GuardLogix controller, then
the two controllers compare results afterwards. If there is a mismatch in any way, a Safety Fault will occur and
the process will stop.

If the requirement for your application is high availability or to keep the system/machine running in the event of
a failure, a Safety Controller is not what you need. You should instead be looking at our ControlLogix Redundancy
system.

Q: If the LSP / L7SP does not take over for the GuardLogix controller, what exactly is the point of Safety?

A: Again, we must understand that there is a difference between Machine Safety, which is usually Failsafe, and
Process Safety (also known as High Availability). All GuardLogix systems are Machine Safe, the purpose of which
is not to keep running in the event of hardware failure. In such a Safety system, the primary requirement is that
no matter what fails in the system, or how it fails, we will always go to a safe mode (outputs OFF) when required.

Q: Can the 1756-L6xS / L7xS internal memory be expanded?

A:AlNo, it is clic
hacer fixedensize.
“Aceptar todas las cookies”, usted acepta que las
cookies se guarden en su dispositivo para mejorar la navegación del
1756-L61S has 2MB for standard task and components, 1MB for safety task and components, and 478KB for I/O
sitio, analizar el uso del mismo, y colaborar con nuestros estudios para
memory.
marketing.
1756-L62S has 4MB for standard task and components, 1MB for safety task and components, and 478KB for I/O

https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/44566 3/8
30/6/23, 11:04 Safety FAQ - GuardLogix 5560 and GuardLogix 5570 Controllers

memory.
1756-L63S has 8MB for standard task and components, 3.75MB for safety task and components, and 478KB for
I/O memory.

L63S is only supported in v17 and newer of RSLogix 5000.

1756-L71S has 2 MB for standard task and components, 1 MB for safety task and components, and 0.98MB for I/O
memory.
1756-L72S has 4 MB for standard task and components, 2 MB for safety task and components, and 0.98MB for I/O
memory.
1756-L73S has 8 MB for standard task and components, 4 MB for safety task and components, and 0.98MB for I/O
memory.

L7xS is only supported in v20 and newer of RSLogix 5000

Q: What firmware options do I have with GuardLogix?

A: GuardLogix was originally supported only in version 14, which was a unique release of RSLogix 5000 just for
safety. Starting with version 16, all major releases support GuardLogix.

Q: What is the minimum series and firmware revisions for hardware components (1756-DNB, 1756-ENBT, etc)?

A: Series and revisions are described in Chapter 1 of the GuardLogix Controller Systems Safety Reference
Manual, in the topic titled GuardLogix System Components.

1756-DNB minimum series A revision 6.2

1756-ENBT or EN2T minimum series A revision 3.6
1756-CN2 minimum series A revision 12.1

Q: Is the 1756-EN2T Series D compatible for use with GuardLogix Controllers?

A: In the Using ControlLogix in SIL 2 Applications Safety Reference Manual, Publication 1756-RM001, Page 41, it is
mentioned that the 1756-EN2T/D is — not for use with safety functions. This only applies to SIL 2 safety and does
not disqualify the 1756-EN2T/D from use with GuardLogix SIL 3 machine safety. Thus, the 1756-EN2T/D is
acceptable for use with GuardLogix.
Al hacer clic en “Aceptar todas las cookies”, usted acepta que las
cookies se guarden en su dispositivo para mejorar la navegación del
Q:sitio, analizar
Do I have el uso
to have del mismo,
a Safety Task yincolaborar con nuestros estudios para
my application?
marketing.
A: Yes. The controller and LSP / L7SP will fault if no Safety Task is present. The recommendation is to create a
Safety Task with at least some sample code within it (to decrease the possibility of the task executing too quickly
and triggering watchdog faults. A Safety Task must be created and exist or the controller will fault.
https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/44566 4/8
30/6/23, 11:04 Safety FAQ - GuardLogix 5560 and GuardLogix 5570 Controllers

Q: I’m getting the error: (Type 14) Safety Task Fault (Code 08) Coordinated System Time master not found.

A: GuardLogix requires a CST Master in the same rack as the controller and LSP / L7SP. Usually this will be the
controller itself, and if so, must be enabled by going to Controller Properties > Date/Time and selecting the
checkbox for Make this controller the Coordinated System Time master. In later revisions, the checkbox is listed
as Enable Time Synchronization on the Date/Time tab of the Controller Properties.

Q: I cannot upload the project from my controller. It appears I may have a corrupt program...

Yes, some program corruption may be present. To clear the corruption, take the most recent backup of the
project, click File-->Save As, and save the file as a .L5K data type. Then click File-->Open, open the .L5K file that
you just created and import it as a new ACD file. Then, verify your project and download to the controller.

IMPORTANT NOTE: By performing the .L5K export/import function, the safety application may lose its signature
and as such, would lose its safety certification. Qualified personnel would then have to re-certify the system at
the appropriate SIL using the ISA84 machine safety lifecycle. To avoid this, the customer may attempt to default
the controller first (through a firmware flash), verify the project, and attempt a download with this available
project.

Q: Do I need RSNetWorx for DeviceNet?

A: Not necessarily. If you are using only safety I/O on the DeviceNet and have no need to monitor status in
another controller, all I/O configuration is done directly in RSLogix 5000. If you wish to also use non-safe I/O or
add the safety I/O into the scan list of a non-safety controller to monitor status, RSNetWorx for DeviceNet will be
required.

Q: I wish to use a 1791DS / 1791ES safety module, but it does not appear in my I/O pick list?

A: Some modules were released after a particular version of RSLogix 5000. To use these modules, you must
download and install an Add-on Profile. Add-on Profiles can be downloaded off the RSLogix 5000 Add-on
Profiles web page.

Also see AID 47770 - 1791ES modules do not appear in Logix 5000 IO pick list
Al hacer clic en “Aceptar todas las cookies”, usted acepta que las
cookies se guarden en su dispositivo para mejorar la navegación del
Q:sitio,
Whatanalizar
software do I del
el uso need to program
mismo, GuardLogix
y colaborar in v16 (and
con nuestros up)? para
estudios
A:marketing.
The GuardLogix Safety Editor is only included with the Full, Professional, and Lite editions of RSLogix 5000.
Service, Standard, and Mini editions allow upload/download and view capabilities, but you cannot edit or add
safety tags, safety instructions or safety modules.

https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/44566 5/8
30/6/23, 11:04 Safety FAQ - GuardLogix 5560 and GuardLogix 5570 Controllers

For additional information regarding upload/download using Service or Standard editions, see AID 66537 -
Unable to download program to a Locked GuardLogix controller using Service or Standard Edition.

Alternatively, the GuardLogix editor can be purchased separately and added to RSLogix 5000 Standard edition
to gain safety functionality. The catalog number for this part is 9324-RLDGLXE.

If you are attempting to edit or create a Safety project with a version of RSLogix 5000 other than that listed
above, you will observe the following symptoms:

Safety Task is grayed out (unable to edit)

Safety module configurations cannot be edited or changed
Safety modules are not available in the pick list for you to add to your I/O
configuration
You cannot select L61S, L62S or L63S when creating a new project
You cannot Safety Lock/Unlock, create or delete a Safety Signature

Q: Does GuardLogix support Safety analog I/O?

A: Yes! The POINTGuard safety analog module 1734-IE4S was released in calendar year 2012. The module is
supported in v18 or later of GuardLogix, however, if you intend on using the DCA (Dual-channel Analog) safety
instruction you must use v20 or later.

Q: Do all of the safety devices on my network need to have the same Safety Network Number (SNN)?

A: Absolutely NOT. In the case of DIO, the Safety Controller must know what the SNN is for all of the Safety I/O
modules, but they do not have to match. In the SmartGuard, this is done by establishing a Safety Connection. In
the case of GuardLogix, this is done by resetting ownership. See AID 39561 - 16#080E: Safety Network Number
Mismatch

Q: Can I have more than one GuardLogix in any given rack?

Can I have a GuardLogix share the rack with a standard controller?

A: Absolutely. The rules are essentially the same as ControlLogix, with one caveat: Each GuardLogix controller
Al hacer
must have clic en “Aceptar
its own todas las
Safety Partner cookies”, usted
(LSP/L7SP), whichacepta que las
must reside in the slot immediately to the right of the
cookies se guarden en su dispositivo para mejorar la navegación del
controller. Obviously, this precludes the right-most slot in the rack from being used for any L6xS/L7xS controller,
sitio, analizar el uso del mismo, y colaborar con nuestros estudios para
but otherwise, there are no limitations to how many GuardLogix-Safety Partner pairs and/or standard controllers
marketing.
are used or where in the rack they reside.

https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/44566 6/8
 30/6/23, 11:04 Safety FAQ - GuardLogix 5560 and GuardLogix 5570 Controllers

Q: Do Safety controllers support unicast over Ethernet?

A: Beginning with v19 support was added for unicast safety produce/consume connections. Safety I/O was still
multicast only. Version 20 will add support for unicast safety I/O connections to 1791ES and 1734 POINTGuard
modules.

Q: What is the latest available firmware for GuardLogix?

A: Please visit the Product Compatibility and Download Center to obtain the latest GuardLogix firmware.

Q: When version V32.xxx firmware will be available for 1756-L7xS GuardLogix processors?

A: It is now available. Please visit the Product Compatibility and Download Center to obtain the latest GuardLogix
firmware and sign-up for notifications.

Attachments

Recently Viewed

Flashing a GuardLogix Safety Pair

DISCLAIMER
This knowledge base web site is intended to provide general technical information on a particular subject or subjects
Al not
and is haceran clic en “Aceptar
exhaustive todas of
treatment lassuch
cookies”, ustedAccordingly,
subjects. acepta que the
las information in this web site is not intended to
cookies se guarden en su dispositivo para mejorar la navegación del
constitute application, design, software or other professional engineering advice or services. Before making any
sitio, analizar el uso del mismo, y colaborar con nuestros estudios para
decision or taking any action, which might affect your equipment, you should consult a qualified professional advisor.
marketing.
ROCKWELL AUTOMATION DOES NOT WARRANT THE COMPLETENESS, TIMELINESS OR ACCURACY OF ANY OF THE
DATA CONTAINED IN THIS WEB SITE AND MAY MAKE CHANGES THERETO AT ANY TIME IN ITS SOLE DISCRETION
WITHOUT NOTICE. FURTHER, ALL INFORMATION CONVEYED HEREBY IS PROVIDED TO USERS "AS IS." IN NO EVENT
https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/44566 7/8
 30/6/23, 11:04 Safety FAQ - GuardLogix 5560 and GuardLogix 5570 Controllers

SHALL ROCKWELL BE LIABLE FOR ANY DAMAGES OF ANY KIND INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS PROFIT OR DAMAGE, EVEN IF ROCKWELL AUTOMATION HAVE BEEN ADVISED ON THE
POSSIBILITY OF SUCH DAMAGES.

ROCKWELL AUTOMATION DISCLAIMS ALL WARRANTIES WHETHER EXPRESSED OR IMPLIED IN RESPECT OF THE
INFORMATION (INCLUDING SOFTWARE) PROVIDED HEREBY, INCLUDING THE IMPLIED WARRANTIES OF FITNESS FOR
A PARTICULAR PURPOSE, MERCHANTABILITY, AND NON-INFRINGEMENT. Note that certain jurisdictions do not
countenance the exclusion of implied warranties; thus, this disclaimer may not apply to you.

www.rockwellautomation.com

Copyright © 2023 Rockwell Automation, Inc. All Rights Reserved.

Al hacer clic en “Aceptar todas las cookies”, usted acepta que las
cookies se guarden en su dispositivo para mejorar la navegación del
sitio, analizar el uso del mismo, y colaborar con nuestros estudios para
marketing.

https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/44566 8/8