betaflight VS betaflight

Op, it seems your gps has m10 chipset, am I right? Because the m10 is not supported on betaflight. Or rather, it works, but betaflight sets it up incorrectly. There is a fix, but not released yet, or you have to set gps to 10hz in ucenter and disable auto convig in betaflight (and lose some features). See https://github.com/betaflight/betaflight/issues/12737 for more information. This might not be your issue, but it might be related.

I got older betaflight configurator 10.3.1 and when I look at boards in firmware flasher there's a small selection of boards and OMNIBUS is missing. So I've downloaded .hex file from here https://github.com/betaflight/betaflight/releases/tag/4.0.0 for 4.0.0 and tried to flash it from local file but nothing happens in betaflight and the quad has a constant beep sound. When I disconnect it from usb and reconnect it still works fine but its on old 3.1.0 version. I'm not sure what to do here.

Which typically run open source firmware called Betaflight https://github.com/betaflight/betaflight

I think the rc.c file has what you’re looking for.

It’s a known issue specific with the M10. I think there a workaround if you need it asap. https://github.com/betaflight/betaflight/issues/12737

Sorry for missing your question, here's a link to the PR: https://github.com/betaflight/betaflight/pull/12738

github-issue

Blackbox logging doesn’t work reliably since the Blackbox and OSD use the same SPI bus (https://github.com/betaflight/betaflight/issues/12583)

You can select between PID profiles 1, 2, or 3 via the OSD or stick commands fairly easily, and there are options to modify the individual P, I, and D terms per axis in flight using AUX channels via the adjustments tab. If you want the option to configure a 3-posiiton switch to select between PID profiles like you currently can with rate profiles, maybe bump the thread for the BF devs here.

I looked on GitHub for a similiar Issue with Darwin AiOs just now and found this from January 6th concercing 4.4 Update Errors with Accel/Gyro: https://github.com/betaflight/betaflight/issues/12145

I had to do this exact thing the other day. Using ELRS 3.0 updating the Firmware on the Cetus X to This using the betaflight program. I had to then change to ESC config Follow the betaFPV's Website on the Flight controller. Using the C_X_30_48_V0.18.1.hex they provide on the website

Release Betaflight 4.3.1 with ELRS 3.0 SPI Support · DLLarson/betaflight · GitHub

Just putting this out there.. you do NOT need to flash a nightly BF 4.4 build to get spi elrs 3.x.x. You can do it by flashing this modified BF 4.3.1 release, which includes the ELRS 3.0 code: https://github.com/DLLarson/betaflight/releases/tag/BF-4.3.1-with-elrs-3.0

Check out https://github.com/DLLarson/betaflight/releases/tag/BF-4.3.1-with-elrs-3.0

It will cause problems. Best bet is to install a version of Betaflight that contains ELRS 3.0 support. Watch https://youtu.be/bPbPCyjhE1Q but instead of using unreleased Betaflight 4.4, you probably want to use https://github.com/DLLarson/betaflight/releases/tag/BF-4.3.1-with-elrs-3.0 as per the first comment under the video.

I tried updating the firmware with this https://github.com/DLLarson/betaflight/releases, but i got no gyro detected after flashing. I followed this tutorial https://www.youtube.com/watch?v=bPbPCyjhE1Q.

One thing I'm not seeing is anything about 3.x being compatible at all with 4.3.2, let alone the only ELRS being compatible. I see Phobos' PR is in betaflight's master branch right now, but nothing in any documentation or release notes. Folks on the ELRS discord were saying Betaflight 4.3.x -> ELRS 2.x and Betaflight 4.4.x -> ELRS 3.x as of this morning. I'm seeing forks of Betaflight that include ELRS 3.x support on top of Betaflight 4.3.x, but I'd steer clear of that unless you really know what you're doing.