Closed ge65luz closed 1 year ago
On a micro-ROS client, the ROS_DOMAIN_ID shall be configured on the source code.
Check this tutorial: link.
Thank you, the link helped. It worked for me after I used cyclone_dds instead of rmw_fastrtps_cpp and ran ros2 run micro_ros_agent micro_ros_agent udp4 --port 8888 -v5
, instead of only ros2 run micro_ros_agent micro_ros_agent udp4 --port 8888
.
Issue template
Steps to reproduce the issue
I try to publish data from a micro ros docker container and receive it in a ros2 humble docker container. Therefore, i have written my own dockerfiles and docker-compose.yaml. But the listener doesn't receive data and when i run "ros2 topic list" the publisher (ping_pong) is not listed.
This is my Dockerfile:
The name of the docker image created by the dockerfile is called "micro_ros_image.v1:latest". And this is my docker-compose.yaml
Expected behavior
The first docker container launches the agent, the second one publishes, and the third one listens/echos.
Actual behavior
Additional information
I also tried to use rmw_cyclonedds_cpp as dds, i gave every container its own image (different names) and I used a real subscriber(listener), but it didn't help. I only receive data if i run everything in one container. Because i want to execute the publisher, directly when i launch docker compose, because i want to create a chain of pub/sub.
Any ideas what i can try. The agent receives the data from the publisher but doesn't transmit the data further.