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

Define a ContactManager / ContactSchedule / ContactPhase interface #5

Open
wxmerkt opened this issue Feb 18, 2022 · 0 comments
Open

Comments

@wxmerkt
Copy link
Contributor

wxmerkt commented Feb 18, 2022

  1. Create a ContactManager msg that contains a set of ContactSchedule msgs, each contact schedule per each leg.
  2. Redefine the ContactSchedule msg in such a way it contains a set of ContactPhase msgs, each one defines timings and /or foothold target. The first phase should be active, the second inactive, and so on. Inactive phases need to define foothold target.
  3. Create the ContactPhase msg as defined in 2.

This format mimics exactly the definition of a contact diagram introduced in Caracal.
It works for any kind of robot.
Below, I provide the code for each message.

  • ContactManager msg
std_mgs/Header
whole_body_mpc_msgs/ContactSchedule[] contacts
  • ContactSchedule msg
string name
whole_body_mpc_msgs/ContactPhase[] phase
  • ContactPhase msg
float64 duration
float64 step_height
geometry_msg/Pose target

Note that Caracal doesn't need the starting foothold, it uses the current one
But, we could publish the starting footstep placement if you think it is relevant for display purpose.

Originally posted by @cmastalli in #4 (review)

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

1 participant