-
Notifications
You must be signed in to change notification settings - Fork 104
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
Add the MAS client usage in WholeBodyDynamics #596
Conversation
I noticed that for @traversaro correct me if I am wrong. I added to this PR some cleanup commit of |
Exactly, that is correct as far as I remember. |
I added also the changes of in the
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved but remember to test it 👍
Let's go back to port-wise managing of the inertial done within the |
In the today meeting, emerged the necessity to connect the TODO:
|
@Nicogene any progress on this? |
This PR depends by robotology/yarp#2098, the minimum yarp version will be bumped. |
The head v2.6 has been handled in this way in I know it is different to how the versioning is handled in If I have green light @traversaro and @pattacini I start testing |
🚦 green lights @Nicogene 👍 |
Today I tested successfully both WBD and It worked both with the classic imu and the imurfe. Ready to be merged. |
Preface: I honestly don't know how the imu data is used in this module, i just kept the logic.
This PR add the possibility to make communicate the IMU and WholeBodyDynamics using the
multipleanalogsensorclient
.cc @marcoaccame