Jump to content

harperhendee

Verified Members
  • Posts

    6
  • Joined

  • Last visited

Everything posted by harperhendee

  1. I have had this problem on multiple headsets over a period of around 4 years: Vive : Worked for about a year, then display black even though VR mirror worked and sound in headset Vive Pro: Worked for a couple of years, then display black and sound working Vive Pro Eye: Same story, but somewhat intermittent I've worked in computer debug for many years, so I have a little more experience in how these things are put together and what things may be wrong. I took the first Vive HMD apart down to motherboard, put it back together and it was in the same state. My current Vive Pro Eye is a little flaky. I also have lots of different cable boosting solutions. I have display port retimers, HDMI boosters, and lots of extender cables. First off, using an extender cable makes it worse. Secondly, sometimes a retimer will help with the issue. The display is usually the thing that fails, though sometimes USB as well. From what I can tell, this is a signal integrity problem. The Vive and Vive pro both send 3 cables to the headset: Display, USB, and Power. No power and you won't get a light. No USB and you won't get sound or position data. No video and you get black screen headset but everything else seems ok. From what I can tell, the display is failing to train the link sufficiently, or perhaps it is trained up, but then fails when things heat up a little. USB is a 2-way interface, but video is mostly 1-way. So if the display stops working, the host may not notice it. Have you ever had a monitor do the same thing with a bad HDMI? This is like that. Now there are multiple places the video can break down. There's from the computer to the link box, from the link box to the HMD plug, and the HMD plug to the display port receiver (if one exists, I can't remember from my teardown..), and from that chip to the actual panels. Any one of these can result in a failure. I suspect the failure is most likely past the link box, because training is successful to the link box, but then the link box fails training to the HMD. This makes it look like the HMD is working fine to the host, but it is still busted. The most likely culprit is the long cable, since it will only deteriorate over time when it gets kinks and mechanical stress over time. A new cable can be a solution, but they cost like $67 to attempt the experiment. I wish I had better solution than that, but that is just about the only thing I can think to do. --Harper
×
×
  • Create New...