Skip to content
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.

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

Pit Mode via Global Function #5270

Closed
swissfreek opened this issue Dec 14, 2019 · 6 comments
Closed

Pit Mode via Global Function #5270

swissfreek opened this issue Dec 14, 2019 · 6 comments

Comments

@swissfreek
Copy link

Current Behavior

Currently Power Level can be changed via Global Function, and for SmartAudio it can be set from 0-3. For a 800mW transmitter, this corresponds to 25mw, 200mW, 500mW, 800mW. There is no way to engage any power level lower than 25mW (aka Pit Mode).

Desired Behavior

It would be nice if it were possible to enable and disable Pit Mode so that you can be in Pit Mode until you flip a switch or something.

Suggested Solution

Add a SET_PIT_MODE to the Global Functions so that it can be controlled via Logic Condition similar to SET_VTX_POWER.

Who does this impact? Who is this for?

Anyone who flies with TBS Unify VTXs and wishes to control Pit Mode, especially those who fly in groups where they don't want to swamp neighbors until they are flying.

@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label Feature request to this issue, with a confidence of 0.96. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@buzkill420
Copy link

bump

@padcom
Copy link

padcom commented Jan 26, 2021

Seriously, this should be simple enough. Just add a mode that will enable pit. It is already there in betaflight.

@sixtyfive
Copy link

sixtyfive commented Feb 5, 2023

It's been 4 years and 6.0.0 is about to be released. Has this Issue received any consideration by the developers?

@OptimusTi
Copy link
Contributor

OptimusTi commented Feb 6, 2023

This is a feature request. Not an issue. I may take a swing at it if I find some free time. I have the vtx

@sixtyfive
Copy link

Sorry, OptimusTi, by Issue (uppercase I) I merely meant to refer to the thing that GitHub decided to call so. Not the lowercase-i issue, as in the thing otherwise known as a problem or similar.

@DzikuVx DzikuVx closed this as completed Feb 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants