Unstable connection problem of ZED X on Jetson AGX Orin 64G DK & Jetpack6.1

JacksonW · November 20, 2025, 8:50am

Hello.
I’m trying to work with my setup of Zed X with a GMSL board (ZED Link Duo) connected to a Jetson AGX Orin 64G.

Device and environment information:

NVIDIA Jetson AGX Orin ( L4T R36 REVISION 4.7, Jetpack 6.1)
Only 1 ZED X Camera
ZED X with a 1-to-4 GMSL2 Fakra Male to Female cable (originally included in the box)
ZED Link Duo GMSL2 capture card
ZED SDK downloaded by https://stereolabs.sfo2.cdn.digitaloceanspaces.com/zedsdk/5.1/ZED_SDK_Tegra_L4T36.4_v5.1.1.zstd.run
ZED Link Driver stereolabs-zedlink-duo_1.3.2-LI-MAX96712-all-L4T36.4.0_arm64

The most core and recurring problems:

I installed the corresponding version of sdk and link driver in strict accordance with the instructions of the official document. And the capture card and a ZED X are connected on AGX Orin when the power is off. However, when I started the system and tried to run ZED Explorer for the first time, my camera could be detected and started, but there was no picture output. Then, if I turn off zed explorer and start it again several times, the camera can no longer be detected.

The diagnostic program also presents this situation of “the ZED X camera can be found in the first diagnosis after starting the system, but the it cannot be detected in each subsequent diagnosis after the first time”.

Similarly, without restarting the system, using the command of deamon to restart:
sudo systemctl restart zed_x_daemon will also lead to the situation of “one-time detection”.

In a nutshell: the camera can be detected by the program once when the system starts or deamon restarts, but does not include the picture output, and then the camera will lose connection. It looks like the camera can only be detected once by any program, and there is no picture output.

Key information:

sudo dmesg | grep zedx :

sudo dmesg | grep zedx
[sudo] password for car: 
[   18.604622] sl_max96712 9-0029: sl_max96712_get_camera_model: zedx camera connected to this port
[   20.015413] sl_max9295 9-0062: probe_serializer: Serializer for zedx detect success
[   20.056998] sl_max9295 9-0063: probe_serializer: Serializer for zedx detect error
[   20.137162] sl_max9295 9-0061: probe_serializer: Serializer for zedxpro detect error
[   20.177350] sl_max9295 9-0060: probe_serializer: Serializer for zedxpro detect error
[   20.381298] sl_max9295 10-0062: probe_serializer: Serializer for zedx detect error
[   20.418775] sl_max9295 10-0063: probe_serializer: Serializer for zedx detect error
[   20.489254] sl_max9295 10-0061: probe_serializer: Serializer for zedxpro detect error
[   20.524612] sl_max9295 10-0060: probe_serializer: Serializer for zedxpro detect error
[   20.608056] zedxpro 9-004f: probing v4l2 sensor.
[   20.608171] zedxpro 9-004f: tegracam sensor driver:video12_v2.0.6
[   20.608850] zedxpro 9-004f: zedxpro_probe: Start streaming fail
[   20.608908] zedxpro 9-004e: probing v4l2 sensor.
[   20.608998] zedxpro 9-004e: tegracam sensor driver:video11_v2.0.6
[   20.609601] zedxpro 9-004e: zedxpro_probe: Start streaming fail
[   20.609643] zedxpro 9-002f: probing v4l2 sensor.
[   20.609709] zedxpro 9-002f: tegracam sensor driver:video10_v2.0.6
[   20.610314] zedxpro 9-002f: zedxpro_probe: Start streaming fail
[   20.610354] zedxpro 9-003f: probing v4l2 sensor.
[   20.610412] zedxpro 9-003f: tegracam sensor driver:video9_v2.0.6
[   20.611003] zedxpro 9-003f: zedxpro_probe: Start streaming fail
[   20.611041] zedxpro 9-002e: probing v4l2 sensor.
[   20.611114] zedxpro 9-002e: tegracam sensor driver:video8_v2.0.6
[   20.611708] zedxpro 9-002e: zedxpro_probe: Start streaming fail
[   20.611745] zedxpro 9-003e: probing v4l2 sensor.
[   20.611800] zedxpro 9-003e: tegracam sensor driver:video7_v2.0.6
[   20.612402] zedxpro 9-003e: zedxpro_probe: Start streaming fail
[   20.612484] zedxpro 10-004f: probing v4l2 sensor.
[   20.612545] zedxpro 10-004f: tegracam sensor driver:video25_v2.0.6
[   20.612955] zedxpro 10-004f: zedxpro_probe: Start streaming fail
[   20.612994] zedxpro 10-004e: probing v4l2 sensor.
[   20.613056] zedxpro 10-004e: tegracam sensor driver:video24_v2.0.6
[   20.613465] zedxpro 10-004e: zedxpro_probe: Start streaming fail
[   20.613503] zedxpro 10-002f: probing v4l2 sensor.
[   20.613564] zedxpro 10-002f: tegracam sensor driver:video23_v2.0.6
[   20.613933] zedxpro 10-002f: zedxpro_probe: Start streaming fail
[   20.613977] zedxpro 10-003f: probing v4l2 sensor.
[   20.614040] zedxpro 10-003f: tegracam sensor driver:video22_v2.0.6
[   20.614407] zedxpro 10-003f: zedxpro_probe: Start streaming fail
[   20.614444] zedxpro 10-002e: probing v4l2 sensor.
[   20.614504] zedxpro 10-002e: tegracam sensor driver:video21_v2.0.6
[   20.614866] zedxpro 10-002e: zedxpro_probe: Start streaming fail
[   20.614924] zedxpro 10-003e: probing v4l2 sensor.
[   20.614988] zedxpro 10-003e: tegracam sensor driver:video20_v2.0.6
[   20.615348] zedxpro 10-003e: zedxpro_probe: Start streaming fail
[   20.620433] zedx 9-0011: Driver Version : v1.3.2
[   20.620437] zedx 9-0011: Probing v4l2 sensor.
[   20.620535] zedx 9-0011: tegracam sensor driver:video5_v2.0.6
[   20.668834] zedx 9-0011: ZED-X detect error
[   20.668852] zedx 9-0011: zedx_probe: ar0234 initialization failed
[   20.668876] zedx: probe of 9-0011 failed with error -1
[   20.668911] zedx 9-0010: Driver Version : v1.3.2
[   20.668912] zedx 9-0010: Probing v4l2 sensor.
[   20.668998] zedx 9-0010: tegracam sensor driver:video4_v2.0.6
[   20.717184] zedx 9-0010: ZED-X detect error
[   20.717199] zedx 9-0010: zedx_probe: ar0234 initialization failed
[   20.717224] zedx: probe of 9-0010 failed with error -1
[   20.717253] zedx 9-0030: Driver Version : v1.3.2
[   20.717255] zedx 9-0030: Probing v4l2 sensor.
[   20.717345] zedx 9-0030: tegracam sensor driver:video3_v2.0.6
[   20.764901] zedx 9-0030: ZED-X detect error
[   20.764946] zedx 9-0030: zedx_probe: ar0234 initialization failed
[   20.765013] zedx: probe of 9-0030 failed with error -1
[   20.765087] zedx 9-0038: Driver Version : v1.3.2
[   20.765094] zedx 9-0038: Probing v4l2 sensor.
[   20.765335] zedx 9-0038: tegracam sensor driver:video2_v2.0.6
[   20.812969] zedx 9-0038: ZED-X detect error
[   20.813021] zedx 9-0038: zedx_probe: ar0234 initialization failed
[   20.813102] zedx: probe of 9-0038 failed with error -1
[   20.813175] zedx 9-0020: Driver Version : v1.3.2
[   20.813180] zedx 9-0020: Probing v4l2 sensor.
[   20.813406] zedx 9-0020: tegracam sensor driver:video1_v2.0.6
[   20.900223] zedx 9-0020: Enable gmsl for channel 0 and id 0
[   21.138703] tegra-camrtc-capture-vi tegra-capture-vi: subdev zedx 9-0020 bound
[   21.164347] zedx 9-0020: Detected ZED-X sensor
[   21.164355] zedx 9-0020: zedx_probe: Serial Number : 42950678
[   21.164358] zedx 9-0020: zedx_probe: CHANNEL: 0 ID: 0
[   21.168065] zedx 9-0028: Driver Version : v1.3.2
[   21.168074] zedx 9-0028: Probing v4l2 sensor.
[   21.168767] zedx 9-0028: tegracam sensor driver:video0_v2.0.6
[   21.256221] zedx 9-0028: Enable gmsl for channel 0 and id 0
[   21.494088] tegra-camrtc-capture-vi tegra-capture-vi: subdev zedx 9-0028 bound
[   21.494729] zedx 9-0028: Detected ZED-X sensor
[   21.494731] zedx 9-0028: zedx_probe: Serial Number : 42950678
[   21.494732] zedx 9-0028: zedx_probe: CHANNEL: 0 ID: 0
[   21.494882] zedx 10-0011: Driver Version : v1.3.2
[   21.494884] zedx 10-0011: Probing v4l2 sensor.
[   21.494981] zedx 10-0011: tegracam sensor driver:video18_v2.0.6
[   21.540575] zedx 10-0011: ZED-X detect error
[   21.540592] zedx 10-0011: zedx_probe: ar0234 initialization failed
[   21.540616] zedx: probe of 10-0011 failed with error -1
[   21.540642] zedx 10-0010: Driver Version : v1.3.2
[   21.540644] zedx 10-0010: Probing v4l2 sensor.
[   21.540715] zedx 10-0010: tegracam sensor driver:video17_v2.0.6
[   21.588570] zedx 10-0010: ZED-X detect error
[   21.588583] zedx 10-0010: zedx_probe: ar0234 initialization failed
[   21.588608] zedx: probe of 10-0010 failed with error -1
[   21.588634] zedx 10-0030: Driver Version : v1.3.2
[   21.588636] zedx 10-0030: Probing v4l2 sensor.
[   21.588710] zedx 10-0030: tegracam sensor driver:video16_v2.0.6
[   21.640556] zedx 10-0030: ZED-X detect error
[   21.640565] zedx 10-0030: zedx_probe: ar0234 initialization failed
[   21.640580] zedx: probe of 10-0030 failed with error -1
[   21.640599] zedx 10-0038: Driver Version : v1.3.2
[   21.640600] zedx 10-0038: Probing v4l2 sensor.
[   21.640655] zedx 10-0038: tegracam sensor driver:video15_v2.0.6
[   21.688544] zedx 10-0038: ZED-X detect error
[   21.688552] zedx 10-0038: zedx_probe: ar0234 initialization failed
[   21.688566] zedx: probe of 10-0038 failed with error -1
[   21.688583] zedx 10-0020: Driver Version : v1.3.2
[   21.688585] zedx 10-0020: Probing v4l2 sensor.
[   21.688640] zedx 10-0020: tegracam sensor driver:video14_v2.0.6
[   21.736563] zedx 10-0020: ZED-X detect error
[   21.736574] zedx 10-0020: zedx_probe: ar0234 initialization failed
[   21.736593] zedx: probe of 10-0020 failed with error -1
[   21.736618] zedx 10-0028: Driver Version : v1.3.2
[   21.736619] zedx 10-0028: Probing v4l2 sensor.
[   21.736681] zedx 10-0028: tegracam sensor driver:video13_v2.0.6
[   21.788569] zedx 10-0028: ZED-X detect error
[   21.788578] zedx 10-0028: zedx_probe: ar0234 initialization failed
[   21.788596] zedx: probe of 10-0028 failed with error -1
[   21.799303] zedxone_uhd 9-001a: tegracam sensor driver:video6_v2.0.6
[   21.799998] zedxone_uhd 9-001a: imx678_probe: imx678 initialization failed
[   21.800281] zedxone_uhd 10-001a: tegracam sensor driver:video19_v2.0.6
[   21.800654] zedxone_uhd 10-001a: imx678_probe: imx678 initialization failed

ZED_Explorer and ZED_Diagnostic terminal (everytime):

(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)

After reboot or deamon restart: ZED_Explorer will be like:

then LIVE with NO PICTURE:

Every explorer after that will FLASH THIS: WAITING FOR CAMERA

Some possibilities:

I found a similar problem in this topic, but it has not been completely solved so far:
https://community.stereolabs.com/t/zed-x-connection-argus-issues/10348

In addition, according to my guess, it may be a problem with Link Driver. After all, I have seen a lot of failure and error information in dmesg, but I have not been able to analyze them yet.

Finally, I repeatedly confirmed that my cable connection is tight and stable, and my capture card indicator light can also light up when the system starts or deamon restarts. I don’t rule out the possibility of loose connection, but in view of the phenomenon of “one-time detection”, I think the problem is that the possibility of physical connection is less.

As a beginner, I apologize for some inconveniences I have caused. I sincerely hope to get some suggestions from the community. Thank you.

mattrouss · November 20, 2025, 4:26pm

Hi @JacksonW,

Welcome to the forums

Can you send the JSON result from the following command:
sudo ZED_Diagnostic -c

If you cannot share files on the support just yet, please send an email to support@stereolabs.com with a link to this thread and we can provide additional support

mattrouss · November 20, 2025, 5:39pm

Hi @JacksonW,

Thank you for sharing the file, can you verify that the capture card is correctly plugged to the board and take a picture of your setup with the camera connected?

JacksonW · November 20, 2025, 5:44pm

Hi @mattrouss, thanks for your reply!

I cannot share my files right now and I have sent a email with a link to this thread.

Here is the content of the JSON file (A reduced version due to the space limitation):

  {
    "AI Models": {
      "info": ["MULTI CLASS DETECTION is not optimized", "..."],
      "valid": ["NEURAL LIGHT DEPTH is optimized"]
    },
    "GMSL DRIVER": {
      "GMSL driver": "ii  stereolabs-zedlink-duo 1.3.2-LI-MAX96712-all-L4T36.4.0
  arm64 ..."
    },
    "Graphics Card": {
      "deviceCount": 1,
      "devices": [{"name": "Orin", "computeCapability": "8.7", "cores": 2048,
  "totalMemoryMB": 62840.2}],
      "initResult": 0,
      "valid": ["<b>Graphics card: </b> Orin"]
    },
    "Processor": {
      "L4T version": "36.4.7",
      "OS": "Ubuntu 22.04.5 LTS",
      "cpu": "ARMv8 Processor rev 1 (v8l)",
      "motherboard": "Jetson, NVIDIA",
      "valid": ["<b>Processor: </b>  ARMv8 Processor rev 1 (v8l)",
  "<b>Motherboard: </b> Jetson, NVIDIA"]
    },
    "ZED SDK": {
      "ZED SDK Version (Diag)": "5.1.1",
      "ZED SDK Version (RT)": "5.1.1",
      "CUDA Toolkit version": "V12.6.68",
      "cudaVersion": 12060,
      "tensorVersion": 100300,
      "binFiles": ["libsl_ai.so", "libsl_zed.so"],
      "resourcesFiles": ["neural_depth_5.3.model", "objects_accurate_3.2.model",
  "..."],
      "valid": ["<b>ZED SDK version:</b> 5.1.1", "<b>CUDA version:</b>
  V12.6.68"]
    },
    "Log Kernel Trace (for ZED X)": {
      "dmesg": {
        "DMESG [DTS] LOG ": [
          "[   16.280513] sl_max96712 9-0029: ... Number of declared cameras
  with this dts 18",
          "[  711.132711] sl_max96712 9-0029: ... Number of declared cameras
  with this dts 18"
        ],
        "DMESG [MAX9x] LOG": [
          "[   16.280513] ... zedx camera connected to this port",
          "[   17.719507] ... camera pipeline operational",
          "[   19.145699] sl_max9295 9-0062: probe_serializer: Serializer for
  zedx detect success",
          "[   20.274293] tegra-camrtc-capture-vi: subdev zedx 9-0020 bound",
          "[   20.279973] zedx 9-0020: Serial Number : 42950678",
          "[   20.608008] zedx 9-0028: Serial Number : 42950678",
          "[   19.800618] zedx: probe ... failed with error -1 (other ports)",
          "... truncated ..."
        ],
        "Driver list": {
          "/usr/lib/modules/.../sl_max9295.ko": "exists",
          "/usr/lib/modules/.../sl_max96712.ko": "exists",
          "/usr/lib/modules/.../sl_zedx.ko": "exists",
          "/usr/lib/modules/.../sl_zedxpro.ko": "exists",
          "/usr/lib/modules/.../sl_zedxone_uhd.ko": "exists"
        },
        "EXTlinux file": [
          "DEFAULT Stereolabs",
          "FDT /boot/dtb/kernel_tegra234-p3737-0000+p3701-0005-nv.dtb",
          "OVERLAYS /boot/tegra234-p3737-camera-zedlink-duo-sl-overlay.dtbo",
          "..."
        ],
        "Jetpack": [
          "# R36 (release), REVISION: 4.7, ... DATE: Thu Sep 18 22:54:44 UTC
  2025"
        ],
        "Linux_uname": [
          "Linux car 5.15.148-tegra #1 SMP PREEMPT Thu Sep 18 15:08:33 PDT 2025
  aarch64 ..."
        ],
        "ZEDX Daemon Status LS": [
          "Active: active (running) since Thu 2025-11-20 19:17:29 CST",
          "Port  0  OPENING for CAM ModeliD  8",
          "Port  0  CLOSING for CAM ModeliD  8",
          "..."
        ],
        "ZEDX Driver State": [
          "sl_zedxone_uhd 36864 0",
          "sl_zedx 28672 1",
          "sl_zedxpro 20480 0",
          "sl_max9295 16384 3 ...",
          "sl_max96712 24576 4 ...",
          "tegra_camera 217088 17 ...",
          "videodev 249856 9 ..."
        ],
        "I2C Trace list": { "...": "full bus scans for i2c-0..13" }
      }
    },
    "USB Camera": {
      "GMSLList": [
        { "Serial": "42950678", "Sub Model": "ZED-XG 120mm", "id": 0, "path": "/
  dev/i2c-9", "state": "Not Available" }
      ],
      "USBList": [
        { "USB_path": "/3", "idVendor": "0x0bda", "idProduct": "0x0420" },
        { "USB_path": "/4/2", "idVendor": "0x046d", "idProduct": "0xc547" },
        "..."
      ],
      "error": [
        "<b>Specific resolutions are not available</b> ...",
        "<b>Specific resolutions are not available</b> ..."
      ]
    }
  }

  Key points preserved: driver version 1.3.2, L4T 36.4.7, kernel 5.15.148-
  tegra, one ZED-X (SN 42950678) detected; other ports fail; required ko modules
  present; overlay in use; ZED SDK 5.1.1/CUDA 12.6; nvargus errors implied by
  “Not Available” state.

And here are more informations:

• Current Status

  - Hardware/link: One ZED-X detected on channel 0, SN 42950678; driver binds as
    zedx 9-0028/9-0020 with /dev/video0 and /dev/video1. Other GMSL ports probe
    and fail (expected since only one camera is attached).
  - Services: nvargus-daemon running, zed_x_daemon running. Both were restarted
    via sudo systemctl restart nvargus-daemon and sudo systemctl restart
    zed_x_daemon.
  - Low-level capture: v4l2-ctl -d /dev/video0 --stream-mmap … succeeded at ~10–
    12 fps, confirming frames over V4L2.
  - GUI app: ZED_Explorer launches GUI but shows no image; terminal
    logs repeated Argus timeouts (ClientSocketManager::send,
    SocketClientDispatch::dispatch) and hangs.
  - Argus pipeline: gst-launch-1.0 nvarguscamerasrc sensor-id=0 … fails
    with Failed to create CaptureSession. nvargus-daemon journal shows many
    V4L2Device not available, Sensor could not be opened, Bad exposure/gain
    range, and “Unidentified sensor placement”.
  - Kernel logs (tail): show successful bind of zedx 9-0028 and then repeated
    “ZED-X detect error … ar0234 initialization failed” on other ports; no fatal
    errors for the active camera after binding.

  What I ran (key commands/results)

  - sudo systemctl restart nvargus-daemon, sudo systemctl restart zed_x_daemon →
    both active/running.
  - v4l2-ctl --list-devices → ZED-X at /dev/video0 /dev/video1.
  - v4l2-ctl -d /dev/video0 --stream-mmap --stream-count=30 → succeeded,
    produced frames.
  - ZED_Explorer → GUI but no image; Argus timeout errors.
  - gst-launch-1.0 nvarguscamerasrc sensor-id=0 … → Failed to create
    CaptureSession.
  - sudo systemctl status nvargus-daemon/journalctl -u nvargus-daemon → Argus
    complaining about missing V4L2 devices and bad parameter ranges; nvargus-
    daemon running.
  - sudo dmesg | tail -n 50 → only one sensor detected; others fail to init
    (non-connected ports).

Thanks again for your timely reply! I hope the information I provide can be helpful.

JacksonW · November 20, 2025, 6:05pm

And here are the pictures when the camera is firstly connected after restarting system/daemon:

ZED_Explorer→

ZED_Diagnostic→(Stopped after successfully testing the camera)

(Picture is under this reply)

These only happen once after restarting system/daemon. If I try again (whatever sdk tools), it will tell there is no valid camera unless I restarting system/daemon. At that time, the Explorer will keep waiting for camera and the Diagnostic will fail in camera testing.

By the way, both of the terminals always show:

(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)
...

Hope these can be helpful! Thanks!

JacksonW · November 20, 2025, 6:05pm

JacksonW · November 20, 2025, 6:08pm

My connection status:

The detection light of the capture card will flash when the system or daemon is restarted. The camera will also heat up when running the SDK. And I also tried to plug them in tightly. I hope this can represent that my wiring has been completed tightly and correctly.

Thanks for your reply!