-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
yaw movement with setTargetPoseRelative actually moves roll #335
Comments
#BTW, the video also shows that with |
Used the following. I had to apply this patch for hrpsys.
|
it seems relative means relative respect to RARM_LINK5 local coordinates and the convention is
so this seems ok. also please look at https://github.com/start-jsk/rtmros_hironx/blob/hydro-devel/hironx_ros_bridge/test/test_hironx_cartesian.py#L88 to learn how to write test code. |
Thank you for the explanation. What about |
This is because of how the RPY gets calculated. When the elbow is rotated 90 degrees the rotation itself can become ambiguous. This is the reason I was trying to push the setTargetPoseMatrix interface. We've implemented this using python and are happy with this for now. |
I see, something like
may solve the problem -- On Mon, Mar 23, 2015 at 1:59 PM, Hajime SAITO [email protected]
|
Addressed in the upstream fkanehiro/hrpsys-base#543. |
Add a testcase for checking #335 (2nd trial)
See the youtube video; Both
roll
movement that comes as the 1st batch, andyaw
, 3rd, rotate about red axis (x) while we expectyaw
rotates about blue axis.Result of getCurrentRPY('RARM_JOINT5') indicates that
yaw
is rotated as expected in the 3rd batch of the movements.Code is below. I don't know yet how to run assertion check so I haven't added this as a unittest.
The text was updated successfully, but these errors were encountered: