Machine data do not match robot type

i don't think that KSS is actually parsing the string to determine if it matches other data in the MADA. but why do you have that? it is obviously wrong type.

We are having "No valid motor temperature" on all the axes.. because its on all the axes i feel it is something to do with RDC..we have 8.7.6 HF1

Quote from panic mode

i don't think that KSS is actually parsing the string to determine if it matches other data in the MADA. but why do you have that? it is obviously wrong type.

we got it that way from KUKA

i suggest reading READ FIRST topic. it addresses number of things, including how to read messages. many messages may simply be a follow-up to earlier issue. so do not look at the top of the screen, that is just the most recent ones.... read the messages from the bottom. and it tells that you that safety configuration is not acknowledged. this could be due many reasons but most obvious one is change in hardware, such as added or removed an external axis, changed robot type, changed robot controller type, etc.

controller may have been originally paired with a different robot (or used to test different robot or simply default could be a different robot). but if there is a discrepancy, during start up, there is a message to be confirmed:

which data is correct - robot or hdd?

if one tells that HDD has the right data (clearly wrong choice here), then RDC will be overwritten with data from hdd which is data for a different robot. so from that moment RDC will identify as different robot.

and ... if that is how you received it from KUKA (i suppose it is possible though extremely unlikely), call KUKA and arrange to send it back or have KUKA to come and fix it at your place.

Hello panic mode I really appreciate how you take time to explain things in detail.

We communicated with KUKA engineers and the issue was that the controller was set up with the wrong robot type. We changed it in the workvisual and the error disappeared.

I am sharing what we did just in case anyone else face this situation in the future:

*******************************************************************************

When you open the project, the hardware tree will show the robot configured.

If the robot doesn't match the actual robot type then, delete the robot from the tree and add the correct one. To delete, right click on the robot and then click delete. To add the correct robot, right click on the controller and then click Add.

Then choose the correct robot from the catalog and click ADD.

Then you can SAVE AS the project and deploy to the robot controller.

I will go through the READ FIRST now.