OSVR-Docs icon indicating copy to clipboard operation
OSVR-Docs copied to clipboard

hdk2 - screen / display device (HDMI) mostly not detected

Open emrum opened this issue 5 years ago • 6 comments

-- got it working a few times, randomly,
but usually the screen (device) is NOT detected . usb device (HDK2) sometimes detected, sometimes errors. firmware hdk2svr-2.00.hex sample scene starts on display 1 (because there is no 2)

is there any particular method that WORKS ? makes me mad.

emrum avatar Dec 14 '19 20:12 emrum

There were problems with the connectors on the junction box where the HDK plugs into the cables on some of the units. They were very sensitive and sometimes worked intermittently. That may be what you are seeing.

russell-taylor avatar Dec 14 '19 21:12 russell-taylor

great info , thanks. that part is called (hdk2 osvr) "hmd belt box module" i could try to re-solder ... but ... at that scale (smd), easily happens more harm than good. i wonder where i would get (re-buy) that part !? will try to contact razer support.

emrum avatar Dec 14 '19 23:12 emrum

These devices are no longer supported, I'm afraid. They are also no longer being manufactured.

russell-taylor avatar Dec 15 '19 12:12 russell-taylor

-- "repairability score 9 of 10" LOL >-))

emrum avatar Dec 15 '19 20:12 emrum

Before blaming hardware, do turn on display mirror first. If that works solidly then you have a version mismatch in drivers support for direct mode which is controlled by GPU driver, which can also cause intermittent behavior depending on changing drivers version and hardware support strategies from your graphics provider. This actually turned out in the past to be the major issue. All the hardware design is documented in detail on github (hence the reparability score) and there are wiki pages that detail all steps for troubleshooting black screens. As far as you don't grab the unit by the cable, you will actually be fine. Also the belt box shows up on device manager because it has a audio card built in for headphones support.

Hope it helps.

On Mon, 16 Dec 2019, 04:43 emrum, [email protected] wrote:

-- "repairability 9 of 10" LOL >-))

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/OSVR/OSVR-Docs/issues/131?email_source=notifications&email_token=ACW223DV3SXDL2RV4PQJMQ3QY2JF5A5CNFSM4J24NTPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG5BXRI#issuecomment-565844933, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACW223A6RWWSBM25TEYXBLLQY2JF5ANCNFSM4J24NTPA .

MulanVR avatar Dec 18 '19 01:12 MulanVR

what , where is "display mirror" ? mirror for what ? and why would that change any HDMI device recognition ?

"hardware support strategies from graphic-card provider " ? sorry, but the rest of my graphics card and driver is working as expected !

"All the hardware design is documented" that is indeed great practice, but still does not mean that I myself with limited budget, time and skills should be debugging any devloper or manifacturer error.

I did not grab , rip any cable at all - don't start blaming me.

thanks for input

emrum avatar Dec 18 '19 14:12 emrum