The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
So I was also able to get it to work with a custom type. This was for talking to a native Connext application. Here's what I had to fix: - Generated a idl file using 'ros2 run rosidl_adapter msg2idl.py <msg_file>' - Mnaually modified the generated idl file to add module dds_ as shown above - Set topic name in the native DDS application to rt/<ros_topic_name> - Modified the native DDS application topic qos to (1) empty partition list since ros2 uses empty partition list and the other endpoints should also have empty partition list otherwise they won't communicate (2) destination order QoS set to "by reception timestamp"
This setup worked for me. The QoS changes required for other native DDS vendor applications e.g. Cyclone or FastDDS, may vary from what I listed above.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
