-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
GPS # of satellites used dropped to 16 (u-blox M9N) #14722
Comments
FYI @bkueng |
Cherrypicked and same result. 16 sats Max. Tried a different firmware in same location at the same time and more than 16 sats so not hardware. On this test mine never went above 16 (with the cherrypicked commit). Just slowly crept up to it and stopped. |
Apparently this is indeed a hardware restriction (in combination with how we configure it): with 10Hz update rate you only get up to 16 satellites. Reducing to 5Hz allows to go higher. I reduced to 5Hz, so we can use more satellites: PX4/PX4-GPSDrivers#57 |
Tested at 25hz and still limited to 16 sats. Tested at 5hz and no limitation so unfortunately it is a hardware constraint. PX4/PX4-GPSDrivers#57 Breaks functionality with the M9N (as a few other things are added in the PR) but testing this with the previous driver change works fine with the reduced hz changes. |
I'm just curious, are you gathering and comparing any other metrics along with the satellite count and output data rate? |
This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions. |
Fixed in PX4/PX4-GPSDrivers#57, right? |
Correct, thanks Julian. |
Describe the bug
I was cherry-picking up
PX4/PX4-GPSDrivers@cf87129
to test M9N module. But as soon as PX4 firmware boots and send few commands to M9N, the number of satellites used on M9N dropped to 16 (fixed number) from around 30~32 satellites.
To Reproduce
Expected behavior
It should have maximum number of satellites observed.
The text was updated successfully, but these errors were encountered: