Unfortunately, we can’t reproduce the issue you’re encountering.
Instead, I created a new device tree and driver that should allow you to use SDK 5 with your setup. To install this fixes please apply those two commands :
Thank you for your help and support so far. The new device tree and driver were very helpful.
I have managed to install SDK 5 and start one ZED X One GS. However, I have to wait until tomorrow to test the ZED X.
In ZED_Explorer, I can start the camera. However, whenever I try to start the camera in ROS2, I receive a calibration error. I have even tried downloading a new calibration file, but the error persists.
[component_container_isolated-2] [ERROR] [1760044125.486706979] [zed.zed_node]: Calibration file error: Calibration file found but it is corrupted. Download your factory calibration file from calib.stereolabs.com or use ZED calibration tool to recalibrate.
[component_container_isolated-2] [2025-10-09 21:08:45 UTC][ZED][INFO] [Init] Invalid calibration file. Recalibrate your camera using ZED Calibration tool or download your calibration file on https://calib.stereolabs.com
[component_container_isolated-2] [2025-10-09 21:08:45 UTC][ZED][WARNING] INVALID CALIBRATION FILE in sl::ERROR_CODE sl::CameraOneImpl::open(const sl::InitParametersOne&)
[ERROR] [component_container_isolated-2]: process has died [pid 5572, exit code 1, cmd '/home/###/ros2_humble/install/rclcpp_components/lib/rclcpp_components/component_container_isolated --use_multi_threaded_executor --ros-args --log-level info --ros-args -r __node:=zed_container -r __ns:=/zed'].
So the ZED X is working now, too.
However, Port 1 only seems to work when no other camera is connected. I tried using two ZED X One GS cameras with the ZED X in Ports 0 and 1, and Port 1 never worked, regardless of which camera was connected.
And now it even runs in ROS, but after sometime the camera just stops working and I get another error. I hope you can help me out ros_zedx_error.txt (6.6 KB)
Indeed, due to the weird behavior you are encountering, I had to constraint the pluggin possibilities. I just saw I made a mistake in my answer earlier. Indeed in order for this system to work, a ZED X should share the same i2c bus as a ZED X One GS.
in order to have all 3 cameras working, connect your cameras as such :
Port 0 : ZED X One GS
Port 1 : ZED X One GS
Port 2 : ZED X
In order to check if the configuration is alright, you can check the i2c buses with : sudo i2cdetect -r 30 and sudo i2cdetect -r 31
If you see two IMUs (0x18 0x68 and 0x19 0x69) on a same bus, it means the configuration is alright.
thank you for your help so far.
If I were to use three ZED X ONE GS cameras and one ZED X camera, how should I connect them? Is there a specific order that I need to follow?
@aperidon
And another question, me applying the new device tree and driver shouldn’t have affect the Capture Card Duo with another Jetson device right?
Because I’m experiencing some weird behavior, when I have four cameras plugged in, the Jetson only detects two cameras, but when I disconnect one, then the Jetson detects all three that are plugged in.
###@jetson-16gb:~$ ZED_Explorer -a
## Cam 0 ##
Model : "ZED-X ONE"
S/N : 309165243
State : "Camera Available"
Path : /dev/i2c-31
ID : 0
Type : "GMSL2"
********************
## Cam 1 ##
Model : "ZED-X"
S/N : 41400471
State : "Camera Available"
Path : /dev/i2c-31
ID : 1
Type : "GMSL2"
********************
###@jetson-16gb:~$ sudo systemctl restart zed_x_daemon.service
[sudo] password for ###:
###@jetson-16gb:~$ ZED_Explorer -a
## Cam 0 ##
Model : "ZED-X"
S/N : 41400471
State : "Camera Available"
Path : /dev/i2c-30
ID : 0
Type : "GMSL2"
********************
## Cam 1 ##
Model : "ZED-X ONE"
S/N : 308071488
State : "Camera Available"
Path : /dev/i2c-30
ID : 1
Type : "GMSL2"
********************
## Cam 2 ##
Model : "ZED-X ONE"
S/N : 301236339
State : "Camera Available"
Path : /dev/i2c-31
ID : 2
Type : "GMSL2"
********************
Changing the Jetson won’t affect the output. The fact that you connect 3 ZED X One GS mean that two of them are overlapping their IMUs and thus the SDK cancel them. That’s why you’re only seing one camera.
Due to this behavior, plugging more than 2 ZED X One GS won’t work.
Before going further into hardware debugging, could you confirm to me that you have the official Jetson kernel and no modification has been made to it except applying the overlay ?
Yes, I used the NVIDIA SDK Manager to flash my Jetson Xavier NX.
However, just to avoid any misunderstanding, the strange behaviour occurred on a different Jetson device, for which I had not yet installed any drivers or device trees. Perhaps this is a new issue that should be posted in a new thread?
And now to go back to my inital Jetson board, for what you’ve sent me a new driver and device tree, it is not possible to plug 3 ZED X One GS and 1 ZED X in? Or would I need a new driver/device tree for that?
