-
Notifications
You must be signed in to change notification settings - Fork 23
Open
Description
Host PC
I'm running a docker container (osrf/ros:jazzy-desktop
) with.
RMW_IMPLEMENTATION =rmw_zenoh_cpp
ROS_DOMAIN_ID=0
and even tried playing around with this config
# echo $ZENOH_SESSION_CONFIG_URI
/root/.ros/DEFAULT_RMW_ZENOH_ROUTER_CONFIG.json5
When I run the router I get
# ros2 run rmw_zenoh_cpp rmw_zenohd
2025-07-24T22:33:23.336315Z INFO ThreadId(02) zenoh::net::runtime: Using ZID: 3904eaf179e47880d2038e6e6a868ff9
2025-07-24T22:33:23.336691Z INFO ThreadId(02) zenoh::net::runtime::orchestrator: Zenoh can be reached at: tcp/[fe80::cff9:d45:fd33:6fda]:7447
2025-07-24T22:33:23.336694Z INFO ThreadId(02) zenoh::net::runtime::orchestrator: Zenoh can be reached at: tcp/[fe80::945:28b0:7131:11d6]:7447
2025-07-24T22:33:23.336695Z INFO ThreadId(02) zenoh::net::runtime::orchestrator: Zenoh can be reached at: tcp/192.168.9.<LAN>:7447
2025-07-24T22:33:23.336696Z INFO ThreadId(02) zenoh::net::runtime::orchestrator: Zenoh can be reached at: tcp/192.168.9.<WIFI>:7447
Started Zenoh router with id 3904eaf179e47880d2038e6e6a868ff9
where WIFI
is the host's IP address and the ROS2 talker/listener cpp examples work as expected.
Embedded device setup.
- I followed this tutorial and purchased a esp32-s3-devkitm-1.
- Setup my platformio.ini for the above device
- Updated SSID and PASS for my network (I can ping the device from my host)
- Updated
CONNECT
with#define CONNECT "tcp/192.168.9.<WIFI>:7447"
to talk to my host PC - Built/uploaded the code to the device
Through the serial interface prints I can see it is able to join my wifi, but the Zenoh Session fails to start.
Any suggestions on how I can debug this further. I'm not sure how to check why z_open fails when you check if the session is valid/open.
Metadata
Metadata
Assignees
Labels
No labels