Hi,
I'm trying to interface a ROS2 subscriber with a DDS publisher. To keep things simple, I'm starting with using a built-in message type from ROS2: trajectory_msgs/msg/JointTrajectory
When running ros2 on QNX with rmw_connext_cpp I get the following error message:
command:
ros2 run demo_nodes_cpp talker
Error message:
Hello,
i want to route certian topics from a docker network to an outside server, which shall perform a task. For that Ros2 has designed an action, wich i want to use,
For testing (avoiding building an docker image for each new try) i build up a test network with 3 different virtual machines:
VM A: Host Only Network (192.168.64.20/24)
VM B: Host Only Network (192.168.80.20/24)
VM Router: Two Host Only Networks (192.168.64.1/24 AND 192.168.80.24/24) which is the connection of the two networks.
I am interfacing `ROS2` with native `RTI DDS Connector` for python where I am publishing messages in RTI connector and subscribing in ROS2.
I am trying to publish a ConnextStaticSerializedData type message, but encountered an issue where transport info do not match:
I want to get a native rti DDS 5.3.1 application running with ROS2 eloquent. For this, I have written a plugin for the rti routing service and set it up to convert messages from native DDS topic to ROS2 eloquent topics.
According to the rtiadminconsole everyting seems fine. The Match Analyses has no complains and I can subscribe and receive the ROS2 topic within the rtiadminconsole. However, in the ROS2 subscriber the subscriber callback method is never called.
How can I further investiagte this issue?