# Zed X IMU odr issues

**URL:** <https://community.stereolabs.com/t/zed-x-imu-odr-issues/10766>\
**Category:** ZED X\
**Tags:** sdk, jetson\
**Created:** [February 9, 2026, 8:38am UTC](https://community.stereolabs.com/t/zed-x-imu-odr-issues/10766 "2026-02-09T08:38:19Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![picci](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/p/e68b1a/32.png) [@picci](https://community.stereolabs.com/u/picci)\
**Post date:** [February 9, 2026, 8:38am UTC](https://community.stereolabs.com/t/zed-x-imu-odr-issues/10766/1 "2026-02-09T08:38:19Z")

</div>

Hi,

I’ve been collecting some camera + IMU data on the Zed X and I noticed I am getting ~186Hz against the advertised 400Hz. I am using your APIs directly, no ROS. But, as the ROS2 implementation, I have two separate threads for getting camera images and sensors data. I tried on two different Zed X cameras and I get the same outcome. I’ve been using the Zed Box Orin mini NX 16gb.

I also get ~190Hz when dumping data with your Zed Sensor Viewer, although I am selecting 400Hz in the settings.

Lastly, the only setup where I can actually get ~400Hz is through Zed Explorer saving data into an .svo2

Moreover, I noticed that I am getting kind of two rate distributions in the data I collect. Here I am plotting the period between IMU samples. This is also visible in the data I collect using the Zed Explorer, or the sensor viewer. The only setup without this two distributions is using the Zed Explorer with 1080p 15Hz cameras.

 ![image](https://community.stereolabs.com/uploads/default/original/2X/2/2a5be5de1704f3c84f977fe2a5ecc471b8043742.png)

I would like to know why I am able to get the desired frequency through the explorer but not through other tools and through the APIs, and why the odr is so unstable with seemingly two distributions and with big spikes. Is there any fundamental difference in how the data is collected when using the different tools and APIs? Is the Zed Box Mini not keeping up with the data coming from the camera?

Thanks,

Marco

---

<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:** [February 10, 2026, 4:39pm UTC](https://community.stereolabs.com/t/zed-x-imu-odr-issues/10766/2 "2026-02-10T16:39:53Z")

</div>

Hi @picci,

Welcome to the forums 👋

We’ve recently released the ZED SDK 5.2 and ZED X Driver 1.4, which come with improvements in IMU stability where the IMU rate spread improved from ~11 Hz (185–197 Hz) to \< 1 Hz (199.5–200 Hz) and fixed data drop issues in complex setups involving 8+ IMUs.

You can find both releases and changelogs here:

- [https://www.stereolabs.com/en-fr/developers/release](https://www.stereolabs.com/en-fr/developers/release)
- [https://www.stereolabs.com/en-fr/developers/drivers](https://www.stereolabs.com/en-fr/developers/drivers)

However, in order to support multi-camera setups, we have reduced the rate from 400Hz to 200Hz on all cameras. As 400Hz IMU has an impact on the overall performance, we are investigating to add a mode when using a reduced number of cameras.

---

<div class="post-metadata">

**Author:** ![picci](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/p/e68b1a/32.png) [@picci](https://community.stereolabs.com/u/picci)\
**Post date:** [February 24, 2026, 3:40pm UTC](https://community.stereolabs.com/t/zed-x-imu-odr-issues/10766/3 "2026-02-24T15:40:09Z")

</div>

Hi @mattrouss ,

I updated to 5.2 and updated the drivers too, and I am getting weird results:

- APIs are recording the IMU at ~125Hz regardless of the camera res
- ZED Explorer records an .svo with IMU at ~90Hz
- ZED Sensor Viewer recorded ~199Hz

---

<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:** [February 27, 2026, 5:59pm UTC](https://community.stereolabs.com/t/zed-x-imu-odr-issues/10766/4 "2026-02-27T17:59:08Z")

</div>

Hi @picci,

Sorry for the late reply, we’re taking a look at this internally to reproduce

---

<div class="post-metadata">

**Author:** ![dieng-calder](https://community.stereolabs.com/user_avatar/community.stereolabs.com/dieng-calder/32/5811_2.png) [@dieng-calder](https://community.stereolabs.com/u/dieng-calder)\
**Post date:** [March 4, 2026, 8:35pm UTC](https://community.stereolabs.com/t/zed-x-imu-odr-issues/10766/5 "2026-03-04T20:35:11Z")

</div>

We’re seeing the same issue on our setup — 3× ZED-X cameras on a Jetson AGX Orin (L4T R36.4.4), running ZED SDK 5.2.1 + ZED X Driver 1.4.0.

After adding deduplication to our getSensorsData(TIME\_REFERENCE::CURRENT) polling loop (filtering out repeated samples with the same timestamp), the actual unique IMU sample rates we  
observe are:

- Camera 0: ~129 Hz
- Camera 1: ~138 Hz
- Camera 2: ~130 Hz

This is consistent with @picci’s observation of ~125 Hz via the APIs after the 5.2 update. The rate varies per camera, suggesting the issue may be related to GMSL2 deserialization  
scheduling rather than the IMU hardware itself.

Our polling thread runs at ~400 Hz (well above the 200 Hz target), so we’re confident we’re not missing samples due to insufficient polling frequency. Before the dedup fix, the raw  
callback rate appeared higher since getSensorsData returns the same sample multiple times between updates.

Environment:

- ZED SDK: 5.2.1
- ZED X Driver: 1.4.0 ([stereolabs](https://www.stereolabs.com/)-zedlink-quad)
- L4T: R36.4.4 (JetPack 6.2)
- Hardware: Jetson AGX Orin, 3× ZED-X Mini via GMSL2
- Polling method: getSensorsData(TIME\_REFERENCE::CURRENT) in a dedicated SCHED\_FIFO thread

Would be great to hear if there’s a timeline for getting closer to the 200 Hz target with multi-camera setups.

---

<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:** [March 9, 2026, 10:40am UTC](https://community.stereolabs.com/t/zed-x-imu-odr-issues/10766/6 "2026-03-09T10:40:06Z")

</div>

Hi @dieng-calder ,

To be sure we can reproduce the same issues, can you confirm that you have the same performance using the following script?

[zed\_svo\_diagnostic.zip](https://community.stereolabs.com/uploads/short-url/i2ebY3ROKy46Eh0xtXCSualcoE0.zip) (5.3 KB)

---

<div class="post-metadata">

**Author:** ![dieng-calder](https://community.stereolabs.com/user_avatar/community.stereolabs.com/dieng-calder/32/5811_2.png) [@dieng-calder](https://community.stereolabs.com/u/dieng-calder)\
**Post date:** [March 10, 2026, 12:15am UTC](https://community.stereolabs.com/t/zed-x-imu-odr-issues/10766/7 "2026-03-10T00:15:23Z")

</div>

Thanks for the diagnostic tool and suggestions! We ran extensive testing on our 4-camera ZED-X setup (Jetson Orin, ZED SDK 5.x) and found the root cause of our IMU rate issues.

### Root Cause

Our capture pipeline was using `getSensorsData(sl::TIME_REFERENCE::CURRENT)` in a dedicated polling thread running at ~400 Hz. Under multi-camera CPU load, this polling thread  
couldn’t keep up and only retrieved the **latest** IMU sample each call, losing ~30% of data:

| Config | Observed IMU Rate | Expected | Loss |
| --- | --- | --- | --- |
| 1 camera | ~195 Hz | 200 Hz | ~2% |
| 3 cameras | 130-138 Hz | 200 Hz | ~30% |
| 4 cameras | 130-135 Hz | 200 Hz | ~33% |

### Fix: `getSensorsDataBatch()`

Switching to `getSensorsDataBatch()` called **inline after each `grab()`** in the capture loop completely resolved the issue. This API returns all IMU samples accumulated since the  
last `grab()` (~6-7 samples per frame at 200 Hz / 30 fps), which is the same mechanism the SDK uses internally for SVO recording.

**Results after fix:**

| Config | IMU Rate | Image Rate | IMU/Frame | Loss |
| --- | --- | --- | --- | --- |
| 3 cameras | 200-207 Hz | 30.0 fps | 6-7 | 0% |
| 4 cameras | 200-207 Hz | 30.0 fps | 6-7 | 0% |

### SVO Recording Validation

We also validated using your `svo_diagnostic` tool that SVO recordings capture the full 200 Hz IMU rate even under 4-camera load. The SVO encoder itself doesn’t drop IMU data — it  
uses the batch mechanism internally.

### Key Takeaway

**`getSensorsData(TIME_REFERENCE::CURRENT)` should not be used for high-frequency IMU capture in multi-camera setups.** It only returns the single latest sample and is subject to  
thread scheduling jitter. `getSensorsDataBatch()` is the correct API for reliable IMU data retrieval.

It would be helpful if the SDK documentation more prominently recommended `getSensorsDataBatch()` for multi-camera or high-throughput use cases, as `getSensorsData` appears to be the  
“default” API in most examples.

---

<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:** [March 10, 2026, 1:53pm UTC](https://community.stereolabs.com/t/zed-x-imu-odr-issues/10766/8 "2026-03-10T13:53:43Z")

</div>

Hi @dieng-calder,

Thank you for the feedback. The recommendation would indeed be either to use `getSensorsDataBatch()`, which provides the batch of IMU data retrieved since the latest `grab()`, or to retrieve all of the IMU data in a separate thread than the grab() thread, at a higher rate (i.e. 200Hz for the ZED X).

We will update our samples to reflect this better.

---

<div class="post-metadata">

**Author:** ![picci](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/p/e68b1a/32.png) [@picci](https://community.stereolabs.com/u/picci)\
**Post date:** [March 10, 2026, 2:15pm UTC](https://community.stereolabs.com/t/zed-x-imu-odr-issues/10766/9 "2026-03-10T14:15:00Z")

</div>

I’ll make sure to use getSensorsDataBatch too. Thanks!

---

<div class="post-metadata">

**Author:** ![picci](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/p/e68b1a/32.png) [@picci](https://community.stereolabs.com/u/picci)\
**Post date:** [March 11, 2026, 4:03pm UTC](https://community.stereolabs.com/t/zed-x-imu-odr-issues/10766/10 "2026-03-11T16:03:37Z")

</div>

Following up on the new API. I get a steady ~200 Hz now with no big gaps between measurements. Many thanks!

I noticed, however, this weird drop at a steady rate. Have you experienced this too?

 ![data.csv_plot (1)](https://community.stereolabs.com/uploads/default/original/2X/b/bf11b5843a6f1b10cca0752c45e6f2180379f4d5.png)

---

<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:** [March 12, 2026, 3:15pm UTC](https://community.stereolabs.com/t/zed-x-imu-odr-issues/10766/11 "2026-03-12T15:15:04Z")

</div>

Hi @picci,

This is indeed a behavior that is known, and due to the updated algorithm in 1.4.0 that tracks the drift between the host Jetson’s clock and the IMU’s internal clock. Unfortunately, to fix this behavior this would require a hardware change to the camera, which we are preparing for our future camera line.

---

<div class="post-metadata">

**Author:** ![picci](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/p/e68b1a/32.png) [@picci](https://community.stereolabs.com/u/picci)\
**Post date:** [March 12, 2026, 3:49pm UTC](https://community.stereolabs.com/t/zed-x-imu-odr-issues/10766/12 "2026-03-12T15:49:20Z")

</div>

Fair enough. Looking forward to the new cameras then!
