[Top][All Lists]

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

Re: gpsd + ubx

From: Florian Kiera
Subject: Re: gpsd + ubx
Date: Wed, 27 May 2020 13:58:18 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.1

Yo Gary!

Am 26.05.20 um 19:21 schrieb Gary E. Miller:
Yo Florian!

On Tue, 26 May 2020 17:50:58 +0200
Florian Kiera<address@hidden>  wrote:

Thinking about it: May gpsd prepares the u-blox device to work with
ubxtool whenever I execute "ubxtool" (like it does on starting
Strange that "gpsd -n /dev/ttyACM0 -D 5 -N" gives output about
sending messages to the M8P whenever "ubxtool" is started (gpsd
doesn't care what ubxtool wants to do, just executing ubxtool will
make gpsd send "prepare"/change settings messages). I am still using
my M8P's tho.
I'd like to see you log of that.

ubxtool_call.txt: gpsd output when ubxtool is called (gpsd -n /dev/ttyACM0 -N -D 5) ubx.txt is the cut out of ubxtool_call.txt line 90 and exspecially this message does something, I'd say gpsd shouldn't do. It changes the output to UBX only.

cat ubx.txt (originally no spaces)
b56206001400 03 00 00 00 d0 08 00 00 80 25 00 00 27 00 01 00 00 00 00 00 c2d1

ubxtool -r -f ubx.txt quits without any response sadly... decoding it by hand:
head: b562
class: 06 (CFG)
id: 00 (PRT)
length: 14
offset: 00
port: 03 (USB)
reserved1: 00
txReady: 00 00
mode: d0 08 00 00
baudrate: 80 25 00 00
inProtoMask: 27 00 (UBX+RTCM2+RTCM3+NMEA)
outProtoMask: 01 00 (UBX)
flags: 00 00
reserved2: 00 00 00

Also quiet interesting that gpsd says the hex string is 14 bytes long while its 20 long (20 is also right following the ubx doc)

You can use the new -p option to gpsd to have it not autoconfigure your
Updated to latest gitlab (gpsd-p.txt line 265-266): --passive doesn't seem to work. Still sends hex messages to the ubx-device (gpsd-p.txt line 136-166) executed "gpsd -n /dev/ttyACM0 --passive -N -D 5". Executing "gpsd -n -p /dev/ttyACM0 -N -D 5" doesn't work: option p unknown. (gpsd-p.txt line 198-264)
Without seeing your -p STATUS -p CONFIG I do not know if you have what you
think you have.

which works fine except the part it still returns fix.status = 2...
Without seeing the logs of the rover, no way to know.

base-conf.txt: Base M8P config
base-status.txt: Base M8P status
rover-conf.txt: Rover M8P config
rover-status.txt: Rover M8P status

ubxtool.patch: contains the additions I made
Which means there are things you are not telling me, that could
also contain errors.  I can't guess.

What do you mean? The file contains all changes I made to ubxtool (added TMODE3 and RTCM3). Attachment?

Regards Florian

Attachment: base-conf.txt
Description: Text document

Attachment: rover-conf.txt
Description: Text document

Attachment: rover-status.txt
Description: Text document

Attachment: base-status.txt
Description: Text document

Attachment: ubxtool_call.txt
Description: Text document

reply via email to

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