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

icub2_5: Add alljoints-inertials_wrapper/remapper #264

Merged

Conversation

martinaxgloria
Copy link
Collaborator

So far, if you want to use the IMU test in icub-tests to test multiple sensors at once, the robot must expose in its yarprobotinterface configuration file a multipleanalogsensorsserver that publishes the orientation measurements for all of available sensors, with a prefix that matches exactly the port parameter of the test (the default one is ${portprefix}/alljoints/inertials).

For this reason, it would be nice to have those files upstream also for iCubV2_* simulated models

cc @Nicogene @pattacini

@martinaxgloria martinaxgloria self-assigned this Mar 8, 2024
@traversaro
Copy link
Member

I totally agree, it would be convenient to have alljoints parts for all type of sensors, also because they can provide a performance benefit for whole-body control applications (fyi @robotology/iit-ami-scrum-masters). Anyhow, I am a bit concerned with simulated models functionality diverging w.r.t. to real robots. Can you at least open an issue in robots-configuration to track adding the same devices to the real robots?

@martinaxgloria
Copy link
Collaborator Author

Can you at least open an issue in robots-configuration to track adding the same devices to the real robots?

Sure, I opened an issue:

Maybe it's useful to open a twin issue in ergocub-software

cc @Nicogene

@Nicogene
Copy link
Member

Maybe it's useful to open a twin issue in ergocub-software

If you change the xml of the real erogcub yes 👍🏻

@traversaro
Copy link
Member

Thanks!

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

Successfully merging this pull request may close these issues.

3 participants