Inav 7.1.2 GPS issues with FlyFishRC M10 Mini GPS Module

[roroid]

Current Behavior

Not able to set GPS satelites to Galileo or Glonas
Not able to arm the vehicle, even if I have more than 10 satelites locked

ScreenRecording_11-18-2024.09-46-36_1.mov

Steps to Reproduce

See above video

Expected behavior

Able to setup Galileo or Glonas.
Arm with more then 6 satelites locked

Suggested solution(s)

if I configure the variable
gps_auto_config=off
system is working

Additional context

This is an old FC, Betaflight F4. I did not have this issue with a Speedeby Mini WING F405 on same INAV version with same type of GPS.
On the INAV Fixed Wing group some other users reported same problem

• FC Board name and vendor:Betaflight F4
• INAV version string:7.1.2

[mmosca]

Please post the output of status and/or try 8.0.0 RC1

[roroid]

# 
# Building AutoComplete Cache ... Done!
# 
# status
INAV/BETAFLIGHTF4 7.1.2 May 31 2024 / 21:59:42 (4e1e59eb)
GCC-10.3.1 20210824 (release)
System Uptime: 188 seconds
Current Time: 2024-11-18T15:48:10.949+00:00
Voltage: 0.55V (0S battery - NOT PRESENT)
CPU Clock=168MHz, GYRO=MPU6000, ACC=MPU6000
STM32 system clocks:
  SYSCLK = 168 MHz
  HCLK   = 168 MHz
  PCLK1  = 42 MHz
  PCLK2  = 84 MHz
Sensor status: GYRO=OK, ACC=OK, MAG=NONE, BARO=NONE, RANGEFINDER=NONE, OPFLOW=NONE, GPS=OK
ESC Temperature(s): Motor Count = 2
ESC 0: 0°C, ESC 1: 0°C, 
Stack size: 6144, Stack address: 0x10010000, Heap available: 1828
I2C Errors: 45, config size: 10423, max available config: 131072
ADC channel usage:
   BATTERY : configured = ADC 2, used = ADC 2
      RSSI : configured = none, used = none
   CURRENT : configured = ADC 1, used = ADC 1
  AIRSPEED : configured = none, used = none
System load: 9, cycle time: 1014, PID rate: 986, RX rate: 9, System rate: 9
Arming disabled flags: NAV RX CLI
OSD: MSP DisplayPort: BetaFlight Compatability mode (HD) [53 x 20]
VTX: not detected
GPS: HW Version: UBLOX10 Proto: 34.00 Baud: 115200
  GNSS Capabilities:
    GNSS Provider active/default
    GPS 1/1
    Galileo 1/1
    BeiDou 1/0
    Glonass 0/0
    Max concurrent: 3

[roroid]

same on inav 8

INAV/BETAFLIGHTF4 8.0.0 Nov 15 2024 / 17:32:07 (5f78f962) dev
GCC-13.2.1 20231009
System Uptime: 16 seconds
Current Time: 2041-06-28T02:04:00.000+01:00
Voltage: 0.55V (0S battery - NOT PRESENT)
CPU Clock=168MHz, GYRO=MPU6000, ACC=MPU6000
STM32 system clocks:
  SYSCLK = 168 MHz
  HCLK   = 168 MHz
  PCLK1  = 42 MHz
  PCLK2  = 84 MHz
Sensor status: GYRO=OK, ACC=OK, MAG=NONE, BARO=NONE, RANGEFINDER=NONE, OPFLOW=NONE, GPS=OK
ESC Temperature(s): Motor Count = 2
ESC 0: 0°C, ESC 1: 0°C, 
Stack size: 6144, Stack address: 0x10010000, Heap available: 1828
I2C Errors: 50, config size: 13411, max available config: 131072
ADC channel usage:
   BATTERY : configured = ADC 2, used = ADC 2
      RSSI : configured = none, used = none
   CURRENT : configured = ADC 1, used = ADC 1
  AIRSPEED : configured = none, used = none
System load: 13, cycle time: 511, PID rate: 1956, RX rate: 9, System rate: 9
Arming disabled flags: NAV THR CMS
  WAITING FOR GPS FIX
OSD: MSP DisplayPort [30 x 16]
VTX: not detected
GPS: HW Version: UBLOX10 Proto: 34.00 Baud: 115200
  SATS: 0
  HDOP:  99.990
  EPH :  99.990 m
  EPV :  99.990 m
  GNSS Capabilities:
    GNSS Provider active/default
    GPS 1/1
    Galileo 1/1
    BeiDou 1/0
    Glonass 0/0
    Max concurrent: 3

[sensei-hacker]

First, you'll want to use "UBLOX7" protocol. That's for N7M or newer. You can first check if just doing that solves your issue.

If not, the next thing is if you manually changed any settings on the GPS using U-Center, go back to U-Center and click the button to reset to defaults. The M10 is very limited hardware - only one single receiver front end, for example. So each channel can only be used by one constellation. If you have a different constellation set to use the channel that INAV is trying to configure for that channel, it'll be a conflict and not work.

[roroid]

First, you'll want to use "UBLOX7" protocol. That's for N7M or newer. You can first check if just doing that solves your issue.

If not, the next thing is if you manually changed any settings on the GPS using U-Center, go back to U-Center and click the button to reset to defaults. The M10 is very limited hardware - only one single receiver front end, for example. So each channel can only be used by one constellation. If you have a different constellation set to use the channel that INAV is trying to configure for that channel, it'll be a conflict and not work.

I’ve also tried using the u-blox 7, but I’m still unable to configure constellations, and the settings keep resetting after each reboot. I know this GPS supports two constellations, as I have the same model on three other aircraft without any issues. This is the first time I’m using the u-blox 7 on my vehicles, though.

In the meantime, I applied the M10 hack to it, set it up on the u-blox 7, and modified the serial connection so it’s powered by the battery. At least now I can get the vehicle to arm.

[sensei-hacker]

I know this GPS supports two constellations

It supports all four constellations concurrently, with our configuration which is built into INAV.

That's done by using a different channel for each constellation, since the M10 has only one receiver. Unlike and M8 or M9, which can use the high-precision channels for all constellations. If you try to use the same channel for two different constellations in an M10 that won't work, because on the M10 they all have to share the same receiver. If you're going to do your own manual configuration rather than letting INAV do it, you have to choose which constellation gets the better channel.

Mixing our recipe, which works well, with another recipe you found on a forum somewhere is like mixing a recipe for chocolate cake with a recipe for chicken soup. You end up with chocolate chicken cake, which isn't likely to be very good.

Using my config works well. Manually configuring it based on some forum post you found may also work fine. Mixing the two together just makes a mess.

[roroid]

I don't think i follow you. I want to setup Galileo, and I'm not able because the settings are getting reset. I'm not trying to mix any settings.

[imotep33]

Hello, i'm having exactly the same issue. I use this model of GPS on a speedybee F405 MINI wing flight controller.
I can't set up the Galileo satellites ON. I only have the GPS satellites working.
I also tried to use Ublox or Ublox7 protocol and there is no difference.

I have exactly the same GPS on a matek F411 WTE and Inav 6. it's working perfectly and the Galileo satellites are ON

[sensei-hacker]

I don't think i follow you. I want to setup Galileo, and I'm not able because the settings are getting reset. I'm not trying to mix any settings.

What exactly do you mean when you say ", I applied the M10 hack to it"? What exactly did you do?

[sensei-hacker]

Hello, i'm having exactly the same issue. I use this model of GPS on a speedybee F405 MINI wing flight controller. I can't set up the Galileo satellites ON. I only have the GPS satellites working. I also tried to use Ublox or Ublox7 protocol and there is no difference.

I have exactly the same GPS on a matek F411 WTE and Inav 6. it's working perfectly and the Galileo satellites are ON

If you indeed have exactly the same problem, you tried to do some kind of "hack" to it? Probably using U-Center?

[imotep33]

Hello, i'm having exactly the same issue. I use this model of GPS on a speedybee F405 MINI wing flight controller. I can't set up the Galileo satellites ON. I only have the GPS satellites working. I also tried to use Ublox or Ublox7 protocol and there is no difference.
I have exactly the same GPS on a matek F411 WTE and Inav 6. it's working perfectly and the Galileo satellites are ON

If you indeed have exactly the same problem, you tried to do some kind of "hack" to it? Probably using U-Center?

hum, no. I don't know how to do it I a preferred to spinelessly downgrade to inav 6.1.1 and Galileo works fine on this version.

[roroid]

I don't think i follow you. I want to setup Galileo, and I'm not able because the settings are getting reset. I'm not trying to mix any settings.

What exactly do you mean when you say ", I applied the M10 hack to it"? What exactly did you do?

What is writen here.

https://iflight-rc.eu/blogs/news/m10-gps-3d-fix-enhancement?gad_source=1&gclid=CjwKCAiA9bq6BhAKEiwAH6bqoCNzhX-oZ7AIqF6fMruQxLgygtqmLqYrekVkk1vZHI_tSTznM-pMlxoChKkQAvD_BwE

[sensei-hacker]

Okay so you

I don't think i follow you. I want to setup Galileo, and I'm not able because the settings are getting reset. I'm not trying to mix any settings.

What exactly do you mean when you say ", I applied the M10 hack to it"? What exactly did you do?

What is writen here.

https://iflight-rc.eu/blogs/news/m10-gps-3d-fix-enhancement?gad_source=1&gclid=CjwKCAiA9bq6BhAKEiwAH6bqoCNzhX-oZ7AIqF6fMruQxLgygtqmLqYrekVkk1vZHI_tSTznM-pMlxoChKkQAvD_BwE

Okay so you applied a bunch of settings from someone who writes "Some cryptic stuff should appear, not sure why but it does. .... Select every available checkbox option ... " In other words, they don't really know what they're doing, and clearly you don't know what you did.

Part of what's in those settings is it tells the module to update every 1 millisecond - 1,000 times per second.
The chip is actually capable of updating 10 times per second.

The suggestion remains the same - reset to defaults in UCenter to get the module back into a sane state, then let INAV configure it as required. Alternatively, you could restore the backup of the factory settings that you saved before making changes. Or maybe the person writing that post didn't know you should save a backup before making changes, so you don't have a backup? To restore your module to a reasonable state, go to View -> Configuration View, select “CFG (Configuration)” on the left, select “Revert to default configuration” on the right, and press “Send” at the bottom.

[roroid]

Okay so you

I don't think i follow you. I want to setup Galileo, and I'm not able because the settings are getting reset. I'm not trying to mix any settings.

What exactly do you mean when you say ", I applied the M10 hack to it"? What exactly did you do?

What is writen here.

https://iflight-rc.eu/blogs/news/m10-gps-3d-fix-enhancement?gad_source=1&gclid=CjwKCAiA9bq6BhAKEiwAH6bqoCNzhX-oZ7AIqF6fMruQxLgygtqmLqYrekVkk1vZHI_tSTznM-pMlxoChKkQAvD_BwE

Okay so you applied a bunch of settings from someone who writes "Some cryptic stuff should appear, not sure why but it does. .... Select every available checkbox option ... " In other words, they don't really know what they're doing, and clearly you don't know what you did.

Part of what's in those settings is it tells the module to update every 1 millisecond - 1,000 times per second.

The chip is actually capable of updating 10 times per second.

The suggestion remains the same - reset to defaults in UCenter to get the module back into a sane state, then let INAV configure it as required. Alternatively, you could restore the backup of the factory settings that you saved before making changes. Or maybe the person writing that post didn't know you should save a backup before making changes, so you don't have a backup? To restore your module to a reasonable state, go to View -> Configuration View, select “CFG (Configuration)” on the left, select “Revert to default configuration” on the right, and press “Send” at the bottom.

Exactly, and the cryptic stuff made it work. Without the cryptic stuff, I had 12 satellites and could not arm. Still, to avoid losing track of where we began, I’m still not able to select Galileo, with or without the cryptic stuff.

[sensei-hacker]

Still, to avoid losing track of where we began I’m still not able to select Galileo

And you probably won't be able to until you reset the module to a sane state.

[roroid]

Still, to avoid losing track of where we began I’m still not able to select Galileo

And you probably won't be able to until you reset the module to a sane state.

Ok. Seems that I'm speaking American and you are understanding English.

[imotep33]

there are 2 things here:

• One issue is about bee able to set the Galileo sats ON which was also my issue in Inav 7, and it's the video enclosed in the first post. the FC just refuses to set galileo ON. when you sent the command, and you check it back. it stays OFF.

• the second issue he is talking about is: not beeing able to arm, even with 12 sats and a steady fix. I also had it by the past on my speedybee FC. I saw it's a common bug, and I solved it by reflashing the card (It was inav 7 at that stage) and re configure from scratch. but it seem it can be solved by flashing + reset the parameters from the diff without the satellites parameters.

[sensei-hacker]

• the second issue he is talking about is: not beeing able to arm, even with 12 sats and a steady fix. I also had it by the past on my speedybee FC. I saw it's a common bug, and I solved it by reflashing the card (It was inav 7 at that stage) and re configure from scratch. but it seem it can be solved by flashing + reset the parameters from the diff without the satellites parameters.

The second issue you're referring to occurs when that Speedybee is upgraded from INAV 6 to INAV 7 with full erase turned off. That causes the max EPH to be set to 1 centimeter, rather than 1,000 centimeters.

[imotep33]

I had some time free on the bench, I upgraded my FC to Inav 8 RC2
Remember, my GPS is stock, i did not modify anything.
The issue still there

---

Entering CLI Mode, type 'exit' to return, or 'help'

Building AutoComplete Cache ... Done!
get gps_ublox_use_galileo
gps_ublox_use_galileo = OFF
Allowed values: OFF, ON

set gps_ublox_use_galileo = ON
gps_ublox_use_galileo set to ON
get gps_ublox_use_galileo
gps_ublox_use_galileo = ON
Allowed values: OFF, ON

Save

Entering CLI Mode, type 'exit' to return, or 'help'

Building AutoComplete Cache ... Done!

get gps_ublox_use_galileo
gps_ublox_use_galileo = OFF
Allowed values: OFF, ON

---

here is some extract from my dump file :
set gps_provider = UBLOX
set gps_sbas_mode = NONE
set gps_dyn_model = AIR_2G
set gps_auto_config = ON
set gps_auto_baud = ON
set gps_auto_baud_max_supported = 230400
set gps_ublox_use_galileo = OFF
set gps_ublox_use_beidou = OFF
set gps_ublox_use_glonass = OFF
set gps_min_sats = 5
set gps_ublox_nav_hz = 10

[sensei-hacker]

Thanks for that info @imotep33
I understand in your case you have NOT used UCenter to mess with any settings; have not loaded any ucf file from any blog post.

The module I would use to run a test to double-check with your exact configuration is broken at the moment, so we'll have to take a different path. The first thing that can cause issues is that upgrading from INAV 6 to INAV 7 with "full chip erase" turned off sometimes messes up settings. be sure to check that box whenever switching between major versions - 6 to 7, 7 to 8, etc. The issue of "not beeing able to arm, even with 12 sats" is an example of that.

You can save a diff and copy settings over as described in the release notes (some settings carry over, others don't).
Can you please do a flash with full erase of either 8.0RC1 or 7.1.2, even if you've already done that before, just to double check? Then we can proceed from there.

Also, troubleshooting may be helped by having a full diff, if you could attach one please.

[imotep33]

hello, I did it again. with the full chip erase function ON. still got the issue with inav 7.1.2 and Inav 8 RC2

[imotep33]

Thanks for that info @imotep33 I understand in your case you have NOT used UCenter to mess with any settings; have not loaded any ucf file from any blog post.

The module I would use to run a test to double-check with your exact configuration is broken at the moment, so we'll have to take a different path. The first thing that can cause issues is that upgrading from INAV 6 to INAV 7 with "full chip erase" turned off sometimes messes up settings. be sure to check that box whenever switching between major versions - 6 to 7, 7 to 8, etc. The issue of "not beeing able to arm, even with 12 sats" is an example of that.

You can save a diff and copy settings over as described in the release notes (some settings carry over, others don't). Can you please do a flash with full erase of either 8.0RC1 or 7.1.2, even if you've already done that before, just to double check? Then we can proceed from there.

Also, troubleshooting may be helped by having a full diff, if you could attach one please.

i'm available this week until saturday if you want to check something on my device. afterward, i'll be a bit more random during the christmas holidays

[tizzism]

I have the SPeedybee Wing Mini. with Be-220 gps from Beitian (off amazon). normalgps baud in inav. I could not get my GPS to lock, with 13 satellites.

I changed the CLI Command: set inav_max_eph_epv = 1000

tested > worked. Fixed enabled.

status

INAV/SPEEDYBEEF405WING 7.1.2 Jun 1 2024 / 00:47:23 (4e1e59e)
GCC-10.3.1 20210824 (release)
System Uptime: 629 seconds
Current Time: 2024-12-18T16:03:34.105+00:00
Voltage: 0.00V (0S battery - NOT PRESENT)
CPU Clock=168MHz, GYRO=ICM42605, ACC=ICM42605, BARO=SPL06
STM32 system clocks:
SYSCLK = 168 MHz
HCLK = 168 MHz
PCLK1 = 42 MHz
PCLK2 = 84 MHz
Sensor status: GYRO=OK, ACC=OK, MAG=NONE, BARO=OK, RANGEFINDER=NONE, OPFLOW=NONE, GPS=OK
SD card: Startup failed
Stack size: 6144, Stack address: 0x10010000, Heap available: 1728
I2C Errors: 0, config size: 10467, max available config: 131072
ADC channel usage:
BATTERY : configured = ADC 1, used = ADC 1
RSSI : configured = ADC 4, used = none
CURRENT : configured = ADC 2, used = ADC 2
AIRSPEED : configured = ADC 3, used = none
System load: 5, cycle time: 1004, PID rate: 996, RX rate: 9, System rate: 9
Arming disabled flags: NAV RX CLI
OSD: MAX7456 [30 x 16]
VTX: not detected
GPS: HW Version: UBLOX10 Proto: 34.09 Baud: 115200
GNSS Capabilities:
GNSS Provider active/default
GPS 1/1
Galileo 1/1
BeiDou 1/1
Glonass 1/0
Max concurrent: 3