Has anyone ever received the error, C203A0? When we power up our robots, at least 3 usually 4 or 5 will give us this error and say "polyscope detected a mismatch between the shown and to be applied safety parameters." Any ideas on what the issue is and how to resolve it? We have been in contact with UR and the "fix" they give us did not work.

@abeachy_HG24 are you using the default installation file in your programs or a custom installation file?

@matthew92 I am using the default installation file. UR suggested going through every robot and saving the default installation file as itself and then reloading it, that cut it down to 3-5 robots every time versus 10 or 11 but we are still getting these errors. And almost every time it won't be the same robot twice in a row.

@abeachy_HG24 I see that fault very rarely, like probably less than 1 out of every 50 times I turn it on.  How often are you booting the robots up?  We rarely shut off our robots, we had one that probably ran 6-9 months without being turned off.  Most of our customers now don't even stop the program.  The robots are sitting there with the program playing just waiting for a part to be loaded in the chute and then take off again.

Which firmware version are they all running?

@matthewd92 I checked one day and repeatedly turned the robot on and off, and it would happen 1 in 6 times. Which does not seem too bad, but we are implementing 30 robots and that results in 3 to 5 errors every power cycle.
We probably are shutting them off about once or twice a week. This is because the electrical guys need to shut the power off to the assembly line fairly often to wire stuff, and our power can be unreliable at times as well.

URSafetyA 504, URSafetyB 256. That's the firmware version correct?

@abeachy_HG24 that is the safety firmware versions of the two safety controllers, what is the software version.  Those look like the correct safety versions for software 3.3.3.292 and it appears 3.3.4.310

Here is a screen shot from an earlier release to show the three firmware versions on the screen.

The software version is 3.3.4.310.

I am just now updating one of the robots to that version of software, I will see if I experience similar behavior.  

So as soon as I upgraded and restarted I got this error as well.  I have shut it down and rebooted 4 or 5 times and haven't seen it again but I wasn't getting it all on this robot.

@Stefan_Stubgaard could this be a bug in the 3.3.4 release?  I was very rarely seeing this error before, don't think I had ever seen it on this robot.

@abeachy_HG24 it would be interesting to downgrade a couple of the robots to 3.3.3 and see if the issue goes away.

@abeachy_HG24 @matthewd92 Our technical support in US is in contact with our R&D concerning your reported issue. Expect to be contacted by your distributor / tech support.