GPS working in BF4.2 but not in BF4.3 RC3

[hugonaneix]

Describe the bug

Flywoo GOKU HD745 EVO 40A
Nameless Tiny GPS

When in BF4.2.x (tested 4.2.8 and 4.2.11) the GPS is correctly recognized and works as expected
When updated to BF4.3 RC3, no GPS is recognized by the FC/Betaflight Configurator
Connected to recommended UART 6 in documentation
No Telemetry output to the radio either (just in case it could have been a GUI flaw)
Wiring is ok
BF configuration is ok (worked in 4.2.x, and replicated in 4.3RC3)
Target board: FLYWOOF745
board_name: FLYWOOF745AIO [EDITED, was: FLYWOOF722EVO (typo)]

To Reproduce

Flash board to BF4.3 RC3
Configure GPS correctly
Observe the GPS is not recognized
gpspassthrough makes BF Configurator freeze

Expected behavior

GPS should work as expected

Flight controller configuration

Below are the 2 dumps

dump_4.2.11.txt
dump_4.3.txt

Flight controller

Flywoo GOKU HD745 EVO 40A

Other components

Nameless Tiny GPS

How are the different components wired up

Soldered on FC, plug on GPS

Add any other context about the problem that you think might be relevant here

No response

[jsk2084]

I have the same GPS on a Flywoo F745 Versatile. I recognize the GPS not working on latest development build (#2646) with similar config settings (Ublox). I changed protocol to NMEA and the GPS is now recognized on the Betaflight GUI.

Edit: Using NMEA may not be preferred, but want to confirm the issue hugpnaneix is having.

Second edit: After flashing development builds, I was able to pinpoint 4.3 #2580 as the build where Ublox protocol no longer works on this.

[hugonaneix]

@jsk2084 so can I assume this is an issue that will be adressed in future builds? Just want to help and not really a pro when it comes to dev collaboration ;)

[hugonaneix]

@jsk2084 I played with uCenter to try to change the GPS configuration, but forgot to backup its configuration...
if, by any chance you could attach your config in that thread that would be very appreciated
Here's how to do it: https://www.youtube.com/watch?v=zxMdOtspUGk&ab_channel=XR-4Drone

[jsk2084]

I imagine someone will look into the changes that broke it and come up with a fix eventually! I know nothing of coding, just a grateful user of Betaflight. I will try to get a default config of the gps device, though earlier I was having issue connecting it to the ucenter software.

[jsk2084]

After additional testing in latest development builds, I've determined that enabling auto-config with this NamelessRC TinyGPS in ublox protocol prevents it from working. Flashing build #2579 from Dec 20th 2021 and enabling auto-config there fixes the issue.

Leaving auto-config disabled seems to be required, otherwise the gps module settings become incompatible. I'm not sure if any other GPS module would be affected by this...

[haslinghuis]

@TonyBlit any idea? There seems to be an issue with #10921

[TonyBlit]

I've been looking for some info about this gps without success, all I found is the barest user manual I've ever seen. I'd need to know what ublox module this is using. However, I fear this may not be using a module manufactured by ublox.
Anyway, I've ordered one from fullspeed and it will take one or two weeks to arrive.
In the meantime, if anyone with this gps is willing to help, you can reach me on Discord (TonyBlitter on the BF server) and I can provide further instructions on how to debug what is happening.

[UglyBabyGaming]

Target board: FLYWOOF745
board_name FLYWOOF722EVO???
are you sure you got the right target?

[hugonaneix]

that's a typo, the board name is FLYWOOF745AIO

[ea-fpv]

Similar issue with RC7 here as reported in #11508 (comment) with HGLRC M80 wired to Betafpv405AIO

[haslinghuis]

@TonyBlit did you get the GPS and had the time to investigate?
As a cheap GPS module is it worth the buy?

[TonyBlit]

Yes I did bought one TinyGPS, but I'm still figuring out why some commands refuse to work.

What I can say for sure is these modules work totally fine:

• Beitian BN-220
• HGLRC Neo-M8N
• Matek SAM-M8Q
• Matek M9N-5883
• Flywoo GM8 Mini

For TinyGPS, I see a few commands are returning a NACK, and debugging this is very painful (compile and flash each try/change, unplugging the GPS every time) so it will take me a bit of time getting a proper fix.

However, in the meantime there is a quick workaround for that module: just disable auto-config. In practice there is little difference as I think the commands sent by BF 4.2 are failing as well so the module is ignoring them. 4.2 code was less strict and it ignored the NACKs, so it's not that it correctly worked in 4.2, it's that there was a nonsensical interchange of commands that was just ignored on both ends. 4.3 code is more strict, so meanwhile I find a clean fix disabling auto-config is quite equivalent to what happened in 4.2.

[haslinghuis]

Thanks for the list @TonyBlit and workaround.

[andytroy]

GPS OSD and GPS rescue are not working for me on RC7, using TBS M8 and Matek M8Q. In BF configurator the satellites are visible. It worked fine in RC6. The work around doesn’t work for me.

[Kriseye]

GPS OSD and GPS rescue are not working for me on production realease, using TBS M8 and Matek M8Q. In BF configurator the satellites are visible.

[TonyBlit]

@Kriseye @andytroy can you provide a clear explanation? if BF configurator shows satellites, it means the module is working.

[andytroy]

@Kriseye @andytroy can you provide a clear explanation? if BF configurator shows satellites, it means the module is working.

The DJI OSD is not showing any satellites, home direction etc. So the whole GPS thing is kinda useless right now for long range flights.

[dukevah]

I have been dealing with this GPS issue for a long time #11508. I flashed the latest release (4.3) and the issue is still there. Now, it detects the GPS but it becomes so unstable that every 10-24 seconds it loses the GPS (zero satellites suddenly) and gains them again. Buzzer beeps show it as well during the flight. This instability started to happen with the NMEA protocol. It seems the ublox protocol is doing ok so far. I disabled auto-config and it didn't help at all. Today, I lost a motor and frame while testing the rescue mode :-(
I use HAKRC F722 with a new HGLRC GPS (NMEA protocol).

[cronosrj]

Same problem here, my HGLRC M80PRO module works normally on BF4.2, but on 4.3 it is not recognized.

FC IFLIGHT_SUCCEX_E_F7
GPS HGLRC M80PRO

[cwchapma]

@cronosrj also having trouble with HGLRC M80PRO. Do you just get a single green flash when the gps powers up and then nothing?

[cwchapma]

Confirmed HGLRC M80PRO works on 4.2.11

but not 4.3.1

[TonyBlit]

@cwchapma if you use ublox protocol with autoconfig disabled, does it work? have you tried nmea?

[cwchapma]

Ublox with auto config disabled does not work. Also tried nmea and ublox at 9600 baud with no success.

[TonyBlit]

if nmea and ublox without autoconfig doesn't work, the problem is clearly unrelated with recent GPS ublox changes, and that would be better addressed in a new issue report. One thing I've noticed though is that all FC's reported so far are F7's. @cwchapma is it your case as well?

[cwchapma]

Yes, it's a speedybee F7

…

On Thu., Aug. 11, 2022, 2:15 a.m. TonyBlit, ***@***.***> wrote: if nmea and ublox without autoconfig doesn't work, the problem is clearly unrelated with recent GPS ublox changes, and that would be better addressed in a new issue report. One thing I've noticed though is that all FC's reported so far are F7's. @cwchapma <https://github.com/cwchapma> is it your case as well? — Reply to this email directly, view it on GitHub <#11453 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALWJQHRWPMNKI3RC2H4LB3VYSLBJANCNFSM5P63SYAQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[haslinghuis]

@TonyBlit FYI:

[LeoniePhiline]

If it helps finding the root cause:

I have an iFlight BLITZ mini f722 v1.0 working with both GNSS and mag on an iFlight M8Q-5883.
Using Betaflight 4.3.1.

This configuration works for me:

The module is powered by an external BEC.

Interestingly, the M8Q-5883 module was not recognized while the FC was only on USB power - even though the module had acquired a 3D fix as indicated by its onboard LED.

Applying LiPo voltage to the quad once, however, made the FC communicate with the module, with GPS and Mag lighting up in the top edge section of the BF configurator.

After having applied LiPo voltage once, however, USB power which had previously been insufficient was suddenly enough to make GPS and Mag work! The FC's behavior appears to be somewhat unpredictable (at least to me).

[cronosrj]

‎também ter problemas com o HGLRC M80PRO. Você só tem um único flash verde quando o GPS aumenta e depois nada?‎

I'm about to change the gps module to another one compatible with BF4.3... apparently this will not be resolved.

[cronosrj]

The M80 works normally.

[cronosrj]

Update?

[Ls4life]

I just like to add to this discussion that I have two FC, "skystars Mini F722 HD pro and the skystar F722HD pro3" and both FC gps stop working after I upgraded to Betaflight above 4.2. I have used the following GPS model: TBS M8-2, Beitian BN-160, BN-220, and Mateksys M8Q-5883. I tried different UART and verify the connectivity. I see some telemetry on my Radio but it will not show any Satellite info, I get not data on the Betafight GPS tap. It seem the info is not making it to the fc. Also I have to initiate the skystars fc on bootloader mode, because it will freeze if I try to upgrade when connected to betafight.

[ctzsnooze]

We have recently introduced significantly improved Betaflight to GPS hardware module connection and configuration code in Betaflight 4.5 zulu. We expect that most modern GPS units should now connect and work reliably. Please give it a try.

These changes will not be back-ported to 4.4.x

[Ls4life]

Thanks for all the help.

…

On Sun, May 12, 2024, 4:04 PM Mark Haslinghuis ***@***.***> wrote: Closed #11453 <#11453> as completed. — Reply to this email directly, view it on GitHub <#11453 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXE7HDCWCNBCWBQBAWN5YCDZB7DOHAVCNFSM5P63SYA2U5DIOJSWCZC7NNSXTWQAEJEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW4OZRGI3TOOJTGI4DENRY> . You are receiving this because you commented.Message ID: ***@***.***>