Using latest ISAAC ROS 3.1 documentation following this guide: Isaac ROS ZED Setup — isaac_ros_docs documentation after doing everything the command: /usr/local/zed/tools/ZED_Explorer doesnt open the camera at all, ie it doesnt know a camera is connected at all. using latest jetpack 6 and jetson AGX ORIN Developer Kit
Hi @nir9
Thanks for your post.
As Isaac ROS ZED Setup — isaac_ros_docs documentation mentioned, ZED driver is required for ZED X or ZED X Mini.
If this is not done yet, please refer to Install the ZED Link driver. You need to download the correspoding ZED Link driver and install for your GMSL2 capture card. If it still doesn’t work, please check if the steps in GMSL2 troubleshooting can help.
Best,
Ahung
Hi, the driver is installed, and working outside of the docker, inside the docker there are lots of issues first and foremost is the docker is unable to see any cameras available due to unavailable zed x daemon ie the docker doesn’t have access to this service for some reason .
So the zed is not opening and even picked up inside the docker .
Hi @nir9
Could you try this step insider the docker to source the built workspace and test again?
cd ${ISAAC_ROS_WS}/ && source install/setup.bash
Best,
Ahung
Done that already, checked everything, please list the steps you want me to take at full, because I am sure I have followed all of them already .
The docker doesn’t have access to the zed_x daemon service although it says it started the systemd
Hi @nir9,
I got a chance to try zedx today. We already have link drivers installed on the jetson device. That is the only prerequsite we have before launching container. While launching container we added zed key (Step 4 in doc) which implicitly installs zed sdk inside container. When zed explorere is launched in docker, I saw the warning “Failed to connect to zed_x_daemon”. However, I’m able to get images from zedx even though I got warnings.
If you are unable to get images, please share your log.
Best,
Ahung
i dont have access to zed x daemon at all while inside the docker .
Hello, I’m wondering if there’s any update here? I’m having issues reliably connecting to two cameras from inside Docker. I can reliably connect to both cameras from outside the Docker container via ZED Explorer. When I open ZED Explorer from within the Docker container I can reliably connect to only 1 of the 2 cameras. I also have this issue when trying to launch a ROS node. I can reliably launch a ROS node targeted at the serial number of the device that appears in ZED Explorer inside docker but not the device which does not. I have a QUAD GSML Card, one ZEDX Mini Camera and One ZEDX camera. Running on an Orin AGX 64 GB Development Kit. Using Jetpack 6.0 rev2. it is actually the ZEDx mini that reliably connects inside Docker. No amount of sudo systemctl restart zed_x_daemon will correct the issue , neither will reboots. I have tried connecting both ZEDx cameras to different ports on the GSML capture card and am running out of ideas. I will attach my ZED Diagnostic dmesg to the next post
here are the logfiles I mentioned in my post above. i created them both with the same command , one from inside the docker container and one from outside the docker container
sudo /usr/local/zed/tools/ZED_Diagnostic --dmesg
dmesg_insideDocker.log (28.9 KB)
dmesg_outside_docker.log (33.7 KB)
There are extra flags that must be written to use ZEDX
--network host \
-v /dev/:/dev/ \
-v /tmp/:/tmp/ \
-v /var/nvidia/nvcam/settings/:/var/nvidia/nvcam/settings/ \
-v /etc/systemd/system/zed_x_daemon.service:/etc/systemd/system/zed_x_daemon.service \
-v ${HOME}/zed_docker_ai/:/usr/local/zed/resources/ \
How to use ZED X with Docker - Stereolabs
I think ISAAC-ROS Docker image has couple of them missing. Also for me what it worked to use the container as a root user. you can try that too.
1 Like
I’m forwarding your flag to the engineerings to double check this issue.
Best,
Raffaello
1 Like