How can I make a KRC2 ED05 cabinet twin . KUKA Kr200 3 comp . and kr210 . In addition, there are differences in the insides of mfc3tech robot cabinets and mfc3 stand ci3 tech stand ci3
How can I make a KRC2 ED05 cabinet twin . KUKA Kr200 3 comp . and kr210
-
Ryno -
April 13, 2022 at 6:04 PM -
Thread is Unresolved
-
-
Change the robot type for the Krc2ed05 cabinet
-
robot cabinet
-
How can I make a KRC2 ED05 cabinet twin . KUKA Kr200 3 comp . and kr210 . In addition, there are differences in the insides of mfc3tech robot cabinets and mfc3 stand ci3 tech stand ci3
"Twin" in what way? If you want two different KRCs to perform the same job, you can simply connect them both to similar-model KR arms and copy the programs across. There's really never any need to make two KRCs identical to each other in hardware. It's more important to make the KR arms match, if they're intended to do identical work.
-
"Twin" in what way? If you want two different KRCs to perform the same job, you can simply connect them both to similar-model KR arms and copy the programs across. There's really never any need to make two KRCs identical to each other in hardware. It's more important to make the KR arms match, if they're intended to do identical work.
I need to copy the robot program from one krc2 ed 05 with a kr210 robot, to another krc 2ed05 but already with a kr200_3 comp robot how to do it. I didn 't find any information . I thank all the participants in advance.
-
you can simply transfer program file(s) from one robot to another.
programs are pieces of software. so what matters most is software version (KSS version).
differences in hardware (MFC, EOAT, robot model etc) are secondary.
-
you can simply transfer program file(s) from one robot to another.
programs are pieces of software. so what matters most is software version (KSS version).
differences in hardware (MFC, EOAT, robot model etc) are secondary.
Is there a manual for step-by-step setup of a different type of robot instead of kr210 kr200 for the krc 2ed05 cabinet
-
Is there a manual for step-by-step setup of a different type of robot instead of kr210 kr200 for the krc 2ed05 cabinet
No, because it really doesn't matter, unless the cell setup was bad, or you have something silly, like picking a robot that physically can't reach the same locations as the KR210.
Note: there is a distinction between the KRC (KUKA Robot Controller, the control cabinet) and KR (KUKA Robot, the actual arm)
The simplest approach is to simply copy the programs from one KRC to the other, usually on a USB stick. Then touch up the motion points on the second KRC. Editing the non-motion code should never be necessary unless the two KRCs have very different KSS versions (like taking programs from KSS 5.6 to KSS 8.3). But the KR makes no difference to the code. It will make a difference to the motion points, but that's all.
If you want two programs to run identically on two different KRs, without touching up points, then you need to perform your setup on the first robot correctly: Teach Bases on the various tooling and stations, program all points using those Bases, then re-teach the Bases in the 2nd robot after copying the programs across. As long as there are no gross physical differences between the cell layouts, this should work 90% of the time.
The tools on the two KRs would also need to be physically identical, and mounted identically, or you will need to re-teach the TCP(s) on the 2nd KR to use the equivalent points on the 2nd tool.
-
Is there a manual for step-by-step setup of a different type of robot instead of kr210 kr200 for the krc 2ed05 cabinet
there is a KUKA training that explains how to create, manipulate, backup and restore program.
there is a documentation on how to do those things, and commission robot.
there is no documentation explaining how to do it on robot A or robot B specifically.
-
-
-
-
🙈Did you create an archive and restore it on the other? Thats not what was explained before. An archive also contains machine configuration and thats not working for a different robot type. You should only copy the relevant program.
Fubini
-
when creating/restoring archive you have an option to archive all or only programs. be careful what you do.
-
when creating/restoring archive you have an option to archive all or only programs. be careful what you do.
These are all translation difficulties. I 'll try to explain what I wanted to get and what I did . I have a working machine cabinet krc 2 ed 05(ci3standart , mfc3 stadart, rdw2) robot krc210 and there is a cabinet krc2 ed05(ci3 extend, mfc3 tech) robot kr200 3com is a learning robot for experiments. What do I want? I want to reproduce the logic of the working machine as the first robot. It does not matter that the length of the shoulders is different, I will make the touchup points different.
-
when creating/restoring archive you have an option to archive all or only programs. be careful what you do.
All hard disk images of both machines and archives are available.Tell me how to make a robot for training similar to a working robot How to change the drives in the configuration?
-
correct, it the robot reach or working envelope do not matter, just copy programs you want onto second system. if the robots have same generation KSS, even inline form motions will be usable without problem.
since both are ed05 they should be close enough. unfortunately due to translation or other difficulties, exact KSS versions are still unknown and we are still seeing more and more of unnecessary description (PC hardware for example).
-
and there you go again with hardware.... why do you want to change drives?
-
so you have two systems:
System A has one robot arm, kuka PC, fieldbusses, EOAT etc.
System B has same or different robot arm, kuka PC hardware options, fieldbusses, EOAT etc.
System A is used in production and System B is used for training. There is no need to exchange any hardware (physically or configuration). At least you did not mention anything that would necessitate that.
You can take program modules from System A and copy them to System B. They will run. But transfer only program modules, not MADA or $config.dat or anything else.
-
so you have two systems:
System A has one robot arm, kuka PC, fieldbusses, EOAT etc.
System B has same or different robot arm, kuka PC hardware options, fieldbusses, EOAT etc.
System A is used in production and System B is used for training. There is no need to exchange any hardware (physically or configuration). At least you did not mention anything that would necessitate that.
You can take program modules from System A and copy them to System B. They will run. But transfer only program modules, not MADA or $config.dat or anything else.
robot A
-