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

allow vtx_power 5 to be considered as a valid setting #4008

Merged
merged 1 commit into from Nov 12, 2018

Conversation

Projects
None yet
5 participants
@DzikuVx
Copy link
Member

commented Nov 11, 2018

Apparently vtx power 5 is valid for Tramp protocol but was considered as invalid value by INAV itself. This allows power level 5 to be used again

this fixes: #3983 #3938 #3924

@DzikuVx DzikuVx added this to the 2.1 milestone Nov 11, 2018

@digitalentity
Copy link
Member

left a comment

LGTM

@DzikuVx DzikuVx merged commit fbb94fd into development Nov 12, 2018

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details

@DzikuVx DzikuVx deleted the dzikuvx-vtx-settings-fix branch Nov 12, 2018

@balbusky21

This comment has been minimized.

Copy link

commented Nov 25, 2018

How do I apply this fix to my flight controller

@avivyam

This comment has been minimized.

Copy link

commented Dec 10, 2018

hello

is it possible to get a 2.0.1 hex file for OMNIBUSF4PRO, with trump protocol vtx fixed ?
Aviv
thanks a lot

@giacomo892

This comment has been minimized.

Copy link
Collaborator

commented Dec 11, 2018

@avivyam

This comment has been minimized.

Copy link

commented Dec 11, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.