# 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:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jamie](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/j/aca169/32.png) [@Jamie](https://community.allstarlink.org/u/Jamie)\
**Post date:** [June 14, 2021, 1:35am UTC](https://community.allstarlink.org/t/rtcm-gps-using-garmin-18-reports-date-as-2001/18690/1 "2021-06-14T01:35:08Z")

</div>

Using an rtcm , garmin 18x, the date reported was" Current Time: Sun Oct 28, 2001 22:55:32.000"  
Using firmware " S/W Version: Chuck-1.50-SMT-WA1JHK 01/06/2021a "  
A second site reports the same time too using above software .

One rtcm reboots some of the time , other times it does not go through the bootloader phase and simply  
does nothing , a reset or power cycle brings it back .  
One other strange thing , had some issues using telnet and this particular rtcm , allowed login but never produced a menu just froze .Ip was correct changed ip then back saved (99 ) seems to work via telnet after .

Has anyone seen these issues and is there an easy fix ?

---

<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, 4:59am UTC](https://community.allstarlink.org/t/rtcm-gps-using-garmin-18-reports-date-as-2001/18690/2 "2021-06-14T04:59:21Z")

</div>

Check out this topic for new firmware that may fix the date problem.

> [@RTCM/VOTER Updated Firmware](https://community.allstarlink.org/t/rtcm-voter-updated-firmware/18451):
>
> I am not going to get in to the politics of the Github repo. I forked the RTCM/VOTER firmware part, prior to things going sideways, so I could do some development. You can find my current work at: [https://github.com/ve7fet/voter](https://github.com/ve7fet/voter) If you look through the Releases, you will see I have made a bunch of changes to the code. Up to you, if you want to experiment. I have run them all on through-hole (VOTER) board, as well as on RTCM’s. Lots of comments have been added to the code, after going over it …

---

<div class="post-metadata">

**Author:** ![Jamie](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/j/aca169/32.png) [@Jamie](https://community.allstarlink.org/u/Jamie)\
**Post date:** [June 14, 2021, 3:58pm UTC](https://community.allstarlink.org/t/rtcm-gps-using-garmin-18-reports-date-as-2001/18690/3 "2021-06-14T15:58:53Z")

</div>

Thanks , will giv it a try !

---

<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…

---

<div class="post-metadata">

**Author:** ![Jamie](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/j/aca169/32.png) [@Jamie](https://community.allstarlink.org/u/Jamie)\
**Post date:** [June 15, 2021, 12:16am UTC](https://community.allstarlink.org/t/rtcm-gps-using-garmin-18-reports-date-as-2001/18690/5 "2021-06-15T00:16:11Z")

</div>

I used the firmware from ve7fet , added 619315201 ( using menu 82 ) .  
found this [Garmin GPS Week Number Rollover Statement | Garmin Support](https://support.garmin.com/en-US/?faq=zWQY6Z2kFiAuY9kDnDBgZ6).

also found  
[Garmin GPS 18x LVC firmware issue](https://www.satsignal.eu/ntp/Garmin-GSP18x-LVC-firmware-issue.htm)  
down the above webpage there is a release for the 18x lvc firmware - did not try this …

thanks !

---

<div class="post-metadata">

**Author:** ![Jamie](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/j/aca169/32.png) [@Jamie](https://community.allstarlink.org/u/Jamie)\
**Post date:** [June 15, 2021, 1:08pm UTC](https://community.allstarlink.org/t/rtcm-gps-using-garmin-18-reports-date-as-2001/18690/6 "2021-06-15T13:08:42Z")

</div>

Garmin has official firmware update ,

[Garmin: GPS 18x PC/LVC Updates & Downloads](https://www8.garmin.com/support/download_details.jsp?id=4055)

might try this soon -
