[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gpsd-dev] Regression test failed on fortrex-201.log.chk
From: |
address@hidden |
Subject: |
Re: [gpsd-dev] Regression test failed on fortrex-201.log.chk |
Date: |
Mon, 01 Jun 2015 12:57:11 +0200 |
Hello,
here is the link to the documentation
http://www.u-blox.com/images/downloads/Product_Docs/u-bloxM8_ReceiverDescriptionProtocolSpec_(UBX-13003221)_Public.pdf
GSV is on page 84.
And the mode switch is described in
"21.11.13.4 Extended NMEA protocol configuration V1" on page 141
Reinhard
-----Original-Nachricht-----
Betreff: Re: Regression test failed on fortrex-201.log.chk
Datum: Mon, 01 Jun 2015 12:29:28 +0200
Von: "Eric S. Raymond" <address@hidden>
An: "address@hidden" <address@hidden>
address@hidden <address@hidden>:
> Hello,
>
> for some reason, gpsd do not switch the m8 to u-blox mode.
>
> This is the reason, why this problem occur.
>
> I do not have a nmea0183 v4.1 spec at the hand now, but the u-blox spec says,
> that NMEA0183 v4.1 added a signal id field at the end of the xxGSV sentence.
>
> For the u-blox m8, you can switch to nmea0183 v4.0 compatibility with the
> windows u-center software.
>
> Until gpsd is able to switch a m8 receiver to u-blox mode, we will get a lot
> of support requests.
>
> And on the long term, i think, that we can not ignore the new revision 4.1 of
> the standard..
>
> Reinhard
That is useful information. Can you point me at a copy of the u-blox spec
that describes this field?
Clearly the ubx driver is going to need some work to support the m8.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
Re: [gpsd-dev] Regression test failed on fortrex-201.log.chk, Hal Murray, 2015/06/01