| Crates.io | cu-zenoh-ros |
| lib.rs | cu-zenoh-ros |
| version | 0.9.1 |
| created_at | 2025-05-27 00:21:33.753561+00 |
| updated_at | 2025-09-12 20:54:08.943277+00 |
| description | Copper example to use zenoh as a ROS 2 bridge. |
| homepage | https://github.com/copper-project |
| repository | https://github.com/copper-project/copper-rs |
| max_upload_size | |
| id | 1690453 |
| size | 130,750 |
ONLY SUPPORTS HUMBLE at the moment.
cargo install zenohd --all-features
Launch a zenoh router.
$ RUST_LOG=debug zenohd
The log as debug will help you understand the INSANE mapping between ROS and zenoh.
Then run this example.
$ cd cuexamples/cu_zenoh_ros
$ cargo run --release
If you don't have access to a perfect Ubuntu version to run ROS, you can do it from the Docker container given
docker build -t ros-jazzy-zenoh . docker run --rm -it --net=host -v "$PWD":/ros2_ws -w /ros2_ws ros-jazzy-zenoh bash
export RMW_IMPLEMENTATION=rmw_zenoh_cpp
ros2 topic echo /output
To inspect zenoh, this is suddedly some python stuff, so let's go and make a virtualenv.
python3 -m venv zcli
source zcli/bin/activate
pip install zenoh-cli
Dumping ALL the traffic:
zenoh subscribe -k '0/output/**'
0 is the ROS2 domain output is the name of the topic
It is followed with some mangled things like the RIHS01 an and QOS.