-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEAT]: Multi robot using Zenoh #19
Comments
I'd suggest making the namespace an environment variable option which by default is no namespace. |
see #20 |
I'm thinking about what @LeonardoGuevara wants to do with the limos, have two limos communicate with each other. E.g. limo 1 publishes a topic and limo 2 subscribes to it. |
Does it work at all or not? It may be best if we deploy a zenoh server just like we do with mqtt, and let all robots connect to that with their namespace |
As a quick "fix" you can launch zenoh bridge |
Sounds exactly like what we need the students to do, I will try it on Monday with the Limos. |
@marc-hanheide This won't work we need to set up a zenoh server/router for this to work properly as @LeonardoGuevara wants four limos to communicate with each other. |
Description
To run zenoh on multiple robots and interact with a single zenoh server need to change the line in the docker compose file and add a namespace e.g. limo number. -n /limo_1522
Topics on the server are /namespace/topic e.g. /limo_1522/imu
command: bash -c "source /opt/ros/lcas/install/setup.bash; (zenoh-bridge-ros2dds -n /limo_1522 -l tcp/0.0.0.0:8888 &); (ros2 launch astra_camera dabai.launch.py &); ros2 launch limo_bringup limo_start.launch.py"
Tried this with two limos and the topic data lags quite a bit.
This is more for Leonardo in ROB1001 for two limo robots to communicate with each other.
Additional Information
No response
The text was updated successfully, but these errors were encountered: