Thanks for all your replys
Posts by Y105657LL
-
-
These days,I have experienced SRVO -062 Alarm。after this fault,I can't figure out the relationship of encoder and battery,so confusing.
1.IF the controller is ON,the supply of encoder should be controller(save battery power),IF controller OFF,the supply of encoder should be battery.IS this right?if not,plz tell me
2.if the controller is always ON and the 4 battery is exhausted,will SRVO-062 alarm occur?
3.Does the SRVO -062 alarm mean "the robot need calibration"?
-
Hi,bro,how was your robot with this err? I'm encountering the same err "kss 01073", how did you solve the kss 01073 finally? Thanks for your reply
-
i would say make sure to have up to date backup for each robot, maintain robot and controller per manuals, don't let things escalate to a point of failure. this means keeping things clean, regular (and correct) work or replacement of wear and tear items (robot oil, batteries, counterbalance, energy supply, fans).
optimizing programs for less frequent stops and less violent acceleration/jerk etc. and for gods sake make sure to tighten all strain reliefs, cable glands, buttons etc. plus one thing everyone forgets - maintenance of proper documentation. people walk on or throw away valuables like CDs, schematics etc. recovery sticks become expensive and no longer functional souvenirs...
i was amazed how many people would complain about lack of documentation or support the moment i arrive... and when i open cabinet i see shoe prints, scratches and all kinds of stains and damage to CDs and schematics. guess where my sympathy levels are after seeing that.
got called once to fix robot that did not work any more. robot was on pedestal, and base was covered with rugs drenched in oil and impregnated with sharp metal chips. and the operator was trying to squeeze past robot to recover dropped part. in process pulled on those rugs and disengaged X30 connector. such nice place to start fire....
Thanks. I got it. About data backup,we did regular program backup every 2 months and system image file. Oil change and counterbalance check are the part of annual maintenance project. As for clean, I can't ensure all of it, the cabinet seems ok,but robot arms is bad,especially the gear box of A3 which is dusty on the surface,the workers can't clean it with dry rag. I'LL make some strategies to handle it.
Optimizing program is important, but I didn't care much about the motions.the speed of most program is 100%,even at A4 huge angle change,maybe I should look over all the robots.
About Docs,I usually find it in accessory USB and the related OPTION DOC file. but I still do not have KUKA PARTS & DOCS,I can't find the CDs.
I'll notice all of you said,thank you
-
Hi! How You guys doing. I am a maintenance technician in a BIW shop, I work with 60 servo KUKA welding robots. This is my second new job and is also a new challenge for me. I used to work as a robot integrator. But now, I have to change my work property, pay more attention to the robot preventive maintenance or repair.I don't know how to start with it. All I did recently is optimizing program and some KRC2 robots upgrade project. So, Can you guys who had worked in factory give me some EXP and maintenance works contents including: 1.reducing robot downtime 2. Diagnostic 3. Finding robot problems in advance(using tools?I even saw that use thermal imagery on robot arms in some factory interview video.etc ...)
THANKS for your suggestion and share
BTW thanks for some friends like panic mode. skyfire.etc in KUKA forum.they helped much
-
yes 40A is pretty much the standard when it comes to servo guns.
both robots will need tech package to control the servo-gun. not sure why you need gripper tech but if you do have things like gripers etc. that will do the job nicely.
for R1 you do not need to replace anything, robot axes stay on KSP40 and KPP3, so you need to add KSP40 for E1.
for R2 you need to replace KPP0 with KPP1-40, so E1 will be connected to this KPP1.
since you are adding only one axis, robot RDC will do just fine to connect servogun resolver.
THANKS!!I haven't thought that add KSP40 for E1,I only think that use KPP1_40 for E1
....oh,my...
As for the OPt,we'll add new servogun TC for both robots.
-
There are 2 robots with different drive configuration:
R1: KPP3-20 + KSP40
R2:KPP0 + KSP20 +KSP40
Both do not have external axis.
Planning:add a servogun to this 2 KRC4 robots.
Related info:
KSS VERSION 8.3.40
Opt: only one basic boardpackage option and one gripper tech.
For R2 I can replace KPP0 with
KPP1 40,but for R1 I don't know the optimal way. or I need a KSP20 and a
KPP1 40 ?that maybe cost too much for R1...
That is right? BTW KPP1 40 is required for servogun.
THANKS for your suggestion in advance
-
I would add that in some ProfiNet devices, like Festo manifolds, there are differences between regular modules and "docking" modules (FSU), and is very common take a look at ProfiNet configuration and find that the network was misconfigured with a normal module, when in fact it should be configured with the docking one. Most of times the regular ones will work, but will take more time to finish the bus coupling. But sometimes You will have timeout problems.
And older GSDML files also can produce this kind of error.
Thanks! You mean add that is "IF ret==1 THEN run KRL command again"?
The module is SMC and I think GSD should be OK? I'll check it.
As you say ,sometimes we still have,It's not easy to figure out the root.thanks for your share
-
well, are you sure timeout value is not set too short?
and why is it hard to post EXACT message - with message number AND timeout value?
did you read READ FIRST?
My bad...this happened few weeks ago,and recently it works well.I think Timeout is easy to understand, the real reason is worth to discuss
. Back to the question,the Timeout value is 1000,I didn't change it. When waiting for RET==0, I just need to run KRL command again and coupling successful
-
Hi! I'm working on a KRC4 robot,here are some related info:
1.KSSVersion :8.3.28
2.Profinet KRC-Nexxt 3.2
3.tools:gripper and servogun
4.tool change device:ATI
The problem is that when I dockon the gripper and coupling the profinet device(USER ID:78) via KRL command :
RET=IOCTL("PNIO-CTRL",50,78)
Wait for RET==0
In most cases , it executed successful. But sometimes it's Timeout, The RET value was 1,so the robot was waiting RET ==0 until we found it's not working,but if I run this coupling KRL command again,it's always coupling successful(the RET value became 0 ). According to the manuals,the RET value means different coupling status,0 is executing successful,1 is executing Timeout,2 is internal error.why?why I need to execute the command second time?or I should optimize the dockon program:
IF the RET==1then run KRL command again.
It's like a useful idea. But my question is:
1.what is the real reason for "Timeout",the profinet cable and power supply is ok.
2.what is the difference between "the profinet device lost connection" error and profinet coupling"Timeout"?
3.how do you bros program the profinet coupling KRL Macro
Thanks for your reply and share.
-
Does the HMI appear if you connect a monitor to the controller?
It appeared on smartpad. Meanwhile, the monitor was showing a SYSTEM ERROR code 0X0000007B with blue screen....this code means there is some ERRORS in HDD
-
What does that mean? You have a monitor, so watch the monitor during boot, not the smartpad.
It's smartpad can't connect to KRC. THE Monitor was showing a system error message with blue screen. Err code is
0X0000007B. I have searched it. It means error in HDD.
-
Sounds like you aren't having the same problem at all. Do you mean you're getting the "Unable to establish connection to KRC. Robot control not possible." message on the teach pendant?
YES.....I even restore the HDD image successful.but after power on. Can't connect to KRC message came out again.
-
You can download the latest update for the stick from Kuka xpert website.
I did this. But another damn things came out again. Restoring is executing well in SILENT AND GUI mode. After turning it on.... still can't connect to KRC.
-
stick should be configured to only work with KUKA controllers.
silent mode is fine and very useful feature unless you don't mind carrying around extra monitor, keyboard and mouse.
It's damn hard...I updated the USB to 2.2. But didn't check the checksum file... Because I don't get how to do it.
Then I updated to 3.0,it seems well,update is success.
After that,I put the imageC&D to USB.Restoring was also going right.I was pleased.....but when I turn it on.cannt connect to KRC came out again..so I decided to use GUI mode, select images,start to restoring.that also works well.after turn off KRC and plug out USB..I TURN it on again....damn. Can't connect to KRC came out.....
Oh.no....Im so tired...help
-
Hi!now I'm facing the same problem...restoring execution is ok.but when i turn on the switch. Can't connect to KRC possible error comes out again....
-
woah... that is really old...
make sure to follow instructions in the update package.
you will need to do it in two steps. first update 1.0->2.2, then 2.2->3.0
.
hmm......It is a important detail!!
-
The KSR stick is only dangerous if:
1. The KSR stick is set for Silent Restore
2. The KSR stick is left in a computer when the computer is rebooted
3. The "Support only KUKA Controllers" option is un-checked.
If all of these conditions are met, then the KSR stick will attempt to wipe the computer's hard drive and replace it with the robot backup. This is why one should never leave the KSR stick set to Silent Restore:
KSS version does not cause the "no KUKA Controller" error -- the KSR stick completely wipes the entire hard drive, down to the bit level, and replaces it with the contents of the .WIM files in the stick's Image directory.
It is possible that an out-of-date KSR stick may fail the check on a newer KRC, due to hardware or BIOS revision levels.
On my KSR stick, the "Support only KUKA Controllers" option is under the Expert Settings menu.
Thanks! Dear moderator
l learned those knowledges.after update my KUKAUSB, I will not setting the silent mode...
-
You can download the latest update for the stick from Kuka xpert website.
Thanks,my kUKAUSB IS 1.0.39
.......The latest update is 3.0.4
-
yes that may work but one need to be careful for same reason you mentioned.
not sure what exactly it checks for. it must be proprietary but there is not much to go after since not much is in the controller PC. i would guess it is trying to identify motherboard (which is one of the things i look for in my software). so when the signature is not in the DB, stick would need to be updated to a newer version.
I'm confused....motherboard is original. I'll try to find the same KSS...