BT GPS

[aardelean]

Hi,

I am trying to connect to a bluetooth GPS, but all attempts are
unsuccessful.
I have followed steps indicated at http://gpsd.berlios.de/bt.html as much as
possible (configuration steps 1-7)
but telnet step does not return any data from GPS

~$ hcitool scan
Scanning ...
    00:0D:B5:31:4A:44    BT-GPS-314A44


~$ telnet localhost 2947
Trying ::1...
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
#and after good seconds last message
Connection closed by foreign host.

I am on the new eeebuntu 3 / Asus 1000H eeepc.  Could somebody please give
me a hint on what to try more to make it work. I am keen to see it working
because I would like in the end to call it with php and integrate in an
browser application. Shall I look for a USB GPS instead?

Thank you,
Adi
_______________________________________________
Gpsd-users mailing list
Gpsd-users@...
https://lists.berlios.de/mailman/listinfo/gpsd-users

[aardelean]

Hi again,

In the end I have managed to read BT GPS data.

Very helpful for this was this blog material:
http://blogs.srijan.in/2008/01/19/bluetooth-gps-devices-with-linux/#hcid.conf
for some reason in my eeebuntu installation /etc/bluetooth/hcid.conf was
empty. a copy and paste and a pin edit solved the probelm.

Now following php examples  I can output DD coordinates. However, I noticed
that altitude is most of times 95%  A=nan.

GPSD,S=1,P=45.722106700 21.170223200,A=nan,M=3,Q=10 0.00 0.80 1.30 1.97
3.54,Y=MID4 1244022657.990 10:8 25 205 21 1:7 63 187 20 1:20 16 133 15 1:13
72 28 35 1:16 18 48 18 1:25 79 117 29 1:4 38 238 12 1:10 7 307 33 1:23 40 70
31 1:2 33 286 34 1:

I have used the same BT GPS on a mobile phone with Symbian and pyS60 and
parsing $GPGCA sentences always returns altitude values. I would like to
know if it is a way to make gpsd return altitude values from GPGCA or other
similar GPS NMEA sentences.

All the best,
Adi


Hi,

>
> I am trying to connect to a bluetooth GPS, but all attempts are
> unsuccessful.
> I have followed steps indicated at http://gpsd.berlios.de/bt.html as much
> as possible (configuration steps 1-7)
> but telnet step does not return any data from GPS
>
> ~$ hcitool scan
> Scanning ...
>     00:0D:B5:31:4A:44    BT-GPS-314A44
>
>
> ~$ telnet localhost 2947
> Trying ::1...
> Trying 127.0.0.1...
> Connected to localhost.
> Escape character is '^]'.
> #and after good seconds last message
> Connection closed by foreign host.
>
> I am on the new eeebuntu 3 / Asus 1000H eeepc.  Could somebody please give
> me a hint on what to try more to make it work. I am keen to see it working
> because I would like in the end to call it with php and integrate in an
> browser application. Shall I look for a USB GPS instead?
>
>
>

_______________________________________________
Gpsd-users mailing list
Gpsd-users@...
https://lists.berlios.de/mailman/listinfo/gpsd-users

[Eric S. Raymond-2]

Adorian Ardelean <mynature@...>:
> I am on the new eeebuntu 3 / Asus 1000H eeepc.  Could somebody please give
> me a hint on what to try more to make it work. I am keen to see it working
> because I would like in the end to call it with php and integrate in an
> browser application. Shall I look for a USB GPS instead?

You should probably look for a USB GPS.  Bluetooth networking is almost
unbelievably nasty at a low level; support for it is difficult to write
and difficult to test.  We're working on it, but it is likely to be flaky
for a couple of releases yet.
--
                <a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
_______________________________________________
Gpsd-users mailing list
Gpsd-users@...
https://lists.berlios.de/mailman/listinfo/gpsd-users

[Eric S. Raymond-2]

Adorian Ardelean <mynature@...>:
> In the end I have managed to read BT GPS data.
>
> Very helpful for this was this blog material:
> http://blogs.srijan.in/2008/01/19/bluetooth-gps-devices-with-linux/#hcid.conf
> for some reason in my eeebuntu installation /etc/bluetooth/hcid.conf was
> empty. a copy and paste and a pin edit solved the probelm.

That's herpful.  I've asked Lukasz Stelmach to revise our Bluetooth recipe
in light of that page.
 

> Now following php examples  I can output DD coordinates. However, I noticed
> that altitude is most of times 95%  A=nan.
>
> GPSD,S=1,P=45.722106700 21.170223200,A=nan,M=3,Q=10 0.00 0.80 1.30 1.97
> 3.54,Y=MID4 1244022657.990 10:8 25 205 21 1:7 63 187 20 1:20 16 133 15 1:13
> 72 28 35 1:16 18 48 18 1:25 79 117 29 1:4 38 238 12 1:10 7 307 33 1:23 40 70
> 31 1:2 33 286 34 1:
>
> I have used the same BT GPS on a mobile phone with Symbian and pyS60 and
> parsing $GPGCA sentences always returns altitude values. I would like to
> know if it is a way to make gpsd return altitude values from GPGCA or other
> similar GPS NMEA sentences.

Do you mean the $GPGGA sentence?  If so, gpsd should already get altitude,
and does on all my test devices and Chris's. There might be some firmware
problem with your specific device.  If you send me a dump of typical output
I might be able to diagnose this.
--
                <a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
_______________________________________________
Gpsd-users mailing list
Gpsd-users@...
https://lists.berlios.de/mailman/listinfo/gpsd-users

[aardelean]

Hi Eric,

Yes. Altitude is there but in 95% case it is not. I get most of times A=nan.
Experience with pyS60 tells me that it should be there most of times. I am
not sure what command to use for generating the dump. However, below you can
see what php reads from socket following a php example presented  in gpsd
source archive:

GPSD,S=1,P=45.722103900 21.170215600,A=nan,M=3,Q=6 0.00 1.80 1.30 1.97
3.54,Y=GND 1244029194.000 8:8 75 243 28 1:10 49 295 33 1:7 60 52 31 1:24 12
315 24 0:13 33 93 20 1:2 12 237 15 1:25 38 57 23 1:3 6 54 0 0:

GPSD,S=1,P=45.722096689 21.170235009,A=87.750,M=3,Q=6 0.00 1.80 1.30 1.97
3.54,Y=MID2 1244029260.000 7:8 76 243 30 1:10 50 295 32 1:7 59 52 28 1:24 12
313 26 0:13 33 93 18 1:2 12 237 16 1:25 38 57 20 1:

GPSD,S=1,P=45.722079300 21.170251300,A=nan,M=3,Q=6 0.00 1.80 1.30 1.97
3.54,Y=GND 1244029277.000 8:8 76 244 27 1:10 50 294 29 1:7 59 52 27 1:24 12
313 26 0:13 33 93 16 1:2 11 237 15 1:25 37 57 16 1:3 6 54 0 0:

Alternatively:
gpspipe -r returns something like rows below:
GPSD,R=1
$GPGGA,204552,4543.3235,N,02110.2145,E,1,06,1.80,,38.318,M,,*36
$GPRMC,000000,A,4543.3235,N,02110.2145,E,0.0000,0.000,000000,,*2C
$GPGSA,A,3,08,10,07,25,13,02,,,,,,,0.0,1.8,1.3*30
$PGRME,1.16,M,1.25,M,0.00,M*1E
$GPGGA,114227,4543.3235,N,02110.2142,E,1,06,1.80,98.85,M,38.318,M,,*75
$GPRMC,114227,A,4543.3235,N,02110.2142,E,2.7590,9.923,030609,,*2C
$GPGSA,A,3,08,10,07,25,13,02,,,,,,,0.0,1.8,1.3*30
$GPGGA,204552,4543.3240,N,02110.2145,E,1,06,2.40,,38.318,M,,*3B
$GPRMC,000000,A,4543.3240,N,02110.2145,E,0.0000,0.000,000000,,*2E
$GPGSA,A,3,08,10,07,25,13,02,,,,,,,0.0,2.4,1.3*3F
$PGRME,1.19,M,1.27,M,0.00,M*13
$GPGSV,3,1,09,08,76,244,25,10,50,294,29,07,58,052,28,24,12,313,23*7C
$GPGSV,3,2,09,13,32,094,14,02,11,237,15,25,37,057,24,03,06,052,16*78
$GPGSV,3,3,09,28,26,169,15*44
$GPGGA,114228,4543.3239,N,02110.2142,E,1,05,2.40,99.56,M,38.318,M,,*75
$GPRMC,114228,A,4543.3239,N,02110.2142,E,1.1372,350.386,030609,,*2A
$GPGSA,A,3,08,10,07,25,02,,,,,,,,0.0,2.4,1.3*3D
$GPGGA,204552,4543.3241,N,02110.2146,E,1,05,1.80,,38.318,M,,*35
$GPRMC,000000,A,4543.3241,N,02110.2146,E,0.0000,0.000,000000,,*2C
$GPGSA,A,3,08,10,07,25,02,,,,,,,,0.0,1.8,1.3*32
$PGRME,1.22,M,1.29,M,0.00,M*15
$GPGGA,114229,4543.3239,N,02110.2142,E,1,06,1.80,99.56,M,38.318,M,,*78
$GPRMC,114229,A,4543.3239,N,02110.2142,E,1.2938,337.061,030609,,*27
$GPGSA,A,3,08,10,07,25,13,02,,,,,,,0.0,1.8,1.3*30
$GPGGA,204552,4543.3244,N,02110.2146,E,1,06,2.40,,38.318,M,,*3C
$GPRMC,000000,A,4543.3244,N,02110.2146,E,0.0000,0.000,000000,,*29
$GPGSA,A,3,08,10,07,25,13,02,,,,,,,0.0,2.4,1.3*3F
$PGRME,1.23,M,1.31,M,0.00,M*1D
$GPGGA,114230,4543.3243,N,02110.2142,E,1,05,2.40,100.28,M,38.318,M,,*49
$GPRMC,114230,A,4543.3243,N,02110.2142,E,1.3982,1.503,030609,,*25
$GPGSA,A,3,08,10,07,13,02,,,,,,,,0.0,2.4,1.3*38
$GPGGA,204552,4543.3248,N,02110.2146,E,1,05,2.40,,38.318,M,,*33
$GPRMC,000000,A,4543.3248,N,02110.2146,E,0.0000,0.000,000000,,*25
$GPGSA,A,3,08,10,07,13,02,,,,,,,,0.0,2.4,1.3*38
$PGRME,1.25,M,1.32,M,0.00,M*18
$GPGGA,114231,4543.3247,N,02110.2142,E,1,05,2.40,101.00,M,38.318,M,,*47
$GPRMC,114231,A,4543.3247,N,02110.2142,E,1.7953,356.738,030609,,*23
$GPGSA,A,3,08,10,07,13,02,,,,,,,,0.0,2.4,1.3*38
$GPGGA,204552,4543.3253,N,02110.2143,E,1,05,2.40,,38.318,M,,*3C
$GPRMC,000000,A,4543.3253,N,02110.2143,E,0.0000,0.000,000000,,*2A
$GPGSA,A,3,08,10,07,13,02,,,,,,,,0.0,2.4,1.3*38
$PGRME,1.26,M,1.34,M,0.00,M*1D
$GPGGA,114232,4543.3250,N,02110.2142,E,1,05,2.40,101.71,M,38.318,M,,*44
$GPRMC,114232,A,4543.3250,N,02110.2142,E,1.5677,1.340,030609,,*27
$GPGSA,A,3,08,10,07,13,02,,,,,,,,0.0,2.4,1.3*38
$GPGGA,204552,4543.3258,N,02110.2138,E,1,05,2.40,,38.318,M,,*3B
$GPRMC,000000,A,4543.3258,N,02110.2138,E,0.0000,0.000,000000,,*2D
$GPGSA,A,3,08,10,07,13,02,,,,,,,,0.0,2.4,1.3*38
$PGRME,1.27,M,1.36,M,0.00,M*1E
$GPGSV,2,1,08,08,76,244,26,10,50,294,29,07,58,052,27,24,12,313,23*70
$GPGSV,2,2,08,13,32,094,12,02,11,237,15,03,06,052,15,28,26,169,15*7E
$GPGGA,114233,4543.3259,N,02110.2135,E,1,05,2.40,102.89,M,38.318,M,,*48
$GPRMC,114233,A,4543.3259,N,02110.2135,E,0.7167,268.261,030609,,*25
$GPGSA,A,3,08,10,07,13,02,,,,,,,,0.0,2.4,1.3*38
$GPGGA,204552,4543.3256,N,02110.2136,E,1,05,2.80,,38.318,M,,*37


Maybe this gives a hint. if not please tell me other gpsd command to run so
you get the right information.

All the best,
Adi


On Wed, Jun 3, 2009 at 2:15 PM, Eric S. Raymond <esr@...> wrote:

> Adorian Ardelean <mynature@...>:
> > In the end I have managed to read BT GPS data.
> >
> > Very helpful for this was this blog material:
> >
> http://blogs.srijan.in/2008/01/19/bluetooth-gps-devices-with-linux/#hcid.conf
> > for some reason in my eeebuntu installation /etc/bluetooth/hcid.conf was
> > empty. a copy and paste and a pin edit solved the probelm.
>
> That's herpful.  I've asked Lukasz Stelmach to revise our Bluetooth recipe
> in light of that page.
>
> > Now following php examples  I can output DD coordinates. However, I
> noticed
> > that altitude is most of times 95%  A=nan.
> >
> > GPSD,S=1,P=45.722106700 21.170223200,A=nan,M=3,Q=10 0.00 0.80 1.30 1.97
> > 3.54,Y=MID4 1244022657.990 10:8 25 205 21 1:7 63 187 20 1:20 16 133 15
> 1:13
> > 72 28 35 1:16 18 48 18 1:25 79 117 29 1:4 38 238 12 1:10 7 307 33 1:23 40
> 70
> > 31 1:2 33 286 34 1:
> >
> > I have used the same BT GPS on a mobile phone with Symbian and pyS60 and
> > parsing $GPGCA sentences always returns altitude values. I would like to
> > know if it is a way to make gpsd return altitude values from GPGCA or
> other
> > similar GPS NMEA sentences.
>
> Do you mean the $GPGGA sentence?  If so, gpsd should already get altitude,
> and does on all my test devices and Chris's. There might be some firmware
> problem with your specific device.  If you send me a dump of typical output
> I might be able to diagnose this.
> --
>                <a href="http://www.catb.org/~esr/<http://www.catb.org/%7Eesr/>">Eric
> S. Raymond</a>
>

_______________________________________________
Gpsd-users mailing list
Gpsd-users@...
https://lists.berlios.de/mailman/listinfo/gpsd-users

[Eric S. Raymond-2]

Adorian Ardelean <mynature@...>:
> Yes. Altitude is there but in 95% case it is not. I get most of times A=nan.
> Experience with pyS60 tells me that it should be there most of times.

While working on the implementation of the new protocol, I found a subtle
bug in the fix buffering logic that may exclain this.  Please try svn
head and see if the problem recurs.
--
                <a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
_______________________________________________
Gpsd-users mailing list
Gpsd-users@...
https://lists.berlios.de/mailman/listinfo/gpsd-users

[hamish_b]

Adorian:
> > Yes. Altitude is there but in 95% case it is not. I get most of
> > times A=nan. Experience with pyS60 tells me that it should be there
> most of times.

Eric:
> While working on the implementation of the new protocol, I found a
> subtle bug in the fix buffering logic that may exclain this.

FWIW I had been seeing something similar with my BU-353 USB puck (SiRF).
.... but only when cgps reset it into SiRF binary mode (without asking I
might add. !@$?@#%!). In NMEA mode I always got a good number for altitude.
See mailing list archive for details. This was a number of releases back
and I haven't tried SiRF mode since.


Hamish


     

_______________________________________________
Gpsd-users mailing list
Gpsd-users@...
https://lists.berlios.de/mailman/listinfo/gpsd-users

[Paul Fox-3]

hamish wrote:
 > Eric:
 > > While working on the implementation of the new protocol, I found a
 > > subtle bug in the fix buffering logic that may exclain this.
 >
 > FWIW I had been seeing something similar with my BU-353 USB puck (SiRF).
 > .... but only when cgps reset it into SiRF binary mode (without asking I
 > might add. !@$?@#%!). In NMEA mode I always got a good number for altitude.

from what i've gathered, it seems to be difficult to keep a sirf
chipset in NMEA mode.  at least, somewhere in the gpsd source
there's a comment to the effect that it switches as a side-effect
of the probe operation.  so i think what happens is that if you
get it set to NMEA, and then for some reason gpsd has to rediscover
the device, it will switch back.  perhaps chris can comment on this.
(if this is true, it might be a good reason to keep the -f option,
in order to allow skipping the probe step on such devices.)

paul
=---------------------
 paul fox, pgf@... (arlington, ma, where it's 57.4 degrees)
_______________________________________________
Gpsd-users mailing list
Gpsd-users@...
https://lists.berlios.de/mailman/listinfo/gpsd-users