You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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
The text was updated successfully, but these errors were encountered: