Closed GoogleCodeExporter closed 9 years ago
The APM_GPS_UBLOX library files include the ability to parse a NAV-SOL message
to get the number of satellites used in a solution, but I haven't observed a
number of satellites reported other than 0 for the Ublox module so I assume the
module doesn't send this message by default.
To get a true number of satellites in view, APM_GPS_UBLOX has to recognize a
RXM-SVSI message (page 82 in the data sheet), which is variable length, so the
code will have to be changed to deal with variable-length packets (perhaps set
_expect to 0 when size-checking should be bypassed). It will probably also
have to send a CFG-MSG command on initialization to enable RXM-SVSI messages
(page 100 in the data sheet).
Original comment by bjpcalt...@gmail.com
on 28 Sep 2010 at 12:00
NAV-SOL needs to be enabled by the uCenter software to get sats information.
Byte Offset: 47 U1 - numSV - Number of SVs used in Nav Solution
This will get the info we need. Can you load uCeter and test it. We also need
to look at the raw output to test the parser does not have an error.
Jason
Original comment by jasonshort
on 28 Sep 2010 at 5:37
Original comment by jasonshort
on 28 Sep 2010 at 10:48
I disabled the NAV-STATUS message and enabled the NAV-SOL. After that the
number of sats is shown correct in APM. Attached my config file for the ublox
which can be used by uploading it to the gps with the uCenter software.
Mirko
Original comment by mir...@googlemail.com
on 5 Dec 2010 at 2:30
Attachments:
[deleted comment]
I will be adding an update to CLI test mode for raw gps, that will allow
bidirectional access of ucenter to the ublox. This change verified the ublox
config that allows more messages through.
My current config is NMEA disabled entirely, and the following UBX messages
enabled.
DOP
POSLLH
SOL
STATUS
SVINFO
VELNED
Original comment by Draconis...@gmail.com
on 24 Feb 2011 at 2:27
this has been fixed in master, with NAV_SOL automatically enabled on startup
Original comment by tridg...@gmail.com
on 19 Jul 2012 at 5:23
Original comment by tridg...@gmail.com
on 19 Jul 2012 at 5:24
Original issue reported on code.google.com by
dewei...@gmail.com
on 27 Sep 2010 at 6:30