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 <[email protected]> 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
