Skip to content
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

Reenable motion retargeting for REEM #21

Open
bit-pirate opened this issue May 23, 2013 · 4 comments
Open

Reenable motion retargeting for REEM #21

bit-pirate opened this issue May 23, 2013 · 4 comments
Assignees

Comments

@bit-pirate
Copy link
Contributor

The new pipeline version does not support REEM yet.
What we need to implement to support it again:

  • Update upper_body_adaption in motion_adaption
  • add an output handler, which talks to REEM's joint controller
  • add self-collision handler based on MoveIt!
  • add a motion retargeting controller for reem
@ghost ghost assigned bit-pirate May 23, 2013
@bit-pirate
Copy link
Contributor Author

In order to easily test motion retargeting for REEM I suggest to add a fake joint controller, which sets the current joint states based on the incoming joint command. This controller together with the robot state publisher would be enough to do a simple kinematics simulation.

As a first step I have catkinized the reem_common stack to allow visualising the resulting motion for testing: pal-robotics-graveyard/reem_common#5

@bit-pirate
Copy link
Contributor Author

Adolfo, which (ROS) controller a you currently using for REEM?

@adolfo-rt
Copy link
Contributor

We have an implementation of the JointTrajectoryActionController. We use the trajectory replacement feature to send commands at up to 10Hz. Not in the Github repo, but we have a simple node that gates the output of teleoperation to the controller, so we can start/stop sending commands without killing the whole teleoperation pipeline.

@bit-pirate
Copy link
Contributor Author

That's nice. We use the same action interface (FollowJointTrajectoryAction). Hence, we probably can use the same output handler. Furthermore, motion retargeting now offers an easy way to enable/disable the output in runtime. So this extra node you added might be obsolete now.

@bit-pirate bit-pirate mentioned this issue Mar 19, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants