Thanks for the help guys! I will try both methods and see which one works better for my application.
Posts by Freedom
-
-
No as that will affect cycle time and the movements will be jerky. The only FINE point will be pick/drop positions. Movements have to be CNT. This program is exactly for error recovery and getting robot back to Home position for new cycle.
-
Hello everyone,
Is it somehow possible to number motion points using registers? On Kuka robots I've done this using a trigger and when the motion point was reached, a step counter was then updated. I can easily say R[1]=1 after the point but I'm worried with the robot reading 3 lines ahead that the registers will have the wrong values for shorter motions.
I need to create a program that returns the robot to Home position regardless of where the robot is. To do this I need to number each point so that the robot knows where it is and will either go forwards or backwards in the program, depending on gripper status, to Home position. I need to find a way to do this so that the register numbers only update when the position coordinated have been reached and motions should be continuous.
Any ideas on how to do this?
-
Thanks for the feedback guys. I found that it had to do with using %INCLUDE and instead I had to use VAR FROM iscom_CFG.
-
Hey guys,
I'm new to programming with Karel and need to modify an existing tech package for a 3D measurement system. The problem that I'm having is trying to build a file called getPath.KL that I wrote and when doing so I get errors that are listed for a file called iscom_CFG.KL(supplied by customer) that can build successfully. I even have the .pc file in the File tree.
What I don't understand is why the error path is the .KL file for iscom_cfg and why is it pointing to the iscom_cfg file which compiles without errors?
Is it possible to write PR[1]=PR[2] in Karel? So far I haven't found code/syntax for that?
will be much appreciated guys!