betaflight_processing VS betaflight

This is a nice chart by mrRobot62 on github how signal processing in betaflight v4.2 works: https://github.com/mrRobot62/betaflight_processing/blob/master/bf-4.2_processing-workflow.png?raw=true

This is a processing chart of the betaflight controller. It basically shows what elements the signal gets processed by to calculate the motor outputs. I didn't know this existed... Apparently someone put in the effort to put it all together. Pretty cool IMO. https://github.com/mrRobot62/betaflight_processing

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