time-nuts@lists.febo.com

Discussion of precise time and frequency measurement

View all threads

u-blox NEO-M8T GPS initial tracking test

MS
Mark Sims
Fri, Feb 10, 2017 9:41 PM

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.


The only thing I haven't been able to do is the GNSS configure and

enable of GAL. Even with the assigned channels well under the 32 max, it
won't accept GAL configurations.

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. ---------------- > The only thing I haven't been able to do is the GNSS configure and enable of GAL. Even with the assigned channels well under the 32 max, it won't accept GAL configurations.
M
MLewis
Sat, Feb 11, 2017 3:31 AM

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.
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?

P.S.
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.

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. 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? P.S. 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. >
PS
Pete Stephenson
Sun, Feb 12, 2017 6:50 PM

On Sat, Feb 11, 2017 at 4:31 AM, MLewis mlewis000@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
running?

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.

Cheers!
-Pete

--
Pete Stephenson

On Sat, Feb 11, 2017 at 4:31 AM, MLewis <mlewis000@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 running? 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. Cheers! -Pete -- Pete Stephenson
M
MLewis
Sun, Feb 12, 2017 11:21 PM

On 12/02/2017 1:50 PM, Pete Stephenson wrote:

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. 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 running?

Your M8T must be newer product (seems to be spring/summer 2016 onward)
to have shipped from the factory with 3.01 TIM firmware that supports
Galileo, seemingly to the same configuration table provided with the SPG
3.01 release notes.

Although purchased in early December, my M8T has the older 2.3 TIM firmware.

at forum.u-blox.com:

The 2.30 TIM firmware will not support Galileo. It is not recommended to
use the SPG (Standard Product) 3.01 firmware to the NEO/LEA-M8T as you'd
lose timing functionality, and have no route back.

... historically u-Blox has not release firmware updates for timing
products publically, only in parts direct from the factory.
... it is probably a factory-only option, which would align with
previous policies not to release Timing firmwares publically.

In discussion: that after the Galileo constellation has completed its
validation phase, the 3.01 TIM firmware that is already shipping with
newer product may come available.

There is some hope. Various comments in the forum imply the 3.01 TIM
firmware is available, at least to valued commercial clients, via
official support channels.

Michael

On 12/02/2017 1:50 PM, Pete Stephenson wrote: > 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. 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 running? Your M8T must be newer product (seems to be spring/summer 2016 onward) to have shipped from the factory with 3.01 TIM firmware that supports Galileo, seemingly to the same configuration table provided with the SPG 3.01 release notes. Although purchased in early December, my M8T has the older 2.3 TIM firmware. at forum.u-blox.com: The 2.30 TIM firmware will not support Galileo. It is not recommended to use the SPG (Standard Product) 3.01 firmware to the NEO/LEA-M8T as you'd lose timing functionality, and have no route back. ... historically u-Blox has not release firmware updates for timing products publically, only in parts direct from the factory. ... it is probably a factory-only option, which would align with previous policies not to release Timing firmwares publically. In discussion: that after the Galileo constellation has completed its validation phase, the 3.01 TIM firmware that is already shipping with newer product may come available. There is some hope. Various comments in the forum imply the 3.01 TIM firmware is available, at least to valued commercial clients, via official support channels. Michael