BU-303 Issues with 2.40dev

[Michael R. Davis]

GPSD Folks,
Over the weekend my gpsd on a BU-303 just stopped working.  I started the process on Oct 20th and it quit shipping data out the TCP Port at 1257084397 (Sun, 1 Nov 2009 14:06:37 UTC).  I guess I need to start logging.  Is there any good documentation on logging for very long periods?

In the past, the two other failures where coincident with changing the device driver.  But, not this time.

$ telnet localhost 2947
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.
{"class":"VERSION","release":"2.40dev","rev":"$Id: gpsd_json.c 6377 2009-10-01 23:24:21Z esr $","proto_major":3,"proto_minor":1}
?DEVICES;
{"class":"DEVICES","devices":[{"class":"DEVICE","path":"/dev/ttyUSB0","activated":1257084408.46,"flags":1,"driver":"SiRF binary","native":1,"bps":4800,"parity":"N","stopbits":1,"cycle":1.00}]}

None of "R", "W" nor "?WATCH={"enable":true};" worked with another session.

One interesting note is that "activated" = 1257084408.46 (Sun, 1 Nov 2009 14:06:48 UTC) is *after* our failure time.

I start my GPSD from init with "-n -F $CONTROL_SOCKET -P $PIDFILE".  I'm going to add in the -b flag and start running again.

I'm up and running again.  gpsctl could not get the device working again but gpsmon could.
Mike (mrdvt92)


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

[Eric S. Raymond-2]

Michael R. Davis <mrdvt92@...>:

> GPSD Folks,
> Over the weekend my gpsd on a BU-303 just stopped working.  I started the process on Oct 20th and it quit shipping data out the TCP Port at 1257084397 (Sun, 1 Nov 2009 14:06:37 UTC).  I guess I need to start logging.  Is there any good documentation on logging for very long periods?
>
> In the past, the two other failures where coincident with changing the device driver.  But, not this time.
>
> $ telnet localhost 2947
> Trying 127.0.0.1...
> Connected to localhost.localdomain (127.0.0.1).
> Escape character is '^]'.
> {"class":"VERSION","release":"2.40dev","rev":"$Id: gpsd_json.c 6377 2009-10-01 23:24:21Z esr $","proto_major":3,"proto_minor":1}
> ?DEVICES;
> {"class":"DEVICES","devices":[{"class":"DEVICE","path":"/dev/ttyUSB0","activated":1257084408.46,"flags":1,"driver":"SiRF binary","native":1,"bps":4800,"parity":"N","stopbits":1,"cycle":1.00}]}
>
> None of "R", "W" nor "?WATCH={"enable":true};" worked with another session.
>
> One interesting note is that "activated" = 1257084408.46 (Sun, 1 Nov 2009 14:06:48 UTC) is *after* our failure time.
>
> I start my GPSD from init with "-n -F $CONTROL_SOCKET -P $PIDFILE".  I'm going to add in the -b flag and start running again.
>
> I'm up and running again.  gpsctl could not get the device working again but gpsmon could.
> Mike (mrdvt92)

Very, very strange. I think the first thing we need to know is whether
the GPS is still sending good data down the wire after one of these
events.  If it's not, then you're having some kind of firmware glitch
that flips it into a bad mode.  If it is, something intenal to gpsd is
going wonky.
--
                <a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
_______________________________________________
Gpsd-dev mailing list
Gpsd-dev@...
https://lists.berlios.de/mailman/listinfo/gpsd-dev