# Your VOTER/RTCM May Have Broken Itself on 01/01/21 00:01

**URL:** <https://community.allstarlink.org/t/your-voter-rtcm-may-have-broken-itself-on-01-01-21-00-01/18031>\
**Category:** AllStarLink\
**Created:** [January 4, 2021, 6:44am UTC](https://community.allstarlink.org/t/your-voter-rtcm-may-have-broken-itself-on-01-01-21-00-01/18031 "2021-01-04T06:44:47Z")\
**Posts on this page:** 1\
**Showing post:** 26

<div class="post-metadata">

**Author:** ![Wa1jhk1](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wa1jhk1/32/1624_2.png) [@Wa1jhk1](https://community.allstarlink.org/u/Wa1jhk1)\
**Post date:** [January 8, 2021, 1:51pm UTC](https://community.allstarlink.org/t/your-voter-rtcm-may-have-broken-itself-on-01-01-21-00-01/18031/26 "2021-01-08T13:51:14Z")

</div>

Hi All,

To check for the problem without rebooting the RTCM, change the debug value to 32 (menu option 14). The symptom shows up as “gps\_time: -1” in the GPS-DEBUG string:

GPS-DEBUG: $GPRMC,201833,A,4004.3350,N,10521.2352,W,000.0,023.1,050121,008.8,E\*6C  
GPS-DEBUG: mon: 0, gps\_time: -1, ctime: Thu Jan 1 00:00:0/ 1970

The -1 is being returned from the mktime library call. mktime evidently has a defect. -1 reports an error.

I have written a replacement for mktime that will work thru 2099. I have it running in V1.50. It displays this debug string:

GPS-DEBUG: $GPRMC,134238,A,4004.3361,N,10521.2338,W,000.0,322.5,080121,008.8,E\*6D  
GPS-DEBUG: mon: 1, gps\_time: 1610113358, ctime: Fri Jan 8 13:42:38 2021

We have this code running in ~10 RTCMs restoring our systems to operation.

I’d be happy to share the code.

73,

Dave  
WA1JHK

---

_[View the full topic](https://community.allstarlink.org/t/your-voter-rtcm-may-have-broken-itself-on-01-01-21-00-01/18031)._