Passing data to multiple instances of HardwareInterface from control node about ros2_control HOT 8 OPEN

Do you need to share data at run-time, or only at loading/initialization of the different components?

from ros2_control.

@tenfoldpaper maybe implementation of gz_ros2_control is interesting in this regard for you? Can you check it?

from ros2_control.

Do you need to share data at run-time, or only at loading/initialization of the different components?

Sorry for the late reply!
I need to share data at run-time. Generally, this should be possible by passing a reference to the mjData* and mjModel* pointers that get instantiated when loading up the scene using Mujoco. So far I've managed that successfully with member variable classes.

Since data is only accessed in the controller's read and write loops (and read and written in those parts), there shouldn't be major issues, as from what I can tell, the respective HardwareInterfaces' read and write functions are executed serially.

There is a mujoco-ros-control repo for ROS1 I found before that did the whole manual initialization thing, which made this possible. So far, I haven't been able to find a solution to this yet.

from ros2_control.

@tenfoldpaper maybe implementation of gz_ros2_control is interesting in this regard for you? Can you check it?

I'll take a look at it in a couple days and update my comment on this, but thank you for the suggestion!

from ros2_control.

So I went through gz_ros2_control, and it appears that the way it is handling ros2-control is not really transferable to MuJoCo.
It seems to work based on Gazebo's Plugin interface, which seems to create instances of ros2-control objects inside the simulation directly.

Since MuJoCo needs to be initialized and executed directly in ros2-control in the main control node, and there is no easy way to create a similar plugin-like interface for it, unfortunately it does not solve the problem.

@christophfroehlich , do you know any way to implement what I asked in the opening post?

from ros2_control.

No I don't know a way to pass data between different hardware components. But maybe I don't understand your problem correctly: You will have to use different hardware components anyways, one (set) for your robot, and another one (set) for your simulation. For example, two hardware components for your real hardware (arm + base), but a single monolithic one for mujoco?

from ros2_control.

@tenfoldpaper Maybe what you are looking for is a System HardwareComponents, where multiple actuators can coexist and share information.

from ros2_control.

@tenfoldpaper Maybe what you are looking for is a System HardwareComponents, where multiple actuators can coexist and share information.

as far as I understood he wants to share data between components which are not known altogether at compile time, but loaded dynamically.

from ros2_control.