# LimeSDR-XTRX how to use GPS chip on board

**URL:** <https://discourse.myriadrf.org/t/limesdr-xtrx-how-to-use-gps-chip-on-board/8627>\
**Category:** LimeSDR\
**Created:** [18 January 2025 10:27 UTC](https://discourse.myriadrf.org/t/limesdr-xtrx-how-to-use-gps-chip-on-board/8627 "2025-01-18T10:27:41Z")\
**Posts on this page:** 1\
**Showing post:** 8

<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:** [7 May 2026 12:22 UTC](https://discourse.myriadrf.org/t/limesdr-xtrx-how-to-use-gps-chip-on-board/8627/8 "2026-05-07T12:22:57Z")

</div>

Newer gateware revisions expose the GNSS UART interface to the host machine at /dev/ttyLimeUART0 (baud rate 9600). This allows directly monitoring all NMEA messages emitted by the chip, as well as configuration, if needed.  
I’d recommend Gateware revisions 3.5+

This, as well as some other GNSS related questions were actually discussed in another recent discussion:

> [@Specific set up for limeSDR XTRX for location data across X5](https://discourse.myriadrf.org/t/specific-set-up-for-limesdr-xtrx-for-location-data-across-x5/13110/4):
>
> 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/limesdr-xtrx-how-to-use-gps-chip-on-board/8627)._