ZED X One GS camera not detected

nemishanv · July 28, 2025, 4:27pm

I have the following hardware setup:

NVIDIA Jetson AGX Orin board Dev kit with Ubuntu 22.04
ZED Link Quad capture card
3 ZED X One GS cameras

Software setup:

Jetson Jetpack installed via SDK manager : Jetpack 6.1, 6.2, 6.2.1
ZED Link Driver : stereolabs-zedlink-quad_1.3.1-SL-MAX96712-all-L4T36.4.0_arm64
ZED SDK : ZED_SDK_Tegra_L4T36.4_v5.0.4.zstd

I installed Driver and SDK following the instructions on the Stereolab website -

Earlier 2 cameras were being detected and working fine, but now non of the cameras are being detected. Last week only one camera was working, today 2 were working, but now none are being detected. I unplugged and plugged the wires to check whether the 3rd camera would work if i change the connection, but now none are working. I did trying restarting the zed_x_daemon, and also rebooting the jetson. But that did not work.

[https://drive.google.com/file/d/1P7wGrTYzpHbSq_W7biGv7Oak97-ABVcm/view?usp=drive_link](https://dmesg.log file)

Myzhar · July 28, 2025, 4:31pm

Hi @nemishanv
Welcome to the StereoLabs community.

Please run the command sudo ZED_Diagnostic and send me the report file that it generates.

nemishanv · July 28, 2025, 4:33pm

Hello,

I have attached the link of the .log file. Since I cannot upload the file

[https://drive.google.com/file/d/1P7wGrTYzpHbSq_W7biGv7Oak97-ABVcm/view?usp=drive_link]

Nemisha.

Myzhar · July 28, 2025, 4:54pm

The three cameras are all detected.
What’s the output of the command ZED_Explorer -a?

What do you use to try to open the cameras?

nemishanv · July 29, 2025, 8:04am

Hello, this is the output of the command ZED_Explorer -a:

Cam 0

Model : “ZED XOne GS”
S/N : 306037354
State : “AVAILABLE”
Path : /dev/i2c-13
ID : 0
Type : “GMSL”

Cam 1

Model : “ZED XOne GS”
S/N : 300190908
State : “AVAILABLE”
Path : /dev/i2c-9
ID : 1
Type : “GMSL”

Cam 2

Model : “ZED XOne GS”
S/N : 305191828
State : “AVAILABLE”
Path : /dev/i2c-10
ID : 2
Type : “GMSL”

I am running this command to check whether the cameras are working or not - ZED_Explorer and following is the output on the terminal:

** [SVO] Hardware compression (NVENC) available **
(Argus) Error Timeout: (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 92)
(Argus) Error Timeout: (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)

nemishanv · July 29, 2025, 8:43am

Hello,

an update:

with the gstreamer 2 cameras (ID 1 and 2) are working fine but camera with iD 3 does not work. I get the following error:

Setting pipeline to PAUSED …
ERROR: from element /GstPipeline:pipeline0/GstZedXOneSrc:zedxonesrc0: Failed to open camera, ‘CAMERA STREAM FAILED TO START’
Additional debug info:
/home/ZED_all_files/zed-gstreamer/gst-zedxone-src/gstzedxonesrc.cpp(862): gst_zedxonesrc_start (): /GstPipeline:pipeline0/GstZedXOneSrc:zedxonesrc0
ERROR: pipeline doesn’t want to preroll.
ERROR: from element /GstPipeline:pipeline0/GstZedXOneSrc:zedxonesrc0: GStreamer error: state change failed and some element failed to post a proper error message with the reason for the failure.
Additional debug info:
…/libs/gst/base/gstbasesrc.c(3556): gst_base_src_start (): /GstPipeline:pipeline0/GstZedXOneSrc:zedxonesrc0:
Failed to start
ERROR: pipeline doesn’t want to preroll.
[2025-07-29 08:38:47 UTC][ZED][WARNING] CAMERA STREAM FAILED TO START in sl::ERROR_CODE sl::CameraOneImpl::open(const sl::InitParametersOne&)
Failed to set pipeline to PAUSED.
Setting pipeline to NULL …
Freeing pipeline …

These are the 3 pipelines, all same, only camera serial number and port number are different

Path : /dev/i2c-13, ID : 0
gst-launch-1.0 zedxonesrc camera-sn=306037354 ! timeoverlay ! tee name=split has-chain=true ! queue ! autovideoconvert ! fpsdisplaysink split. ! queue max-size-time=0 max-size-bytes=0 max-size-buffers=0 ! autovideoconvert ! x264enc byte-stream=true tune=zerolatency speed-preset=ultrafast bitrate=3000 ! h264parse ! rtph264pay config-interval=-1 pt=96 ! queue ! udpsink clients=:5004 max-bitrate=3000000 sync=false async=false

Path : /dev/i2c-9, ID : 1
gst-launch-1.0 zedxonesrc camera-sn=300190908 ! timeoverlay ! tee name=split has-chain=true ! queue ! autovideoconvert ! fpsdisplaysink split. ! queue max-size-time=0 max-size-bytes=0 max-size-buffers=0 ! autovideoconvert ! x264enc byte-stream=true tune=zerolatency speed-preset=ultrafast bitrate=3000 ! h264parse ! rtph264pay config-interval=-1 pt=96 ! queue ! udpsink clients= :5002 max-bitrate=3000000 sync=false async=false

Path : /dev/i2c-10, ID : 2
gst-launch-1.0 zedxonesrc camera-sn=305191828 ! timeoverlay ! tee name=split has-chain=true ! queue ! autovideoconvert ! fpsdisplaysink split. ! queue max-size-time=0 max-size-bytes=0 max-size-buffers=0 ! autovideoconvert ! x264enc byte-stream=true tune=zerolatency speed-preset=ultrafast bitrate=3000 ! h264parse ! rtph264pay config-interval=-1 pt=96 ! queue ! udpsink clients= :5000 max-bitrate=3000000 sync=false async=false

Myzhar · July 29, 2025, 10:15am

Please upgrade the ZED SDK to the latest v5.0.5 to check if the problem is fixed.

nemishanv · July 29, 2025, 10:34am

I installed the latest zed sdk 5.0.5
Still same issue

ZED_Explorer -a

Cam 0

Model : “ZED XOne GS”
S/N : 306037354
State : “NOT AVAILABLE”
Path : /dev/i2c-13
ID : 0
Type : “GMSL”

Cam 1

Model : “ZED XOne GS”
S/N : 300190908
State : “NOT AVAILABLE”
Path : /dev/i2c-9
ID : 1
Type : “GMSL”

Cam 2

Model : “ZED XOne GS”
S/N : 305191828
State : “AVAILABLE”
Path : /dev/i2c-10
ID : 2
Type : “GMSL”

sudo systemctl restart zed_x_daemon

ZED_Explorer -a

Cam 0

Model : “ZED XOne GS”
S/N : 306037354
State : “AVAILABLE”
Path : /dev/i2c-13
ID : 0
Type : “GMSL”

Cam 1

Model : “ZED XOne GS”
S/N : 300190908
State : “AVAILABLE”
Path : /dev/i2c-9
ID : 1
Type : “GMSL”

Cam 2

Model : “ZED XOne GS”
S/N : 305191828
State : “AVAILABLE”
Path : /dev/i2c-10
ID : 2
Type : “GMSL”

ZED_Explorer

** [SVO] Hardware compression (NVENC) available **
(Argus) Error Timeout: (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 92)
(Argus) Error Timeout: (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 92)
(Argus) Error Timeout: (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 92)
(Argus) Error Timeout: (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 92)
(Argus) Error Timeout: (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 92)
(Argus) Error Timeout: (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 92)
[2025-07-29 10:29:30 UTC][ZED][INFO] Cannot find a valid camera.
(Argus) Error Timeout: (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)

Myzhar · July 29, 2025, 10:38am

How do you connect the cameras?
All three to the same GMSL2 port, or two to one port and one to the other?

nemishanv · July 29, 2025, 11:03am

2 cameras in 1 port and 1 in the other.

I removed the camera0 since it is giving issues. After that only camera 1 and 2 are connected as shown above. The behavior seems to be random. these are the terminal outputs without any hardware changes now.

1)only 1 camera was detected and it was opening in ZED_Explorer as well.

ZED_Explorer

** [SVO] Hardware compression (NVENC) available **
^C

ZED_Explorer -a

Cam 0

Model : “ZED XOne GS”
S/N : 305191828
State : “AVAILABLE”
Path : /dev/i2c-9
ID : 0
Type : “GMSL”

after restart, 2 were detected, but only one worked, 2nd camera gave an error.

sudo systemctl restart zed_x_daemon

ZED_Explorer -a

Cam 0

Model : “ZED XOne GS”
S/N : 300190908
State : “AVAILABLE”
Path : /dev/i2c-9
ID : 0
Type : “GMSL”

Cam 1

Model : “ZED XOne GS”
S/N : 305191828
State : “AVAILABLE”
Path : /dev/i2c-10
ID : 1
Type : “GMSL”

ZED_Explorer

** [SVO] Hardware compression (NVENC) available **
(Argus) Error Timeout: (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 92)
^C

after again restarting, only 1 camera was detected.

sudo systemctl restart zed_x_daemon

ZED_Explorer -a

Cam 0

Model : “ZED XOne GS”
S/N : 305191828
State : “AVAILABLE”
Path : /dev/i2c-9
ID : 0
Type : “GMSL”

sudo systemctl restart zed_x_daemon

ZED_Explorer -a

Cam 0

Model : “ZED XOne GS”
S/N : 305191828
State : “AVAILABLE”
Path : /dev/i2c-9
ID : 0
Type : “GMSL”

log file before and after replugging the camera wires and power supply using

sudo ZED_Diagnostic

Before
ZED_Diagnostic_Results.json (26.2 KB)

After
ZED_Diagnostic_Results_after_replug_wire_and_power_supply.json (159.0 KB)

i have one more question, if i set up the 2 zed x one cameras in the stereo setup and configure it, will it have all the features that a stereo camera has like object detection?

Aldric · July 29, 2025, 11:58am

Hi,

Can you try to reboot your board with your 3 cameras connected and then run:
sudo ZED_Diagnostic --dmesg
and share the log file as you previously did? We just need to have the output from a clean reboot as the previous ones have some incoherence.

Your configuration has been tested and is working properly on our setup so you should not encounter an issue.
Since you shared a gst command, you can also use the following command to open the cameras with gstreamer:
gst-launch-1.0 nvarguscamerasrc sensor-id=0 ! nvvidconv ! autovideosink

nemishanv · July 29, 2025, 12:13pm

Hello, please find below the log file after reboot and 3 cameras connected.

dmesg_1.log (45.8 KB)

Currently in my system the 2 camera which were always working are working now, but the 3rd camera which never worked is not even being detected by ZED_Explorer -a

Aldric · July 29, 2025, 12:18pm

Thank you for the log, can you do the same operations but plug the third camera on the same connector than the other two ?

nemishanv · July 29, 2025, 12:23pm

Logs immediately after interchanging connection of the non working camera with a working one and reboot.

dmesg_2.log (46.1 KB)

Aldric · July 29, 2025, 12:30pm

I meant can you plug all 3 cameras on the same connector, from the log you have just shared with me are your 3 cameras opened in ZED_Explorer ?
Because they are now all properly detected.

You may have some faulty cable or wrong connections on the camera or capture card connector

nemishanv · July 29, 2025, 2:06pm

I connected all 3 camers to the same capture card connector. After rebooting the jetson, all 3 were detected. so i tried to run ZED_Explorer and i could see all 3 cmeras are detected. I would see the stream of the 1st 2 cameras but when i selected the 3rd camera i got the following error, I have attached the logs that i took after this error:

ZED_Explorer -a

Cam 0

Model : “ZED XOne GS”
S/N : 305191828
State : “AVAILABLE”
Path : /dev/i2c-9
ID : 0
Type : “GMSL”

Cam 1

Model : “ZED XOne GS”
S/N : 300190908
State : “AVAILABLE”
Path : /dev/i2c-10
ID : 1
Type : “GMSL”

Cam 2

Model : “ZED XOne GS”
S/N : 306037354
State : “AVAILABLE”
Path : /dev/i2c-9
ID : 2
Type : “GMSL”

ZED_Explorer

** [SVO] Hardware compression (NVENC) available **
(Argus) Error Timeout: (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 92)
(Argus) Error Timeout: (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 92)

dmesg_3.log (47.2 KB)

Aldric · July 29, 2025, 2:28pm

Is the faulty camera always the same one ? If you try to open them independently through gst-launch for example ?

nemishanv · July 29, 2025, 2:58pm

yes, it is always the same one, immediately after reboot i tried opening it with gstreamer, it did open and run for a second and then it froze. this happens only in the faulty one.

could it be somethings related to argus?
WARNING Argus: 3 client objects still exist during shutdown:
following is the complete error.
Because after i run the working cameras with gstreamer, then if i stop and try to run again the camera becomes unavailable, after I restart the daemon it again works. This keeps happening every time specially after updating the zed sdk today.

gst-launch-1.0 zedxonesrc camera-sn=306037354 ! timeoverlay ! tee name=split has-chain=true ! queue ! autovideoconvert ! fpsdisplaysink split. ! queue max-size-time=0 max-size-bytes=0 max-size-buffers=0 ! autovideoconvert ! x264enc byte-stream=true tune=zerolatency speed-preset=ultrafast bitrate=3000 ! h264parse ! rtph264pay config-interval=-1 pt=96 ! queue ! udpsink clients=10.149.49.178:5000 max-bitrate=3000000 sync=false async=false
Setting pipeline to PAUSED …
[2025-07-29 14:54:17 UTC][ZED][ERROR] [ZED] Cannot initialize the camera.
ERROR: from element /GstPipeline:pipeline0/GstZedXOneSrc:zedxonesrc0: Failed to open camera, ‘CAMERA FAILED TO SETUP’
Additional debug info:
/home/ZED_all_files/zed-gstreamer/gst-zedxone-src/gstzedxonesrc.cpp(862): gst_zedxonesrc_start (): /GstPipeline:pipeline0/GstZedXOneSrc:zedxonesrc0
ERROR: pipeline doesn’t want to preroll.
ERROR: from element /GstPipeline:pipeline0/GstZedXOneSrc:zedxonesrc0: GStreamer error: state change failed and some element failed to post a proper error message with the reason for the failure.
Additional debug info:
…/libs/gst/base/gstbasesrc.c(3556): gst_base_src_start (): /GstPipeline:pipeline0/GstZedXOneSrc:zedxonesrc0:
Failed to start
ERROR: pipeline doesn’t want to preroll.
Failed to set pipeline to PAUSED.
Setting pipeline to NULL …
Freeing pipeline …
(Argus) Error Timeout: (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 92)
(Argus) Error InvalidState: Argus client is exiting with 1 outstanding client threads (in src/rpc/socket/client/ClientSocketManager.cpp, function recvThreadCore(), line 366)
WARNING Argus: 3 client objects still exist during shutdown:
281473527151376 (0xaaaad2364410)
281473527546528 (0xaaaad23742c0)
281473538591280 (0xaaaad2354ef0)
(Argus) Error NotInitialized: (propagating from src/eglstream/FrameConsumerImpl.cpp, function acquireFrame(), line 249)

Myzhar · July 29, 2025, 3:26pm

Hi @nemishanv
Please send an email to support@stereolabs.com for details.