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

MSP VTX -Current Band and Channel not shown on entry into OSD menu -> Features -> VTX #13029

Closed
pitts-mo opened this issue Aug 12, 2023 · 0 comments · Fixed by #13032
Closed
Labels
BUG Bugs are excluded from automatically being marked as stale

Comments

@pitts-mo
Copy link

Describe the bug

OSD menu -> Features -> VTX does not show current Band and Channel for MSP-VTX devices.

To Reproduce

Use OpenVTX or HDZero with MSP-VTX
open OSD menu -> Features -> VTX

Expected behavior

OSD menu -> Features -> VTX should open to show the current Band and Channel being utilized by the VTX.

Support ID

MATEKF722MINI default 4.4.2 build w/OpenVTX on UART 3
BETAFLIGHTF4 default 4.4.2 build w/HDZero on UART 1
Both test images show a VTX that had already been set to R8 @25mw.

Flight controller

MATEKF722MINI w/OpenVTX and BETAFLIGHTF4 w/HDZero

Other components

MATEKF722MINI default 4.4.2 build w/OpenVTX on UART 3 ELRS on UART 2 (minimal test config)
BETAFLIGHTF4 default 4.4.2 build w/HDZero on UART 1 (Mobula8 HD ready for flight)
Both test images show a VTX that had already been set to R8 @25mw.

How are the different components wired up (including port information)

No response

Add any other context about the problem that you think might be relevant here

vlcsnap-00011
vlcsnap-00012

@pitts-mo pitts-mo added the Template: Bug Set by auto_close_issue. label Aug 12, 2023
@haslinghuis haslinghuis added BUG Bugs are excluded from automatically being marked as stale and removed Template: Bug Set by auto_close_issue. labels Aug 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BUG Bugs are excluded from automatically being marked as stale
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants