If your ZED camera is not working as expected, the ZED Diagnostics tool can generate a diagnostic report that allows our support team to analyze your system configuration and identify the source of the problem.
Please follow the procedure below to generate the diagnostic file and send it to support@stereolabs.com.
Step 1: Install the latest ZED SDK
Download and install the latest ZED SDK from our Developers page. Many issues are solved by simply updating to the most recent SDK version.
After the installation, restart your computer to reload the environment variables and to be sure that nothing is interfering with the ZED SDK.
Step 2: Connect the camera
Connect the ZED camera to your device. If you own multiple cameras, please connect and test one camera at a time.
Note for GMSL2 cameras (ZED X, ZED X One): any modification in the hardware configuration, such as plugging or unplugging a camera, or changing the camera order, requires either rebooting the Jetson or restarting the daemon with:
sudo systemctl restart zed_x_daemon
Step 3: Run the ZED Diagnostics tool
-
Windows: open the Start menu and search for "ZED Diagnostic" in the ZED SDK folder, or run
C:\Program Files (x86)\ZED SDK\tools\ZED Diagnostic.exe(right-click, "Run as Administrator"). -
Linux / NVIDIA Jetson: open a terminal and type
ZED_Diagnostic, or run it from the ZED SDK installation directory:/usr/local/zed/tools/ZED_Diagnostic.
Press the Start button; the tool will automatically detect the connected camera and perform a series of checks: ZED SDK and CUDA versions, processor and motherboard information, GPU model, AI model status, camera hardware tests (model and firmware version), and connectivity status.
Step 4: Save and send the diagnostic file
Once the diagnostic process is complete, press the Save button to export the diagnostic report as a JSON file.
Send the file to support@stereolabs.com, including a detailed description of the issue you are experiencing: what happens, when it started, and the exact error messages, if any. The more context you provide, the faster we can help you.
GMSL2 cameras: include the kernel logs
If you are using a ZED X or ZED X One camera with a ZED Link capture card, a ZED Box, or a third-party carrier board, please also attach the kernel/driver logs, which are essential to debug GMSL2 connection issues. You can retrieve them with the dedicated ZED Diagnostics option:
sudo /usr/local/zed/tools/ZED_Diagnostic --dmesg
or manually with:
sudo dmesg | grep zedx
For more information about common GMSL2 issues (camera not detected, driver upgrade, MIPI lane speed on Xavier NX / Orin NX, blurry images after a system update), please refer to our dedicated troubleshooting guides:
Headless systems (no display available)
If your device has no GUI available, for example a Jetson accessed via SSH, you can run the tool in command line mode:
ZED_Diagnostic -c
The full list of command line options is available with ZED_Diagnostic -h and is documented in the ZED Diagnostics documentation.
Additional information
The ZED Diagnostics tool can also download and optimize the AI models used by the ZED SDK (NEURAL depth modes, object detection, body tracking), and recover a ZED 2 / ZED 2i MCU module with an invalid serial number. See the ZED Diagnostics documentation for details.