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
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 abso
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 s
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
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 system
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
> hw.sensors.nmea
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
7 matches
Mail list logo
