-
Notifications
You must be signed in to change notification settings - Fork 391
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
[Question] No data published to any topic, ZED2 in Docker #748
Comments
Hi @XDGFX |
Bah, I can't believe I didn't check that. Topics are populated inside the container (tested with Seems like a Docker networking issue. I'm more familiar with ROS2 and Docker networking so I've likely missed something here. |
Check that all the ports used by ROS are opened: |
Got it working 👍. As ROS1 seems to need a lot of ports open I've set the networking to host ( Many thanks for the nearly instant help :) |
@XDGFX would it be possible for you to share the Dockerfile for ZED2? Cheers |
@Leovilhena The Dockerfile I'm using is here 😄 |
I'm having trouble setting up a ZED 2 camera.
Running on a Jetson Xavier NX (Ubuntu 18.04, L4T 32.5.0). I've set up a Docker container for the 3.5 SDK and wrapper (although for reference, the same issue is happening with the provided
3.4-ros-devel-jetson-jp4.3
image).The ROS master is running on the host, and the container is using bridge networking. Therefore, I set the environment variable
ROS_MASTER_URI=http://172.17.0.1:11311
. I can start the wrapper usingroslaunch zed_wrapper zed2.launch
, and topics appear on the host as expected.However I cannot get any data from the topics, they all appear empty. I've tried opening rviz with the zed2 config provided in the examples repo. I've also tried echoing various topics, and using
image_view
to show a raw image (rosrun image_view image_view image:/zed2/zed_node/right/image_raw_color
).Hopefully this is just a simple config issue, help is much appreciated!
For reference, the startup appears fine, shown below:
The text was updated successfully, but these errors were encountered: