Closed alberthli closed 11 months ago
Hi @alberthli what is the SDK version that you are using?
We're using version 4.0. Specifically, we're using the Stereolabs base image stereolabs/zed:4.0-devel-cuda12.1-ubuntu20.04
from Dockerhub (file provided near the top of the issue).
This is a problem not related to the ZED ROS2 Wrapper, but to the ZED SDK. The ZED SDK team is already on it and a fix will be released as soon as possible with one of the next patch versions. Thank you for reporting and for the useful information. If you have other useful information please send an email to support@stereolabs.com. I close this issue.
Thank you for the speedy reply. I'll keep an eye out for the next release. If the team needs more specific information, feel free to tag me on this issue as well, and I would be happy to provide it.
We are also running into the exact same problem - may I ask is there any update on the timeline of the patch? Thank you!
Preliminary Checks
Description
We're experiencing a bug where when using multiple ZED 2i cameras, the detection of the cameras is inconsistent. We are using a containerized setup via Docker. The relevant files to reproduce are attached here.
When running the multi-camera launch file provided in the Zed ROS2 examples repository with the command
we see the following error:
Additional details regarding the error:
ros2 launch zed_wrapper zed2i.launch.py
Additional things we have tested:
lshw
import pyzed.sl as sl; sl.Camera.get_device_list()
)Steps to Reproduce
Because it is unclear what exactly causes the failure, we cannot reproduce the bug with 100% accuracy. However, doing something in the following list usually causes it.
Build the provided docker image using the command
Start a container using the provided bash script with the command
in the directory where the provided files are unzipped.
In the container, run the command (possibly multiple times until failure)
If step 3 does not cause failure, try joining the existing container by opening a new one using the command
Run the command from step 3 repeatedly.
If step 4 does not cause failure, try exiting the container from step 4 and rejoining. Again, run the command from step 3 until failure.
If step 5 does not cause failure, unplug and replug the cameras in the same or different port and repeat step 5.
Expected Result
We would expect that the two cameras should launch and be detected without issue.
Actual Result
However, only one is detected most of the time, and usually the issue comes up when we need to start/stop our Zed-related nodes.
ZED Camera model
ZED2i
Environment
Output of
nvcc --version
: