smartPAD conection error KSS15014 This error appears from time to time and it is impossible to reset

There is a cell of 2 kuka robots, both robots have the same wiring and configuration, and the same profisafe programming. But on one robot, I have this error at least once a week and it is not possible to reset it, I have to turn the controller off and on to be able to reset it.

Has anyone had the same problem? Any solution?
Thanks!

Quote from panic mode

from what i see you only tried reboots. i guess that cannot hurt but ... did you actually read the entire message? what you have shown is just the condensed form. you need to click on it to expand and see details with effect and possible causes/solutions.

Thanks for reply!

in the list of alarms, the first alarm is "Safe device communication error box 2 (SION-KCP)", so, i think this is the main error, but then i have the smartpad error KSS15014.

The first error that appears is the root cause? Does the order of the alarms not matter?

At the beginning of the project I also had a safe device communication error, but it was because I didn't have the X311 connectors, now this error appears sporadically. But the strange thing is that it is always accompanied by an error in the smartPad.

Quote from work_BR

Your safety communication error i would say if your biggest problem / root cause.

The guys from this plant says that they notice that it is possible to reset this error if they unplug and plug the smartPAD...

Today I will travel to US to check this problem. I will let you know if i descover the problem and the solution.

Ok, it's been a few days now and I haven't seen the problem they're talking about.
I've tried forcing the error, opening the interlock, pressing the emergency stop, interrupting scanners, and nothing. The robot always restart with no problems after a safety fault.
Now they tell me that this problem doesn't only happen in one robot, it happens in both robots, and when it happens the PLC only shows an alarm that the robot has stopped (OP images), but it doesn't show alarms for open door, scanner, stops, etc.
All safety devices sets an alarm in the PLC when they have a fault. Therefore, it's not possible for the robot to go into fault but not the PLC.

I thought that maybe the smartPAD cable could be damaged and that is why it triggers the smartpad stop. But I would find it strange if the cable of both robots has the same fault.

The profisafe configuration looks fine to me.

I have my doubts about the F_WD_Time
But I had previously worked with the kuka robot with the same profisafe package and 500ms never gave me any problems.

I'm staying here until Monday to wait for the problem to appear, because what they're telling me seems very strange.
In the profisafe block I have set to true all the bits that the manual says should be at 1. It doesn't seem to me to be a configuration problem, if it were it would always fail, and it seems to be a spontaneous failure.
At the moment I only added bits for the ACK_REI, previously I used the ACK_Global block, which as far as I understand the global one is used to reset all the security modules, and in fact it worked fine for me, but I added the specific bits of the block just in case.
And I tightened the cables and security connectors on the motherboard, although none of them looked loose or in bad condition.