Open roboticshard opened 2 months ago
You didn't specify a concrete link for getCurrentPose()
. Probably MoveIt reports the pose of a different link than the one you looked up in rviz' TF. Another reason could be a different base transform. MoveIt reports poses relative to the planning frame, which is usually the robot's root link. If you introduced a virtual joint or the robot is otherwise offset w.r.t. (0,0,0), a different pose will be reported. In that case, change rviz' fixed frame to the same frame too.
This issue is being labeled as stale because it has been open 45 days with no activity. It will be automatically closed after another 45 days without follow-ups.
I am working on so simple Moveit2 tutorial. I am trying to just get robot position and orientation information by using Moveit2 Script .
I am getting robot pose information by using ( getCurrentPose() method). When I tried to verify the getCurrentPose information, I found that it was inconsistent with TF information.
Your environment
Steps to reproduce
Expected behaviour
TF Gui Output tool0, wrist_3_link Position: X: 0.382871 Y:0.351937 Z:0.808952 Orientation X:-0.70715 Y:0.0057097 Z: 0.00065606 W: 0.70709
Actual behaviour
Moveit2 Output Current pose: pos.X:0.193414 pos.Y:0.286017 pos.Z:0.546773 ori.x:-0.707120 ori.y:0.000571 ori.z:0.000656 ori.w:0.707093
Why they are different from each other between Moveit2 Console and TF in Rviz GUI ?
Backtrace or Console output
Use gist.github.com to copy-paste the console output or segfault backtrace using gdb.