I've recently decided to get a GM10 GPS for my drone and went with a Goku GM10 mini V3 with compass. The FC I am using is the SpeedyBee F405 V3 stack.

On the wiring, I have double checked RX TX comnections, checked resistance between all connects to make sure there is no bridge. I have tried with SDA and SCL connected and without with no luck.

The GPS has a solid green led and a blinking red. I coudln't find anything only about indication, but the blinking red seems to be TX activity from a varely readable marking on the PCB.

GPS is connected to serial 6 which is set on 115200 baudrate as suggested by flywoo page.

Here is my get serial:

# get serial
serialrx_provider = SBUS
Allowed values: SPEK1024, SPEK2048, SBUS, SUMD, SUMH, XB-B, XB-B-RJ01, IBUS, JETIEXBUS, CRSF, SRXL, CUSTOM, FPORT, SRXL2, GHST
Default value: CRSF

serialrx_inverted = OFF
Allowed values: OFF, ON

serialrx_halfduplex = OFF
Allowed values: OFF, ON

serial_update_rate_hz = 100
Allowed range: 100 - 2000

vtx_softserial_alt = OFF
Allowed values: OFF, ON

serialmsp_halfduplex = OFF
Allowed values: OFF, ON



And here is my resources:

# resource show all
Currently active IO resource assignments:
(reboot to update)
--------------------
A00: SERIAL_TX 4
A01: SERIAL_RX 4
A02: FREE
A03: SERIAL_RX 2
A04: GYRO_CS 1
A05: SPI_SCK 1
A06: SPI_MISO 1
A07: SPI_MOSI 1
A08: FREE
A09: SERIAL_TX 1
A10: FREE
A11: USB
A12: USB
A13: SWD
A14: SWD
A15: FREE
B00: FREE
B01: FREE
B02: FREE
B03: FREE
B04: FREE
B05: FREE
B06: MOTOR 1
B07: MOTOR 2
B08: MOTOR 3
B09: MOTOR 4
B10: I2C_SCL 2
B11: I2C_SDA 2
B12: OSD_CS
B13: SPI_SCK 2
B14: SPI_MISO 2
B15: SPI_MOSI 2
C00: ADC_BATT
C01: ADC_CURR
C02: FREE
C03: PINIO 1
C04: GYRO_EXTI
C05: BEEPER
C06: SERIAL_TX 6
C07: SERIAL_RX 6
C08: LED 1
C09: FREE
C10: FREE
C11: FREE
C12: FREE
C13: FREE
C14: FREE
C15: FREE
D00: FREE
D01: FREE
D02: SERIAL_RX 5
D03: FREE
D04: FREE
D05: F: FREE
E03: FREE
E04: FREE
E05: FREE
E06: FREE
E07: FREE
E08: FREE
E09: FREE
E10: FREE
E11: FREE
E12: FREE
E13: FREE
E14: FREE
E15: FREE
F00: FREE
F01: FREE
F02: FREE
F03: FREE
F04: FREE
F05: FREE
F06: FREE
F07: FREE
F08: FREE
F09: FREE
F10: FREE
F11: FREE
F12: FREE
F13: FREE
F14: FREE
F15: FREE

Currently active Timers:
-----------------------
TIM1: FREE
TIM2: FREE
TIM3: FREE
TIM4:
CH1 : MOTOR 1
CH2 : MOTOR 2
CH3 : MOTOR 3
CH4 : MOTOR 4
TIM5: FREE
TIM6: FREE
TIM7: FREE
TIM8: FREE
TIM9: FREE
TIM10: FREE
TIM11: FREE
TIM12: FREE
TIM13: FREE
TIM14: FREE

Currently active DMA:
--------------------
DMA1 Stream 0: FREE
DMA1 Stream 1: FREE
DMA1 Stream 2: FREE
DMA1 Stream 3: SPI_MISO 2
DMA1 Stream 4: SPI_MOSI 2
DMA1 Stream 5: FREE
DMA1 Stream 6: TIMUP 4
DMA1 Stream 7: FREE
DMA2 Stream 0: ADC 1
DMA2



I am not aure what else I could try at this point

Another thing I just noticed is that the built-in barometer stops working if SCL is soldered on (Not lit yellow in betaflight)
Also, I have tried with a second identical unit with no luck.
Resoldered all data cables again with no luck.
Given all these, I assume it has to be something related to the FC such as configuration.

The issue seems similar to what was posted here, but it doesn't seem to be the exact same give @SnowLeopardFPV 's explanation there.

For GM10 type gps i suggest you load latest betaflight 4.5 development build, which recently got a huge update for type 10 gps detection and stability.
(of course backup and reload your settings before doing that)
Dont connect the sda/scl cables as compas is pretty useless for betaflight rth and actualy is strongly adviced against using it.
Also helps with your baro conflict when you dont connect these.

There's no 4.5 release yet for Betaflight. You suggest I load a pre-release build?

I could see why getting a more recent firmware might help, but I would prefer to stay on releases, and even then, I don't see why the GPS wouldn't be seen at all.

You can always flash back to your current release but then you know if its related to the M10 suport, whiich only since the last development builds has been majorly updated, not only for initial detection but also for stability and in flight connect disconnct issues and a billion more things.
I have about 10 quads with gps (7 of them are flywoo type 10 gps modules and 3 mateks type 10) and all of them fly 4.5 latest dev build specificaly for all the work done on gps support and rth stuff.
If it also does not work then you at least know its something else you need to figure out.
Uart 6 seems no problem as its even used as an example in the manual for the speedybee. Only make sure you have rx to tx and tx to rx and activate gps on the ports tab for uart 6 . Nothing special needed besides proper suport in betaflight.
You can try with different connect baud rates if you dont want to upgrad as that may sometimes help. Latest dev release solves that also automaticaly and scans all baud rates to find what the gps listens to.

Already made sure RX TX are wired properly, even tried reverse in case labeling was wrong. Same for trying all baudrates.
My main issue with flashing a different firemware is that I've managed to lose the USB-C connector on the FC and didn't pull myself yet to solder a new one. I guess I'll do that and try the firmware and come back afterward if it doesn't solve anything.
Thanks a lot for all the input!

Ah that sucks with the USB connector.
Good luck and hope you eventualy get it sorted.

If they get flashing firmware working from the phone, SpeedyBee will be really amazing.

(02-Sep-2023, 07:01 AM)Cristaling Wrote: If they get flashing firmware working from the phone, SpeedyBee will be really amazing.

Yeah i got speedybee adaptor on a few birds, but in the end i am not realy using it.
Flashing would be cool for USB broken situations.
Other than that, nowadays you can adjust almost 100% of betaflights parameters right from the OSD via the recent OSD menu updates. All my tuning and even gps setting i do just via that now. 
Also its always up to date while (as i am almost always running latest dev releases) speedybee only supports the latest current stable version.
And flashing wise, sometimes flashing from betaflight configurator does not work right with speedybee adapter installed as during dfu boot that bluetooth thing steals the connection and requires multiple attempts. GPS modules also can do that if connected to uart 3 for example (known issue) . Depends a bit on FC and uart , but can be a pain in the but.
So may in the end remove it from all (unless inbuild like in the speedybee stacks)