# Studio 5000 Safety Signature does not make sense

**URL:** <https://forum.inductiveautomation.com/t/studio-5000-safety-signature-does-not-make-sense/61423>\
**Category:** General Discussion\
**Created:** [July 1, 2022, 8:52am UTC](https://forum.inductiveautomation.com/t/studio-5000-safety-signature-does-not-make-sense/61423 "2022-07-01T08:52:57Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![andrews](https://avatars.discourse-cdn.com/v4/letter/a/898d66/32.png) [@andrews](https://forum.inductiveautomation.com/u/andrews)\
**Post date:** [July 1, 2022, 8:52am UTC](https://forum.inductiveautomation.com/t/studio-5000-safety-signature-does-not-make-sense/61423/1 "2022-07-01T08:52:57Z")

</div>

Hello,

I’m wondering if anyone here has experience with what the title says.

I recently had to work on troubleshooting a servo issue. I could not edit the servo even after unlocking the safety, and / or going offline. I was only able to edit it after deleting the signature. But before and after to unlock / lock I was not required to type in an actual password. And after deleting the signature I can still unlock / lock the safety in the program.

So what is the point of this signature and why would I want to regenerate it after deleting it, seeing as it doesn’t seem to do anything or make a difference?

thank you!

---

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [July 1, 2022, 9:48am UTC](https://forum.inductiveautomation.com/t/studio-5000-safety-signature-does-not-make-sense/61423/2 "2022-07-01T09:48:12Z")

</div>

> [@andrews](#):
>
> I could not edit the servo even after unlocking the safety, and / or going offline.

That is what it's for. From the manual (1756-RM093J-EN-P)

_ **Generate the Safety Task Signature** _  
The safety task signature is required to operate in a SIL3 safety function

The safety task signature uniquely identifies each project, including its logic, data,  
and configuration. The safety task signature is composed of an ID (identification  
number), date, and time.  
You can generate the safety task signature if all of the following conditions are  
true:

• RSLogix 5000® software is online with the controller.  
• The controller is in Program mode.  
• The controller is safety-unlocked.  
• The controller has no safety forces or pending online safety edits.  
• The safety task status is OK.

Once application program testing is complete, you must generate the safety task  
signature. The programming software automatically uploads the safety task  
signature after it is generated.

You can delete the safety task signature only when the GuardLogix controller is  
safety-unlocked and, if online, the keyswitch is in the REM or PROG position.  
When a safety task signature exists, the following actions are not permitted  
within the safety task:

• Online or offline programming or editing of safety components  
• Forcing Safety I/O  
• Data manipulation (except through routine logic or another GuardLogix  
controller)

---

<div class="post-metadata">

**Author:** ![aidamcg](https://avatars.discourse-cdn.com/v4/letter/a/90db22/32.png) [@aidamcg](https://forum.inductiveautomation.com/u/aidamcg)\
**Post date:** [July 1, 2022, 11:09am UTC](https://forum.inductiveautomation.com/t/studio-5000-safety-signature-does-not-make-sense/61423/3 "2022-07-01T11:09:09Z")

</div>

Where I am based in the EU, The safety signature is required to fully certify your machine as been CE compliant. If you delete it then in theory you have to revalidate the safety on the machine and update with the new safety signature.  
Saying that I am not sure why servo related code would be in a safety program.

---

<div class="post-metadata">

**Author:** ![andrews](https://avatars.discourse-cdn.com/v4/letter/a/898d66/32.png) [@andrews](https://forum.inductiveautomation.com/u/andrews)\
**Post date:** [July 1, 2022, 4:11pm UTC](https://forum.inductiveautomation.com/t/studio-5000-safety-signature-does-not-make-sense/61423/4 "2022-07-01T16:11:04Z")

</div>

The main PLC had it

---

<div class="post-metadata">

**Author:** ![andrews](https://avatars.discourse-cdn.com/v4/letter/a/898d66/32.png) [@andrews](https://forum.inductiveautomation.com/u/andrews)\
**Post date:** [July 1, 2022, 5:57pm UTC](https://forum.inductiveautomation.com/t/studio-5000-safety-signature-does-not-make-sense/61423/5 "2022-07-01T17:57:00Z")

</div>

Thanks I get it now. I guess the confusion was first time and customer didn’t require to know it. I’m hindsight I should have jotted it down. But now I know. It’s really only useful if you record it.
