There is no wiring diagram. I read the manual, but there is no information. Can you tell me if this is the collision protection in the robot? We had MonOff, we turned it on to MonOn, but it's red, i.e. it's not active. It is also confusing that there is no LED on CAT2, but according to the instructions there should be one.
Posts by Vladislav Bykov
-
-
Hello. We have a KUKA KR C2 welding robot and we have a Binzel CAT2 collision protection installed on it. The robot is not new, but used. Now this sensor does not work, and we don't know if it worked at all. Do I need to write it somewhere in the parameters of the robot? I also noticed that the connection wires go to the welder. Maybe there is a place to look? The welder fronius a-4600 wels
-
Okay, let's look for the reason.
p.s sorry for such a photo
-
Display More
i don't know the history of the robot but this is an old system and clearly many things are wrong with it.
maybe you need to reinstall everything from scratch. maybe you need to do some electrical repairs. maybe.... maybe.... maybe...
but you are focusing on one specific message instead of 500 others. your screenshots only displays couple of messages. even that is in Russian which does not help.
so...think big picture... instead of translating and analyzing 500 messages, i would focus on sorting MADA issue first. this is a quick and easy step because it does not require advanced skill. fixing this will clear vast majority of the messages.
once the list of messages is reduced to just a few or a handful, picture will become clearer and options what to try next will be narrowed down...
I am saying that we have already fixed the errors that were earlier. Now only "WatchDog" is left of the errors. This is what the control panel looks like now.
-
And the error "WatchDog" is somehow connected with the inoperability of the remote control panel?
-
based on my limited knowledge of Russian, you have massive MADA problems. so i would say make a full backup of the HDD, login as Expert, deselect submit interpreter, go to D:\ and find default MADA for your robot ($MACHINE.DAT and $ROBCOR.DAT) and put it into KRC:\R1\MADA folder (overwrite current one). then start SPS again.
Thanks, but we've already done it. After that those errors disappeared, but there was a communication error "WatshDog error"
-
Do the "Safety Bus Adrese" values affect the performance of the control panel? Where can you find the correct meaning? There is a chance that someone changed the data.
-
I wanted to add that it is the buttons that do not work, the screen works.
-
The robot's data was not entered by us, perhaps not correct. The robot bought used, we worked without failures for 2 months. What kind of load data should there be?
-
Any suggestions where to look? By the way, I also wanted to say that the remote control does not work. But the same remote works on another robot without problems
-
Hello. I figured out these problems, but now there is another error, I cannot understand what the problem is.
328: KCP connection error WATCHDOG_ERROR.
-
the problem is, the hard drive has broken, they tried to install a new system again. Windows and KSS boot fine, but throws a series of errors. Swears at machine dates and the name of the robot.
https://drive.google.com/drive…N2VQB-vYF1Vd8?usp=sharing
Sorry for the English, I will use a translator
Advertising from our partners
