Skip to content

Add TBS Unify Pro32 DP VTX table #583

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
andybrwr wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Add TBS Unify Pro32 DP VTX table #583

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
23feed9
Add Unify Pro32 DP VTX table
andybrwr Jun 25, 2026
718d7f5
Update discussion link
andybrwr Jun 25, 2026
af37a9a
Add new firmware versions to DP preset
andybrwr Jun 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 32 additions & 0 deletions presets/4.3/vtx/Unify_Pro32_DP_SA2_1.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
#$ TITLE: TBS Unify Pro32 DP SA 2.1
#$ FIRMWARE_VERSION: 4.2
#$ FIRMWARE_VERSION: 4.3
#$ FIRMWARE_VERSION: 4.4
#$ FIRMWARE_VERSION: 4.5
Comment thread
andybrwr marked this conversation as resolved.
#$ FIRMWARE_VERSION: 2025.12
#$ FIRMWARE_VERSION: 2026.6
#$ CATEGORY: VTX
#$ STATUS: COMMUNITY
#$ KEYWORDS: vtx, vtx table, tbs, unify , pro32, DP, SA 2.1
#$ AUTHOR: andybrwr
#$ DESCRIPTION: VTX table for TBS Unify Pro32 DP SA 2.1. NOTE 1. Max power set to 65dB as it will force the VTX to output max power. NOTE 2. This table is as provided by the manufacturer.

@coderabbitai coderabbitai Bot Jun 30, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟠 Major | ⚖️ Poor tradeoff

Document the missing "all bands" limitation.

The PR objectives explicitly state this preset excludes the all-bands option because it "could not be made to work in Betaflight during testing." This caveat is absent from the DESCRIPTION fields, so users will not understand the preset is incomplete. Add a DESCRIPTION line noting this limitation.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@presets/4.3/vtx/Unify_Pro32_DP_SA2_1.txt` at line 12, The DESCRIPTION for the
Unify_Pro32_DP_SA2_1 preset is missing the explicit limitation that the
all-bands option was excluded because it could not be made to work in Betaflight
during testing. Update the DESCRIPTION entry in this preset file to add a clear
note about that limitation alongside the existing power and manufacturer notes,
so users can see that the preset is intentionally incomplete.

#$ DESCRIPTION: !!! Make sure to use the correct broadband antenna to avoid damaging the VTX !!!
#$ DESCRIPTION: The information provided on this preset is for educational and entertainment purposes only. Betaflight makes no representations as to the safety or legality of the use of any information provided herein. End users assume all responsibility and liability for ensuring they are complying with all relevant laws and regulations.
#$ DESCRIPTION: ----------
#$ DESCRIPTION: Using the VTX tables as provided may be in breach of your local RF laws. It is up to the end user to research and comply with local regulations and in using these presets the user assumes all liability associated with breaching local regulations.
Comment on lines +12 to +16

@coderabbitai coderabbitai Bot Jun 25, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Document the missing “all bands” limitation.

The PR intent says this preset could not make the all-bands option work in Betaflight testing, but that caveat is not reflected here. Please add it to avoid presenting the preset as fully complete when it isn’t.

🧰 Tools
🪛 LanguageTool

[style] ~11-~11: Using many exclamation marks might seem excessive (in this case: 6 exclamation marks for a text that’s 1844 characters long)
Context: ... band antenna to avoid damaging the VTX !!! #$ DESCRIPTION: The information provide...

(EN_EXCESSIVE_EXCLAMATION)

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@presets/4.3/vtx/Unify_Pro32_DP_SA2_1.txt` around lines 10 - 14, The preset
description for Unify_Pro32_DP_SA2_1 is missing the caveat that the all-bands
option could not be made to work in Betaflight testing. Update the DESCRIPTION
comments in this VTX table so they clearly note this limitation alongside the
existing manufacturer and safety notes, keeping the wording consistent with the
other preset metadata.

#$ DISCUSSION: https://github.com/betaflight/firmware-presets/pull/583
#$ INCLUDE_DISCLAIMER: misc/disclaimer/en/vtxtable.txt

# vtxtable
vtxtable bands 6
vtxtable channels 8
vtxtable band 1 BOSCAM_A A FACTORY 5865 5845 5825 5805 5785 5765 5745 5725
vtxtable band 2 BOSCAM_B B FACTORY 5733 5752 5771 5790 5809 5828 5847 5866
vtxtable band 3 BOSCAM_E E FACTORY 5705 5685 5665 5645 5885 5905 5925 5945
vtxtable band 4 FATSHARK F FACTORY 5740 5760 5780 5800 5820 5840 5860 5880
vtxtable band 5 RACEBAND R FACTORY 5658 5695 5732 5769 5806 5843 5880 5917
vtxtable band 6 RACE_LOW L FACTORY 5362 5399 5436 5473 5510 5547 5584 5621

vtxtable powerlevels 8
vtxtable powervalues 10 14 20 23 26 27 30 65
vtxtable powerlabels 10 25 100 200 400 500 999 3k
Loading