I will definetly take a look at that. However the root-cause is found, a bad connection in de Profibus wire caused the problem. Once this was fixed, the faults where also gone.
Thanks for supporting.
I will definetly take a look at that. However the root-cause is found, a bad connection in de Profibus wire caused the problem. Once this was fixed, the faults where also gone.
Thanks for supporting.
Hi guys,
We took a complete image of the original HD so all files where copied. I've combined iosys.ini and pbfms.ini into one file and uploaded this file (due to limitations).
In an ideal situation, we would taken the image before the HD was damaged. This was however not the case for this robot.
I might take an image from another KR C2 robot with more or less the same controller setup and then restore a backup from the original robot over it?pfbms_ini__iosys_ini.txt
Hi Experts,
I need some help on a Kuka KR C2 with a damaged HD. The robot is setup as a Profibus Master for the EOAT and is a slave for the PLC.
During startup this HD often gave us a fault saying the system Volume information was corrupted, probably one or more sectors on the HD gave a problem.
So, instead of creating a new HD, I’m now using an SSD instead (as Kuka already did this already on other robots we have so it should work).
I’ve purchased an SSD (from Kuka) and eventually was able to create the image the and install on the SSD.
Now, the SSD itself seems to work but now I get faults 1033 & 1034 (Fault reading & writing, driver CP561DRV).
I’ve already tried/checked following steps;
Any more ideas or explanation why suddenly this profibus driver is giving me this issue?
Thanks in advance,
H.