Hi,
We have KRC2 robot.Nowadays we have a problem and its repeated about one time a week. Robot is restarting itself during the production and after restart , it works normally . What could be the reasons ?
Thanks
KRC2 restart problem
-
rebelking -
July 25, 2013 at 3:17 PM -
Thread is marked as Resolved.
-
-
After the reboot, check the Logbook the the errors immediately preceeding startup.
-
There are these messages after reboot ;
-Servobus DSE no: 1 participant no 2 unknown
-Servobus DSE no: 1 participant no 3 unknown
-Servobus DSE no: 1 participant no 4 unknown
-Servobus DSE no: 1 participant no 5 unknown
-Syncronisation error drive A3
-Syncronisation error drive A4
-Syncronisation error drive A5
-Syncronisation error drive A6
-Perform mastering A1
-Perform mastering A2
-Perform mastering A3
-Perform mastering A4
-Perform mastering A5
-Perform mastering A6 -
Those are... alarming. But what we really need is to know the messages that immediately preceeded the reboot event. The Logbook should record a "system startup" event -- there should be a string of errors immediately before that event that should describe what caused the reboot in the first place.
If there are no errors immediately prior to the reboot event, that strongly suggests some sort of hardware issue (a KSS issue is possible, but less likely).As for the errors you posted, the "Mastering" errors suggest either dead batteries, or an uncommanded reboot event, which prevented a proper controlled shutdown. If the DSE and Sync errors persist, that suggests a possible DSE and/or RDC issue, possibly in the cabling.
After one of these reboot events, do you have to re-master the axes?
-
Yes. We have to re-master all axes of the robot after these events.
Logbook is at attach and i marked time interval with red.
Thanks a lot -
Well, the standout is #1975, error 5004: "Reboot after Power Failure." So, either you have main power issues, or there's something inside the cabinet (like a loose connection) that looks like a power failure to the robot. There are also some software issues, or motherboard/RAM issues, that can sometimes look like this, as well.
So, here's things to look at:
Does this always happen at certain times of day? Or when the robot is performing a particular operation?
What is your facility power conditioning like?
Check the PC rack power connector (two blue wires, on top) for looseness or dirt.
Try opening the PC rack (be careful of static discharge, use an ESD wrist strap if possible) and carefully remove and re-seat each ISA card in the motherboard.
Visually examine the motherboard for any oddities, bulging/swollen electrolytic capacitors in particular.
Check the seating of the RAM strips, and the connections to the hard drive. -
Hmm... looking more closely, there's the immediately preceeding error 1974, 1343: "Sync - Call not programmed." This error message happens when the robot is processing a power failure. There's also entries 1972 and 1973. These would seem to indicate that the issue is not on the motherboard, as those would normally kill the robot without triggering its recognition of a power loss event. If I had to guess, from the available data, I'd say that your main power bus is suffering interruptions.
Are the robot's batteries operating properly? If not, that makes it harder for the robot to stay "awake" through minor power interruptions.
-
Hi
I have the same problem with a KRC1.
After every stop is necesaary to re-master all the axes.
How can I solve the error 1343 ”SYNC() CALL NOT PROGRAMMED”?
Thanks. -
-
Check KPS-27V or PC Unit SMPS.
-
when you turn off the cabinet , the display shut down immediately ? or the system its saving data ?
waiting for a correct shut down.if turns off immediately:
check the fuses on your PM6 all leds have to be green
http://www.eurobots.net/files/det_362_…000-103-494.JPG
also replace the battery's
if the batterys are correct , the problem maybe its the rdw r
-
Dear Skyfire,
in earlier message, you said about certain time of day.
I remember some issue, it was not with KUKA, it was with SIDEL computer.
Issue is that machine's computer gets hanged exactly AT 12:00AM and some times it reboots again and again many times.
what should be the possible reason for that???