search

iNavFlight / inav-configurator

GNU General Public License v3.0
582 stars 314 forks source link

all three gps sattelites get disabled when enabling BeiDou #1914

Open tippfehlr opened 10 months ago

tippfehlr commented 10 months ago

When I try to enable BeiDou Sattelites (CN) via GPS tab or cli, after rebooting all three, Galileo, BeiDou and Glonass are disabled again (in ui and in cli).

Steps to reproduce:

  1. enable Galileo and Glonass and reboot: works as expected
  2. enable BeiDou Sattelites and reboot: all three are disabled again

expected result: all three stay activated

CONFIGURATOR: 7.0.0
FC FIRMWARE: 7.0.0 [SPEEDYBEEF405WING]
tippfehlr commented 10 months ago

probably an issue with INAV itself.

MrD-RC commented 10 months ago

I’m sure this is expected behaviour. Either your GPS module doesn’t support having 4 GNSS. Or I believe I’ve read that BeiDou and GLONASS share something, that means they can’t be selected at the same time.

Maybe Configurator needs some kind of warning?

@mmosca could we get some clarification?

tippfehlr commented 10 months ago

Alright, reopened this one and closed the issue in inav. If indeed glonass and BeiDou share something, maybe disable the other switch to indicate that only one is supported.

mmosca commented 10 months ago

The valid combinations are defined by the gps and are not known to inav. If we add that to the configurator it may prevent other valid use cases. []s,Marcelo Bezerra @.>On 7 Dec 2023, at 18:09, tippfehlr @.> wrote: Alright, reopened this one and closed the issue in inav. If indeed glonass and BeiDou share something, maybe disable the other switch to indicate that only one is supported.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

MrD-RC commented 10 months ago

I was meaning just an info box for explaining that. Not actually denying enabling certain clusters. Is that documented anywhere?

mmosca commented 10 months ago

The data sheet for each gps model. The status command does report the maximum number of constellations a gps supports though, and I am sure that his gps does not say 4. (Gps counts as one, btw)[]s,Marcelo Bezerra @.>On 8 Dec 2023, at 08:17, Darren Lines @.> wrote: I was meaning just an info box for explaining that. Not actually denying enabling certain clusters. Is that documented anywhere?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

tippfehlr commented 10 months ago 
# status
INAV/SPEEDYBEEF405WING 7.0.0 Dec  5 2023 / 11:06:36 (895a4f31)
GCC-10.3.1 20210824 (release)
System Uptime: 44 seconds
Current Time: 2041-06-28T03:04:00.000+02: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
ESC Temperature(s): Motor Count = 2
ESC 0: 0°C, ESC 1: 0°C, 
SD card: Manufacturer 0x1b, 994816kB, 04/2008, v1.0, '00000'
Filesystem: Ready
Stack size: 6144, Stack address: 0x10010000, Heap available: 1728
I2C Errors: 0, config size: 9541, 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: 12, cycle time: 1035, PID rate: 966, RX rate: 9, System rate: 9
Arming disabled flags: NAV RX CLI
OSD: MAX7456 [30 x 16]
VTX: band: A, chan: 2, power: 1 (25 mW), freq: 5845 MHz
GPS: HW Version: UBLOX10 Proto: 34.09 Baud: 115200
  GNSS Capabilities:
    GNSS Provider active/default
    GPS 1/1
    Galileo 1/1
    BeiDou 0/1
    Glonass 1/0
    Max concurrent: 3

Max concurrent: 3

ok, so my gps (HGLRC M100 Mini) does indeed only do 3 at a time. And BeiDou and Glonass don’t work at the same time, doesn’t matter is Galileo is enabled or not.

mmosca commented 10 months ago

That is a hard thing to say these days. Glonass is provided by a country that is engaged in a war in europe. beidou has global coverage, but works better in the asia pacific region.

I would say that your gps defaults of galileo and beidou is probably a good combo.

On Fri, Dec 8, 2023 at 3:51 PM tippfehlr @.***> wrote:

status

INAV/SPEEDYBEEF405WING 7.0.0 Dec 5 2023 / 11:06:36 (895a4f31) GCC-10.3.1 20210824 (release) System Uptime: 44 seconds Current Time: 2041-06-28T03:04:00.000+02: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 ESC Temperature(s): Motor Count = 2 ESC 0: 0°C, ESC 1: 0°C, SD card: Manufacturer 0x1b, 994816kB, 04/2008, v1.0, '00000' Filesystem: Ready Stack size: 6144, Stack address: 0x10010000, Heap available: 1728 I2C Errors: 0, config size: 9541, 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: 12, cycle time: 1035, PID rate: 966, RX rate: 9, System rate: 9 Arming disabled flags: NAV RX CLI OSD: MAX7456 [30 x 16] VTX: band: A, chan: 2, power: 1 (25 mW), freq: 5845 MHz GPS: HW Version: UBLOX10 Proto: 34.09 Baud: 115200 GNSS Capabilities: GNSS Provider active/default GPS 1/1 Galileo 1/1 BeiDou 0/1 Glonass 1/0 Max concurrent: 3

Max concurrent: 3

ok, so my gps (HGLRC M100 Mini) does indeed only do 3 at a time. And BeiDou and Glonass don’t work at the same time, doesn’t matter is Galileo is enabled or not.

  • If this is confirmed, wouldn’t disabling the other switch make it clear?
  • And I don’t know if there are gps with less than 3 max concurrent gps systems, if yes maybe display used/max gps systems.
  • I’m in Europe/Germany, does it matter which one I activate? Or should I disable both?

— Reply to this email directly, view it on GitHub https://github.com/iNavFlight/inav-configurator/issues/1914#issuecomment-1847319229, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFTWX5F5Z637PWF73GY3WU3YIMSPBAVCNFSM6AAAAABALIMYYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBXGMYTSMRSHE . You are receiving this because you were mentioned.Message ID: @.***>

druckgott commented 10 months ago

I have same problem. I have Config 7.0.0 and Inav 7.0.0. Can only switch on 2 of 3: grafik

mmosca commented 10 months ago

I was meaning just an info box for explaining that. Not actually denying enabling certain clusters. Is that documented anywhere?

That is probably ok. A basic warning that not all combinations of constellations may be supported by a particular GPS unit and that the settings will revert to default on invalid configurations would at least avoid more issues like this.

mmosca commented 10 months ago

I have same problem. I have Config 7.0.0 and Inav 7.0.0. Can only switch on 2 of 3: grafik

Normal, and expected. Just read the rest of the discussion.

tippfehlr commented 10 months ago

I think showing the actual capabilities of the gps unit is much more user friendly than letting the user figure out what works and what doesn’t. Is there a reason you are against disabling the options? The note can still be in the tooltips.

mmosca commented 10 months ago

There is no way to find out before hand what combinations are valid, but if you do find a way in the ublox documentation, please share and we may look into improving the configurator behavior.

On Fri, Dec 8, 2023 at 11:18 PM tippfehlr @.***> wrote:

I think showing the actual capabilities of the gps unit is much more user friendly than letting the user figure out what works and what doesn’t. Is there a reason you are against disabling the options? The note can still be in the tooltips.

— Reply to this email directly, view it on GitHub https://github.com/iNavFlight/inav-configurator/issues/1914#issuecomment-1847912486, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFTWX5DWKLBSPZ7H5CZCHQDYIOG3XAVCNFSM6AAAAABALIMYYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBXHEYTENBYGY . You are receiving this because you were mentioned.Message ID: @.***>

tippfehlr commented 10 months ago

@mmosca I would just disable BeiDou/Glonass and (maybe) display a warning if Max concurrent is less than 3.

mmosca commented 10 months ago

@mmosca I would just disable BeiDou/Glonass and (maybe) display a warning if Max concurrent is less than 3.

You are assuming that combination is not valid in other gps models (current and future).

tippfehlr commented 10 months ago

That is true, I was assuming that it was a limitation of the gnss itself (without having done research -_-) A note is fine I guess