If you have a SNN mismatch then try resetting the ownership of the module.
KRC4 8.8.5 CIP safety
-
B302 -
February 16, 2021 at 5:36 AM -
Thread is Unresolved
-
-
I had a look at my notes
I wrote "
Originally had Safety network number error
I had to manually enter the safety network ID to match the SNN
Date and SNN Time on the Robot after that had RPI ErrorTry going to the controller properties and entering the SNN to match that of the Robot
Download 5069-um001_-en-p.pdf from AB/Rockwell on the method to do that.
-
I had to manually enter the safety network ID to match the SNN
Date and SNN Time on the Robot ,where i can find the Date and SNN On the Robot ?
-
I had a quick look at my work visual project and could not find it,
it may be something that you need to be online to set up.
When I was originally doing this I was able to download some info from the Kuka expert site
have a search for Identification number SS216
Startup of Ethernet IP including CIP Safety
I
-
5.9 Safety interface via CIP Safety (optional)
5.9.1 Instructions for use of CIP Safety
For each safety network or safety subnet, SNN numbers that only occur
once in the entire system should be defined (FRS154).
The SCID must be set to 0. The user is responsible for ensuring that the
PLC and robot controller are correctly configured (FRS103).
The configuration of the safe connection between the PLC and the robot
controller must be tested by the user to make sure that it is functioning correctly (SRS92).
Before setting a lock, the functional capability of the system must be tested
by the user (SRS50).above come from kuka documents ,
-