gpsd-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gpsd-users] PPS problem with u-blox 8


From: Christian Rossi
Subject: Re: [gpsd-users] PPS problem with u-blox 8
Date: Fri, 24 Nov 2017 13:52:15 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0

Hello Gary,

  Any other problems?

With GPS receiver for timing it's possible to use a fixed position to increase the precision. With the receiver I use it is only possible to use a fixed altitude.

So with cgps and a fixed altitude there is "Altitude: n/a" with the ublox data and a blinking altitude with the NMEA data (the altitude and N/A).

And with gegps there is no altitude and an error:

% gegps
Traceback (most recent call last):
  File "gegps", line 101, in <module>
    f.write(kmlize(report))
  File "gegps", line 56, in kmlize
    altitude = tpv['alt']
  File "client.py", line 231, in __getitem__
    return self.__dict__[key]
KeyError: 'alt'
%

This is not really a problem for timing but it's link with timing application.

Regards

--
Christian





reply via email to

[Prev in Thread] Current Thread [Next in Thread]