# Specific set up for limeSDR XTRX for location data across X5

**URL:** <https://discourse.myriadrf.org/t/specific-set-up-for-limesdr-xtrx-for-location-data-across-x5/13110>\
**Category:** LimeSDR\
**Created:** [27 April 2026 09:52 UTC](https://discourse.myriadrf.org/t/specific-set-up-for-limesdr-xtrx-for-location-data-across-x5/13110 "2026-04-27T09:52:29Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![tomasS](https://avatars.discourse-cdn.com/v4/letter/t/6de8d8/32.png) [@tomasS](https://discourse.myriadrf.org/u/tomasS)\
**Post date:** [29 April 2026 05:18 UTC](https://discourse.myriadrf.org/t/specific-set-up-for-limesdr-xtrx-for-location-data-across-x5/13110/4 "2026-04-29T05:18:49Z")

</div>

Your current understanding is correct.

The 1980 timestamp you’re seeing without a lock is data taken directly from the ZDA message. Gateware assumes data provided by ZDA messages is always valid (unless checksum fails), so as soon as the GNSS chip achieves lock and starts emitting correct time information, it will be used for timestamps.

---

_[View the full topic](https://discourse.myriadrf.org/t/specific-set-up-for-limesdr-xtrx-for-location-data-across-x5/13110)._