On the nano/micro v1 there is a constant flashing of the image as if it is trying to change between day and night mode. This is mostly visible when going from sunny to darker areas.

HDZero does not support the new OSD configuration in Betaflight 4.4

as the title says i want to know if its possible to use the sa pad as rx because the original pad is shorted to ground and i cant get osd.

I asked on the discord, and got an answer about the shutter values that doesn't seem to make sense, so I went digging through the source, and was trying to decipher how the values of 1-32 are sent to the camera. And though I figured out the values being sent and the addresses where those values are set in the camera, without camera documentation, they don't make much sense. For example, why is auto sending 1120, but the fixed value range is from 1 (25) to 32 (800)?

From my discord conversation, they said 1 -> 0.37ms, and 32 -> 12.12ms.. I have no idea what that means. Tinkering with the values in the camera, and testing didn't result in much of a difference, although at lower values the color of the image seemed to change a bit (less saturated) in certain lighting conditions.

It would be great to have values here that made more sense as to the actual shutter speed, and it would be even better if we had a broader range for setting a fixed shutter speed.

At the very least, some insight into what the values mean, and if there is any difference for the user when setting them. And if there is no practical difference for the user, it doesn't make sense to even have a setting.

The VRX 2sma or 4sma actually doesn't work with the nano 90 camera, but works with the event vrx.
Could it be possible to update the vrx 2sma/4sma to make them work with the nano 90 just like the event vrx ?
Many people are keeping their old vrx to use them as event vrx, but this isn't actually possible with the new camera.

The three Modes, LP Mode, Pit Mode, Vtx OFF on first boot do not working on INAV 6.0 and FETTEC Alpha.
On both the MSP communication is enabled for OSD and Stick commands (FC and Vtx Menu)

Tested it with older firmwares from FETTEC Alpha and the actual INAV 6.0. Its always the same behavior.

This issue is since Vtx Firmware Rev 06012023

To arm multirotors in ArduPilot (and I believe PX4) you need to hold the left stick (throttle), right and down for 2+ seconds. The issue we are having is every time we arm the aircraft this also opens the RunCam camera menu (which is throttle stick right for 3 sec). Note: putting "arm" on a dedicated switch is not an option for us.

How do we prevent this from happening?
a) Would it be possible to increase the time you need to hold the sticks in side/corner positions for activation of Cam and VTX menus to say 10 seconds (instead of 3s). It would be great if there was an option to change this time, maybe between 3s or 10s or something like that?
b) Is there a way to turn off stick commands (we don't have the ability to use Smart Audio).

As the title says, there is no blue light on my freestyle vtx with a digisight v3.
Not a big problem, but can it be fixed?

With FW 06022023 I can´t switch the VTX off with stick command.
On FW 06012023 its working.

Tested on Freestyle VTX and Race V2

Smartaudio is not connected.
FC firmware is FETTEC Alpha.
I also tested a few versions. It does not influence the issue.

Any chance one of the Led's could flash at say 1hz if its in pit mode?

Currently (as far as I can tell) the blue LED works as follows:

Eight fast flashes followed by solid on
= Normal operation

Flashing once a second
= Problem with MIPI or camera
OR
= throttling power because of overheat (maybe more than once a second ?)

No Blue LED
= Problem with MIPI or camera
OR
= incorrect firmware installed

It would be an improvement if we can make it easier to diagnose and distinguish between the above states which are very confused. Especially where a single state can represent multiple possible problems, and, where multiple states can represent the same problem.

I am not sure if Pit mode or Low Power mode flash to indicate when they are active, but I think such indications would be useful, but they would need to be distinguishable from everything else.

Encoding at say 1hz v 2hz v 4hz, may not be obvious for a user to distinguish, so codes should flash slower than this or use long pulses mixed with short pulses to make code identification easier.

Please Add Option for the dvr to write over the oldest dvr file when the sd card is full.. This allows for continous dvr recording and allows the use to use only the dvr files they wish..

Further more to this, a option in the playback menu to save a favorite dvr file so the dvr wont overwrite that favorate file.

Similar to FPV-Combat system, recognize high intensity blinking LED for hit detection.

https://www.fpv-combat.com/

LP Mode in 25mw still interferes with my friends on other channels (esp those on analog), and I have found that setting my 25mw offset value to -10 certainly helps, and does not impact me, so it's a win-win.
If there's no technical reason why it's limited to -10, then I would like to be able to adjust it down all the way to -24 or -25, to create a kind of variable Pit Mode.

I could also see use-cases where people might want to use it to create a power setting that is between 25mw and 200mw

I see

temp_err = 1;

in a couple of places, for example after entering pit mode, which then applies a pwr_offset = 10 in PowerAutoSwitch(), but don't see temp_err revert to 0 anywhere.

This suggests there's always pwr_offset = 10 applied after having been in pit mode once.

Currently for each camera type there is an auto and manual setting. Whilst in the camera menu, the first option is to scroll through the different camera type settings. For Auto, the setting is named as per the camera type and the settings are default. None of the settings besides HV flip can be changed when this is selected. For Manual, the setting is named as per the camera type with an "M" at the end and the settings all start at the lowest (eg brightness is 0 and saturation is lvl 1). All of the available settings can be changed when this is selected.

I believe having these different settings will become confusing for the users and I can not see it providing any benefit.

I recommend having a single settings profile per camera type and have the default set to the best know settings for that camera.

I'm using Unlocked Freestyle VTX on latest master ( november.11.2022) on latested Betaflight master too (4.4) using the MSP VTX funcion.

The VTX Table is incorrectly populated:

vtxtable

vtxtable bands 6
vtxtable channels 8
vtxtable band 1 BOSCAM_A A FACTORY 0 0 0 0 0 0 0 0
vtxtable band 2 BOSCAM_B B FACTORY 0 0 0 0 0 0 0 0
vtxtable band 3 BOSCAM_E E FACTORY 0 0 0 0 0 0 0 0
vtxtable band 4 FATSHARK F FACTORY 0 5760 0 5800 0 0 0 0
vtxtable band 5 RACEBAND R FACTORY 5658 5695 5732 5769 5806 5843 5880 5917
vtxtable band 6 IMD6 I FACTORY 0 0 0 0 0 0 0 0
vtxtable powerlevels 5
vtxtable powervalues 14 23 0 0 0
vtxtable powerlabels 25 200 0 0 0

The expected is:

vtxtable

vtxtable bands 6
vtxtable channels 8
vtxtable band 1 BOSCAM_A A FACTORY 0 0 0 0 0 0 0 0
vtxtable band 2 BOSCAM_B B FACTORY 0 0 0 0 0 0 0 0
vtxtable band 3 BOSCAM_E E FACTORY 0 0 0 0 0 0 0 0
vtxtable band 4 FATSHARK F FACTORY 0 5760 0 5800 0 0 0 0
vtxtable band 5 RACEBAND R FACTORY 5658 5695 5732 5769 5806 5843 5880 5917
vtxtable band 6 IMD6 I CUSTOM 0 0 0 0 0 0 0 0
vtxtable powerlevels 5
vtxtable powervalues 14 23 27 30 0
vtxtable powerlabels 25 200 500 MAX 0

I thought this might be a very cool feature. A color OSD with special features like: Battery turning red once it gets low, A red warning indicator, maybe even when there is a warning for example not enough sat's It could just say warning in the midddle of the screen and then flash the sat indicator in red (where you have it setup in your osd)

A common stick command/gesture in iNav is to save settings after tuning things like auto level, auto tune, auto trim.
This is normally done after landing and disarming.
It is useful to see confirmation that this has happened on the iNav OSD after saving.
If the video is being recorded (which it usually is) this can be checked later if necessary too.

However. The same stick command/gesture used in INav to Save Settings, is now used by HDZero to set 0mW power.
This command works even if LP MODE and PIT MODE are OFF.

The result is that Save Settings in iNav simply records the video going to HDZero Rainbow display, rather than showing confirmation of iNav save. It probably does Save Settings too, but who knows.

A secondary issue (though not the point of the one being raised) is that trying to bring the vtx out of 0mW mode (sticks in and down) does not work under these circumstances. One has to cycle the power on the aircraft to get the video to come back).

This is all a bit of a mess.

Can we please allow 0mW to be put on a different stick gesture so that it does not conflict with iNav, or, allow it to be disabled.

1. ELRS LUA script set to Pwr lvl 2 and LP mode off. VTX currently at 200mw power
2. Enter VTX menu (Sticks down and together)
3. Enable LP Mode
4. At this point, the menu shows Power: 200, LP Mode: ON
5. Exit VTX menu
6. Enter VTX menu
7. ERROR: Menu shows Power: 25, LP Mode ON

ie it appears to the user that when they arm, power will not be set to 200
When you do arm, it does go to 200mw

Fix: In the VTX menu, it should not show the CURRENT VTX power, it should show the power level that it WILL go to when you arm.

Fimrware dated "Rev 06012023"
The osd link quality drops to 0 after a few minutes, the osd freezes then drops out.

I originally posted this on the BetaFlight Github issue tracker, but it's seeming likely that this is an HDZero issue...

Describe the bug

When I flash BF 4.4.1, it appears as if the coordinate system of the OSD is wrong - elements are off-screen to the right and bottom.
This affects both the HUD elements, and menus.
On one quad (The GHF405), flashing back to 4.4.0 solved the issue. I then flashed back to 4.4.1 and the issue came back. I then set the port to nothing, saved, then back to MSP+Displayport, and the issue went away.
On the GHF411 quad, this "turn it off and on again" trick did not work.

In the below image, I have moved the OSD elements to the top left quadrant of the screen to compensate for this issue, but as you can see, on the actual OSD they are filling the screen.
This is a screen grab from my DVR - I am plugged into USB with the configurator open (So you can see my OSD settings), and recording the screen with my quad

To Reproduce

FW: BF 4.4.1
HD OSD (I am using HDZero)

Expected behavior

OSD elements should be on-screen

Support ID

Id: "9f9ddcd8-110d-4a83-8c3d-0fab939feb3f"

Flight controller

JHEMCU GHF411Pro AIO MPU / JHEMCU GHF405Pro AIO MPU

Other components

HDZero whoop lite VTX (FW v1.2.0)
HDZero nano lite camera
720p60 mode
HDZero Goggles (app 9.0.12 rx:0 va:161)

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

GHF411: VTX on UART 1
GHF405: VTX on UART 2

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

No response

Navigating the VTX settings menu is very slow. It seems I must hold my transmitter stick for 0.5sec before an action is registered

It would be wonderful if the vtx could support the irc tramp protocol for us ghost users. It is a feature that is working so awesome in the ghost ecosystem and I miss that I could change channel on the back of the radio a lot.

Hi, is it possible to update the vtx modules directly through usb from a computer. With new devices like frsky x20hd which supports hdzero lacks upgrade port for vtx and if the radio is the only thing that one is having like me there is no way to upgdate the firmware on vtx as of now.

Ryan(discord) report:

1. Sometimes when I arm the drone, the video goes to rainbow then back to my desired power level - it is a split second

2. (probably a betaflight issue) if smart audio is enabled in the ports tab, then msp-vtx doesn't work

3. This video shows that VTX turns on immediately on boot rather than waiting for FC to assign channel and power level (I need the VTX to boot up at 0mW!)
   https://1drv.ms/v/s!AibfK-JCIxFUjfYRoMr5nj46T1OTow?e=Ste5f1

4. When I arm the drone after enabling video via radio switch, the video flashes off then on for a split second
   https://1drv.ms/v/s!AibfK-JCIxFUjfYSJZ5nf7boY_kMbQ?e=pxaeVv

5. Video turns off after takeoff - very dangerous!
   https://1drv.ms/v/s!AibfK-JCIxFUjfYQJNkI5LhFXp6uGw?e=IpoiUq

To reproduce the issue, make sure that VTX power is controlled by a switch on the radio. I set my switch up so that power is 0mW by default and I must flip the switch from default position for the vtx power to come on

vtx 0 3 0 0 3 900 1300
vtx 1 3 0 0 1 1300 1700
vtx 2 3 0 0 1 1700 2100

aviphysics(discord) report:

"the power low until first arm" option doesn't stick. That seems like a BF issue.

If its possible, to make it clean, can we get one unified vtx firmware in future?
Instead of different vtx files, just one to avoid confusion.

I have updated my sb vrx to 22122022. New fonts are visible.
When my freestyle vtx's are updated to 22122022, the video cuts every few seconds. Using the Foxeer digisight v3. Video - https://www.youtube.com/watch?v=xphZvGRcftI

The video is ok when the vtx is at 11062022.
The video is ok on the latest using the micro v2 camera

I read that you are looking at replacing Keil IDE with an opensource alternative.

I believe SDCC is supported with platformIO.

Also it is easy for new developers to get hacking away and contributing to the project without a huge learning curve from a custom IDE like STM/Microchip/others are known for.

Since #117 doesnt work anykind and I dont know why its merged..
Can we instead have an option to chose pitmode default power?
For example:
Team Race = OFF - Default pitmode (idk its real power but its powerfull enough to fly 100m)
Team Race = ON - Default pitmode is 0mw, and then we dont need paralize state from FC, just make PIT+Paralize in modes and your stuck on race quad can be paralized as it should be.

Also PITMODE now have some bugs where on 1/5 runs VTX is stuck in pit even after arm. (osd says its not in pitmode, but it is, and only powercycle helps). Not suitable for race events where you have your quad in pitmode all the time before arming.

On the whoop lite vtx seeing an extremely high contrast video feed every ~5 power cycles. Its looks like the contrast settings are being messed up, but then power cycling makes it go back to normal. This is using the whoop camera on a 65mm 1s whoop.

I have an FC with a lifted RX pad.
The OSD still works, however LP mode does not appear to work.
I have also seen this happen on a quad where the wire going from the RX pad on the FC has come off - the OSD still updates and says it has left LP mode, but the VTX has not actually exited LP mode.
My guess is that what is happening is something like the FC requests from the VTX what power level it should enter when it leaves LP mode, and if it does not receive a response, then it does not know what power level to request on arming, so does not send the request to change power level, but does update the OSD
ie the comms goes something like:
FC: What power level should I request on arming?
VTX: Responds 2
(On Arm): FC: Set power level 2

Could this not be refactored to:
(On Arm): FC: Leave LP mode

Surely the latter would only require one-way comms?

I am not sure why the OSD updates when the RX pad is not connected - at the very least, the OSD should NOT change power level on arm if LP mode does in fact require a two-way connection - it's most confusing that you are flying around, wondering why your signal is terrible, when your OSD shows you are not in LP mode. If the OSD still showed 25mw even when you armed, at least that would give you a clue that there was a comms problem between the FC and the VTX

Now I can't be sure, but I assume the timer icon showing a battery would be the "on time" and the one showing a quad would be the "armed time".

However from what I can see the icons are transposed in the VRX4.

Using Race 2 VTX, Runcam Micro V2, HDZero VRX4. All with Rev 22122022 firmware

Temperature issues with new FW on my Whoop Lite VTX.
1st issue: On 25mW the VTX gets hot within seconds. Physically feelable and the temperature indication goes up as well.
2nd issue: The 200mW is selectable but after hitting safe/exit the VTX stay on 25mW no matter if armed or disarmed.

Rolled FW back to 1.2.0 - no issues.

Can we turn off analog bay audio recording?
Now when analog module is powered up it always recorded as audio source, doesnt metter if you have chose line in / av / mic
My analog quads doesnt have any mic, I just want to record audio only from linein / googles mic.

Hi. It's nice to have the Betaflight OSD in HDZero. I wish it could be easier to display the OSD with Arduino.
I'm trying to replace my analog VTX/VRX on my arduino robot with HDZero but I fail to understand how the MSP OSD work in Betaflight. I used to use AT7456E to display voltage, status, data and menu on the analog screen.
An MSP OSD library with example, or a simple arduino example project is nice to have. Wish HDZero could be popular in the Arduino Community.

I was playing around, and found that if I switching camera profiles on the Micro V2, and then save&exit, the display goes into an erratic rainbow flashing display that can only be fixed by powering the vtx off and back on. Running 06012023 firmware.

It would be cool to have a shortcut to enter/exit 25mw mode.

The LP_Mode set to 1st is great, but I like to talk to the camera after flying (and possibly multiple disarms), so it would be nice to be able to quickly set the power level to 25mw to help reduce the interference when the drone is close to the goggles. Since I fly in areas where I don't always want 25mw mode after disarm, it would be nice to have a shortcut to get there without having to go to the vtx menu, and change the power setting, and then change it back.

Is it possible to access the vtx/camera menu or use smart audio for wings that don't have flight controllers, I was hoping that i could connect SA from my Crossfire Nano to the SA on the HDZero VTX's and access the menu's but i have tried several configurations but unable to have any control

Please feel free to review my changes. I made sure to remain compatible with Keil compiler while supporting an open source variant. It would be nice to know if it compiles without issue on Keil.

https://github.com/SumolX/hdzero-vtx/tree/cmake_support

I will provide instructions once I've ported the startup code on how to build with cmake. At this time all source files compile and showcase a few warnings in the codebase that must have pre-existed.

It would be nice if it was possible to start DVR Recording when i flipp a switch on my radio - like it’s with the runcam HD is possible. I can left my fingers at the radio i case i have forgot to start the DVR recording.

I ran into a small problem for the first time today. I had a bad/partially attached MIPI cable, so the VTX wouldn't broadcast. However, the MIPI cable was apparently good enough that the blue LED light came on, which made me think the MIPI was fine and the VTX was bad. Eventually switched out the cable and all good now.

Suggest when the VTX doesn't broadcast because of a MIPI situation, it broadcasts out "No MIPI" at pit mode level (0.1mW) so the user knows what the issue is.
Sending out error codes at low wattage may be helpful in other circumstances.

In the VRX the firmware version number is displayed (XX.YY.ZZ), but only the date is shown in the files on the download page (Rev ddmmyyyy).
This makes it difficult to identify which firmware you have installed as the two things do not correlate in any helpful way.

Hi. What is maximum refresh rate HdZero is capable of?
Now its only updates 3 times per second (when I add milisecond timer to OSD).
Maybe we need to define MSP osd elemets and preoritize some for fast updates (like horizon and timers), and some like osd names and channels could update less frequently?

https://youtu.be/38icuAvK5w4

See MultiGP Icestorm stream at time stamp 1:32:55 where the event VRX also picked up the green screen so seems to be a vtx issue.

https://www.youtube.com/live/JvQt6s9y...

I am occasionally having an issue when trying to change channels on HDZERO whoop lite + nano 90 camera. I use the beta flight lua script to change channels and then it pops up as a green white image which made it impossible to see the gates and flags. Also interesting was that it was outputting 25mw still but my osd showed it at 0.

I did find that restarting my radio and plugging the quad back in fixed it 50% of the time. When I changed channels using my laptop I didnt see this issue pop up.

This started popping up in brackets unfortunately and lost me a heat. Happened across two different quads with the same setup.

Firmware revision "Rev_13042023".