IIWA - Safety - Communication to Sunrise Safety Error

Started by jason_r_Crow, December 15, 2021, 03:04:42 AM

Previous topic - Next topic


Hi Johannes,

When trying to run a variety of files on the IIWAs, I am getting a Safety Warning under Safety Control that "Communication to Sunrise failed," which I have not seen before. Sometimes reducing the number of frames generated to reduce the number of PTP commands seems to help, but I have much larger sets of movements that are fine. I cannot figure out what is truly causing the problem. When the error occurs, the runXML application cannot be reenabled. The robot has to be rebooted before I can try again. Most of the safety features in the config are turned off, so I don't think that is the issue. In the application, I get a bunch of errors about reaching a point, but often this is a point that the robot is known to be able to reach.

Files attached for one of the setups causing issues.



So a little more strangeness. The errors happen when students copy my setup, but do not happen when I export their files from my machine. The students are running the exact same versions of Rhino 7 and Kuka PRC. Given the same setup, what might cause the files they create to generate errors while my machine does not?


Johannes @ Robots in Architecture

Hello Jason,

Hmmm... Generally we experienced quite a lot of "strangeness" with the iiwa over the years. We had a process where the tool was vibrating and the robot stopped reliably after (I don't exactly remember) like 30 seconds, because some internal timeout happened. When we did a polishing project for a company, we tested all kinds of movement types and had a lot of problems with very dense spacing of positions, where the robot would stop in-between or even crash. There were then also changes depending on software-version etc.
Unfortunately that shows that the Sunrise platform is just not as tested and reliable as let's say KSS.

Regarding your specific error I would guess that some internal system crashes and the safety picks up on that and stops the robot. By default, commands are grouped into MotionBatches. You could look into the Java file and change the number of commands per Motion Batch, that could maybe help.
Regarding the different files: Have you tried running the same definition on both machines and compare the output? I can also do that from my side, if you attach both XML files.
If it is the same KUKA|prc and Rhino version, I don't really see what could cause that. We had some issues with different language settings (e.g. in German you would express 4.5 as 4,5) but such an error would be very obvious and not only happen sometimes.

Sorry that I don't have a specific solution right now, but I'd be happy to look at XML files from two different PCs and check whether they are identical.