-
Notifications
You must be signed in to change notification settings - Fork 2
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
problems while using zenoh with simulation #22
Comments
The warnings about liveliness tokens are a direct consequence of the
The node didn't perform a clean exit, removing all its pub/subs/clients/services before to stop. Please, reproduce the issue with the |
Sure! Here is the back trace for you..
|
This is probably the same issue than ros2/rmw_zenoh#170 . |
That's correct. Then alright. I will proceed with the other tests then. Closing this issue . |
I was trying to launch the gz simulation using the command:
ros2 launch rox_bringup bringup_sim_launch.py
[jazzy-devel branch]if you want to use this, then you also need to export the gz resource path like this :
export GZ_SIM_RESOURCE_PATH=~/rolling_ws/src/rox/:~/rolling_ws/src/neo_gz_worlds/models
and also clone the neo_gz_worlds
while doing so, the spawn
create
node fails for some reason. with the following error:Also on the teleop terminal, I can see the following piece of warning:
we don't see this while using other dds vendors.
Although we are able to move the robot like as usual, I thought, this might be something helpful to improve zenoh
Here is the full logs:
The text was updated successfully, but these errors were encountered: