That’s great news, Thank You!
I was surprised when searching to see that Microchip’s fix in other compilers solved the problem through 2037. I kept wondering why they would use that date or what they know about the future that I don’t.
73,
Kevin
W8KHW
···
On Jan 8, 2021, at 9:01 AM, Wa1jhk1 via AllStarLink Discussion Groups noreply@community.allstarlink.org wrote:
| Wa1jhk1
January 8 |
- | - |
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/ 1970The -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 2021We have this code running in ~10 RTCMs restoring our systems to operation.
I’d be happy to share the code.
73,
Dave
WA1JHK
Visit Topic or reply to this email to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, click here.