# Dual ZED X on AGX Orin: capped at 15fps despite idle CPU/GPU, single-camera hits 30fps cleanlySetup

**URL:** <https://community.stereolabs.com/t/dual-zed-x-on-agx-orin-capped-at-15fps-despite-idle-cpu-gpu-single-camera-hits-30fps-cleanlysetup/11596>\
**Category:** ROS2\
**Tags:** sdk\
**Created:** [July 30, 2026, 11:14pm UTC](https://community.stereolabs.com/t/dual-zed-x-on-agx-orin-capped-at-15fps-despite-idle-cpu-gpu-single-camera-hits-30fps-cleanlysetup/11596 "2026-07-30T23:14:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![shahid\_malik](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/s/b4bc9f/32.png) [@shahid\_malik](https://community.stereolabs.com/u/shahid_malik)\
**Post date:** [July 30, 2026, 11:14pm UTC](https://community.stereolabs.com/t/dual-zed-x-on-agx-orin-capped-at-15fps-despite-idle-cpu-gpu-single-camera-hits-30fps-cleanlysetup/11596/1 "2026-07-30T23:14:53Z")

</div>

Dual ZED X on AGX Orin: capped at 15fps despite idle CPU/GPU, single-camera hits 30fps cleanly  
Setup

• Jetson AGX Orin Developer Kit (64GB), JetPack (ROS 2 Humble).  
• 2x ZED X (serials 47903798, 41704206) on ZED Link Duo capture card.  
• ZED SDK 5.2.3, zed-ros2-wrapper (latest master).  
• NITROS not installed.  
• Launched via zed\_multi\_camera.launch.py (stock tutorial launch file, both cameras composed into one zed\_multi\_container).  
Config

• grab\_resolution: HD1200, grab\_frame\_rate: 30, pub\_frame\_rate: 30, grab\_compute\_capping\_fps: 30.  
• depth\_mode: NONE (also tested with PERFORMANCE, no difference to the symptom).  
• pos\_tracking\_enabled auto-disabled by depth\_mode: NONE.  
• enable\_24bit\_output: true (tested both true/false, no difference).  
• enable\_ipc left at wrapper default (true) — not overridden by zed\_multi\_camera.launch.py, which does not forward this argument to the underlying zed\_camera.launch.py includes.  
System-level fixes already applied (confirmed necessary)

• Switched nvpmodel from MODE\_30W to MAXN (mode 0).  
• Ran jetson\_clocks (locks GPU/CPU/EMC to max).  
• Forced performance governor on all 12 CPU cores (schedutil was not sustaining high clocks under load even with jetson\_clocks applied).  
• All three now persisted via systemd services.  
Isolation testing performed

1. Single ZED X (cam0) alone, via zed\_camera.launch.py directly (not multi-camera):.  
◦ Before power-mode fix: hard-capped at ~15.0-15.3 Hz, extremely tight std dev (0.002-0.02s), regardless of grab\_frame\_rate/pub\_frame\_rate/depth\_mode settings..  
◦ After MAXN + jetson\_clocks + forced performance governor: sustains a clean, stable ~29.8 Hz over 30+ second windows. This fully resolved the single-camera case..
2. Both cameras together, via zed\_multi\_camera.launch.py, same system-level fixes applied:.  
◦ Still capped at exactly ~15.0 Hz (confirmed via multiple bag recordings, 60s-730s durations)..  
◦ tegrastats during a live dual-camera recording shows CPU at 0-11% across all 12 cores, GR3D\_FREQ at 17-20%, temps stable ~55-58°C — system is essentially idle. This rules out compute/thermal/power throttling as the cause for the dual-camera case specifically..
3. Cam0/cam1 timestamp offset analysis (nearest-neighbor matching on header.stamp from left/color/rect/image/compressed):.  
◦ Confirms both cameras are decimating to 15Hz from an underlying (presumably still 30Hz-triggered) hardware clock, but each camera’s internal “keep every other tick” decimation locks onto its own phase independently..  
◦ When both cameras happen to lock onto the same phase, timestamp offsets are excellent: median offset ~7-12us, p99 under 150-200us — consistent with the ~15us GMSL2 hardware sync guarantee documented at [https://support.stereolabs.com](https://support.stereolabs.com) (grab period tolerance)..  
◦ When they lock onto opposite phases, offsets sit at a clean, tight cluster at exactly one grab period (~33.3ms at 30fps-underlying-clock), both +33ms and -33ms clusters observed across different recordings and even within a single long recording (see attached offset\_over\_time.png — a single sharp phase-flip event partway through a 12-minute recording, followed by continued occasional flips)..  
◦

---

<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:** [August 3, 2026, 3:53pm UTC](https://community.stereolabs.com/t/dual-zed-x-on-agx-orin-capped-at-15fps-despite-idle-cpu-gpu-single-camera-hits-30fps-cleanlysetup/11596/2 "2026-08-03T15:53:53Z")

</div>

Hi @shahid_malik  
thank you for the exhaustive information.

Have you tried to apply the configuration described here:

> **[DDS and Network Tuning for ROS 2 | StereoLabs](https://docs.stereolabs.com/docs/integrations/ros-2/dds-and-network-tuning)**

also carefully read this guide:

> **[Stereo Node Frequency Tuning | StereoLabs](https://docs.stereolabs.com/docs/integrations/ros-2/node-frequency-tuning)**

Finally, why not trying this?

> **[Using Zenoh as ROS 2 Middleware | StereoLabs](https://docs.stereolabs.com/docs/integrations/ros-2/using-zenoh-as-middleware)**

I also recommend you use this to test your configuration:

> **[ZED Topic Benchmark Tool | StereoLabs](https://docs.stereolabs.com/docs/integrations/ros-2/topic-benchmark-tool)**
