The issue comes up when the tcp rotation is other than x,y,z,0,0,0. the api generated waypoints do have the tcp offset tho. See Here. This was implemented a year ago and should work. To prevent it from calculating the false inverse kinematics we calculated the rotation manually (rx = -0.58,ry=0,rz=0). After that the bug no longer occurs tho it is not possible to move the robot in the tool space correctly😉
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| FixedPositionDefinedWaypoint | 1 | 885 | December 6, 2021 | |
| Wrong inverse calculation when adding a waypoint to a movej node | 14 | 1298 | August 5, 2021 | |
| Calling Pose from URCap generated Waypoint misses TCP Offset | 16 | 2401 | March 25, 2019 | |
| Joints differ from RTDE values | 10 | 1396 | September 27, 2022 | |
| API generated Waypoints lack in Range of TCP Offset | 10 | 1919 | September 23, 2019 |