| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Which bumps the JSON minor rev.
|
|
|
|
|
|
| |
The rawdata_t structure was written into, but never read from. So
a change to it is low impact. Reorder it to simplify pointer
arithmetic. In preparation for more changes.
|
| |
|
| |
|
|
|
|
|
| |
The u-blox 9 tracks 120 signals. That is all the satellites in all
the constellations, plus all the signals from each satellite.
|
|
|
|
| |
Get all these binary changes in at once. mtime not used yet.
|
|
|
|
|
|
|
| |
Both u-blox 9 and NMEA 4.1 no longer use PRN. They refer
to each satellite signal by gnssid:svid:sigid.
No decodes yet for the new feild.
|
| |
|
| |
|
|
|
|
|
| |
This macro was wrong, and causing valid sats to not be included in
the COP calculations.
|
|
|
|
|
| |
GPS_PRN(), GBAS_PRN() and GNSS_PRN() were wishful thinking
and enver used.
|
|
|
|
|
|
|
| |
INCOMPATIBLE CHANGE!
No two GPS encode PRN the same way, so be more explicit about
constellation and PRN within the constellation.
|
|
|
|
|
|
| |
The navcom driver could overflow subtype. This is an incompatible
change to the size of devconfig_t. But API version already changed
this dev cycle.
|
|
|
|
|
| |
This showed up a bug where rtcm3_unpack() was not clearing its
rtcm3 data, which is a union with the attitude data.
|
|
|
|
|
|
| |
This is to prevent a conflict with Boost version 1.67.
No functional change.
|
|
|
|
| |
New ?DEVICE:{"hexdata":"data" option.
|
|
|
|
|
|
|
| |
Now pass an optional message buffer to gps_read(). Finally
the JSON display in cgps works.
Thanks to Virgin Orbit for their support fixing this bug.
|
|
|
|
| |
Signed-off-by: Gary E. Miller <gem@rellim.com>
|
| |
|
| |
|
|
|
|
| |
Gotta check each value for isfinite() anyway.
|
|
|
|
| |
More work to do so cgps, xgps, etc. see the new data.
|
|
|
|
|
|
|
|
| |
Time to stop throwing away the ecef data from GPS devices. u-blox
sends ECEF date to mm precision.
Major API change as this moves things down in gps_data_t
Until this works end to end, don't expect the API to be binary stable.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was causing problems in sign extension.
On amd64/Gentoo sign was extended:
(unsigned int)(char 0x80) became: 0xfffffff80
But on Pi2/Wheezy the same thing became: 0x80.
The obvious fix is to make it unsigned, as god intended.
All regression tests pass on pi2/wheezzy and amd64/gentoo.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Testing maskaudit.py with Python 3 revealed that two comments in gps.h
(lines 285 and 294) were using non-ASCII minus signs in the comments.
This resulted in exceptions with Python >=3.3 and LANG unset. Since
there's no intention to actually use non-ASCII characters here, it
doesn't seem worthwhile to fix the code.
TESTED:
Using a version of SConstruct patched to use the target Python for
build helpers, ran "scons build-all" with all six supported Python
versions.
|
| |
|
|
|
|
| |
Signed-off-by: Michael Brown <mbrown@fensystems.co.uk>
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
That is where the JSON read wwould put the data.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The proximate cause was that we've been seing emission of error
messages that were randomly and disturbingly variable across different
environments - notably Raspbian and Gentoo splint gave nontrivially
different results than Ubuntu 14.10 splint. And this was *not* due to
Ubuntu patches! A pristine splint built from the 3.1.2 tarball on
Ubuntu didn't match the Raspbian and Gentoo results either.
But this has been coming for a while. Easy access to more modern
static analyzers such as coverity, scan-build and cppcheck has been
decreasing the utility of splint, which is unmaintained and somewhat
buggy and not easy to use.
Only file not cleaned is ppsthread.c, because Gary has been working
on it during this cleanup.
All regression tests pass. PPS observed live on GR601-W.
|
| |
|
| |
|
|
|
|
|
|
|
| |
All knowledge of the ntpd SHM format is now confined to the three
files ntpshm.h, ntpshmread.c, and ntpshmwrite.c.
No logic changes. All regression tests pass. PPS works on GR-601W.
|
|
|
|
|
|
|
|
|
|
|
| |
This change removes some macros which assured both source and object
compatibility with client API version 6.0 in spite of some internal
renames.
But it turns out the gps.h we shipped had a broken inclusion and would
have blown up any compile if it was used from /usr/include, anyway.
So nobody can have built with the changed names and we can remove
this cruft.
|
|
|
|
|
|
|
| |
It's bad that this get past me. Anybody who tries writing a C client
with 3.12 is going to lose. Requires a release to fix.
All regression tests pass.
|
|
|
|
|
|
| |
All regression tests pass. PPS observed live with gosmon.
gpsmon presently ignores this message, but shout display its contents near PPS.
|
|
|
|
| |
No logic changes. All regression tesrs pass. Live PPS observed.
|
|
|
|
|
| |
All regression tests pass. Clients are working live. PPS observed on Macx-1.
|
|
|
|
|
|
|
|
| |
Also, use PPSDRIFT_SET as a client-side status flag for JSON PPS rather
than the (not yet shipped) TIMEDRIFT_SET. Next release we're probably
going to add a drift object for in-line time.
No logic changes. All regression tests pass.
|
| |
|
|
|
|
| |
All regression tests pass.
|
| |
|
|
|
|
|
| |
Converting a timespec to a printable string is odd, so
placed in a new function for ease of use.
|