Black Bird FPV "Next Level" Sbang Tune Preset for 4.5 and 2025.12 #540
Conversation
📝 WalkthroughWalkthroughAdds two new Betaflight tune presets named blackbird_nextlevel for firmware versions 2025.12 and 4.5; each file contains full metadata, extensive PID/filter/motor/RC settings, multiple mutually-exclusive option groups, and includes of baseline/default fragments. Changes
Sequence Diagram(s)(Skipped — changes are configuration presets without multi-component control-flow warranting a sequence diagram.) Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Suggested reviewers
Poem
Pre-merge checks✅ Passed checks (3 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
presets/4.5/tune/blackbird_nextlevel.txt (1)
76-93: Remove duplicate filter configuration lines.Lines 77–78 and 83–84 redundantly set
gyro_lpf1_dyn_min_hzandgyro_lpf1_dyn_max_hzto the same values. Eliminate the duplication at lines 83–84.🔎 Proposed cleanup
set gyro_lpf1_static_hz = 300 set gyro_lpf1_dyn_min_hz = 0 set gyro_lpf1_dyn_max_hz = 0 set gyro_lpf2_static_hz = 0 set dyn_notch_count = 1 set dyn_notch_q = 500 set dyn_notch_min_hz = 150 -set gyro_lpf1_dyn_min_hz = 0 -set gyro_lpf1_dyn_max_hz = 0 set simplified_gyro_filter = OFFpresets/2025.12/tune/blackbird_nextlevel.txt (1)
76-93: Remove duplicate filter configuration lines.Lines 77–78 and 83–84 redundantly set
gyro_lpf1_dyn_min_hzandgyro_lpf1_dyn_max_hzto the same values. Eliminate the duplication at lines 83–84 (identical to the 4.5 file).🔎 Proposed cleanup
set gyro_lpf1_static_hz = 300 set gyro_lpf1_dyn_min_hz = 0 set gyro_lpf1_dyn_max_hz = 0 set gyro_lpf2_static_hz = 0 set dyn_notch_count = 1 set dyn_notch_q = 500 set dyn_notch_min_hz = 150 -set gyro_lpf1_dyn_min_hz = 0 -set gyro_lpf1_dyn_max_hz = 0 set simplified_gyro_filter = OFF
📜 Review details
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
presets/2025.12/tune/blackbird_nextlevel.txtpresets/4.5/tune/blackbird_nextlevel.txt
🧰 Additional context used
🧠 Learnings (4)
📓 Common learnings
Learnt from: bensonk
Repo: betaflight/firmware-presets PR: 509
File: presets/4.5/osd/bensonk.txt:138-152
Timestamp: 2025-05-25T22:26:17.328Z
Learning: BrainFPV commands in Betaflight preset files are safely ignored on non-BrainFPV flight controllers, making it safe to include them in presets even when they might be applied to different hardware.
Learnt from: Jaz7Mutant
Repo: betaflight/firmware-presets PR: 512
File: presets/4.5/tune/basher_jazzmutant_tune.txt:118-119
Timestamp: 2025-06-20T20:39:08.723Z
Learning: In Betaflight firmware presets, rates defaults from presets/4.3/rates/defaults.txt are used across multiple firmware versions including 4.5, as the file explicitly declares support for firmware versions 4.3, 4.4, and 4.5. There is no separate defaults.txt file in presets/4.5/rates/ directory.
Learnt from: Jaz7Mutant
Repo: betaflight/firmware-presets PR: 512
File: presets/4.5/tune/basher_jazzmutant_tune.txt:1-8
Timestamp: 2025-06-20T18:08:54.334Z
Learning: In Betaflight firmware preset files, embedded double quotes in metadata fields like TITLE and KEYWORDS (e.g., `5"`, `3" to 5"`, `8"/9"`) are standard and do not need escaping. The preset parser handles this syntax correctly as evidenced by widespread usage throughout the codebase.
📚 Learning: 2025-05-25T22:26:17.328Z
Learnt from: bensonk
Repo: betaflight/firmware-presets PR: 509
File: presets/4.5/osd/bensonk.txt:138-152
Timestamp: 2025-05-25T22:26:17.328Z
Learning: BrainFPV commands in Betaflight preset files are safely ignored on non-BrainFPV flight controllers, making it safe to include them in presets even when they might be applied to different hardware.
Applied to files:
presets/2025.12/tune/blackbird_nextlevel.txtpresets/4.5/tune/blackbird_nextlevel.txt
📚 Learning: 2025-06-20T20:39:08.723Z
Learnt from: Jaz7Mutant
Repo: betaflight/firmware-presets PR: 512
File: presets/4.5/tune/basher_jazzmutant_tune.txt:118-119
Timestamp: 2025-06-20T20:39:08.723Z
Learning: In Betaflight firmware presets, rates defaults from presets/4.3/rates/defaults.txt are used across multiple firmware versions including 4.5, as the file explicitly declares support for firmware versions 4.3, 4.4, and 4.5. There is no separate defaults.txt file in presets/4.5/rates/ directory.
Applied to files:
presets/2025.12/tune/blackbird_nextlevel.txtpresets/4.5/tune/blackbird_nextlevel.txt
📚 Learning: 2025-06-20T18:08:54.334Z
Learnt from: Jaz7Mutant
Repo: betaflight/firmware-presets PR: 512
File: presets/4.5/tune/basher_jazzmutant_tune.txt:1-8
Timestamp: 2025-06-20T18:08:54.334Z
Learning: In Betaflight firmware preset files, embedded double quotes in metadata fields like TITLE and KEYWORDS (e.g., `5"`, `3" to 5"`, `8"/9"`) are standard and do not need escaping. The preset parser handles this syntax correctly as evidenced by widespread usage throughout the codebase.
Applied to files:
presets/2025.12/tune/blackbird_nextlevel.txtpresets/4.5/tune/blackbird_nextlevel.txt
🔇 Additional comments (8)
presets/4.5/tune/blackbird_nextlevel.txt (3)
1-54: Well-structured metadata and includes.The header, description, and warning sections are clear and comprehensive. The preset correctly documents the aggressive nature of the tune and provides actionable guidance for hardware compatibility. Embedded double quotes in the KEYWORDS field (e.g.,
5") are standard and properly formatted.
203-212: The rc_link presets referenced are correct for Betaflight 4.5. The preset files atpresets/4.3/rc_link/generic/(50hz_hd_freestyle.txt, 150hz_hd_freestyle.txt, 250hz_hd_freestyle.txt, 500hz_hd_freestyle.txt) explicitly declare support for firmware versions 4.3, 4.4, and 4.5 in their metadata, making them properly applicable across these versions. No separate 4.5 rc_link directory is needed.
228-279: Reset values correctly match Betaflight 4.5 firmware defaults.The reset section (lines 228–279) restores firmware defaults as intended. All verified values—including
d_roll = 40,d_pitch = 46,d_min_roll = 30,d_min_pitch = 34, and others—match the official defaults in presets/4.5/tune/defaults.txt. These correctly differ from the preset values (e.g.,d_roll = 37,d_pitch = 40), ensuring that toggling the reset option reverts only to firmware defaults, not to the preset's tuned values.presets/2025.12/tune/blackbird_nextlevel.txt (5)
1-54: Well-structured metadata and appropriate includes for 2025.12.The header and description are identical to the 4.5 version (appropriately so for firmware compatibility documentation). The includes correctly reference 2025.12-specific tune defaults while reusing 4.5 filter defaults, which aligns with the PR objective of "adjusted for new tune defaults, renamed Dmin/Dmax parameters, and updated rc_link presets."
98-98: Motor idle parameter correctly renamed for 2025.12.The main config and propeller options correctly use
motor_idle(lines 98, 182, 185) instead of the 4.5 parameter namedshot_idle_value. This aligns with the Betaflight 2025.12 API changes.Also applies to: 182-182, 185-185
203-212: rc_link preset paths are correct. All referenced files (50hz_hd_freestyle.txt, 150hz_hd_freestyle.txt, 250hz_hd_freestyle.txt, 500hz_hd_freestyle.txt) exist in presets/2025.12/rc_link/generic/ as included.
59-66: Parameter naming correctly updated for Betaflight 2025.12.The preset uses
d_pitch,d_roll,d_max_roll, andd_max_pitch—the correct parameter names for 2025.12. This aligns with the framework's shift fromd_min_*(4.5) tod_max_*(2025.12). All parameters are valid and match the 2025.12 defaults specification.
228-279: Remove the incorrect explanation about firmware defaults changing.The reset values in lines 228–279 are preset-specific tuning parameters, not Betaflight firmware defaults. These parameters (
feedforward_averagingandfeedforward_smooth_factor) do not appear in the officialpresets/2025.12/tune/defaults.txtorpresets/4.5/tune/defaults.txtfiles. The differences between the 4.5 and 2025.12 versions of this preset reflect evolving tuning choices by the preset author, not changes to firmware defaults.Likely an incorrect or invalid review comment.
|
Looks good to me for the Experimental category as this approach may not work with all builds as stated...only thing I might suggest is to set the 'Low Quality' build to use two dynamic notches with Q400. This will help those who want to fly it but have more resonant frames. The difference in latency will be small. |
@saturn-fpv can you share the comparison logs |
|
Thanks for the quick review! @SupaflyFPV I like your suggestion, I will make those changes right away.
Yes, absolutely. They were done on two different days, but same quad (Jeno 5.1 with GTS v4 1960kv and J37 props) and same Halo ESC settings (AM32 2.19 24-48khz pwm). |
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
presets/4.5/tune/blackbird_nextlevel.txt (1)
77-84: Remove duplicate filter parameter assignments (also present in 4.5).Lines 83–84 duplicate lines 77–78 by re-setting
gyro_lpf1_dyn_min_hzandgyro_lpf1_dyn_max_hzto zero. This same issue appears in both the 2025.12 and 4.5 versions.🔎 Proposed fix: remove duplicate lines
set gyro_lpf1_static_hz = 300 set gyro_lpf1_dyn_min_hz = 0 set gyro_lpf1_dyn_max_hz = 0 set gyro_lpf2_static_hz = 0 set dyn_notch_count = 1 set dyn_notch_q = 500 set dyn_notch_min_hz = 150 - set gyro_lpf1_dyn_min_hz = 0 - set gyro_lpf1_dyn_max_hz = 0 set simplified_gyro_filter = OFF
📜 Review details
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
presets/2025.12/tune/blackbird_nextlevel.txtpresets/4.5/tune/blackbird_nextlevel.txt
🧰 Additional context used
🧠 Learnings (4)
📓 Common learnings
Learnt from: bensonk
Repo: betaflight/firmware-presets PR: 509
File: presets/4.5/osd/bensonk.txt:138-152
Timestamp: 2025-05-25T22:26:17.328Z
Learning: BrainFPV commands in Betaflight preset files are safely ignored on non-BrainFPV flight controllers, making it safe to include them in presets even when they might be applied to different hardware.
Learnt from: Jaz7Mutant
Repo: betaflight/firmware-presets PR: 512
File: presets/4.5/tune/basher_jazzmutant_tune.txt:118-119
Timestamp: 2025-06-20T20:39:08.723Z
Learning: In Betaflight firmware presets, rates defaults from presets/4.3/rates/defaults.txt are used across multiple firmware versions including 4.5, as the file explicitly declares support for firmware versions 4.3, 4.4, and 4.5. There is no separate defaults.txt file in presets/4.5/rates/ directory.
Learnt from: Jaz7Mutant
Repo: betaflight/firmware-presets PR: 512
File: presets/4.5/tune/basher_jazzmutant_tune.txt:1-8
Timestamp: 2025-06-20T18:08:54.334Z
Learning: In Betaflight firmware preset files, embedded double quotes in metadata fields like TITLE and KEYWORDS (e.g., `5"`, `3" to 5"`, `8"/9"`) are standard and do not need escaping. The preset parser handles this syntax correctly as evidenced by widespread usage throughout the codebase.
📚 Learning: 2025-06-20T20:39:08.723Z
Learnt from: Jaz7Mutant
Repo: betaflight/firmware-presets PR: 512
File: presets/4.5/tune/basher_jazzmutant_tune.txt:118-119
Timestamp: 2025-06-20T20:39:08.723Z
Learning: In Betaflight firmware presets, rates defaults from presets/4.3/rates/defaults.txt are used across multiple firmware versions including 4.5, as the file explicitly declares support for firmware versions 4.3, 4.4, and 4.5. There is no separate defaults.txt file in presets/4.5/rates/ directory.
Applied to files:
presets/4.5/tune/blackbird_nextlevel.txtpresets/2025.12/tune/blackbird_nextlevel.txt
📚 Learning: 2025-05-25T22:26:17.328Z
Learnt from: bensonk
Repo: betaflight/firmware-presets PR: 509
File: presets/4.5/osd/bensonk.txt:138-152
Timestamp: 2025-05-25T22:26:17.328Z
Learning: BrainFPV commands in Betaflight preset files are safely ignored on non-BrainFPV flight controllers, making it safe to include them in presets even when they might be applied to different hardware.
Applied to files:
presets/4.5/tune/blackbird_nextlevel.txtpresets/2025.12/tune/blackbird_nextlevel.txt
📚 Learning: 2025-06-20T18:08:54.334Z
Learnt from: Jaz7Mutant
Repo: betaflight/firmware-presets PR: 512
File: presets/4.5/tune/basher_jazzmutant_tune.txt:1-8
Timestamp: 2025-06-20T18:08:54.334Z
Learning: In Betaflight firmware preset files, embedded double quotes in metadata fields like TITLE and KEYWORDS (e.g., `5"`, `3" to 5"`, `8"/9"`) are standard and do not need escaping. The preset parser handles this syntax correctly as evidenced by widespread usage throughout the codebase.
Applied to files:
presets/4.5/tune/blackbird_nextlevel.txtpresets/2025.12/tune/blackbird_nextlevel.txt
🔇 Additional comments (4)
presets/2025.12/tune/blackbird_nextlevel.txt (2)
173-179: Low Quality Build option correctly implements feedback.The option appropriately applies dynamic notch filtering with Q=400 and two notches as suggested in the PR review, helping more resonant frames while managing latency impact.
245-246: Verify intentional tuning difference in feedforward_smooth_factor between firmware versions.The reset-to-defaults option sets
feedforward_smooth_factor = 65in 2025.12 (line 246) but25in 4.5 (line 246)—a 2.6× difference. These are explicit preset values rather than inherited firmware defaults. Confirm this tuning adjustment is intentional for the 2025.12 firmware version, not an oversight.presets/4.5/tune/blackbird_nextlevel.txt (2)
59-66: Verify: Bothd_min_*andd_*parameters are set throughout.The file consistently sets both parameter naming conventions (e.g.,
d_min_pitchandd_pitchfor the same tuning concept) across all PID sections and options. Confirm whether Betaflight 4.5 firmware requires both parameter names to be set, or if only one naming convention should be used.
204-215: Verify RC link preset versions referenced in 4.5 file.The Radio Link options include
presets/4.3/rc_link/generic/*rather thanpresets/4.5/rc_link/generic/*. While backward compatibility is used elsewhere (e.g., filter defaults), confirm that 4.3 rc_link presets are the correct choice for 4.5 firmware and are compatible/available.
thanks - it might be a bit over-pid - what was the weight of your quad all up? The LPF1 should also be off so maybe I need to check |
@SupaflyFPV 750g with Action 2. |
Actually yes only if you want to, but I think it would be better to use RPM notch 1 and 3 which are the most noisy motor harmonics when using triblades - with a higher Q - (Q500 is wider than neccessary for 5") set rpm_filter_harmonics = 3 This will give better filtering and lower latency |
Thanks for the suggestion! Those settings are definitely reasonable and I understand the rationale behind them, especially for triblades. That said, for this preset the goal was to reflect the original BlackBird FPV tune as closely as possible, so pilots applying it get what they’re expecting based on the source. For that reason I’m inclined to keep the RPM filtering as-is. |
|
One comment: I'm french and also watched BB Next Level Tune video in french. I don't want to create a drama... Just informing you that he already tried to suggest adding this preset to BF Preset. This had been rejected. |
Thanks for your comment. I am well aware. He mentioned that in english version, too. But he never opened a PR, and we don't know how the discussion went. So a few things:
So what's your experience with this preset and what improvement suggestion do you have? Was there anything else in the french version that you suggest to have included in this preset? I have posted this preset in the facebook sbang group for pilots to try, and from Damien himself and others I have only heard positive feedback. |
it wasn't outright rejected, we spoke about it at the time but he decided to release direct I spoke more with the development team and they said it was fine in the experimental category so this fits no problem. It's nice to have a Blackbird Preset in the Betaflight repo. I assumend @saturn-fpv was contributing on behalf of Damien - and had his blessing. Is this all ok? |
Into the english version, there are some comments regarding to his discussion with the BF team which are missing. If you take a moment to look at this specific part I added for information, you could make your own opinion. "BF Devs don't know how a quad flies, works" "They do know codding, but they don't know how to make a roll / flip"... From a known YTber, these kind of words do not make any sense when speaking about some people who spend their free time to provide us for free a flight controller firmware. Regarding to some settings, 'Thrust Linear = 1..." --> It does not impact the throttle at all. It boosts PID from 0%... but it's def not linear at all. 1% is def placebo. Double BIQUAD filter on DTerm filtering, whereas you are looking for less filtering latency, no sense neither. Supafly here and other do not make any tune without looking at logs. When some guys promote some tunes, they should take care about all these parameters and understand how they impact flight characteristics. I read also on some FB groups that a lot of people experienced some troubles with this tune. I'm not on the "top FPV pilots" but I like to understand how BF works. Looking at this tune, I went away and never tried it, because lot of misunderstanding are in. I'm also not this kind of people who apply blindly something... He said" just copy and paste and don't ask"... Woow. Now, hope you have a better view about my concerns and my approach to warn about this. Finally, if some folks enjoy this tune, no problem. I'm ok (who I am to avoid anyone having fun... indeed, I'm a simple random FPV pilot lol). |
I understand what you say and agree in some aspects. However - we at the team decided in the Experimental category we can try things and keep an open mind. Let's see how it goes. I also understand what Damien is trying to achieve and maybe this can start some conversation about doing the approach 'by textbook' and doing the approach by raw feel. Both have some validity. |
No problem, Let's see how it goes. Anyway, as I said, if some are happy with this tune, no issues. |
lols forget the top 3 tuners in the whole world are BF devs and NOT YouTubers.. any one saying this crap should not be taken seriously at all ..... |
| #$ OPTION_GROUP END | ||
|
|
||
| #$ OPTION_GROUP BEGIN: (EXCLUSIVE) Radio Link | ||
| #$ OPTION BEGIN (CHECKED): BB Stick Feel |
There was a problem hiding this comment.
please make unchecked since it's not part of the tune
| #$ OPTION_GROUP END | ||
|
|
||
| #$ OPTION_GROUP BEGIN: (EXCLUSIVE) Deadband | ||
| #$ OPTION BEGIN (CHECKED): For high Center Rates |
There was a problem hiding this comment.
please, make unchecked by default
| #$ WARNING: **DO NOT** select this preset unless your ESCs support Bi-Directional DSHOT communication! **WARNING:** This is an aggressive tune that may cause overheating motors, oscillations, or flyaways if applied to unsuitable hardware. Apply cautiously and test thoroughly. | ||
|
|
||
| # -- Includes -- | ||
| #$ INCLUDE: presets/4.5/filters/defaults.txt |
There was a problem hiding this comment.
please include 2025 defaults in 2025 preset
There was a problem hiding this comment.
we are using 4.5 filter defaults in 2025.12 as they are the same parameters
There was a problem hiding this comment.
please include 2025 defaults in 2025 preset
Thanks for checking the preset.
There are no 2025 filter defaults as far as I can see. The Supafly presets as well as UAVTech presets also use a mix of 4.5 filters and 2025 tune. I think the filter defaults haven't changed (names, values)?
About the checked options: Yes I'll change those to unchecked. Good point!
There was a problem hiding this comment.
we are using 4.5 filter defaults in 2025.12 as they are the same parameters
oh nice i didn't know that!
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
presets/2025.12/tune/blackbird_nextlevel.txtpresets/4.5/tune/blackbird_nextlevel.txt
🚧 Files skipped from review as they are similar to previous changes (1)
- presets/2025.12/tune/blackbird_nextlevel.txt
🧰 Additional context used
🧠 Learnings (11)
📓 Common learnings
Learnt from: spatzengr
Repo: betaflight/firmware-presets PR: 0
File: :0-0
Timestamp: 2025-12-29T17:25:33.791Z
Learning: In the betaflight/firmware-presets repository, when a preset is updated across firmware versions, the #$ DISCUSSION field should continue to reference the original PR where the preset was first introduced (e.g., PR #210), not the current update PR (e.g., PR #554), to keep all preset-related discussions and feedback centralized in one location.
Learnt from: spatzengr
Repo: betaflight/firmware-presets PR: 0
File: :0-0
Timestamp: 2025-12-29T04:01:38.863Z
Learning: When creating derivative Betaflight presets, the #$ DISCUSSION field should reference the original preset PR number (e.g., PR #202) to maintain preset lineage, not the current PR being reviewed.
Learnt from: bensonk
Repo: betaflight/firmware-presets PR: 509
File: presets/4.5/osd/bensonk.txt:138-152
Timestamp: 2025-05-25T22:26:17.328Z
Learning: BrainFPV commands in Betaflight preset files are safely ignored on non-BrainFPV flight controllers, making it safe to include them in presets even when they might be applied to different hardware.
Learnt from: spatzengr
Repo: betaflight/firmware-presets PR: 0
File: :0-0
Timestamp: 2025-12-29T04:01:38.863Z
Learning: In Betaflight firmware presets, filter defaults from presets/4.5/filters/defaults.txt are shared across firmware versions including 2025.12, as there is no separate defaults.txt file in presets/2025.12/filters/ directory.
Learnt from: haslinghuis
Repo: betaflight/firmware-presets PR: 0
File: :0-0
Timestamp: 2025-12-29T18:54:48.142Z
Learning: In the betaflight/firmware-presets repository (and all Betaflight repositories), preset files use space characters for indentation (typically 2 spaces), not tabs. This is the standard across all firmware versions including 4.5 and 2025.12.
Learnt from: spatzengr
Repo: betaflight/firmware-presets PR: 0
File: :0-0
Timestamp: 2025-12-29T13:48:41.244Z
Learning: In UAV Tech Betaflight presets, the option label "low Build Quality" uses lowercase 'l' by design and is the established pattern across all UAV Tech presets in versions 4.4, 4.5, and 2025.12.
Learnt from: haslinghuis
Repo: betaflight/firmware-presets PR: 0
File: :0-0
Timestamp: 2025-12-29T18:02:44.149Z
Learning: Contributor spatzengr uses Windows for development work in the betaflight/firmware-presets repository. When providing file modification commands or scripts, provide Windows-compatible solutions (PowerShell) rather than Linux/macOS commands (sed, bash).
Learnt from: Jaz7Mutant
Repo: betaflight/firmware-presets PR: 512
File: presets/4.5/tune/basher_jazzmutant_tune.txt:118-119
Timestamp: 2025-06-20T20:39:08.723Z
Learning: In Betaflight firmware presets, rates defaults from presets/4.3/rates/defaults.txt are used across multiple firmware versions including 4.5, as the file explicitly declares support for firmware versions 4.3, 4.4, and 4.5. There is no separate defaults.txt file in presets/4.5/rates/ directory.
Learnt from: Jaz7Mutant
Repo: betaflight/firmware-presets PR: 512
File: presets/4.5/tune/basher_jazzmutant_tune.txt:1-8
Timestamp: 2025-06-20T18:08:54.334Z
Learning: In Betaflight firmware preset files, embedded double quotes in metadata fields like TITLE and KEYWORDS (e.g., `5"`, `3" to 5"`, `8"/9"`) are standard and do not need escaping. The preset parser handles this syntax correctly as evidenced by widespread usage throughout the codebase.
Learnt from: spatzengr
Repo: betaflight/firmware-presets PR: 0
File: :0-0
Timestamp: 2025-12-29T13:49:52.463Z
Learning: In UAV Tech presets, the filter option "low Build Quality" uses lowercase "low" intentionally. This is the consistent naming convention across all UAV Tech preset files (4.3, 4.4, 4.5, and 2025.12 versions).
📚 Learning: 2025-12-29T04:01:38.863Z
Learnt from: spatzengr
Repo: betaflight/firmware-presets PR: 0
File: :0-0
Timestamp: 2025-12-29T04:01:38.863Z
Learning: In Betaflight firmware presets, filter defaults from presets/4.5/filters/defaults.txt are shared across firmware versions including 2025.12, as there is no separate defaults.txt file in presets/2025.12/filters/ directory.
Applied to files:
presets/4.5/tune/blackbird_nextlevel.txt
📚 Learning: 2025-12-29T17:25:33.791Z
Learnt from: spatzengr
Repo: betaflight/firmware-presets PR: 0
File: :0-0
Timestamp: 2025-12-29T17:25:33.791Z
Learning: In the betaflight/firmware-presets repository, when a preset is updated across firmware versions, the #$ DISCUSSION field should continue to reference the original PR where the preset was first introduced (e.g., PR #210), not the current update PR (e.g., PR #554), to keep all preset-related discussions and feedback centralized in one location.
Applied to files:
presets/4.5/tune/blackbird_nextlevel.txt
📚 Learning: 2025-06-20T20:39:08.723Z
Learnt from: Jaz7Mutant
Repo: betaflight/firmware-presets PR: 512
File: presets/4.5/tune/basher_jazzmutant_tune.txt:118-119
Timestamp: 2025-06-20T20:39:08.723Z
Learning: In Betaflight firmware presets, rates defaults from presets/4.3/rates/defaults.txt are used across multiple firmware versions including 4.5, as the file explicitly declares support for firmware versions 4.3, 4.4, and 4.5. There is no separate defaults.txt file in presets/4.5/rates/ directory.
Applied to files:
presets/4.5/tune/blackbird_nextlevel.txt
📚 Learning: 2025-12-29T04:01:38.863Z
Learnt from: spatzengr
Repo: betaflight/firmware-presets PR: 0
File: :0-0
Timestamp: 2025-12-29T04:01:38.863Z
Learning: When creating derivative Betaflight presets, the #$ DISCUSSION field should reference the original preset PR number (e.g., PR #202) to maintain preset lineage, not the current PR being reviewed.
Applied to files:
presets/4.5/tune/blackbird_nextlevel.txt
📚 Learning: 2025-12-29T18:54:48.142Z
Learnt from: haslinghuis
Repo: betaflight/firmware-presets PR: 0
File: :0-0
Timestamp: 2025-12-29T18:54:48.142Z
Learning: In the betaflight/firmware-presets repository (and all Betaflight repositories), preset files use space characters for indentation (typically 2 spaces), not tabs. This is the standard across all firmware versions including 4.5 and 2025.12.
Applied to files:
presets/4.5/tune/blackbird_nextlevel.txt
📚 Learning: 2025-05-25T22:26:17.328Z
Learnt from: bensonk
Repo: betaflight/firmware-presets PR: 509
File: presets/4.5/osd/bensonk.txt:138-152
Timestamp: 2025-05-25T22:26:17.328Z
Learning: BrainFPV commands in Betaflight preset files are safely ignored on non-BrainFPV flight controllers, making it safe to include them in presets even when they might be applied to different hardware.
Applied to files:
presets/4.5/tune/blackbird_nextlevel.txt
📚 Learning: 2025-06-20T18:08:54.334Z
Learnt from: Jaz7Mutant
Repo: betaflight/firmware-presets PR: 512
File: presets/4.5/tune/basher_jazzmutant_tune.txt:1-8
Timestamp: 2025-06-20T18:08:54.334Z
Learning: In Betaflight firmware preset files, embedded double quotes in metadata fields like TITLE and KEYWORDS (e.g., `5"`, `3" to 5"`, `8"/9"`) are standard and do not need escaping. The preset parser handles this syntax correctly as evidenced by widespread usage throughout the codebase.
Applied to files:
presets/4.5/tune/blackbird_nextlevel.txt
📚 Learning: 2025-12-29T13:48:41.244Z
Learnt from: spatzengr
Repo: betaflight/firmware-presets PR: 0
File: :0-0
Timestamp: 2025-12-29T13:48:41.244Z
Learning: In UAV Tech Betaflight presets, the option label "low Build Quality" uses lowercase 'l' by design and is the established pattern across all UAV Tech presets in versions 4.4, 4.5, and 2025.12.
Applied to files:
presets/4.5/tune/blackbird_nextlevel.txt
📚 Learning: 2025-12-29T18:02:44.149Z
Learnt from: haslinghuis
Repo: betaflight/firmware-presets PR: 0
File: :0-0
Timestamp: 2025-12-29T18:02:44.149Z
Learning: Contributor spatzengr uses Windows for development work in the betaflight/firmware-presets repository. When providing file modification commands or scripts, provide Windows-compatible solutions (PowerShell) rather than Linux/macOS commands (sed, bash).
Applied to files:
presets/4.5/tune/blackbird_nextlevel.txt
📚 Learning: 2025-12-29T13:50:53.977Z
Learnt from: spatzengr
Repo: betaflight/firmware-presets PR: 0
File: :0-0
Timestamp: 2025-12-29T13:50:53.977Z
Learning: In UAV Tech Betaflight presets, the capitalization "withOUT" (with capital OUT) in preset titles is intentional and used for emphasis when highlighting the absence of an item (e.g., "withOUT GoPro"). This design choice should not be flagged as a style issue.
Applied to files:
presets/4.5/tune/blackbird_nextlevel.txt
🔇 Additional comments (3)
presets/4.5/tune/blackbird_nextlevel.txt (3)
56-91: PID and filter configuration appears sound and intentionally aggressive.The tuning aligns with the preset's documented aggressive "Next Level" philosophy: elevated P/I gains, low D values, and strong filtering for high-KV 5-inch quads. Parameters use correct Betaflight 4.5 naming conventions.
104-322: Option groups are well-structured and provide comprehensive tuning paths.The six mutually exclusive option groups plus reset options offer flexible configuration while maintaining preset coherence. Default values reset options (lines 228–321) properly include all affected settings to restore Betaflight 4.5 baseline behavior.
228-321: Reset options correctly implement official Betaflight 4.5 factory defaults.The tune parameters in both reset options match the official defaults from presets/4.5/tune/defaults.txt (p_pitch=47, i_pitch=84, d_min_pitch=34, p_roll=45, i_roll=80, d_min_roll=30, p_yaw=45, i_yaw=80, d_roll=40, d_pitch=46, d_max_advance=20, iterm_relax_cutoff=15, throttle_boost=5, thrust_linear=0, feedforward_max_rate_limit=90, tpa_mode=D, tpa_breakpoint=1350, pidsum_limit=500, pidsum_limit_yaw=400). The additional filter and RC smoothing parameters come from presets/4.5/filters/defaults.txt. The distinction between "with RC Link" and "without RC Link" variants correctly excludes feedforward and RC smoothing settings in the second option, providing appropriate flexibility.
Oh I am really sorry, this was not intended! Is this an issue? |
As long as total changed files are only your files, it's all good. So do we have any problems left here? @SupaflyFPV @sugaarK or merging? |
I spotted the need for rc_link includes but should be good to go after that - pls @saturn-fpv test it in configurator first to ensure it loads properly etc. You can use the 'preset sources' option to test your branch inside configurator presets. |
|
|
||
| #$ OPTION_GROUP BEGIN: (EXCLUSIVE) Gyro / Filter Strength | ||
| #$ OPTION BEGIN (CHECKED): ICM42688 | ||
| set gyro_lpf1_static_hz = 300 |
There was a problem hiding this comment.
frankly there way the 42688 is setup in BF it can use the same filters as the m6k
| #$ OPTION END | ||
| #$ OPTION BEGIN (UNCHECKED): MPU6000 | ||
| set gyro_lpf1_static_hz = 500 | ||
| set gyro_lpf1_dyn_min_hz = 0 |
There was a problem hiding this comment.
if you are going to use a static lpf turn off lpf1 and use lpf2 as the static as it includes anti-aliasing filter
| set iterm_relax_cutoff = 15 | ||
| set throttle_boost = 5 | ||
| set thrust_linear = 0 | ||
| set feedforward_averaging = OFF |
There was a problem hiding this comment.
with the 2025:12 build we totally recommend using averaging unless your running a really low link rate like 50hz. if you try to run 500hz+ with no averaging you will have junk radio data and may get un-commanded FF events from the bad radio data you are 100% going to get. this has changed in the way its handled from 4.5 and the link rate settings for FF are automatically negotiated now.. I think you should rethink this as you are setting up for glitchy radio data with the higher speed links..
There was a problem hiding this comment.
Thanks for checking once more!
@SupaflyFPV The generic rc links are already inlcuded (and they include the defaults) , or do you mean the default preset should be set inside the blackbird option? I had forgotten about that. Or do you mean options for the uarts like in your preset?
I have checked both versions (4.5 and 2025.12) initially and just now again and applying them is fine. Do you want me to do another test flight?
@sugaarK thanks for your suggestions!
- lpf2 makes sense to me, I will change that.
- if it's not a deal breaker, I would leave the seperate settings for the gyros. the description explains, which gyro has a bit more filtering and the pilots can make an informed decision based on that.
- that's a great insight with the feedforward. And that leads me to another suggestion. Because a lot of sbang pilots actually fly crossfire (often 50hz), those settings for low rates might actually be okay. But you still had a good point and I was thinking to rename "BB Stick Feel" to "50-150Hz BB Stick Feel". That makes clear, who should or shouldn't consider that option. In the description I have mentioned that blackbird uses those settings personally, but you / the developers recommend the official presets. I assume most people will use the seperate official rc link presets outside of this tune preset and this will barely be selected anyway.
This would introduce some improvements and still stay close to the tuning video, that sbang pilots are used to.
By the way, I am considering changing the "HD-Freestyle" rc link presets to "Freestyle", as it suits the sbang flying style better. Any thoughts about this?
Oh and one more thing, @SupaflyFPV . I haven't checked thoroughly yet, but if I am not mistaken, "feedforward_smooth_factor" is set by the defaults to 65 and then never changed again by any of the packet rate presets. The description says 25 for 50-150hz, 40-50 for 250hz and 60-65 for 500hz. And the 4.3 rc link presets do include those changes. Could you double check that or did I miss something why it should always be the same or did I not compare correctly?
Thanks for your patience and your help in getting the most out of this preset.
There was a problem hiding this comment.
"feedforward_smooth_factor" is set by the defaults to 65 and then never changed again by any of the packet rate presets. The description says 25 for 50-150hz, 40-50 for 250hz and 60-65 for 500hz. And the 4.3 rc link presets do include those changes. Could you double check that or did I miss something why it should always be the same or did I not compare correctly?
Thanks for your patience and your help in getting the most out of this preset.
this has change.. this is now auto negotiated. at 50hz I would turn off the averaging, for any thing else let the auto system deal with it. for more aggressive stick feel lower the jitter to 3 or even have it off. for different flying styles you just adjust the rc smoothing.. in racing we now leave the settings stock and we are always chasing the sharpest stick feel.
in regards to the 42688. with the LPF set to 500hz your gona get less prop wash than 300hz.
on a racer with the lpf set to 500hz the 42688 wi'll be a little be lower in latency over the m6K and it will feel a bit sharper.
its up to you on that one but it is perpetuating a 'trust me bro' myth that it needs more filtering.
6 participants
Hi everyone,
this is my first pull request, so please feel free to point out anything that could be improved in terms of structure, wording, or implementation.
This PR proposes adding a Black Bird FPV "Next Level" preset, inspired by Damien Gans' tuning video on YouTube (Link). The goal was to create a clearly documented, transparent, and reversible preset that offers Sbang pilots a faster way of implementing his suggested tuning settings.
The preset might be on the spicy side and therefor offers clear warnings in the description and as a pop up. It also includes options to reduce the PID terms slightly as Damien suggests in his video. Further options include the official rc link presets (HD Freestyle), as well as an option to revert all settings that have been changed by this preset.
The 4.5 and 2025.12 versions set the exact same settings, but have been adjusted to the new tune defaults, the new Dmin/Dmax parameter names, as well as the new rc_link presets. I have tried to structure the preset clearly and have used 4 spaces for indentation inst. The index files are not included in this pr.
As far as I can tell, this tune is being used by some top pilots around the world on several different frames like the ImpulseRC Apex, Echo, Fusion F212 and C220, Luma frames and others. It's usually paired with high-kv motors and 4.9 inch low pitched props. In case you find the tune too specific for the broad betaflight user base, please make suggestions how to change this preset to accommodate this. Further options could include some official filter presets (clean, normal, noisy etc.) for example.
For testing (index files included) you can use this preset source:
URL: https://github.com/saturn-fpv/betaflight-firmware-presets
Branch: blackbird-nextlevel
Thank you for checking and looking forward to improving this preset!
Following are screenshots of the preset as it appears in Betaflight Configurator:
And these are the options:
And a quick comparison of the 2025.12 default PID tune, the Black Bird tune as well as the Supafly tune with three throttle punches (includes calculated filter delay):
And PD balance with Brians wobble script:
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.