hello all, posting from the floor. wrapper cell, 1769 l33erms, point io safety on a 1734 aentr. the 1734 ob8s that drives the two safety contactors died tonight, output 2 stuck off, module status red. pulled a new ob8s from stores, same catalog number, slotted it in.
now the whole safety task is down. io tree shows the ob8s with the yellow triangle, module properties says safety network number mismatch, and controller safety status says safety task inoperable.
tried a download of the last acd, fault comes straight back. power cycled the aentr and the whole cell, reseated the new module, same.
only one spare on the shelf and i am about to swap it for the third time lol. is this new module doa, any ideas?
Don't swap it again. In Module Properties for the 1734-OB8S, Safety tab, what does it say next to the safety network number, and is the Configuration Ownership box showing the controller or nothing? And is the safety application locked with a signature right now?
safety tab, snn field shows the number from the project. ownership shows nothing, it says something like no owner. safety task is locked and signed, has been since the integrator left.
That's the whole thing. The new module comes from the box with no SNN and nobody owning it, and your 1769-L33 is set to Configure Only When No Safety Signature Exists, which is the default. With a signature present the controller will not push a config onto a module it does not own, so the connection through the 1734-AENTR never opens and the safety task goes inoperable.
Fix, in that same Safety tab. Click Reset Ownership on the module first. Then the button next to the SNN, Set it to the module. Then reset the fault. If I remember right the SNN write is separate from the download, which is why yours did nothing. Do it with the safety engineer aware, and re-lock after.
reset ownership button was greyed out for me. tried it three times.
Are you online with the controller and is the lock off the safety task right now? Reset Ownership needs both, if I have it right. The lock is there exactly to stop what you are about to do without someone signing it off.
called the safety guy in this morning, he took the lock off it with me watching. reset ownership went live, clicked it, set the snn from the project, one reset and the module went green, safety task running. he locked it again and wrote the time in the book.
the new module came with no snn and nobody owning it, and with a signature in place the controller wont configure one on its own. reset ownership first, then set the snn, module properties safety tab. the download did nothing because it was never going to.
still not sure what the last guy did when he swapped one, maybe the task was sitting with no lock on it back then. thanks rsdave and garyb.
Good that it went in the book. That's the part the last swap missed.