Globalsat ND100 support?

[Ed Wildgoose-2]

Hi, Globalsat have a new ND100 out which is a usb stick type package and
slightly better sensitivity to the BU353 (and less money)

My observation after testing it for a few mins is that it's not
correctly working with gpsd because it uses only 38400 for baud rate
(nothing else works and apparently no autobaud)

So far I observe:
- If I manually change ttyUSB0 to a baud of 38400 then
- gpsmon correctly picks it up
- cat /dev/ttyUSB0 spews nmea

- However, if I then run "gpsd /dev/ttyUSB0" then it seems that gpsd
doesn't see the device and attempting to use telnet into the port and
change the baud does nothing (perhaps it's not supported to use NMEA at
a different baud than 4800?)

- I notice if the baud is not set pre-set to 38400 then gpsmon won't
detect the device.

- The date on the top line of gpsmon shows (sic):
        Time: 1953-11-28T09:55:440.0Z
- I'm not sure where this date comes from, but an example GPRMC line
(19/8/2009 - 16:24 GMT) is:
   
$GPRMC,162424.000,A,5124.4428,N,00013.2253,W,0.0,155.4,030190,,,A*79\x0d\x0a
(Gah, 1990?? But why does gpsd show 1953?)

I requested gpsctl try to flick the device to a sirf binary mode, but it
refused - however, this could well be because of baud rate differences


I would be happy to supply one (potentially more if required) of these
devices to any developer who would like to implement full support in gpsd?

It looks like a potentially rather nice device given the higher baud
rate, but I guess only if it can be made to talk raw sirf binary
protocol?  I haven't probed further, but it seems probable that it will
talk a binary protocol if the baud rate were taken into account?

Regards

Ed W

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

[Chris Kuethe]

I'd be interested in getting ahold of one. My bu353 died and I haven't looked at replacing it yet.

CK

On Aug 19, 2009 9:39 AM, "Ed W" <lists@...> wrote:

Hi, Globalsat have a new ND100 out which is a usb stick type package and
slightly better sensitivity to the BU353 (and less money)

My observation after testing it for a few mins is that it's not
correctly working with gpsd because it uses only 38400 for baud rate
(nothing else works and apparently no autobaud)

So far I observe:
- If I manually change ttyUSB0 to a baud of 38400 then
- gpsmon correctly picks it up
- cat /dev/ttyUSB0 spews nmea

- However, if I then run "gpsd /dev/ttyUSB0" then it seems that gpsd
doesn't see the device and attempting to use telnet into the port and
change the baud does nothing (perhaps it's not supported to use NMEA at
a different baud than 4800?)

- I notice if the baud is not set pre-set to 38400 then gpsmon won't
detect the device.

- The date on the top line of gpsmon shows (sic):
       Time: 1953-11-28T09:55:440.0Z
- I'm not sure where this date comes from, but an example GPRMC line
(19/8/2009 - 16:24 GMT) is:

$GPRMC,162424.000,A,5124.4428,N,00013.2253,W,0.0,155.4,030190,,,A*79\x0d\x0a
(Gah, 1990?? But why does gpsd show 1953?)

I requested gpsctl try to flick the device to a sirf binary mode, but it
refused - however, this could well be because of baud rate differences


I would be happy to supply one (potentially more if required) of these
devices to any developer who would like to implement full support in gpsd?

It looks like a potentially rather nice device given the higher baud
rate, but I guess only if it can be made to talk raw sirf binary
protocol?  I haven't probed further, but it seems probable that it will
talk a binary protocol if the baud rate were taken into account?

Regards

Ed W

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

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

[Eric S. Raymond-2]

Ed W <lists@...>:

> Hi, Globalsat have a new ND100 out which is a usb stick type package and
> slightly better sensitivity to the BU353 (and less money)
>
> My observation after testing it for a few mins is that it's not
> correctly working with gpsd because it uses only 38400 for baud rate
> (nothing else works and apparently no autobaud)
>
> So far I observe:
> - If I manually change ttyUSB0 to a baud of 38400 then
> - gpsmon correctly picks it up
> - cat /dev/ttyUSB0 spews nmea

Good, that means it's emitting sane data.
 
> - However, if I then run "gpsd /dev/ttyUSB0" then it seems that gpsd
> doesn't see the device and attempting to use telnet into the port and
> change the baud does nothing (perhaps it's not supported to use NMEA at
> a different baud than 4800?)

Fully supported, by gpsd, anyway.  And 38400 is in our supported baud
rate list.  The normal hunt loop should find it; the question is why
that's not working.

> - I notice if the baud is not set pre-set to 38400 then gpsmon won't
> detect the device.

gpsmon's low-level mode uses the same hunt loop gpsd does.  If we
answer one question we'll also answer the other.

> - The date on the top line of gpsmon shows (sic):
>         Time: 1953-11-28T09:55:440.0Z
> - I'm not sure where this date comes from, but an example GPRMC line
> (19/8/2009 - 16:24 GMT) is:
>    
> $GPRMC,162424.000,A,5124.4428,N,00013.2253,W,0.0,155.4,030190,,,A*79\x0d\x0a
> (Gah, 1990?? But why does gpsd show 1953?)

Dunno.  I could probably figure that out, given a log of data
from the device.
 
> I would be happy to supply one (potentially more if required) of these
> devices to any developer who would like to implement full support in gpsd?

I'll give it a try, the device sounds interesting.  I'll mail you my surface
address if you need, or you can have Amzon ship it.  
--
                <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

[Chris Kuethe]

On Mon, Oct 26, 2009 at 12:46 PM, Eric S. Raymond <esr@...> wrote:
>> I would be happy to supply one (potentially more if required) of these
>> devices to any developer who would like to implement full support in gpsd?
>
> I'll give it a try, the device sounds interesting.  I'll mail you my surface
> address if you need, or you can have Amzon ship it.

Ed sent me one; if you want to play with it, let me know and send it your way.


--
GDB has a 'break' feature; why doesn't it have 'fix' too?
_______________________________________________
Gpsd-dev mailing list
Gpsd-dev@...
https://lists.berlios.de/mailman/listinfo/gpsd-dev

[Eric S. Raymond-2]

Chris Kuethe <chris.kuethe@...>:
> On Mon, Oct 26, 2009 at 12:46 PM, Eric S. Raymond <esr@...> wrote:
> >> I would be happy to supply one (potentially more if required) of these
> >> devices to any developer who would like to implement full support in gpsd?
> >
> > I'll give it a try, the device sounds interesting.  I'll mail you my surface
> > address if you need, or you can have Amzon ship it.
>
> Ed sent me one; if you want to play with it, let me know and send it your way.

Oh, OK.  If you're on it, I've got plenty of other things to do.
--
                <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

[Evrard Patrick]

could you remove my email address from your list
thanks

-----Original Message-----
From: gpsd-dev-bounces@... [mailto:gpsd-dev-bounces@...] On Behalf Of Chris Kuethe
Sent: Monday, October 26, 2009 8:57 PM
To: gpsd-dev@...; esr@...
Subject: Re: [Gpsd-dev] Globalsat ND100 support?

On Mon, Oct 26, 2009 at 12:46 PM, Eric S. Raymond <esr@...> wrote:
>> I would be happy to supply one (potentially more if required) of these
>> devices to any developer who would like to implement full support in gpsd?
>
> I'll give it a try, the device sounds interesting.  I'll mail you my surface
> address if you need, or you can have Amzon ship it.

Ed sent me one; if you want to play with it, let me know and send it your way.


--
GDB has a 'break' feature; why doesn't it have 'fix' too?
_______________________________________________
Gpsd-dev mailing list
Gpsd-dev@...
https://lists.berlios.de/mailman/listinfo/gpsd-dev
_______________________________________________
Gpsd-dev mailing list
Gpsd-dev@...
https://lists.berlios.de/mailman/listinfo/gpsd-dev

[Ed Wildgoose-2]

Hi

- However, if I then run "gpsd /dev/ttyUSB0" then it seems that gpsd 
doesn't see the device and attempting to use telnet into the port and 
change the baud does nothing (perhaps it's not supported to use NMEA at 
a different baud than 4800?)
    

Fully supported, by gpsd, anyway.  And 38400 is in our supported baud
rate list.  The normal hunt loop should find it; the question is why
that's not working.
  

...

- I notice if the baud is not set pre-set to 38400 then gpsmon won't 
detect the device.
    

gpsmon's low-level mode uses the same hunt loop gpsd does.  If we
answer one question we'll also answer the other.
  

I do wonder if I'm not looking at the wrong code?  I was using I think the most recent released code and at least eyeballing it, the code I looked at did not appear to have a baudrate hunt loop in it?

I haven't had any time to work on this further since I started this thread and need to work on some other stuff soon .  Are we due a release soon?  If not I guess I better play with svn?

- The date on the top line of gpsmon shows (sic):
        Time: 1953-11-28T09:55:440.0Z
- I'm not sure where this date comes from, but an example GPRMC line 
(19/8/2009 - 16:24 GMT) is:
    
$GPRMC,162424.000,A,5124.4428,N,00013.2253,W,0.0,155.4,030190,,,A*79\x0d\x0a
(Gah, 1990?? But why does gpsd show 1953?)
    

Dunno.  I could probably figure that out, given a log of data 
from the device

I haven't updated my unit yet, but it appears that the bogus date is a firmware issue and it's fixed if you grab the update off their website... Just a heads up to anyone who hasn't yet played with this unit


Cheers

Ed W


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

[Eric S. Raymond-2]

Ed W <lists@...>:
> I do wonder if I'm not looking at the wrong code?  I was using I think  
> the most recent released code and at least eyeballing it, the code I  
> looked at did not appear to have a baudrate hunt loop in it?

Look at the function next_hunt_setting in serial.c

> I haven't had any time to work on this further since I started this  
> thread and need to work on some other stuff soon .  Are we due a release  
> soon?  If not I guess I better play with svn?

Play with svn.,  I've wanted to ship 2.40 for a couple weeks now;
it's waiting on Chris Kuethe to do a minor upgrade to the TSIP driver
and Gary Miller to make the Garmin USB code work again.

>> Dunno.  I could probably figure that out, given a log of data from the
>> device
>
> I haven't updated my unit yet, but it appears that the bogus date is a  
> firmware issue and it's fixed if you grab the update off their  
> website... Just a heads up to anyone who hasn't yet played with this unit

That's good to know.
--
                <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