RoboDK joint position does not match actual UR joint position——革命制度党ntable Version +- RoboDK Forum (//www.sinclairbody.com/forum) +-- Forum: RoboDK (EN) (//www.sinclairbody.com/forum/Forum-RoboDK-EN) + - - -论坛:通用RoboDK问题(//www.sinclairbody.com/forum/Forum-General-questions-about-RoboDK) +--- Thread: RoboDK joint position does not match actual UR joint position (/Thread-RoboDK-joint-position-does-not-match-actual-UR-joint-position) |
RoboDK joint position does not match actual UR joint position-bkanzelmeyer-07-26-2022 I have manually created a program for our UR10e robot using Polyscope on the teach pendant that works excellently. We execute several G-Code toolpaths within, using remote routers (Remote TCPS). I am attempting to recreate this program in RoboDK. I have entered into RoboDK all the RTCP positions and targets as they are indicated in the robot program. However, when I move to a target in RoboDK, I notice that the joint positions are not the same as they are on the actual robot; some off by several tenths of a degree; others as many as 6 to 8 degrees. (I have checked all the various Change config. options available). Is there a way to calibrate RoboDK to precisely reflect the positioning of the actual robot program, which I assume will be necessary to properly execute it? I am concerned that I will not be able to create a program offline that runs accurately on the robot without considerable tweaking afterwards, to align it correctly with the remote TCPs and/or the Base. Does anyone have thoughts or suggestions? Thanks, Bruce RE: RoboDK joint position does not match actual UR joint position-Albert-07-28-2022 When you create Cartesian targets in RoboDK, the joint coordinates are calculated and recorded as well with the active tool and active coordinate system. If you move the tool or the coordinate system, the original joints don't change. This behavior allows remembering the configuration that was used when the target was first taught. If you want to recalculate the joint values for Cartesian targets you can force to recalculate all targets by following theses steps:
If you want this operation to happen automatically every time you generated a program, we recently added the following option that will allow you to do so:
RE: RoboDK joint position does not match actual UR joint position-laelasher-09-21-2022 (07-28-2022, 02:57 PM)Albert Wrote:When you create Cartesian targets in RoboDK, the joint coordinates are calculated and recorded as well with the active tool and active coordinate system. If you move the tool or the coordinate system, the original joints don't change. This behavior allows remembering the configuration that was used when the target was first taught. It does work. Thank you! |