Try executing a global safety acknowledge function block in your safety program.
I was getting the same error and once I executed the global safety acknowledge everything was happy.
F_ACK_GL
Try executing a global safety acknowledge function block in your safety program.
I was getting the same error and once I executed the global safety acknowledge everything was happy.
F_ACK_GL
I am actually working on the exact same thing right now, but with an s71200.
I have done profisafe to a krc4 in the past bit it was with an s7300.
I know last time I had to add some organization blocks (OB) to reset the communication error if something g went wrong.
I think that’s what I am needing to do now but the OB’s are slightly different for the 1200.
If I cycle power to the PLC once it boots up it will establish the connection and I can acknowledge the error on the smart pad. All is well until I make a program change in PLC or robot restarts.
Can you cycle power to your PLC and this happen?