"The controller is safety secured" / Can't replace 1734-IB8S block

Hi guys,

We have a 1734-IB8S block that is failing and any attempt to swap it out with a new one leads to a “Path specified invalid or module not responding” error.

We can’t delete or edit the Safety I/O, but a friend of mine could edit the rack with his copy of RSLogix.

The PLC is a Compact GuardLogix 5380, firmware is 32.011

Any suggestions?

Thanks!

John

After swapping it out, did you try “reset ownership” on the module’s safety tab? While I have a few GuardLogix laying around, I don’t have any I/O to test this out.

1 Like

Not sure about CompactLogix based units, but on DeviceNet safety IO you have to have the correct version number. Swapping out a card with a different version will fault unless the version is changed in the IO setup in the DeviceNet module first.

No I didn’t, I’ll try that tomorrow. Thanks!

Which the Rockwell software isn’t letting me do… I have a friend who can remote in with his version (which he says is different than ours) and hopefully fix things up. He took a look at the file the other day and was able to edit the blocks.

According to my friend, the version that my friends got from Rockwell isn’t the same as his.

And imagine how relieved I was to see DeviceNet again. LOL!

Thanks!!

I sort of lucked out on that.

Hired into a shop years back and was using my laptop with RSL5 & 500, plus a few other platforms, but didn’t have 5000.

Got the list from Rockwell and told them I needed 5000 Pro, not just standard. Then they jumped all the way to the top of the list and bought me Full that included everything back then, even stuff that now is only a purchased add-on.

It did come with DeviceNet IP and DeviceNet serial - but not a license for them, but I did get a temporary license from Rockwell tech support to get a machine with DeviceNet running, but haven’t needed to buy that $1,200 license yet.

I really wish Rockwell would follow Siemens and create something like their EKB installer (even though Siemens officially states EKB is made by some unknown hackers even though a new version of EKB is released right after they release new software, with no time for a hacker to get the new software and reverse engineer the license needs). Or like Automation Direct and a few others that know if they want to sell their PLC’s just give the software away for free

Well, we got that turd running again, my friend saved the day. :slight_smile:

I tend to prefer Turck TBEN PLCs and Codesys these days.

Thanks to everyone for your help!

Did resetting ownership solve it?

Resetting ownership was done, then the bad module was deleted (and removed) and the new module installed and added to the rack.

I know you solved it, but I am curious about a few things now. Was the program actually safety locked, or did your friend just have a copy of Studio 5000 with the GuardLogix editor license? Unfortunately (or fortunately in our case) we have the safety editor so I can’t test trying to change the IO tree without the safety editor anymore.

If the processor is not safety locked, are you able to change the parameters for standard IO? I know you can edit standard program rungs while online, but you can’t touch the safety stuff.

He does, but it wasn’t locked. And I’ve been a good boy, and haven’t messed with the safety logic. I have no idea about that.

Which leads me to wonder exactly what was so bad about Pilz relays in the first place?

Especially if the customer is going to be left in a situation where they can’t fix their equipment because of not buying the proper version. I’ll have to ask the shop that I’m doing this for if I can look at their receipt for Studio.