# ZED X Driver working fail...but Camera is Working!

**URL:** <https://community.stereolabs.com/t/zed-x-driver-working-fail-but-camera-is-working/8586>\
**Category:** ZED X\
**Tags:** sdk, jetson\
**Created:** [April 14, 2025, 5:36am UTC](https://community.stereolabs.com/t/zed-x-driver-working-fail-but-camera-is-working/8586 "2025-04-14T05:36:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![woawo1213](https://community.stereolabs.com/user_avatar/community.stereolabs.com/woawo1213/32/3010_2.png) [@woawo1213](https://community.stereolabs.com/u/woawo1213)\
**Post date:** [April 14, 2025, 5:36am UTC](https://community.stereolabs.com/t/zed-x-driver-working-fail-but-camera-is-working/8586/1 "2025-04-14T05:36:06Z")

</div>

Hi,

I’m using ZED X series cameras, but I’ve encountered some warning messages.

Hardware environment: Jetson Developer Kit, ZED X (x3), ZED X Mini (x1)  
Software environment: ZED SDK L4T 36.4 v5.0.0, zedlink\_quad\_1.3.0\_max96712

The cameras work fine — image topics are being published correctly.

However, I noticed some error logs related to ZED X in the output of dmesg.

I’ve attached the outputs of the following commands for your reference:

1. sudo ZED\_Diagnostic --dmesg
2. sudo dmesg | grep zedx  
[dmesg.log](https://community.stereolabs.com/uploads/short-url/qQ5jb7a3CUvfrjg0XjkgV7DCSbv.log) (17.2 KB)  
[zedx.txt](https://community.stereolabs.com/uploads/short-url/wSLlEdR44JMG3w2mYSuqdRNSos1.txt) (16.9 KB)

Given the current environment, is it safe to continue using the setup as is?

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [April 14, 2025, 5:09pm UTC](https://community.stereolabs.com/t/zed-x-driver-working-fail-but-camera-is-working/8586/2 "2025-04-14T17:09:57Z")

</div>

Hi @woawo1213  
The `dmesg.log` file contains information that only members of the [StereoLabs](https://www.stereolabs.com/) team can correctly understand.  
The errors and warnings that you read are only related to hardware that is not detected because it’s not connected to your device.

You can run `ZED_Diagnostic` without `--dmesg` to check your system status.

While your camera works with ZED Explorer and ZED Depth Viewer, everything is good.

PS You did not use `sudo` to generate the `dmseg.log` file

---

<div class="post-metadata">

**Author:** ![woawo1213](https://community.stereolabs.com/user_avatar/community.stereolabs.com/woawo1213/32/3010_2.png) [@woawo1213](https://community.stereolabs.com/u/woawo1213)\
**Post date:** [April 18, 2025, 8:16am UTC](https://community.stereolabs.com/t/zed-x-driver-working-fail-but-camera-is-working/8586/3 "2025-04-18T08:16:11Z")

</div>

@Myzhar Thank you for reply.  
According to your answer, ZED\_Depth\_Viewer and ZED\_Explorer should work if the camera is working properly. I ran the camera with zed\_wrapper first and saw that raw\_image and depth\_image are coming out, and ZED\_Explorer is working relatively well, but ZED\_Depth\_Viewer is not working properly.  
I’ll attach related images. Is everything okay with the camera?

 ![화면 캡처 2025-04-18 165740](https://community.stereolabs.com/uploads/default/original/2X/e/e06ca9bf4f0abcae58f2d29d8b0f5948d2667c5e.jpeg)  
[ZED\_Diagnostic\_Results.json](https://community.stereolabs.com/uploads/short-url/dqtZNHrh9wgxFonmcia7ZjmJIgS.json) (27.0 KB)

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [April 18, 2025, 9:14am UTC](https://community.stereolabs.com/t/zed-x-driver-working-fail-but-camera-is-working/8586/4 "2025-04-18T09:14:17Z")

</div>

> [@woawo1213](#):
>
> but ZED\_Depth\_Viewer is not working properly.

You cannot open the camera in different applications simultaneously.  
If the ROS Wrapper opened the camera, ZED Depth Viewer cannot see it as available.
