Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Simulation does not match Kuka

#1
Hi,

Via Python API I am trying to jog the robot with both linear and rotational movements in/around x, y, z. In the RDK simulation, when the robot 'Kuka 150 KR 2700-2' is not connected, jogging via Python works exactly as expected for both linear and rotational movements. I calculate the new poses via the following code, followed by executingMoveJandMoveL.


linear: newPose = transl(x, y, z) * robot.Pose()
rotational: newPose = robot.Pose() * rotx(..) * roty(..) * rotz(..)

However, when I connect to the Kuka, the requestedlinearjogging movements result in unexpected movements (x,y,z translations, a,b,c rotations, rather than only the requested translation). The rotational jogging movements do work as expected for both simulation and the Kuka.

I checked the cartesian coordinates and the joint values for the Kuka and RDK, and they match. I tried to modify theKuka KR 150 R2700-2via RDK and found here that theBase reference, Base, joint 1,..., joint 6不选择正确的部分the robot (see image attached). Could this be a mistake in the RDK file that was sent to me? Or do you have any other idea what could be the reason for this mismatch? Thank you in advance!


Attached Files Image(s)



Messages In This Thread
Simulation does not match Kuka - byluuk_endlich- 02-28-2023, 10:55 AM
RE: Simulation does not match Kuka - byAlbert- 02-28-2023, 11:19 AM
RE: Simulation does not match Kuka - byAlbert- 02-28-2023, 01:32 PM
RE: Simulation does not match Kuka - byAlbert- 02-28-2023, 02:46 PM
RE: Simulation does not match Kuka - byAlbert- 02-28-2023, 04:10 PM
RE: Simulation does not match Kuka - bymaexbecks- 03-03-2023, 02:43 PM
RE: Simulation does not match Kuka - byJeroen_F- 09-04-2023, 09:03 AM
RE: Simulation does not match Kuka - byAlbert- 09-04-2023, 04:38 PM



Users browsing this thread:
1 Guest(s)