Re: nmea0 huge timedelta while system clock is in sync

2020-03-31 Thread Theo de Raadt
Martin, I think you misread what is below. Since you won't file a complete bug report with all details, you are on your own. Good luck! Martin wrote: > Still can't find a solution. I'm suspect backup battery. > > ‐‐‐ Original Message ‐‐‐ > On Sunday, March 22, 2020 9:12 PM, Otto

Re: nmea0 huge timedelta while system clock is in sync

2020-03-31 Thread Martin
Still can't find a solution. I'm suspect backup battery. ‐‐‐ Original Message ‐‐‐ On Sunday, March 22, 2020 9:12 PM, Otto Moerbeek wrote: > On Sun, Mar 22, 2020 at 08:26:25PM +, Martin wrote: > > > Hello Otto, > > I can't share any coordinates, but after analyzing NMEA messages from

Re: nmea0 huge timedelta while system clock is in sync

2020-03-22 Thread Otto Moerbeek
On Sun, Mar 22, 2020 at 08:26:25PM +, Martin wrote: > Hello Otto, > > I can't share any coordinates, but after analyzing NMEA messages from > receiver I see the correct UTC time in first field of $GPGGA, $PQXFI > (Qualcomm extended fix information), $GNSNS sentences. In repeating sentences

Re: nmea0 huge timedelta while system clock is in sync

2020-03-22 Thread Martin
But NMEA datestamp is incorrect: $GPGGA,194458.00,_coordinates_,..,..,060800,0.0,E,A*35 ^^^ Martin ‐‐‐ Original Message ‐‐‐ On Sunday, March 22, 2020 3:28 PM, Otto Moerbeek wrote: > On Sun, Mar 22, 2020 at 03:22:40PM +, Martin wrote: > > > The position is

Re: nmea0 huge timedelta while system clock is in sync

2020-03-22 Thread Martin
Hello Otto, I can't share any coordinates, but after analyzing NMEA messages from receiver I see the correct UTC time in first field of $GPGGA, $PQXFI (Qualcomm extended fix information), $GNSNS sentences. In repeating sentences time data changes every second as it should be. System's time in

Re: nmea0 huge timedelta while system clock is in sync

2020-03-22 Thread Martin
The position is absolutely correct. I forgot to mention I changed Latitude and Longitude by different values. The timedelta is *incorrect* and it's only the question why. I missed a moment when huge time skew appeared. Just system clock was changed significantly to incorrect value. Now

Re: nmea0 huge timedelta while system clock is in sync

2020-03-22 Thread Otto Moerbeek
On Sun, Mar 22, 2020 at 03:22:40PM +, Martin wrote: > The position is absolutely correct. I forgot to mention I changed Latitude > and Longitude by different values. > The timedelta is *incorrect* and it's only the question why. > > I missed a moment when huge time skew appeared. Just

Re: nmea0 huge timedelta while system clock is in sync

2020-03-22 Thread Otto Moerbeek
On Sun, Mar 22, 2020 at 12:19:39PM +, Martin wrote: > hw.sensors.nmea0.indicator0=On (Signal), OK > hw.sensors.nmea0.timedelta0=619313970.981246 secs (GPS autonomous), OK, Sun > Mar 22 12:47:08.981 >^^ > hw.sensors.nmea0.angle0=10.0 degrees (Latitude), OK >

nmea0 huge timedelta while system clock is in sync

2020-03-22 Thread Martin
hw.sensors.nmea0.indicator0=On (Signal), OK hw.sensors.nmea0.timedelta0=619313970.981246 secs (GPS autonomous), OK, Sun Mar 22 12:47:08.981 ^^ hw.sensors.nmea0.angle0=10.0 degrees (Latitude), OK hw.sensors.nmea0.angle1=20.0 degrees (Longitude), OK