Re: [gpsd-users] Getting data from U-Blox 6 receiver (native or NMEA protocol)

[Askar Ibragimov]

Hello,

So, I had to fight with u-blox a but, becase it for some reason did not saved the configuration. But I managed to set it up and confirm so that it sends NMEA at certain bit rate:

address@hidden ~]# stty -F /dev/ttyUSB0 ispeed 57600
address@hidden ~]# cat /dev/ttyUSB0 
$GPRMC,191317.00,A,6013.99471,N,02443.49086,E,0.092,,210415,,,A*70
$GPVTG,,T,,M,0.092,N,0.170,K,A*2E
$GPGGA,191317.00,6013.99471,N,02443.49086,E,1,07,1.38,43.3,M,17.8,M,,*63
$GPGSA,A,3,29,02,31,21,05,20,16,,,,,,2.90,1.38,2.55*09
$GPGSV,2,1,07,02,14,053,29,05,33,077,45,16,20,306,26,20,28,053,40*7D
$GPGSV,2,2,07,21,43,198,36,29,64,100,43,31,27,235,33*43
$GPGLL,6013.99471,N,02443.49086,E,191317.00,A,A*61
$GPZDA,191317.00,21,04,2015,00,00*6B
$GPRMC,191318.00,A,6013.99474,N,02443.49081,E,0.093,,210415,,,A*7C
$GPVTG,,T,,M,0.093,N,0.173,K,A*2C
$GPGGA,191318.00,6013.99474,N,02443.49081,E,1,07,1.38,43.2,M,17.8,M,,*6F
$GPGSA,A,3,29,02,31,21,05,20,16,,,,,,2.90,1.38,2.55*09
$GPGSV,2,1,07,02,14,053,29,05,33,077,44,16,20,306,26,20,28,053,40*7C
$GPGSV,2,2,07,21,43,198,36,29,64,100,43,31,27,235,33*43
$GPGLL,6013.99474,N,02443.49081,E,191318.00,A,A*6C
$GPZDA,191318.00,21,04,2015,00,00*64
^C 

Then I run gps 3.14 (that I managed to get compiled on my system after commenting out in SConfigure file offending lines) and the log is attached. Parameters were gpsd -N -D 6 /dev/ttyUSB0.  In short, some "kind of hooking" happens, but then gpsd for some reason moves on to different setups. Also, it circles just across three drivers, not all the list, and UBlox is not mentioned at all.

Best, Askar

2015-04-18 18:26 GMT+03:00 Eric S. Raymond <address@hidden>:

Askar Ibragimov <address@hidden>:
> I am trying to run gpsd 3.11 to work with U-Blox 6 receiver. I noticed that
> gpsd should work with Ublox native protocol. I run gpsd -N -D 6 so I can
> see what protocols it scans. For some reason, I see a circle across three
> protocols, nmea, garmin and trimble, and obviously nothing happens.
>
> How I can tell gpsd 3.11 that it should attempt using ublox protocol?

You're not expected to have to.  It automatically syncs to uBlox packets.
This is something I test frequently because the GPS I use for experimeing PPS
is uBlox-6-based.

gpsd is designed to autoconfigure itself based on what comes over the
wire. The right question to ask is not "how do I tell it", but why
it's losing packet lock in your environment.  Can you mail us a -D 6
log illustrating the cycling?

> Ublox can be set to NMEA of course (which I do using windows utility), but
> for some reason it can not "capture" properly NMEA protocol. So any help is
> appreciated in getting in touch with receiver.

That is an even weirder report. I'd like to see a log of this "not capturing"
behavior.
--
                <a href="" href="http://www.catb.org/~esr/" target="_blank">http://www.catb.org/~esr/">Eric S. Raymond</a>

gpsd314.log
Description: Binary data