Neil Jerram <[email protected]> writes:
> Is "-r" definitely the right one to use? "gpspipe -r" gives me:
>
> =============
> root@om-gta02 ~ # gpspipe -r
> netlib_connectsock() returns socket on fd 3
> GPSD,W=1,A=42.875,T=169.7809,C=1.00,E=5.22 3.12 4.18,N=0,A=42.875,B=?,L=3 0.8
> abcdefgijklmnopqrstuvwxyz,E=5.22 3.12 4.18,T=169.7809,R=1,U=0.000,E=5.22 3.12
> 4.18,N=0,M=3,E=5.22 3.12 4.18,A=42.875,T=169.7809,R=0,U=0.000,E=5.22 3.12 4.18
> GPSD,O=- 1296502099.000 ? 51.530356 -0.115981 42.89 3.12 4.18 169.7809 0.590
> 0.000 ? ? ? 3
> GPSD,O=- 1296502099.000 ? 51.530356 -0.115981 42.89 3.12 4.18 177.3715 0.550
> 0.000 ? ? ? 3
> GPSD,O=- 1296502100.000 ? 51.530356 -0.115981 42.89 3.12 4.18 177.3715 0.550
> 0.000 ? ? ? 3
> GPSD,Y=- 1296502100.000 11:28 45 121 0 0:15 29 287 0 0:26 71 299 24 1:5 54
> 194 27 1:7 22 59 29 1:8 56 60 27 1:21 17 307 0 0:10 16 159 0 0:19 5 37 0 0:3
> 1 9 0 0:27 18 237 19 1:
> =============
I'm pretty sure this is the problem. "gpspipe -r" is supposed to
generate NMEA data, and I guess that normally happens by
- gpspipe telling gpsd the format that it wants
- gpsd generating output in that format.
The problem then would be fso-gpsd not taking any notice of the initial
format instruction.
I wonder - as an alternative to the option of trying to install and use
gpsd - if it would be trivial to write a program (e.g. in Python) to
convert from the GPDS format above to the NMEA format.
Regards,
Neil
_______________________________________________
Shr-User mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-user
