You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When sending ros2 messages over a topic from a client to a server via zenoh, they sometimes do not arrive.
To establish a connection over the zenoh bridge, a ros2 subscriber is to be created automatically on the client that reads in the messages from the desired topic. This does not happen in some cases, resulting in no messages transferred to the server.
We use zenoh-dds-bridge as router on server, and as client to the router on our robot.
then restart the zenoh bridge on robot -> new zenoh subscriber on robot (matching to zenoh server publisher) is sometimes created and sometimes not. Thus, the messages published on the robot only sometimes arrive on the server, sometimes not.
System info
Client: Jetson Xavier (Ubuntu 22.04)
Server: Jetson Xavier (Ubuntu 22.04)
connection: Wifi
Ros2 version: iron
zenoh_bridge_ros2dds version: 1.1.0
The text was updated successfully, but these errors were encountered:
Describe the bug
When sending ros2 messages over a topic from a client to a server via zenoh, they sometimes do not arrive.
To establish a connection over the zenoh bridge, a ros2 subscriber is to be created automatically on the client that reads in the messages from the desired topic. This does not happen in some cases, resulting in no messages transferred to the server.
With our workaround (removing some code) it works for us, but removing some code is probably not ideal: https://github.com/pixel-robotics/zenoh-plugin-ros2dds/tree/always_create_subscriber
To reproduce
For a ros2 topic we have a
We use zenoh-dds-bridge as router on server, and as client to the router on our robot.
then restart the zenoh bridge on robot -> new zenoh subscriber on robot (matching to zenoh server publisher) is sometimes created and sometimes not. Thus, the messages published on the robot only sometimes arrive on the server, sometimes not.
System info
The text was updated successfully, but these errors were encountered: