Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removed Galileo nav rate change. Slightly reduced Galileo's maximum tracking channel. #597

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

dndx
Copy link

@dndx dndx commented May 14, 2017

The current setting we use is incorrect for a 2 Hz configuration. The update interval is set to 166 Hz and sample for calculation is set to 500 and is outside of the chip's capability. This causes NEO-M8 to fallback to the default 1 Hz update rate and is not really desirable.

According to answer from Ublox forum, we actually do not need to tune down the nav rate when enabling Galileo at all as the chip will automatically scale down as necessary. I have been able to confirm this behavior, that is, the nav rate only goes down when Galileo is being tracked and stays at 10 Hz when no Galileo satellite was used in the calculation (and appears to scale down linearly as the number of Galileo satellite tracked goes up). Adding a toggle switch for Galileo is also no longer necessary as older chip user should receive no negative impact from enabling Galileo with this change. The increased update rate should help AHRS calculations greatly.

This PR also reduces the maximum tracking channel of Galileo from 8 to 5 as there are currently only 11 operational satellite inside the Galileo system and it is not likely to observe more than ~5 satellites at a given point on earth. With this change we free up 3 more tracking channels for GPS/GLONASS/SBAS.

Before:
screen shot 2017-05-13 at 9 30 32 pm

After:
screen shot 2017-05-13 at 9 54 43 pm

@VirusPilot
Copy link

I confirm that this 2 Hz configuration is wrong. No need to change the RATE configuration from what is used for ublox 7.
Furthermore as of February 2019 there are significantly more GALILEO satellites up so that the max. number could be set to 10 which is the maximum that the ublox 8 chip can do anyway.

@cyoung
Copy link
Owner

cyoung commented May 15, 2020

Anyone able to test with higher tracking channel settings, now that there are more active Galileo satellites?

@VirusPilot
Copy link

We are successfully running ublox 8 units with 10Hz and Galileo now for more than a year in the Stratux Europe. I can prepare a pull request if you want to bring these changes back.

@VirusPilot
Copy link

And furthermore we have set the number of tracking channels for Galileo to 10 and it workes fine. As we speak, 22 Galileo sats are active: https://www.gsc-europa.eu/system-service-status/constellation-information

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants