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

GPS # of satellites used dropped to 16 (u-blox M9N) #14722

Closed
limhyon opened this issue Apr 21, 2020 · 9 comments
Closed

GPS # of satellites used dropped to 16 (u-blox M9N) #14722

limhyon opened this issue Apr 21, 2020 · 9 comments
Labels
Drivers 🔧 Sensors, Actuators, etc question

Comments

@limhyon
Copy link
Contributor

limhyon commented Apr 21, 2020

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

  1. Connect u-center to M9N with USB port.
  2. Wait PX4 booted.
  3. Check u-center.

Expected behavior
It should have maximum number of satellites observed.

@julianoes julianoes added the Drivers 🔧 Sensors, Actuators, etc label Apr 22, 2020
@julianoes
Copy link
Contributor

FYI @bkueng

@ryanjAA
Copy link
Contributor

ryanjAA commented Apr 23, 2020

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.

@bkueng
Copy link
Member

bkueng commented Apr 24, 2020

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

@ryanjAA
Copy link
Contributor

ryanjAA commented Apr 27, 2020

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.

@dagar
Copy link
Member

dagar commented Apr 27, 2020

Tested at 25hz and still limited to 16 sats. Tested at 5hz and no limitation so unfortunately it is a hardware constraint. 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?

@ryanjAA
Copy link
Contributor

ryanjAA commented Apr 27, 2020

What specifically? HDOP and VDOP? HDOP drops by half when going from 16 to 22-24 sats and when hitting 29+ starts to decrease further.

Screen Shot 2020-04-25 at 10 15 19 PM

Screen Shot 2020-04-25 at 3 24 45 PM

@stale
Copy link

stale bot commented Jul 26, 2020

This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions.

@stale stale bot added the stale label Jul 26, 2020
@julianoes
Copy link
Contributor

Fixed in PX4/PX4-GPSDrivers#57, right?

@stale stale bot removed the stale label Jul 27, 2020
@bkueng
Copy link
Member

bkueng commented Jul 27, 2020

Correct, thanks Julian.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Drivers 🔧 Sensors, Actuators, etc question
Projects
None yet
Development

No branches or pull requests

5 participants