[time-nuts] u-blox NEO-M8T GPS initial tracking test
mlewis000 at rogers.com
Fri Feb 10 22:31:19 EST 2017
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
And that's with the required NEMA of 4.1.
Specifically, from u-center, the Signals checkbox for E1 - with a
Signals selection listed as a mandatory requirement for configuration -
never becomes selectable.
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."
The 301 release notes does specify that Time Pulse is supported. And
like Mark says about no SBAS, the one supported 301 configuration with
both Time Pulse & Galileo supported, specifies GPS, GLO & Galileo
together without SBAS or QZSS.
Mark, have you managed to run Galileo from an M8T? If so, which firmware?
Lady Heather worked immediately with the USB as Com driver I got from
u-blox. And LH's finer resolution on the signal level map (compared to
u-center) is wonderful to use. I can actually discern the influence of:
the profiles of the bank of buildings opposite me, a hydro transformer
on a pole and my building's door's structural-steel canopy (both
blocking line-of-sight and reflecting from ~175 degrees from that).
Doesn't appear that LH will list the full 32 channels that my M8T has.
On 10/02/2017 4:41 PM, Mark Sims wrote:
> The Ublox multi-GNSS receivers are incredibly picky about the channel allocations. Basically if you don't use the default channel min/max values they either won't work or are very flakey. I tried values other than min=4/max=8 for Galileo and nothing worked. Also, if you have SBAS enabled you cannot select Galileo.
More information about the time-nuts