-
Notifications
You must be signed in to change notification settings - Fork 49
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
Set home positions #59
Comments
I guess is some-way related to robotology/icub-main#4 . |
The robotMotogGui should call an usual positionMove so the plugin is fine with that i think, have you already tried to fill the config file? |
Yes, I agree with Alberto. Home can be defined in the robotMotorGui.iniFrancesco Nori Robotics Brain Cognitive Science Department Phone: (+39) 010 71 781 420 Fax: +39 010 71 70 817On Feb 13, 2014, at 2:37 PM, barbalberto wrote: The robotMotogGui should call an usual positionMove so the plugin is fine with that i think, have you already tried to fill the config file? — |
It also makes sense to extend robotInterface with a “home” function that allows to park the robot. Given this is already there for parking at startup I think this solution has the advantage that it avoids duplicating information. From: Francesco Nori [mailto:notifications@github.com] Yes, I agree with Alberto. Home can be defined in the robotMotorGui.iniFrancesco Nori Robotics Brain Cognitive Science Department Phone: (+39) 010 71 781 420 Fax: +39 010 71 70 817On Feb 13, 2014, at 2:37 PM, barbalberto wrote: The robotMotogGui should call an usual positionMove so the plugin is fine with that i think, have you already tried to fill the config file? — — |
I guess providing a proper robotMotorGui configuration file is for now something robot/model specific (as in robotology-legacy/icub-gazebo-legacy@057728a) and eventually when the changes discussed in robotology/icub-main#4 will be introduced we will have to implement the necessary interfaces, but in the meanwhile we can close this issue. |
We should support the "set home positions". Currently from the robotMotorGui it is impossible to reset the robot to the original pose.
I think, a part from adding the relevant lines in the config files, we should also implement something in the interface.
@barbalberto
The text was updated successfully, but these errors were encountered: