Supafly 3/4 version 4.5 tune fix

[SupaflyFPV]

Correct the LPF frequency typo

Summary by CodeRabbit

• Chores
  • Updated tuning configuration in the Supafly FPV Freestyle 3.4 Inch preset with refined filter settings for improved performance in the High Performance profile.

[coderabbitai]

📝 Walkthrough

Walkthrough

A single configuration parameter in the Supafly FPV Freestyle preset has been modified. The dterm_lpf2_static_hz setting in the "Clean Build (High Performance)" filter option was adjusted to 120 Hz, optimizing the digital term low-pass filter configuration.

Changes

Cohort / File(s)	Summary
SupaflyFPV Preset Configuration presets/4.5/tune/supafly_fpv/SupaflyFPV_Freestyle_3_4_Inch_EasyTune.txt	Updated dterm_lpf2_static_hz to 120 in the "Clean Build (High Performance)" filter option while maintaining dterm_lpf2_type as PT3.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Supafly Tunes Updates #558: Modifies the same dterm_lpf2_static_hz setting in SupaflyFPV preset filter configs to 120 alongside PT3 dterm type.
• Supafly Tunes 4.5 update #559: Adjusts dterm_lpf2_static_hz in the same file and filter option that was introduced/modified by this update.
• Include 4.5 filter defaults in Supafly 2025.12 tunes #542: Touches 4.5 filter defaults by adding an include statement, while this PR modifies configuration values in a 4.5 tune file.

Suggested reviewers

• nerdCopter
• sugaarK
• haslinghuis

Poem

🐰 A whisker's tweak, a filter's hum,
One-twenty hertz, the tuning's done,
In SupaflyFPV's freestyle dance,
The numbers shift, performance prance,
Clean and high, the frequencies gleam! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description is minimal but accurately describes the change (correcting an LPF frequency typo). However, it lacks the detailed template structure and context expected by the repository guidelines.	Expand the description to include context about why the change was needed, what the correct value should be, and testing performed. Consider following the repository's pull request template more closely.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the specific change: fixing a tune configuration in the Supafly 3/4 version 4.5 preset, which aligns with the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

No actionable comments were generated in the recent review. 🎉

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}