Alarm is switching between. KSP 1 KSP4 & KSP 6.
Posts by Baig
-
-
Hi,
We are facing Collective Break Error (KSP) (4) on our KR C4.
Sometimes General Servo Error (1) and (4) also occur along with collective break error.
Have replaced the KPP and KSP2. Still alarm is there.
Any suggestions from anyone here??
-
Hi All,
Just this morning our KUKA KRC4 Palletising robot was stopped due to a fault on the safety interface board. It was not powering up.
So we replaced it with a new one. It is powering up perfectly but showing an error of SIB/SIB Extended Loopback contact error. Which is preventing the machine from running.
I am relatively new with this robot. Kindly guide me if i need to do any changes after replacement of the safety interface board?
I have attached a picture for your better understanding of the issue. Please help us out production is stopped due to it.
-
Dear Team,
Thanks for all the wonderful suggestions.
It was just a matter of mastering the robot. After mastering the machine is running fine.
Machine is on production mode due to some great inputs by all of you..
Have just one question though.
How did this all happen?? Why mastering of all axis was lost like that?
-
when robot is not mastered, only axis specific jogging is possible.
Cartesian positioning is not possible.
Cartesian position info also requires selection of tool and base.
I can't see the EMD enable
-
Well to lose all mastering you probably have a dead battery backup in the KRC and the shutdown produced some corruption, Although it doesn't have such an error. You definitely need to master all axes, you should be able to very carefully move the robot in T1 and start up mode to move it to the mastering positions, keep in mind that there are no safety limits on robot movement so proceed with caution.
Ok. I am doing mastering right now. Machine actually doesnt know the position it is standing on. Take a look at the attached image.
-
Dear team,
We are having a breakdown at our KRC4 Kuka Robotic palletiser. We are facing Workspace monitoring functions deactivated ( mastering error) since the start of production today. I understand that there are threads about similar issues on this forum, but in their case machine was able to move on Jog which meant that it was not exactly a mastering error!! Their 24v power supply was faulty. Our machine however is on complete stop. And not moving at all? I am relatively new to KUKA so might not know all the terminologies we use here. What i want to ask is it possible to lose all the axis mastering like this? And should i master all the axis first or check anything else?
System is running KSS 8.2
Alarm picture is attached
-
Did you look in to the System folder? if config.dat is crossed, then everything else will be like in your picture(any other program....), if it is you can take config.dat from your working backup archive....
Did exactly that even though the config.dat file seemed ok.
After retrieving only config.dat file from the healthy archive, problem was resolved.
Thanks a bunch for pointing me to the right direction.
-
Did you look in to the System folder? if config.dat is crossed, then everything else will be like in your picture(any other program....), if it is you can take config.dat from your working backup archive....
no. it is not crossed. Means that it is in good health.
-
My first suggestion will be to do a fast check-up. Compare the whole current program files with your last Backup.
Normally, after a robot is (re)commissioned it is recommended to have an image copy. Do you have any current one?
Are you talking about the whole hard drive image or just the archive files?
I have both.
-
Hello,
did you uninstall any Technology Package?
No..Did not do anything.
Production ended normally yesterday. Today we could not load the program as mentioned in the attached picture in the original thread.
-
How to tell if is damaged or not?
-
Hi,
I am new to the forum so kindly excuse any misconceptions and misunderstandings of forum rules.
My KUKA robot is down due to some reason.
The contents of programs are not accessible. Hence we are unable to run the machine.
On the message page it says.
KSS00203 General Motion enable
Effect: Ramp-Down Braking
Input of active commands (Robot motions, Program start is blocked)
I have attached the pictures of the messages as well.
Prompt responses will be highly appreciated.