# ZedX Timestamps

**URL:** <https://community.stereolabs.com/t/zedx-timestamps/8924>\
**Category:** Software\
**Created:** [May 27, 2025, 5:58pm UTC](https://community.stereolabs.com/t/zedx-timestamps/8924 "2025-05-27T17:58:28Z")\
**Posts on this page:** 4\
**Page:** 2

<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:** [November 9, 2026, 8:08am UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/21 "2026-11-09T08:08:06Z")

</div>

Hi @Parv-Maheshwari,

replies to threads that have been inactive for months can easily go unnoticed, because they do not trigger the usual notifications to the support team.  
I recommend always opening a new thread and adding links to the older threads that contain relevant details.

> [@Parv-Maheshwari](#):
>
> Does `camera.get_timestamp(sl.TIME_REFERENCE.IMAGE)` return:
> 
> 1. **End of exposure time** — i.e. when the sensor finished integrating, synchronized to the trigger edge, or
> 2. **Host receive time** — i.e. when the frame arrived on the Jetson after GMSL transfer and ISP processing (~1 frame later)?

`TIME_REFERENCE::IMAGE` is the start of the sensor readout, which on the global shutter [ZED X](https://www.stereolabs.com/products/zed-x) corresponds to the end of the exposure. The ISP buffering on the Jetson delays when the frame is available to `grab()`, not the timestamp value.

> [@Parv-Maheshwari](#):
>
> If so, is there a way to get the actual exposure timestamp from the SVO, or should we subtract one frame period to approximate it?

No subtraction is required.  
In addition, [ZED SDK v5.5.0](https://www.stereolabs.com/developers/release#550-6a4d834b210dc1332e9d80f04af676dd) introduced `TIME_REFERENCE::IMAGE_CENTER_OF_EXPOSURE`, which returns the middle of each frame’s exposure, also from SVO files.  
[ZED SDK v5.5.1](https://www.stereolabs.com/developers/release#551-241d3578fe3c) fixed an offset of the per-frame exposure data stored in SVO2 files; files recorded with older versions keep this offset, so new recordings are required to use it.

> [@Parv-Maheshwari](#):
>
> Let’s say we send a pulse of 1111010010011, then the camera images are \_111101001001 → basically delayed by 1 frame relative to the trigger. Is this correct ?

Your reasoning is consistent with how the slave mode works: the exposure start is computed so that the exposure ends on the trigger rising edge, so each exposure is scheduled before the edge it is aligned to.  
If this is the case, the one frame shift comes from the pulse to frame matching and not from the timestamp, which agrees with the answer above.

You are using ZED SDK v5.2. Can you repeat the test with ZED SDK v5.5.1, the latest [ZED X Driver](https://www.stereolabs.com/developers/drivers) (v1.4.4) and the latest ZED ROS 2 Wrapper, recording a new SVO and comparing the `IMAGE` timestamps with the trigger edges shifted by one pulse?  
ZED SDK v5.5.0 also improved the capture latency consistency of stereo GMSL cameras, which requires ZED X Driver v1.4.3 or newer.

---

<div class="post-metadata">

**Author:** ![Parv-Maheshwari](https://community.stereolabs.com/user_avatar/community.stereolabs.com/parv-maheshwari/32/5756_2.png) [@Parv-Maheshwari](https://community.stereolabs.com/u/Parv-Maheshwari)\
**Post date:** [November 13, 2026, 3:59pm UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/22 "2026-11-13T15:59:12Z")

</div>

Unfortunately, since we are in the middle of a data collection campaign, upgrading our stack with new SDKs, drivers, etc., runs the risk of newer data not following the same distribution as the old, so upgrading is not possible right now.

Regarding the trigger matching and slave mode, I did not understand your comment. Simply put. If I have a dropped trigger at T and I sent triggers at T-1 and T+1 in system time, will my corresponding dropped image be at T or T+1? Based on the ZEDX docs, which say that the camera syncs the end of exposure to the rise of an edge, it would seem that a drop at Time T results in a dropped image at T and not at T+1, but this is not what we see in the data. Can you please clarify?

---

<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:** [November 13, 2026, 4:18pm UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/23 "2026-11-13T16:18:38Z")

</div>

Hi @Parv-Maheshwari,

> [@Parv-Maheshwari](#):
>
> Unfortunately, since we are in the middle of a data collection campaign, upgrading our stack with new SDKs, drivers, etc., runs the risk of newer data not following the same distribution as the old, so upgrading is not possible right now.

Understood. The behavior described below also applies to your current setup. I still recommend upgrading once the campaign is over.

> [@Parv-Maheshwari](#):
>
> If I have a dropped trigger at T and I sent triggers at T-1 and T+1 in system time, will my corresponding dropped image be at T or T+1?

The dropped image is the one at T+1, which matches what you see in your data.

In slave mode, the camera does not start the exposure on the rising edge; it aligns the **end** of the exposure with the rising edge. Each rising edge is the reference used to schedule the next frame, whose exposure ends one trigger period later, on the following edge. This means:

- the edge at T-1 generates the image whose exposure ends at T, so its `IMAGE` timestamp is close to T;
- if the edge at T is missing, no frame is scheduled to end at T+1, so the image at T+1 is dropped.

> [@Parv-Maheshwari](#):
>
> Based on the ZEDX docs, which say that the camera syncs the start of exposure to the rise of an edge,

Our documentation says the rising edge is synchronized with the end of the exposure phase of the CMOS sensor: [ZED Link Quad GPIO Triggering](https://docs.stereolabs.com/docs/products/embedded/zed-link-capture-card/zed-link-quad/zed-link-quad-gpio-triggering). The slave-mode behavior is also covered in this thread: [Understanding Slave mode on the Quad capture card](https://community.stereolabs.com/t/understanding-slave-mode-on-the-quad-capture-card/10777). If you found a page that says the exposure _starts_ on the rising edge, please share the link so we can correct it.

This also explains your 31.76 ms measurement. If you pair each image with the edge that scheduled it (T-1), you get an offset of about one period. If you pair it with the edge it is aligned to (T), the `IMAGE` timestamp falls close to the end of the exposure.

---

<div class="post-metadata">

**Author:** ![Parv-Maheshwari](https://community.stereolabs.com/user_avatar/community.stereolabs.com/parv-maheshwari/32/5756_2.png) [@Parv-Maheshwari](https://community.stereolabs.com/u/Parv-Maheshwari)\
**Post date:** [November 13, 2026, 4:38pm UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/24 "2026-11-13T16:38:02Z")

</div>

Apologies on my last post. There was a typo. I meant end of exposure is synced to Rising edge. I have updated the last post.

Also, for the future, I think adding this clarity that a trigger at T affects the image at T+1 should also be added to the docs, since the docs only say “the rising edge is synchronized with the end of the exposure phase of the CMOS sensor” .

[Previous page](https://community.stereolabs.com/t/zedx-timestamps/8924.md?page=1)
