nmea0 huge timedelta while system clock is in sync

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

nmea0 huge timedelta while system clock is in sync

Martin Got
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
hw.sensors.nmea0.distance0=30.0 m (Altitude), OK
hw.sensors.nmea0.velocity0=0.000 m/s (Ground speed), OK

It works for about two years before like a charm, but now timedelta 619313970.981246 secs.
Tried to change GPS receiver, no effect.

Martin
Reply | Threaded
Open this post in threaded view
|

Re: nmea0 huge timedelta while system clock is in sync

Otto Moerbeek
On Sun, Mar 22, 2020 at 12:19:39PM +0000, 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
> hw.sensors.nmea0.angle1=20.0 degrees (Longitude), OK
> hw.sensors.nmea0.distance0=30.0 m (Altitude), OK
> hw.sensors.nmea0.velocity0=0.000 m/s (Ground speed), OK
>
> It works for about two years before like a charm, but now timedelta 619313970.981246 secs.
> Tried to change GPS receiver, no effect.
>
> Martin

You position is also suspect. Can you run cu on the port the GPS is
atteched to and get a snippet of the output?

        -Otto

Reply | Threaded
Open this post in threaded view
|

Re: nmea0 huge timedelta while system clock is in sync

Martin Got
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 ntpd.conf set to NTP pool, but hope I can fix radioclocks.

Martin

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, March 22, 2020 12:54 PM, Otto Moerbeek <[hidden email]> wrote:

> On Sun, Mar 22, 2020 at 12:19:39PM +0000, 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
> > hw.sensors.nmea0.angle1=20.0 degrees (Longitude), OK
> > hw.sensors.nmea0.distance0=30.0 m (Altitude), OK
> > hw.sensors.nmea0.velocity0=0.000 m/s (Ground speed), OK
> > It works for about two years before like a charm, but now timedelta 619313970.981246 secs.
> > Tried to change GPS receiver, no effect.
> > Martin
>
> You position is also suspect. Can you run cu on the port the GPS is
> atteched to and get a snippet of the output?
>
> -Otto


Reply | Threaded
Open this post in threaded view
|

Re: nmea0 huge timedelta while system clock is in sync

Otto Moerbeek
On Sun, Mar 22, 2020 at 03:22:40PM +0000, 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 system clock was changed significantly to incorrect value. Now ntpd.conf set to NTP pool, but hope I can fix radioclocks.
>
> Martin
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Sunday, March 22, 2020 12:54 PM, Otto Moerbeek <[hidden email]> wrote:
>
> > On Sun, Mar 22, 2020 at 12:19:39PM +0000, 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
> > > hw.sensors.nmea0.angle1=20.0 degrees (Longitude), OK
> > > hw.sensors.nmea0.distance0=30.0 m (Altitude), OK
> > > hw.sensors.nmea0.velocity0=0.000 m/s (Ground speed), OK
> > > It works for about two years before like a charm, but now timedelta 619313970.981246 secs.
> > > Tried to change GPS receiver, no effect.
> > > Martin
> >
> > You position is also suspect. Can you run cu on the port the GPS is
> > atteched to and get a snippet of the output?
> >
> > -Otto
>
>

Sigh, you are making troubleshooting this harder than needed by
editing output without saying so. Also, I asked for an NMEA output
log.

Uncomment your ldattach line in /etc/ttys
kill -1 1
cu -l ttyXX -s 4800

(Change speed to match your device). Without log I cannot help.

        -Otto

Reply | Threaded
Open this post in threaded view
|

Re: nmea0 huge timedelta while system clock is in sync

Martin Got
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 sync with NTP pool currently, so it has minimum delta possible.

$GPGGA,194359.00,_coordinates_,.....
$PQXFI,194359.00,_coordinates_,.....
$GNSNS,194359.00,_coordinates_,.....
...
$GPRMC,194359.00,_coordinates_,.....
...
$GPGGA,194400.00,_coordinates_,.....
$PQXFI,194400.00,_coordinates_,.....
$GNSNS,194400.00,_coordinates_,.....
...
$GPRMC,194400.00,_coordinates_,.....

Any way to perform manual 'reset' timedelta to any 'default' value?

Martin

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, March 22, 2020 3:28 PM, Otto Moerbeek <[hidden email]> wrote:

> On Sun, Mar 22, 2020 at 03:22:40PM +0000, 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 system clock was changed significantly to incorrect value. Now ntpd.conf set to NTP pool, but hope I can fix radioclocks.
> > Martin
> > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > On Sunday, March 22, 2020 12:54 PM, Otto Moerbeek [hidden email] wrote:
> >
> > > On Sun, Mar 22, 2020 at 12:19:39PM +0000, 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
> > > > hw.sensors.nmea0.angle1=20.0 degrees (Longitude), OK
> > > > hw.sensors.nmea0.distance0=30.0 m (Altitude), OK
> > > > hw.sensors.nmea0.velocity0=0.000 m/s (Ground speed), OK
> > > > It works for about two years before like a charm, but now timedelta 619313970.981246 secs.
> > > > Tried to change GPS receiver, no effect.
> > > > Martin
> > >
> > > You position is also suspect. Can you run cu on the port the GPS is
> > > atteched to and get a snippet of the output?
> > > -Otto
>
> Sigh, you are making troubleshooting this harder than needed by
> editing output without saying so. Also, I asked for an NMEA output
> log.
>
> Uncomment your ldattach line in /etc/ttys
> kill -1 1
> cu -l ttyXX -s 4800
>
> (Change speed to match your device). Without log I cannot help.
>
> -Otto


Reply | Threaded
Open this post in threaded view
|

Re: nmea0 huge timedelta while system clock is in sync

Martin Got
In reply to this post by Otto Moerbeek
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 <[hidden email]> wrote:

> On Sun, Mar 22, 2020 at 03:22:40PM +0000, 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 system clock was changed significantly to incorrect value. Now ntpd.conf set to NTP pool, but hope I can fix radioclocks.
> > Martin
> > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > On Sunday, March 22, 2020 12:54 PM, Otto Moerbeek [hidden email] wrote:
> >
> > > On Sun, Mar 22, 2020 at 12:19:39PM +0000, 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
> > > > hw.sensors.nmea0.angle1=20.0 degrees (Longitude), OK
> > > > hw.sensors.nmea0.distance0=30.0 m (Altitude), OK
> > > > hw.sensors.nmea0.velocity0=0.000 m/s (Ground speed), OK
> > > > It works for about two years before like a charm, but now timedelta 619313970.981246 secs.
> > > > Tried to change GPS receiver, no effect.
> > > > Martin
> > >
> > > You position is also suspect. Can you run cu on the port the GPS is
> > > atteched to and get a snippet of the output?
> > > -Otto
>
> Sigh, you are making troubleshooting this harder than needed by
> editing output without saying so. Also, I asked for an NMEA output
> log.
>
> Uncomment your ldattach line in /etc/ttys
> kill -1 1
> cu -l ttyXX -s 4800
>
> (Change speed to match your device). Without log I cannot help.
>
> -Otto


Reply | Threaded
Open this post in threaded view
|

Re: nmea0 huge timedelta while system clock is in sync

Otto Moerbeek
In reply to this post by Martin Got
On Sun, Mar 22, 2020 at 08:26:25PM +0000, 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 time data changes every second as it should be. System's time in sync with NTP pool currently, so it has minimum delta possible.
>
> $GPGGA,194359.00,_coordinates_,.....
> $PQXFI,194359.00,_coordinates_,.....
> $GNSNS,194359.00,_coordinates_,.....
> ...
> $GPRMC,194359.00,_coordinates_,.....
> ...
> $GPGGA,194400.00,_coordinates_,.....
> $PQXFI,194400.00,_coordinates_,.....
> $GNSNS,194400.00,_coordinates_,.....
> ...
> $GPRMC,194400.00,_coordinates_,.....
>

Double sigh. The datestamp in the $GPRMC message is important.

But I give up, you are only making things difficult.

        -Otto

> Any way to perform manual 'reset' timedelta to any 'default' value?
>
> Martin
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Sunday, March 22, 2020 3:28 PM, Otto Moerbeek <[hidden email]> wrote:
>
> > On Sun, Mar 22, 2020 at 03:22:40PM +0000, 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 system clock was changed significantly to incorrect value. Now ntpd.conf set to NTP pool, but hope I can fix radioclocks.
> > > Martin
> > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > On Sunday, March 22, 2020 12:54 PM, Otto Moerbeek [hidden email] wrote:
> > >
> > > > On Sun, Mar 22, 2020 at 12:19:39PM +0000, 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
> > > > > hw.sensors.nmea0.angle1=20.0 degrees (Longitude), OK
> > > > > hw.sensors.nmea0.distance0=30.0 m (Altitude), OK
> > > > > hw.sensors.nmea0.velocity0=0.000 m/s (Ground speed), OK
> > > > > It works for about two years before like a charm, but now timedelta 619313970.981246 secs.
> > > > > Tried to change GPS receiver, no effect.
> > > > > Martin
> > > >
> > > > You position is also suspect. Can you run cu on the port the GPS is
> > > > atteched to and get a snippet of the output?
> > > > -Otto
> >
> > Sigh, you are making troubleshooting this harder than needed by
> > editing output without saying so. Also, I asked for an NMEA output
> > log.
> >
> > Uncomment your ldattach line in /etc/ttys
> > kill -1 1
> > cu -l ttyXX -s 4800
> >
> > (Change speed to match your device). Without log I cannot help.
> >
> > -Otto
>
>

Reply | Threaded
Open this post in threaded view
|

Re: nmea0 huge timedelta while system clock is in sync

Martin Got
Still can't find a solution. I'm suspect backup battery.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, March 22, 2020 9:12 PM, Otto Moerbeek <[hidden email]> wrote:

> On Sun, Mar 22, 2020 at 08:26:25PM +0000, 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 time data changes every second as it should be. System's time in sync with NTP pool currently, so it has minimum delta possible.
> > $GPGGA,194359.00,coordinates,.....
> > $PQXFI,194359.00,coordinates,.....
> > $GNSNS,194359.00,coordinates,.....
> > ...
> > $GPRMC,194359.00,coordinates,.....
> > ...
> > $GPGGA,194400.00,coordinates,.....
> > $PQXFI,194400.00,coordinates,.....
> > $GNSNS,194400.00,coordinates,.....
> > ...
> > $GPRMC,194400.00,coordinates,.....
>
> Double sigh. The datestamp in the $GPRMC message is important.
>
> But I give up, you are only making things difficult.
>
> -Otto
>
> > Any way to perform manual 'reset' timedelta to any 'default' value?
> > Martin
> > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > On Sunday, March 22, 2020 3:28 PM, Otto Moerbeek [hidden email] wrote:
> >
> > > On Sun, Mar 22, 2020 at 03:22:40PM +0000, 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 system clock was changed significantly to incorrect value. Now ntpd.conf set to NTP pool, but hope I can fix radioclocks.
> > > > Martin
> > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > On Sunday, March 22, 2020 12:54 PM, Otto Moerbeek [hidden email] wrote:
> > > >
> > > > > On Sun, Mar 22, 2020 at 12:19:39PM +0000, 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
> > > > > > hw.sensors.nmea0.angle1=20.0 degrees (Longitude), OK
> > > > > > hw.sensors.nmea0.distance0=30.0 m (Altitude), OK
> > > > > > hw.sensors.nmea0.velocity0=0.000 m/s (Ground speed), OK
> > > > > > It works for about two years before like a charm, but now timedelta 619313970.981246 secs.
> > > > > > Tried to change GPS receiver, no effect.
> > > > > > Martin
> > > > >
> > > > > You position is also suspect. Can you run cu on the port the GPS is
> > > > > atteched to and get a snippet of the output?
> > > > > -Otto
> > >
> > > Sigh, you are making troubleshooting this harder than needed by
> > > editing output without saying so. Also, I asked for an NMEA output
> > > log.
> > > Uncomment your ldattach line in /etc/ttys
> > > kill -1 1
> > > cu -l ttyXX -s 4800
> > > (Change speed to match your device). Without log I cannot help.
> > > -Otto


Reply | Threaded
Open this post in threaded view
|

Re: nmea0 huge timedelta while system clock is in sync

Theo de Raadt-2
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 <[hidden email]> wrote:

> Still can't find a solution. I'm suspect backup battery.
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Sunday, March 22, 2020 9:12 PM, Otto Moerbeek <[hidden email]> wrote:
>
> > On Sun, Mar 22, 2020 at 08:26:25PM +0000, 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 time data changes every second as it should be. System's time in sync with NTP pool currently, so it has minimum delta possible.
> > > $GPGGA,194359.00,coordinates,.....
> > > $PQXFI,194359.00,coordinates,.....
> > > $GNSNS,194359.00,coordinates,.....
> > > ...
> > > $GPRMC,194359.00,coordinates,.....
> > > ...
> > > $GPGGA,194400.00,coordinates,.....
> > > $PQXFI,194400.00,coordinates,.....
> > > $GNSNS,194400.00,coordinates,.....
> > > ...
> > > $GPRMC,194400.00,coordinates,.....
> >
> > Double sigh. The datestamp in the $GPRMC message is important.
> >
> > But I give up, you are only making things difficult.
> >
> > -Otto
> >
> > > Any way to perform manual 'reset' timedelta to any 'default' value?
> > > Martin
> > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > On Sunday, March 22, 2020 3:28 PM, Otto Moerbeek [hidden email] wrote:
> > >
> > > > On Sun, Mar 22, 2020 at 03:22:40PM +0000, 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 system clock was changed significantly to incorrect value. Now ntpd.conf set to NTP pool, but hope I can fix radioclocks.
> > > > > Martin
> > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > > On Sunday, March 22, 2020 12:54 PM, Otto Moerbeek [hidden email] wrote:
> > > > >
> > > > > > On Sun, Mar 22, 2020 at 12:19:39PM +0000, 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
> > > > > > > hw.sensors.nmea0.angle1=20.0 degrees (Longitude), OK
> > > > > > > hw.sensors.nmea0.distance0=30.0 m (Altitude), OK
> > > > > > > hw.sensors.nmea0.velocity0=0.000 m/s (Ground speed), OK
> > > > > > > It works for about two years before like a charm, but now timedelta 619313970.981246 secs.
> > > > > > > Tried to change GPS receiver, no effect.
> > > > > > > Martin
> > > > > >
> > > > > > You position is also suspect. Can you run cu on the port the GPS is
> > > > > > atteched to and get a snippet of the output?
> > > > > > -Otto
> > > >
> > > > Sigh, you are making troubleshooting this harder than needed by
> > > > editing output without saying so. Also, I asked for an NMEA output
> > > > log.
> > > > Uncomment your ldattach line in /etc/ttys
> > > > kill -1 1
> > > > cu -l ttyXX -s 4800
> > > > (Change speed to match your device). Without log I cannot help.
> > > > -Otto
>
>