ralphieraccoon

It should be possible if you define your own labels in `.add_coordinates([-30, -20, -10, 0], None)` or similar (the second argument `None` is needed to use the default azimuth labels...

Hi, if someone still wants me to do this, let me know and I'll start a PR.

I'm not sure if discovering which command interfaces are claimed inside `Ros2ControlSystem::init()` is possible since it doesn't provide access to the `ResourceManager` which has this function. To make it work...

> I would prefer that you test and eventually solve the problem in this PR, rather than committing something which is unfinished or buggy. That's fair, though at the moment...

> Open3D 0.18 for Ubuntu Noble will be available from my [PPA](https://launchpad.net/~roehling/+archive/ubuntu/open3d) as soon as Launchpad has finished building the binary packages. FYI, this seems to conflict with PCL, seems...

> I would like to work on this bug. Please assign it to me. Thanks! I don't believe that's nessecary, if you've got a fix you can make a pull...

I think this may actually be caused by an earlier error: ``` what(): URDF cannot be parsed by a `ros2_control` component parser: no ros2_control tag ```

I've done a little debugging, and it seems the `parse_control_resources_from_urdf` function in `ros2_control` is receiving the wrong URDF, it's receving the robot description with all the joints and links instead...

OK, so I think the first issue is down to deprecated behavior in `webots_ros2_universal_robot`, as `ros2_control` now ignores URDF files passed in as parameters and instead always reads the `\robot_description`...

Upgrading to `ros2_control` [4.28.0](https://github.com/ros-controls/ros2_control/releases/tag/4.28.0) seems to fix this. You can get it from the `ros2` testing repository, see [instructions](https://docs.ros.org/en/jazzy/Installation/Testing.html) here on how to change your sources list (remember to run...