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

I have a system that has been running for years without requiring any fiddling. I noticed the RTCM’s were running v1.50, so I decided to setup a spare RTCM and test v1.51. The updated version doesn’t report an error, but it also doesn’t set the System Time. I am running one of the QRP Labs GPS devices on the test unit (and also at a couple receive sites). When checking status with menu 98 it reports

I would be happy to test v1.54 and see if that works if the binary was available. I had difficulty getting the compiler working correctly the last time I tried.

Lee, the original link you provided from microchip had a “work around” post in the thread. I believe it mentioned using an alternate library.

Thanks for everybody’s help with this.

Kevin
W8KHW

···

On Jan 5, 2021, at 2:50 PM, Lee via AllStarLink Discussion Groups noreply@community.allstarlink.org wrote:

| ve7fet
January 5 |

  • | - |

Hi Chuck,

I don’t believe that is going to help in this case. I am running a similarly modified firmware (have been testing a number of similar changes to what you have in that branch), and they were all running fine, until we rolled over on NYE.

The problem isn’t a week rollover issue, it is a bug in the mktime routine, causing it to return -1 when you send it the tm struct to convert to epoch time.

That causes gpstime to be -1, so, it always starts counting at something like Dec 31, 1970 at 1600 (I can’t recall the exact time off the top of my head).

So, resetting the GPS, always causes it to start counting from that date, regardless of what the real date/time is.

At least, that is what I am seeing on both the TSIP (Trimble) and NMEA devices I have access to, they’re both behaving the same (and were previously working just fine).

I think the fix will be to convert the date/time from the GPS to epoch with a stand-alone function, that doesn’t use the built-in mktime from time.h.

Unfortunately, the box I was using to compile test code on decided to blow up (thanks Microsoft updates), so I haven’t had a chance to compile and test a fix, yet.

Lee


Visit Topic or reply to this email to respond.


In Reply To

| Chuck_Henderson
January 5 |

  • | - |

You need “S/W Version: 1.54 04/14/2020” the source can be found at https://github.com/ccie2285/voter or at https://github.com/AllStarLink/voter/tree/testing or at https://github.com/pttlink/voter/tree/testing This 1.54 has multiple fixes for different GPS versions and can accept different values fo…


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.