Closed mmurooka closed 2 years ago
There indeed seems to be issues. I just tried on a simple controller, and:
In choreonoid:
init_pos
In ticker: it works.
This fails after the controller's reset, before that the pose is properly set.
https://github.com/jrl-umi3218/mc_openrtm/pull/21 fixes the init_pos
issue.
https://github.com/jrl-umi3218/mc_rtc/pull/286 fixes initialization of the real robot's attitude when using
InitAttitudeFromSensor: true
InitAttitudeSensor: FloatingBase
With these patches you can test either:
init_pos:
translation: # ...
InitAttitudeFromSensor: true
InitAttitudeSensor: FloatingBase
From a quick trial of LIPMStabilizer
controller with both JVRC1
and HRP2KAI
(using the Attitude
observer), I could not reproduce https://github.com/jrl-umi3218/mc_rtc/issues/177, neither by setting the robot's init_pos
or by changing the robot initial pose in choreonoid and using InitAttitudeFromSensor
.
From a quick trial of LIPMStabilizer controller with both JVRC1 and HRP2KAI (using the Attitude observer), I could not reproduce https://github.com/jrl-umi3218/mc_rtc/issues/177
That is different from the behavior I have tried in my local environment.
With putting control/real robot to 20m forward from the origin with init_pos
thanks to https://github.com/jrl-umi3218/mc_openrtm/pull/21, JVRC1 falls down forward after around 10 secs in choreonoid with lipm_walking_controller. And https://github.com/jrl-umi3218/mc_rtc/pull/285 solved it.
Thanks @mmurooka for the report and @arntanguy for the quick fix!
I added the following line to the controller configuration file to reproduce this but it seems not working.
I assume that the robot is displayed away from the origin on Rviz, but it is displayed at the origin. I tried it in several kinds of controllers (LIPMStabilizer, LIPMWalking, and my own controller) and it didn't seem to work in any of them.
There is the following message in controller output.