Re: [gpsd-users] NAVILOCK NL-402U cgps GPS timeout without fix

[Philipp Seelig]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

propably...

wasn't sure so tried it again:

address@hidden:~# gpsd -n /dev/ttyACM0
address@hidden:~# cgps
cgps: GPS timeout
address@hidden:~#

without any luck as you can see.

I also tried this:

gpsd -F /tmp/gpsd.sock -b -N /dev/ttyACM0
gpsd:ERROR: can't bind to IPv6 port gpsd, Cannot assign requested address
^Z
[1]+  Stopped                 gpsd -F /tmp/gpsd.sock -b -N /dev/ttyACM0
address@hidden:~# bg
[1]+ gpsd -F /tmp/gpsd.sock -b -N /dev/ttyACM0 &
address@hidden:~# cgps
cgps: GPS timeout

and:

address@hidden:~# gpsd -F /tmp/gpsd.sock -b -n /dev/ttyACM0
address@hidden:~# cgps
cgps: GPS timeout

in all cases cat /dev/ttyACM0 shows data

address@hidden:~# cat /dev/ttyACM0
$GPRMC,000731.800,V,0000.0000,N,00000.0000,E,0.00,0.00,060180,,,N*74
$GPVTG,0.00,T,,M,0.00,N,0.0,K,N*02
$GPGGA,000731.800,0000.0000,N,00000.0000,E,0,00,99.9,-17.0,M,17.0,M,,0000*74
$GPGSA,A,1,,,,,,,,,,,,,99.9,99.9,99.9*09
$GPGSV,1,1,00*79
$GPGLL,0000.0000,N,00000.0000,E,000731.800,V,N*4C
$GPRMC,000732.000,V,0000.0000,N,00000.0000,E,0.00,0.00,060180,,,N*7F
$GPVTG,0.00,T,,M,0.00,N,0.0,K,N*02
$GPGGA,000732.000,0000.0000,N,00000.0000,E,0,00,99.9,-17.0,M,17.0,M,,0000*7F
$GPGSA,A,1,,,,,,,,,,,,,99.9,99.9,99.9*09
$GPGSV,1,1,00*79
$GPGLL,0000.0000,N,00000.0000,E,000732.000,V,N*47
$GPRMC,000732.200,V,0000.0000,N,00000.0000,E,0.00,0.00,060180,,,N*7D
$GPVTG,0.00,T,,M,0.00,N,0.0,K,N*02
$GPGGA,000732.200,0000.0000,N,00000.0000,E,0,00,99.9,-17.0,M,17.0,M,,0000*7D
$GPGSA,A,1,,,,,,,,,,,,,99.9,99.9,99.9*09
$GPGSV,1,1,00*79
$GPGLL,0000.0000,N,00000.0000,E,000732.200,V,N*45
$GPRMC,000732.400,V,0000.0000,N,00000.0000,E,0.00,0.00,060180,,,N*7B
$GPVTG,0.00,T,,M,0.00,N,0.0,K,N*02
$GPGGA,000732.400,0000.0000,N,00000.0000,E,0,00,99.9,-17.0,M,17.0,M,,0000*7B
$GPGSA,A,1,,,,,,,,,,,,,99.9,99.9,99.9*09
$GPGSV,1,1,00*79

So the device is present and 'works' (except that it has no fix).

On 19.02.2015 14:47, nick wrote:
> On 19/02/15 12:40, Philipp Seelig wrote:
>> The problem is, as long as the device doesn't have a fix, cgps 
>> gets a timeout (<user>@<machine> ~ % cgps cgps: GPS timeout).
> 
> Did you try gpsd -n <device> ?
> 
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJU7GXSAAoJEKBj+3JQ/lDk5ocIAJ/l4gfxGEfyjf81VdAK7hW8
df/VM8KWqmRn2IKPc7GVzJ56NkiDyJev7MLgTgUnI1b6CmaAibV1CKcIiNo8nbWz
GQmPPbco1Kum38KIkemPRfYv7QeIH+rWPZNcoquBNcnhbi60vU0GnZC0QCH1McCA
4inHVdE3AZLUIM6krf/iBBcQCpl1wb1IBniB7sx25x204rMvWmX2jf+dFXf02tOs
GfTZwDqu6GG2BqiSOor/KmCB12x24nd8n7FsavFXWStvGgrcDHUYXXsQfPu6q+pv
QLojE1fUuhwukyL2vdo0OxZ2WHIqNRik54y7YovDpm2fMeBH6EjcAD3X3/YWruY=
=HJxV
-----END PGP SIGNATURE-----