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.