On Saturday 09 April 2005 18:50, olli-MrzJEd1NSjzR7s880joybQ@xxxxxxxxxxxxxxxx
wrote:
> > But anyway, I will be happy to provide any debug help you may need.
>
> Sorry for numerous posts, but I think I found the reason:
>
> 1) Error message about invalid number of fields in GPGGA does not cause
> the incorrect longitude, since latitude and longitude are taken from GPRMC
> sentence. Although it would be nice to found the cause for that as well.
> =)
>
> 2) Cause for the incorrect longitude is caused by different forms of
> $GPRMC sentences. With the new gpsd there is no preceeding zero in the
> longitude field and with old one, there is. GpsDrive expects that the
> first three numbers make up the degrees (now this becomes 024 vs. 244!)
> and this causes the problem. Now I don't know what the NMEA standard says
> about this, since unfortunately it is not an open standard - so I cannot
> know if this is a gpsd or GpsDrive issue.
I think it's not a question of: If this is NMEA standard or not. I think the
question is: is there a problem if we change the behavior of gpsdrive so it
can parse both types of data. As of what you described it looks like we would
be able to write code which can recognize both types of Data.
If you can have a look at the appropriate code part and send me a patch this
would be great. I think this will be really import as soon as we change from
gpsd 1.1 to gpsd 2.20.
-
Thanks in advance
joerg
--
This message was part of the gpsdrive mailinglist
unsubscribing can be done by sending a mail containing a body of:
-quote--
unsubscribe gpsdrive
-unquote--
to majordomo-ahljRfkWE0EwtzFM8z8+AfP6llvjuJOh@xxxxxxxxxxxxxxxx
|
