Re: [gpsd-users] Ublox EVK-M8T

[John Klug]

Before we start the commands, we are at 9600 baud/NMEA, which is the default on 
our hardware.

It winds up in U-Blox mode at 115200.  I have not tried to analyze why this 
works.

All I know is I could not prevent it from switching back to 9600 baud (the 
default) without using the two steps, plus the stty to set the baud on the 
line.  Maybe the -T2 prevents NMEA from being set?

We always do this before starting gpsd, and gpsd is always in U-Blox mode after 
this.

The gpsd options we use are -n -D 1

git dot multitech dot 
net/cgi-bin/cgit.cgi/meta-mlinux.git/tree/recipes-navigation/gpsd/gpsd/gpsd

git dot multitech dot 
net/cgi-bin/cgit.cgi/meta-mlinux.git/tree/recipes-navigation/gpsd/gpsd/gpsd-default


John Klug
Senior Software Engineer

From: Denny Page address@hidden
Sent: Tuesday, September 19, 2017 3:34 PM
To: John Klug
Cc: address@hidden; address@hidden
Subject: Re: [gpsd-users] Ublox EVK-M8T

> On Sep 19, 2017, at 07:46, John Klug <address@hidden> wrote:
>
> gpsctl -t 'u-blox' -s $GPS_BAUD -b  -f $GPS_LINE
> gpsctl -T 2 -f $GPS_LINE
> stty -F $GPS_LINE $GPS_BAUD

John,

I’m confused regarding the intent of the second gpsctl…

If the baud rate on the port (and unit) is originally at a rate of 115200, then 
the second gpsctl will succeed and reset the unit to NMEA mode.

If the baud rate on the port (and unit) is originally at a rate of other than 
115200, say 9600, then the second gpsctl will sends and receive some garbage 
bits, and then time out. But what is the actual effect on the port or the unit?

Thanks,
Denny