# 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:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![robots](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/r/48db29/32.png) [@robots](https://community.stereolabs.com/u/robots)\
**Post date:** [May 28, 2025, 3:03pm UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/3 "2025-05-28T15:03:31Z")

</div>

Good to know. Can you verify my understanding?

1. 

> It’s the system time when the full sample has been received by the GMSL2 deserializer.

Will this timestamp will be 1-2 frames after the exposure ended? Based on  
[GMSL ZED x vs regular zed and usb cable --- latency - #2 by Myzhar](https://community.stereolabs.com/t/gmsl-zed-x-vs-regular-zed-and-usb-cable-latency/2681/2) . Also does the latency really scale inversely with framerate?  
2.

> The SDK cannot be aware of this information because there’s no link between the deserializer GPIO and the SDK.

Has there been any consideration around integrating this into the SDK? The setup I’m imagining is connecting the capture card GPIO pins to the Jetson’s GPIO pins. Would that allow for syncronizing the timestamps with the true exposure time? Is there any way to transmit this over the CSI port? Any information you can provide here is useful both in the context of potential future SDK features and just general knowledge as I may try to build this setup myself.

---

_[View the full topic](https://community.stereolabs.com/t/zedx-timestamps/8924)._
