# RTCM gps using garmin 18 reports date as 2001

**URL:** <https://community.allstarlink.org/t/rtcm-gps-using-garmin-18-reports-date-as-2001/18690>\
**Category:** AllStarLink\
**Created:** [June 14, 2021, 1:35am UTC](https://community.allstarlink.org/t/rtcm-gps-using-garmin-18-reports-date-as-2001/18690 "2021-06-14T01:35:08Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)\
**Post date:** [June 14, 2021, 6:31pm UTC](https://community.allstarlink.org/t/rtcm-gps-using-garmin-18-reports-date-as-2001/18690/4 "2021-06-14T18:31:21Z")

</div>

I hear Dave @WB6WTM already mentioned this to you but (for the benefit of others who may be reading this) the Garmin firmware may need an update.

> [@Strange RTCM GPS behavior](https://community.allstarlink.org/t/strange-rtcm-gps-behavior/15660/2):
>
> Looks like I may have found an answer to the second issue I was seeing with incorrect date on my third RTCM, and it even might even have something to do with the first problem I mentioned. It looks like the Garmin’s firmware wasn’t coded to rollover during the “GPS Rollover” event on April 26, 2019. I noted that the Hours/Minutes/Seconds was being read exactly correctly at the same on all three RTCMs’ consoles, but the week and year was obviously off on the third RTCM (953192179 vs the 15725073…

---

_[View the full topic](https://community.allstarlink.org/t/rtcm-gps-using-garmin-18-reports-date-as-2001/18690)._
