# Nvargus-daemon have some error, Wrong frequency range!

**URL:** <https://community.stereolabs.com/t/nvargus-daemon-have-some-error-wrong-frequency-range/10486>\
**Category:** ZED X\
**Tags:** sdk, jetson\
**Created:** [December 5, 2025, 1:10pm UTC](https://community.stereolabs.com/t/nvargus-daemon-have-some-error-wrong-frequency-range/10486 "2025-12-05T13:10:25Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![m986883511](https://community.stereolabs.com/user_avatar/community.stereolabs.com/m986883511/32/5378_2.png) [@m986883511](https://community.stereolabs.com/u/m986883511)\
**Post date:** [December 5, 2025, 1:10pm UTC](https://community.stereolabs.com/t/nvargus-daemon-have-some-error-wrong-frequency-range/10486/1 "2025-12-05T13:10:25Z")

</div>

We bought 10 Zed Link Quad on Agx Orin, use this [ZED Link Quad on AGX Orin - Stereolabs](https://www.stereolabs.com/docs/embedded/zed-link/quad-jetson-orin-agx-devkit-setup#enable-full-8-camera-onboard-synchronization), 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

```

---

<div class="post-metadata">

**Author:** ![mattrouss](https://community.stereolabs.com/user_avatar/community.stereolabs.com/mattrouss/32/2452_2.png) [@mattrouss](https://community.stereolabs.com/u/mattrouss)\
**Post date:** [December 9, 2025, 4:51pm UTC](https://community.stereolabs.com/t/nvargus-daemon-have-some-error-wrong-frequency-range/10486/2 "2025-12-09T16:51:40Z")

</div>

Hi @m986883511,

Could you share the resulting JSON file from this command:

```auto
sudo ZED_Diagnostic -c

```

---

<div class="post-metadata">

**Author:** ![m986883511](https://community.stereolabs.com/user_avatar/community.stereolabs.com/m986883511/32/5378_2.png) [@m986883511](https://community.stereolabs.com/u/m986883511)\
**Post date:** [December 10, 2025, 2:58am UTC](https://community.stereolabs.com/t/nvargus-daemon-have-some-error-wrong-frequency-range/10486/3 "2025-12-10T02:58:08Z")

</div>

> [@mattrouss](#):
>
> `sudo ZED_Diagnostic -c`

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](https://community.stereolabs.com/uploads/short-url/vvcJAlfqVawTAVWHySuo4CxcGQo.json) (63.0 KB)

---

<div class="post-metadata">

**Author:** ![mattrouss](https://community.stereolabs.com/user_avatar/community.stereolabs.com/mattrouss/32/2452_2.png) [@mattrouss](https://community.stereolabs.com/u/mattrouss)\
**Post date:** [December 17, 2025, 2:08pm UTC](https://community.stereolabs.com/t/nvargus-daemon-have-some-error-wrong-frequency-range/10486/4 "2025-12-17T14:08:08Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![m986883511](https://community.stereolabs.com/user_avatar/community.stereolabs.com/m986883511/32/5378_2.png) [@m986883511](https://community.stereolabs.com/u/m986883511)\
**Post date:** [December 18, 2025, 1:01am UTC](https://community.stereolabs.com/t/nvargus-daemon-have-some-error-wrong-frequency-range/10486/5 "2025-12-18T01:01:13Z")

</div>

yes, I can open camera

---

<div class="post-metadata">

**Author:** ![mattrouss](https://community.stereolabs.com/user_avatar/community.stereolabs.com/mattrouss/32/2452_2.png) [@mattrouss](https://community.stereolabs.com/u/mattrouss)\
**Post date:** [December 18, 2025, 8:59am UTC](https://community.stereolabs.com/t/nvargus-daemon-have-some-error-wrong-frequency-range/10486/6 "2025-12-18T08:59:47Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![jaapcrezee](https://community.stereolabs.com/user_avatar/community.stereolabs.com/jaapcrezee/32/5665_2.png) [@jaapcrezee](https://community.stereolabs.com/u/jaapcrezee)\
**Post date:** [January 16, 2026, 1:03pm UTC](https://community.stereolabs.com/t/nvargus-daemon-have-some-error-wrong-frequency-range/10486/7 "2026-01-16T13:03:03Z")

</div>

We also have this warning/error in our syslog but want to get rid of it. Simply ignoring it is not desirable, we only want to log meaningful things. This also prevents the flash from wearing too quickly. So what is the root cause and how can be get rid of it?

---

<div class="post-metadata">

**Author:** ![17njensen](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/1/58956e/32.png) [@17njensen](https://community.stereolabs.com/u/17njensen)\
**Post date:** [April 9, 2026, 5:13pm UTC](https://community.stereolabs.com/t/nvargus-daemon-have-some-error-wrong-frequency-range/10486/8 "2026-04-09T17:13:36Z")

</div>

Did you happen to find any resolution to avoid just “ignoring” things?

---

<div class="post-metadata">

**Author:** ![jaapcrezee](https://community.stereolabs.com/user_avatar/community.stereolabs.com/jaapcrezee/32/5665_2.png) [@jaapcrezee](https://community.stereolabs.com/u/jaapcrezee)\
**Post date:** [April 10, 2026, 1:49pm UTC](https://community.stereolabs.com/t/nvargus-daemon-have-some-error-wrong-frequency-range/10486/9 "2026-04-10T13:49:46Z")

</div>

I reflashed our devices and since then I haven’t seen this message. But why and how is still a riddle…

(reflashing: activate recovery mode with `fc rec` jumper to gnd, then use sdkmanager and/or instructions from [stereolabs](https://www.stereolabs.com/))
