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 controlboard for nested model #233

Open
traversaro opened this issue Feb 9, 2025 · 3 comments
Open

Define controlboard for nested model #233

traversaro opened this issue Feb 9, 2025 · 3 comments

Comments

@traversaro
Copy link
Member

In Gazebo Classic/gazebo-yarp-plugins, it was possible to have a plugin-less model, and then include it in a model in which the gazebo controlboard plugin for its joints, for example something like:

<model name="pendulum_with_yarp_plugins">
    <include>
        <uri>model://single_pendulum_no_initial_configuration.sdf</uri>
    </include>
    <plugin name="gzyarp::ControlBoard" filename="gz-sim-yarp-controlboard-system">
        <yarpConfigurationFile>
            model://conf/gazebo_controlboard.ini
        </yarpConfigurationFile>
    </plugin>
</model>

This is not possible anymore with gz-sim-yarp-plugins, and for example created duplication in test files added in #232 . It would be great to support this pattern also in gz-sim-yarp-plugins .

@traversaro
Copy link
Member Author

See gazebosim/gz-sim#1844 for a similar bug in gz-sim.

@xela-95
Copy link
Member

xela-95 commented Feb 10, 2025

@traversaro do you think this is a current limitation of the plugins or it depends on gz-sim itself?

Issue gazebosim/gz-sim#1844 is closed as completed and the related PRs merged if I'm not mistaken, so it gz-sim should allow this, right?

@traversaro
Copy link
Member Author

I would guess mostly a current limitation of the plugin. In

auto jointEntity = model.JointByName(_ecm, jointFromConfigName);
we should make sure that we also search for the joints of the nested models, and I guess somehow gz-sim allows that as gazebosim/gz-sim#1844 was solved.

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