VA-191 Causing issue on analog
Closed this issue · 17 comments
The following commit: fix hdmi in 1080p60 glitch; 1080p30 vsync tearing is introducing a bug in analog mode:
- Sometimes (completely random) the analog video will be fill with pink pixels here is a photo to illustrate:
- The issue can be solve (or introduce again) by going back to the main menu and selecting expansion bay again. Sometimes I need to do this 5 times to get those pink pixels away. It can also switch between a working state to a degraded one my opening the vrx menu and going back.
- I can confirm that the previous commit is completely fine
- I did try to incrementaly revert back changes of hardware.c and oled.c without success
- I revert back VA from 191 to 186 without changing anything else: that fixes the issue !! (but causing tearing in the main menu which is kinda expected because I didn't revert back anything else accordingly)
- This issue is also the root cause of Issue_#375
- During all those tests a rapidfire vrx has been used
I get this too except that the pink pixels are usually white or green in my case. They seem to be dependent on what’s in view. The more black in the picture, the more green artifacts I see.
I’m also using rapidfire (1.3.3 / 1.1.6) but a friend (same rapidfire versions) is not. We are both using ntsc.
Exactly same issue here, using True D receiver. Can fix by going to the menu and back into analog until its clear. Didnt have the issue on the previous version.
I have this issue on goggle firmware 9.3. Going back to 9.2 resolved for me.
9.3
9.2:
I just found out that I've got the same issue on an Eachine Pro58 module running Pirx firmware.
Another thing that I noticed: Before this issue comes up, switching from main menu to video seems to take longer. At least I see a black screen for a longer time than when everything works as expected. The duration of the black screen varies. Sometimes, I have to switch input modes back and forth so that the analog module gets turned off and on again.
I didn't have this issue prior to updating DM5680 and the FPGA in the course of updating the whole goggles firmware.
I have the same problem, TBS Fusion. Works fine on 9.2, broken as described on 9.3, also tested the newest build from the actions (specifically this one: https://github.com/hd-zero/hdzero-goggle/actions/runs/7442913409), issue still persists.
If debugging is needed, I can oblige.
Same issue here with latest firmware, in my case it is a Pro58 module. I have a DVR of an entire flight with it here: video
On my video you can see it even after the feed has ended in the static. I'm flying in NTSC mode. This also happens with AV cable. To me this looks like it fails to detect horisontal sync of the analog signal, but IDK for sure.
It happens maybe 10% of times I power on. Power cycling usually fixes it until next power on.
I tried to revert just the VA version while keeping all the code to see what happens. But this breaks the main menu (various flashes, I didn't want to take a chance the oled is driven wrong so I reverted to 9.2 without a lot of testing).
Later I made myself a v9.3 (unofficial custom version) with the pull request mentioned above reverted, with the pull request that fixes the "sleep bug" added. I'm not recommending anyone actually uses this, but I'm posting a link in case someone else wants it. This of course re-introduces the 1080p30 tearing bug, but fixes analog, which is more important for me now.
https://github.com/lukolszewski/hdzero-goggle/actions/runs/7678690622
@asyncnomi or anyone else, did you ever see this start happening while flying?
Yesterday I flown for an hour on analog without touching the goggles and it didn't trigger itself (once I restarted to fix it initially). But I mostly fly indoors during the winter.
If anyone has had it happen during the flight, please post a recording if possible. I'm very interested if it only happens on initialisatation, or later during the flight too. Especially if the analog signal is lost and recovered. During my hour long session yesterday I swapped many batteries, disconnecting and reconnecting the quad and it has never happened, other than initially.
@asyncnomi mentioned it was triggered by opening vrx menu. Is this the goggle source menu? Or on the vrx itself? Can you post a recording if the latter?
If anyone has had it happen during the flight, please post a recording if possible. [...]
This has never happened to me so far, always was there from the beginning, or not at all. However I have switched back to 9.2 now, so my usage was limited.
Hello, i Update yesterday my goggles to the latest firmware, and i have also this issue. I use speedybee Analog VRS. Would be nice if it could be fixed.
https://github.com/hd-zero/hdzero-goggle/actions/runs/8866084371
Please test this fw.
Hy, I have flown totaly about 4 hours with Analog and HD Zero so far. Everything has been smooth so far. It seems that the problem has been fixed. Thank you very much.
I've tried this firmware too, and this is a weird one;
Picture of the camera feed seems to be consistently good now, but when I enter the menu of my TBS Fusion the picture seems to be always bad now (purple static around the osd elements).
@Babdef i can confirm this
I have the same problem, TBS Fusion.
