[time-nuts] u-blox NEO-M8T GPS initial tracking test
pete at heypete.com
Sun Feb 12 13:50:15 EST 2017
On Sat, Feb 11, 2017 at 4:31 AM, MLewis <mlewis000 at rogers.com> wrote:
> With this NEO-M8T, I've even turned off everything but min=4/max=8 for GPS &
> GLO, and it won't accept any configuration for Galileo, let alone enable.
> And that's with the required NEMA of 4.1.
What firmware version are you using?
Are you sure it's an authentic u-blox receiver? There's a bunch of
fakes out there that identify as u-blox but lack some functionality.
> But someone emailed me that I'm just banging my head against the wall as the
> M8 timing firmware won't config Galileo.
> They and others have had success configuring & enabling Galileo by changing
> the firmware to UBX_M8_301 (from January 2016), although that is
> specifically identified as "It should not be used for Timing, Dead Reckoning
> or High Precision GNSS products."
I recently purchased an M8T and the UBX-MON-VER message shows the
firmware version as "EXT CORE 3.01 (111141)". What version are you
Galileo works fine on mine, with a few caveats:
1. There's only particular combinations of signals that can be
received simultaneously. For example, GPS, GLONASS, and Galileo will
work together, as will GPS, Galileo, and BeiDou, but GPS, GLONASS, and
BeiDou won't work together. See the user guide for the specific
combinations. Trying to enable invalid combinations will result in it
automatically reverting to the last working combination.
2. WAAS and EGNOS only seem to work with GPS. You can enable other,
non-GPS signals, but only GPS will have the corrections applied. The
other, non-GPS signals will be marked as "ready" but won't turn green
and be used in the calculations.
More information about the time-nuts