nvargus-daemon have some error, Wrong frequency range!

Hardware ZED X
,
1

We bought 10 Zed Link Quad on Agx Orin, use this ZED Link Quad on AGX Orin - Stereolabs, we sync_mode=1, and Connect the pin #13 (brown) to the pin #16 (red); but every agx nvargus-daemon.service have this error, is that error?

```shell

jetson@ubuntu:~$ journalctl -fu nvargus-daemon.service
Dec 04 11:52:25 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:25 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:25 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:25 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:25 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:25 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:25 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:25 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:25 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:25 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:26 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:26 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:26 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:26 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:26 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:26 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:26 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:26 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:26 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:26 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:26 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:26 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:26 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:27 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:27 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:27 ubuntu nvargus-daemon[574725]: Wrong frequency range!
Dec 04 11:52:27 ubuntu nvargus-daemon[574725]: Wrong frequency range!
^C
jetson@ubuntu:~$
jetson@ubuntu:~$ systemctl cat zed_x_daemon

/etc/systemd/system/zed_x_daemon.service

[Unit]
Description=ZED-X Daemon service
After=nvargus-daemon.service driver_zed_loader.service
Requires=driver_zed_loader.service
StartLimitIntervalSec=0

[Service]
Type=simple
Restart=always
RestartSec=1
User=root
StandardOutput=syslog
ExecStart=/usr/sbin/ZEDX_Daemon

0 = no sync(Default), 1 = master/slave mode, 2 = slave mode only

sync_mode=1

[Install]
WantedBy=multi-user.target
jetson@ubuntu:~$ sudo dmesg |grep sync
[sudo] password for jetson:
[ 8.738754] systemd[1]: /etc/systemd/system/zed_x_daemon.service:16: Unknown key name ‘sync_mode’ in section ‘Service’, ignoring.
[ 9.276373] nvgpu: 17000000.gpu nvgpu_nvhost_syncpt_init:122 [INFO] syncpt_unit_base 60000000 syncpt_unit_size 4000000 size 10000
[ 10.179830] scare-pigeon 13e00000.host1x:vi0-thi@15f00000: syncpt_unit_base 60000000 syncpt_unit_size 4000000 size 10000
[ 10.181124] scare-pigeon 13e00000.host1x:vi1-thi@14f00000: syncpt_unit_base 60000000 syncpt_unit_size 4000000 size 10000
[ 10.192558] scare-pigeon 13e00000.host1x:isp-thi@14b00000: syncpt_unit_base 60000000 syncpt_unit_size 4000000 size 10000
[ 10.208730] nvdla 15880000.nvdla0: syncpt_unit_base 60000000 syncpt_unit_size 4000000 size 10000
[ 10.217783] nvdla 158c0000.nvdla1: syncpt_unit_base 60000000 syncpt_unit_size 4000000 size 10000
[ 10.287790] pva 16000000.pva0: syncpt_unit_base 60000000 syncpt_unit_size 4000000 size 10000
jetson@ubuntu:~$
jetson@ubuntu:~$ systemctl status zed_x_daemon
● zed_x_daemon.service - ZED-X Daemon service
Loaded: loaded (/etc/systemd/system/zed_x_daemon.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2025-12-03 17:20:24 CST; 18h ago
Main PID: 2684 (ZEDX_Daemon)
Tasks: 5 (limit: 74765)
Memory: 3.9M
CPU: 4.878s
CGroup: /system.slice/zed_x_daemon.service
└─2684 /usr/sbin/ZEDX_Daemon

Dec 03 17:26:29 ubuntu ZEDX_Daemon[2684]: [ “Wed Dec 3 17:26:29 2025” ][ZED-X Daemon] Port 2 Running for CAM ModeliD 9
Dec 04 11:37:03 ubuntu ZEDX_Daemon[2684]: [ “Thu Dec 4 11:37:03 2025” ][ZED-X Daemon] Restart NVArgus Daemon
Dec 04 11:37:03 ubuntu ZEDX_Daemon[2684]: [ “Thu Dec 4 11:37:03 2025” ][ZED-X Daemon] Received invalid message : “ZEDX#1#13#FROZEN”
Dec 04 11:37:03 ubuntu ZEDX_Daemon[2684]: [ “Thu Dec 4 11:37:03 2025” ][ZED-X Daemon] Received invalid message : “ZEDX#0#13#FROZEN”
Dec 04 11:37:05 ubuntu ZEDX_Daemon[2684]: [ “Thu Dec 4 11:37:05 2025” ][ZED-X Daemon] Port 1 OPENING for CAM ModeliD 13
Dec 04 11:37:08 ubuntu ZEDX_Daemon[2684]: [ “Thu Dec 4 11:37:08 2025” ][ZED-X Daemon] Port 1 Running for CAM ModeliD 13
Dec 04 11:37:08 ubuntu ZEDX_Daemon[2684]: [ “Thu Dec 4 11:37:08 2025” ][ZED-X Daemon] Port 0 OPENING for CAM ModeliD 13
Dec 04 11:37:11 ubuntu ZEDX_Daemon[2684]: [ “Thu Dec 4 11:37:11 2025” ][ZED-X Daemon] Port 0 Running for CAM ModeliD 13
Dec 04 11:37:14 ubuntu ZEDX_Daemon[2684]: [ “Thu Dec 4 11:37:14 2025” ][ZED-X Daemon] Port 2 OPENING for CAM ModeliD 9
Dec 04 11:37:14 ubuntu ZEDX_Daemon[2684]: [ “Thu Dec 4 11:37:14 2025” ][ZED-X Daemon] Port 2 Running for CAM ModeliD 9

richtech@ubuntu:~$ jetson_release -s
Software part of jetson-stats 4.3.2 - (c) 2024, Raffaello Bonghi
Jetpack missing!

  • Model: NVIDIA Jetson AGX Orin Developer Kit
  • L4T: 36.4.4
    NV Power Mode[0]: MAXN
    Serial Number: 1420125020150
    Hardware:
  • P-Number: p3701-0005
  • Module: NVIDIA Jetson AGX Orin (64GB ram)
    Platform:
  • Distribution: Ubuntu 22.04 Jammy Jellyfish
  • Release: 5.15.148-tegra
    jtop:
  • Version: 4.3.2
  • Service: Active
    Libraries:
  • CUDA: 12.6.68
  • cuDNN: 9.3.0.75
  • TensorRT: 10.3.0.30
  • VPI: 3.2.4
  • Vulkan: 1.3.204
  • OpenCV: 4.8.0 - with CUDA: NO

```

2

Hi @m986883511,

Could you share the resulting JSON file from this command:

sudo ZED_Diagnostic -c
3

richtech@ubuntu:~$ sudo ZED_Diagnostic -c
[sudo] password for richtech:
MoTTY X11 proxy: No authorisation provided
MoTTY X11 proxy: No authorisation provided
MoTTY X11 proxy: No authorisation provided
MoTTY X11 proxy: No authorisation provided
nvbufsurftransform: Could not get EGL display connection
ZED Diagnostic Tool

  • Running ZED SDK Diagnostic : OK
    ZED SDK version: 5.0.5
    CUDA version: V12.6.68
  • Running Processor Diagnostic : OK
    Processor: ARMv8 Processor rev 1 (v8l)
    Motherboard: Jetson, NVIDIA
    MoTTY X11 proxy: No authorisation provided
    Error: unable to open display localhost:10.0
  • Running Graphics Card Diagnostic : OK
    Graphics card: Orin
  • Running AI Models Diagnostic : OK
    MULTI CLASS DETECTION is not optimized
    MULTI CLASS MEDIUM DETECTION is not optimized
    MULTI CLASS ACCURATE DETECTION is not optimized
    HUMAN BODY FAST DETECTION is not optimized
    HUMAN BODY MEDIUM DETECTION is not optimized
    HUMAN BODY ACCURATE DETECTION is not optimized
    HUMAN BODY 38 FAST DETECTION is not optimized
    HUMAN BODY 38 MEDIUM DETECTION is not optimized
    HUMAN BODY 38 ACCURATE DETECTION is not optimized
    PERSON HEAD DETECTION is not optimized
    PERSON HEAD ACCURATE DETECTION is not optimized
    REID ASSOCIATION is not optimized
    NEURAL LIGHT DEPTH is not optimized
    NEURAL PLUS DEPTH is not optimized
    NEURAL DEPTH is optimized
  • Running Camera Test Diagnostic : OK
  • Running Devices Diagnostic : OK
  • Running Log Kernel Trace (for ZED X) Diagnostic : OK

Diagnostic finished, a file has been generated : ZED_Diagnostic_Results.json

ZED_Diagnostic_Results.json (63.0 KB)

4

Hi @m986883511,

Your diagnostic file appears to be correct.

The “wrong frequency range” is a warning from argus. Are you able to open and use the cameras in your setup?

5

yes, I can open camera

6

If the camera can be opened and used normally, you can safely ignore the warning.