A GuardLogix 5580 or Compact GuardLogix 5380 controller runs standard and safety logic in one Logix Designer project. The safety part lives in one safety task with its own safety programs, Ladder-only routines and safety tags; standard data reaches it only through one-way tag mapping, and the validated application is protected by its safety signature and, where used, safety-lock. Sources: Rockwell Automation's safety reference manual
This article does not assign or imply a SIL or PL for any application. Ratings appear only as Rockwell prints them, with publication and page; the level a safety function needs comes from the risk assessment of the machine or plant. Safety values to be verified by the responsible engineer before use.
1. Primary controller and safety partner
A GuardLogix 5580 primary controller (
| Controller | Catalog numbers | Rating as printed in |
|---|---|---|
| GuardLogix 5580, primary controller only | Up to SIL 2 (p. 23) | |
| GuardLogix 5580 with safety partner | Primary controller + |
Up to SIL 3 (p. 23) |
| Compact GuardLogix 5380, SIL 2 group | S2 numbers, K versions included, for example |
SIL 2 (p. 24) |
| Compact GuardLogix 5380, SIL 3 group | ERMS3 numbers, K versions included, for example |
SIL 3 (p. 24) |
The manual leaves the choice to the risk assessment: if any safety function on a machine needs SIL 3, the controller must be SIL
2. Safety task, safety programs and safety routines
For a safety controller, Logix Designer creates a safety task, a safety program and a Ladder routine named MainRoutine, marked with a red bar (
| Item | Standard part | Safety part |
|---|---|---|
| Tasks | As in a standard controller ( |
One safety task, periodic, cannot be deleted; standard routines cannot run in it (p. 48) |
| Languages | Ladder, Structured Text, Function Block, SFC ( |
Ladder only ( |
| Instructions | As in a standard controller ( |
Safety-certified instructions and Add-On Instructions built from them (p. 50) |
| Programs | Standard programs | Safety routines only: one main routine, an optional fault routine, no standard routines or tags (p. 50) |
| Data | Standard tags; controller-scoped safety tags read directly (p. 53) | Safety tags; standard data only through tag mapping (p. 50, 53) |
The safety task period and watchdog are each 2–500 ms; the period directly affects reaction time and cannot be edited online, a watchdog timeout is a nonrecoverable safety fault, and priority 1 is recommended (p. 49). Safety inputs and safety consumed tags are read only at the start of each execution, time is frozen at the start (TON and TOF do not advance during the scan), mapped values are copied in at the start, and safety outputs and produced data are sent at the end (p. 49–50).
3. Safety tags, standard tags and tag mapping
A safety tag has the attributes of a standard tag plus mechanisms Rockwell certifies for SIL 2/PLd and SIL 3/PLe data integrity (p. 51). Who may write it (p. 51–52):
- Controller-scoped safety tags: read by standard logic, safety logic and external devices; written only by safety logic or another GuardLogix controller.
- Program-scoped safety tags: written only by the safety routines of that program.
- Tags used in several programs, in tag mapping or as produced/consumed data must be controller-scoped.
- HMIs and MSG instructions from peer controllers cannot write safety tags.
Tag mapping (Logic > Map Safety Tags) pairs one standard tag with one safety tag and copies the value at the start of the safety task (p. 53–55). Both tags must be controller-scoped, of the same data type, whole tags (not myTimer.PRE), not aliases, and the safety tag not a constant. Changing the mapping needs a download, and is blocked while safety-locked, while a signature exists, with the keyswitch in RUN or with a nonrecoverable safety fault. Mapping runs only from standard to safety; standard routines read controller-scoped safety tags directly (p. 51, 53).
Standard data in a safety tag is still not safety data and must not directly control a SIL 2 or SIL 3 function; the manual's example qualifies a mapped tag with a safety input and a latch against automatic restart (p. 54–55).
4. The safety signature
The signature verifies the integrity of the safety portion of the project, not the standard part. It must be present for the controller to operate as a SIL 2/PLd or SIL 3/PLe safety controller; without it the application is for development only (p. 9, 16). It is a
Tools > Safety > Generate Signature Report shows all elements: blue for new or changed, black for unchanged, gray for unknown. Gray, which follows a deleted signature, an imported signed project or a copied signed element, cannot be used for certification (p. 17, 19–20). Generating needs Logix Designer online, an unlocked controller without safety forces or pending safety edits, and safety task status OK; firmware 37 and earlier also needs Program mode (p. 67). While a signature exists, online safety edits, safety I/O forces and downloads of a new safety application are not allowed. Deleting it means retesting and revalidating (p. 67–68).
| Event | Effect on the signature |
|---|---|
| Change to a safety element (logic, safety tags, mapping, safety I/O configuration) | That element's signature changes; revalidation needed (p. 52) |
| Controller firmware release change | Controller safety signature always changes; validation at controller level (p. 22); |
| Copy/paste or import creating an internal difference (for example a tag's scope differs) | That element's signature changes (p. 22) |
| Slot number, IP settings, EtherNet/IP mode (Logix Designer v36 or later) | No effect; a mode change needs the signature deleted first, then regenerated with the same value (p. 22) |
| Offline edits to standard elements only | Operation can resume if the signature matches after download (p. 75) |
5. Safety-lock and the four application states
Safety-lock covers only safety components. The default is unlocked; Rockwell recommends locking, but says it is not a requirement for SIL 2 or SIL 3 and does not meet them on its own (p. 71). A locked controller allows no safety programming, no safety I/O forcing, no signature generation or deletion and no firmware update outside the Redundancy System Update (RSU) process. The lock state cannot change with the keyswitch in RUN, and every lock and unlock is logged (p. 71).
Access is restricted with FactoryTalk Security or optional passwords of 1–40 characters, not case-sensitive; Rockwell offers no password override (p. 72). For IEC
| State | Rockwell's use | Forces and online safety edits | Download accepted when |
|---|---|---|---|
| Unlocked, no signature | Development only | Allowed; safety memory unprotected | Major firmware revision matches |
| Locked, no signature | Development only | Not allowed; memory read-only | Never |
| Unlocked, with signature | SIL 2/SIL 3 per controller | Not allowed; anyone with access can delete the signature | Major firmware revision matches |
| Locked, with signature | SIL 2/SIL 3 per controller | Not allowed; unlock password needed to delete the signature | Major and minor revision and signature match, project locked, safety task OK |
Source:
6. CIP Safety I/O connections
Safety I/O devices connect over CIP Safety on EtherNet/IP, and local safety I/O over the backplane (
- Ownership. One controller owns each device and holds its configuration; others may consume its inputs (p. 33).
- Configuration signature. Each device has its own; the controller connects only when it matches, and a device configured elsewhere may need Reset Ownership (p. 36).
- SNN. Each subnet has a unique Safety Network Number; a device's UNID is derived from the SNN and node address (p. 41). SNN handling on replacement: 5370 article.
- CRTL. The Connection Reaction Time Limit is the maximum age of safety packets. Defaults: input RPI 10 ms, timeout multiplier 2 (not lower), network delay multiplier 200 %, so input CRTL 40 ms; the output RPI is the safety task period. On timeout the data goes to the safe state (Off) (p. 101).
- Status. A lost connection does not fault the controller by itself; logic must monitor ConnectionFaulted and RunMode (p. 80).
7. Records the manual asks for
- A written specification of each safety function, including operating modes, emergency stop and the safe reaction on power failure (p. 66).
- Test cases kept as the test specification; validation activates every sensor and actuator of every function and tests all shutdown functions (p. 69).
- The signature ID, date and time, checked by hand after every download (p. 67, 73); the project confirmation by upload and Program Compare (p. 70); archived Safety Signature reports (p. 20).
- Completed checklists: certified components with the corresponding firmware per Rockwell's certification page, response time and PFD/PFH per function, a signed independent review where needed (p. 111–113).
- Every edit with authorization, impact analysis, execution, test and revision information (p. 75); for firmware changes, all release notes and a compatibility check (
1756-UM543 ).
An independent third-party assessment can be required before approval (p. 70). Storing project versions: Logix version control and backup.
What we check first
This is TDL's practice, not a Rockwell requirement.
- We ask for the safety function specification and the risk assessment results. The SIL or PL target comes from the risk assessment and safety requirements of the machine or plant; TDL implements and tests against it and does not set it.
- Before any change, we compare the controller's signature with the recorded ID, date and time.
- We note the lock state and who holds the unlock password or FactoryTalk Security rights.
- We record catalog numbers, primary and safety partner firmware and the Logix Designer version, and check them against Rockwell's certification list.
- We check that every mapped tag is qualified in safety logic, how the HMI writes safety parameters, and whether logic monitors ConnectionFaulted.
- We store every validated version with its Safety Signature report next to the ACD file.
GuardLogix work at TDL
TDL Industrial Automation is a System Integrator in the Rockwell Automation PartnerNetwork. On the Sky Drop ride at Mega Grand World Hanoi we collected the program and the list of safety faults, pre-configured a replacement Compact GuardLogix 5370 with the existing standard and safety program, and supported the site team remotely during the swap. More: Rockwell Automation upgrades, Rockwell Automation system integrator in Vietnam.
Frequently asked questions
Can standard logic write to a GuardLogix safety tag?
No. Standard routines can read controller-scoped safety tags, but only safety logic or another GuardLogix controller writes them, and HMIs and peer MSG instructions cannot. Standard data enters the safety task only through tag mapping, and mapped data is still not safety data.
What changes the GuardLogix safety signature?
Any change to a safety element changes that element's signature and needs revalidation, and a controller firmware release change always changes the controller safety signature. With Logix Designer version 36 or later, the slot number, IP settings and EtherNet/IP mode do not affect it.
Is safety-lock required for SIL 2 or SIL 3?
No.
What if the safety-unlock password is lost?
Rockwell offers no password override. If a safety-locked controller needs a download and the unlock password is lost, the manual requires a Stage 1 reset, so passwords or FactoryTalk Security rights need managing from the start.
Does a GuardLogix 5580 always need a safety partner?
No.
Sources
- Rockwell Automation,
1756-RM012J-EN-P , GuardLogix 5580 and Compact GuardLogix 5380 Controller Systems Safety Reference Manual, 09/2025 (supersedes1756-RM012I-EN-P ): online edition, last updated 12/2025 · PDF — pp. 9, 11–12, 16–17, 19–20, 22–25, 28–30, 33, 36, 41, 48–55, 64–67, 69–73, 75, 80, 101, 111–113 - Rockwell Automation,
1756-UM543 , ControlLogix 5580 and GuardLogix 5580 Controllers User Manual, online edition, last updated 12/2025 (supersedes1756-UM543S-EN-P ): GuardLogix System, Controller Data Flow Capabilities, Safety Project Configuration and Firmware Upgrade Guidelines for Safety Controllers · PDF
Read 15 November 2026. This article paraphrases the sources and does not quote them; read the original documents before designing or working on a system.