rosbridge_server does not support "*.idl"-message specifications

[StahlTim]

When trying to forward custom *.idl messages via the rosbridge_server, each iteration triggers an error (here shown for an autoware_auto_planning_msgs ): [rosapi_node-2] Error processing 'module autoware_auto_planning_msgs {' of 'autoware_auto_planning_msgs/Trajectory': ''module' is an invalid message name. It should have the pattern '^[A-Z][A-Za-z0-9]*$''

• Library Version: 1.1.2
• ROS Version: galactic
• Platform / OS: ubuntu 20.04

Steps To Reproduce

• Using the definition of autoware auto messages (see at the top of this issue)
• Launching a rosbridge_sever via: ros2 launch rosbridge_server rosbridge_websocket_launch.xml

Are *.idl messages generally excluded from rosbridge support, or is there a way to work with them?

[jtbandes]

I'm not aware of any special support for this in rosbridge. The error message you're getting looks like it is trying to parse the .idl as if it were a .msg file. Do you have a stack trace for the error? And is there a strong reason that these messages are written as custom .idl files rather than custom .msg?

[jhurliman]

There are no plans to support custom .idl files that do not have accompanying .msg ROS message definitions in rosbridge.

[StahlTim]

Okay, thanks for the info!

In this case we can probably close this issue. However, it might be helpful to include this info in the Readme/Docs (unless it already exists and I haven't found it).

[github-actions[bot]]

This issue has been marked as stale because there has been no activity in the past 12 months. Please add a comment to keep it open.

[jtbandes]

FYI, nowadays the foxglove_bridge supports .idl definitions.