toggle quoted messageShow quoted text
This is not how gpsd works at all. Direwolf works with gpsd regardless of the underlying NMEA sentence format. This is what a gpsd position looks like:
There is no GNGGA, there is no GPGGA. No change is required. Direwolf just works.
On Apr 22, 2019, at 3:27 PM, Basil Gunn <basil@...
Regardless of the format (string, json, xml) all the GPS informationcomes in sentences. If you look at the sentences in what ever format youwill find that the SkyTraq Venus 8 GPS module used on the DRAWS boardoutputs NMEA-0183 V3.01 sentences. The way Tom Russo fixed Xastir heparsed GN sentences as well as the old style GP sentences ie. GNGGA aswell as the older GPGGA sentences. Direwolf needs to do the same or youcan solve your problem in some other way./BasilBrian Badger <brian@...> writes:
Direwolf uses the GPSD wire interface (which is JSON based) not NMEA.
On Apr 22, 2019, at 2:29 PM, Basil Gunn <basil@...> wrote:
Ways to read GPS sentences to verify:
# or kill gpsd
systemctl stop gpsd
cat -v /dev/ttySC0
See answers embedded.
David Lowry <huskyrunnr@...> writes:
From the Direwolf User Guide: Dire Wolf reads NMEA sentences ( $GPRMC
and $GPGGA ) from the receiver and parses them to extract position
Whereas the SkyTraq model we have apparently does not support either
sentence. Please confirm this,
More than likely this is the case because the issue FIXED in Xastir was
Unable to get GPS data from DRAWS hat [because Xastir does not support
GNGGA or GNRMC sentences] #53
I am rushing between teaching classes and I could be mistaken.
Nope you are not mistaken.
I just quickly looked to see if it could be the same problem as with
What exactly do you want to do that you are trying to configure Direwolf
to do? Perhaps I can suggest another way.