Everything is working fine but DK2 never gets a video signal

[lohan]

Yes I know there are some threads already touching this or a very similar issue. But since this issue is affecting so many users and there still is not a single official word on this issue I guess it shouldn't be a bad thing to add another thread.

I am on Win 7 64-Bit Home Premium using a GTX-690 graphics card (beside the Oculus DK2 there is the Sony HMZ-T3 plugged into the GTX-690 as well as my main monitor Samsung Syncmaster 2233rz).
I was able to install Oculus Runtime without any problems. The Runtime-application runs flawlessly: My DK2 is detected, camera is working just fine (blue LED always on). I can even launch the desk-demo scene. Since it is displayed on my monitor I even can confirm that headtracking seems to work just fine.

Now here comes the problem: Since I first opened the DK2 I never saw the DK2 screen active. It just never gets a video signal, the specific LED stays orange all the time.

To this point I even didn't get it to work in extended mode.

Right now I am desperate to the point where I will buy a USB 2.0 hub with additional power adapter today because my PC only has USB 3.0 ports which could cause problems according to cyber and some other sources (a USB 2.0 hub plugged into a USB 3.0 port seems to solve this problem).

Any idea?

[joueur]

Try another computer, nothing.
I wonder where everyone is now? Do we go for replacement process, we don't have any instruction. I agree we are developers, but hardware or software, do we have guide to open this thing to test the screen or something?
It's not clear if my Oculus is broken or not.

[sneakyminky]

"joueur" wrote:
Try another computer, nothing.
I wonder where everyone is now? Do we go for replacement process, we don't have any instruction. I agree we are developers, but hardware or software, do we have guide to open this thing to test the screen or something?
It's not clear if my Oculus is broken or not.

I find it doubtful that all of our units are faulty, man 🙂
More likely it's a software issue with certain hardware configurations.

We just have to wait for Oculus to fix it.

[PacalB]

"ColinB" wrote:

"sneakyminky" wrote:
Add me to the list, folks.
Same thing. Orange light and no display.

Disappointed to say the least...

Would be interested in seeing the serial number of these units. Possibly there was a batch of (maybe) faulty headsets sent out?
Of course this pre supposes that the folk having this problem do actually have faulty rifts !
In my case I certainly did!

EDIT
my info. For the faulty one:

Sensor s/n 203Y1H04V7VB
Camera s/n 213Y1H04V7VB

Hey there ColinB, my info:

Oculus Configuration Utility
Version 1.4 Rev 1 (SDK 0.4.2)

------
Display Driver Version: 1.0.25.0
Camera Driver Version: 0.0.1.6

AMD Radeon R9 200 Series 4095MB
Connected to OVRService server.
------

Firmware: 2.12
Sensor s/n 205JBR04SBK3
Camera s/n 215JBR04SBK3

It would be interesting to hear what was the outcome of those returned units like yours? I wonder if anyone at Oculus tell us whether there were faults found in the return units with this problem? If so where/what was the fault and what was the method of finding it? I get that this could come across a bad PR but this is a dev unit, its going to have teething problems, I think most of get that when we signed up to experiment with the unit.

I was playing around with a USB analyzer last night, seems like the headset is not talking to graphics card as there seems to be no back and forth communication going on between the two things.

----
Connection Information
Port: 1
Speed: Full Speed
Device address: 2
Open pipes: 1
Connection status: Device connected

Device Descriptor
USB version: 2.0
Device class: 0x0 - (Defined at Interface level)
Device subclass: 0x0 - Unknown
Device protocol: 0x0 - Unknown
Control pipe max size: 64 bytes
Vendor ID: 0x2833 (Unknown)
Product ID: 0x21 (Unknown)
Product version: 2.12
Manufacturer: Oculus VR, Inc.
Product: Rift DK2
Serial Number: H1DEMAR6N1E23K00R000
Configurations: 1

----
Packet view mode:

00000000 22.10.2014 23:23:35.290 UP PnP: Device Connected
00000001 22.10.2014 23:23:36.918 +1.628 DOWN 0x00000000 URB_FUNCTION_CLASS_INTERFACE
00000002 22.10.2014 23:23:36.918 +0.0 UP 0x00000000 URB_FUNCTION_CONTROL_TRANSFER
00000003 22.10.2014 23:23:39.918 +3.0 DOWN 0x00000000 URB_FUNCTION_CLASS_INTERFACE
00000004 22.10.2014 23:23:39.918 +0.0 UP 0x00000000 URB_FUNCTION_CONTROL_TRANSFER

Above HMD switched off.
Below HMD Switch on.

00000007 22.10.2014 23:23:41.056 +0.002 UP 0x00000000 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
00000009 22.10.2014 23:23:41.058 +0.002 UP 0x00000000 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
00000011 22.10.2014 23:23:41.060 +0.002 UP 0x00000000 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
00000013 22.10.2014 23:23:41.062 +0.002 UP 0x00000000 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
00000015 22.10.2014 23:23:41.064 +0.002 UP 0x00000000 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
00000017 22.10.2014 23:23:41.066 +0.002 UP 0x00000000 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER

------
URB Mode:

The USB device has just been connected to the system.
000001: Class-Specific Request (DOWN), 22.10.2014 23:23:36.918 +1.628 (1. Device: USB Input Device)
Destination: Interface, Index 0
Reserved Bits: 34
Request: 0x9
Value: 0x311
Send 0x6 bytes to the device

11 00 00 0B 10 27 .....'
000002: Control Transfer (UP), 22.10.2014 23:23:36.918 +0.0. (1. Device: USB Input Device) Status: 0x00000000
Pipe Handle: Control Pipe
11 00 00 0B 10 27 .....'
Setup Packet
21 09 11 03 00 00 06 00 !.......
Recipient: Interface
Request Type: Class
Direction: Host->Device
Request: 0x9 (Unknown)
Value: 0x311
Index: 0x0
Length: 0x6
000003: Class-Specific Request (DOWN), 22.10.2014 23:23:39.918 +3.0 (1. Device: USB Input Device)
Destination: Interface, Index 0
Reserved Bits: 34
Request: 0x9
Value: 0x311
Send 0x6 bytes to the device

11 00 00 0B 10 27 .....'

000004: Control Transfer (UP), 22.10.2014 23:23:39.918 +0.0. (1. Device: USB Input Device) Status: 0x00000000
Pipe Handle: Control Pipe
CA 01 DF 7C 00 AB Ê.ß|.«
Setup Packet
21 09 11 03 00 00 06 00 !.......
Recipient: Interface
Request Type: Class
Direction: Host->Device
Request: 0x9 (Unknown)
Value: 0x311
Index: 0x0
Length: 0x6

Above HMD switched off.
Below HMD Switch on.

000007: Bulk or Interrupt Transfer (UP), 22.10.2014 23:23:41.056 +0.002. (1. Device: USB Input Device) Status: 0x00000000
Pipe Handle: 0x842fcb8 (Endpoint Address: 0x81)
Get 0x40 bytes from the device
0B 00 00 02 B1 C0 87 0C CA 01 DF 7C 00 AB B8 5A ....±À‡.Ê.ß|.«¸Z
DA 3F C6 24 00 00 00 00 00 00 00 00 FF C8 C8 68 Ú?Æ$........ÿÈÈh
F1 C0 F5 A2 00 00 00 00 00 00 00 00 30 04 92 E1 ñÀõ¢........0.’á
CF 02 00 00 00 00 00 00 00 06 B7 B9 DF 57 53 4F Ï.........·¹ßWSO


000009: Bulk or Interrupt Transfer (UP), 22.10.2014 23:23:41.058 +0.002. (1. Device: USB Input Device) Status: 0x00000000
Pipe Handle: 0x842fcb8 (Endpoint Address: 0x81)
Get 0x40 bytes from the device
0B 00 00 02 B3 C0 87 0C 81 09 DF 7C 00 A2 C0 61 ....³À‡..ß|.¢Àa
7A BF C2 68 00 00 00 00 00 00 00 00 FF DD A8 70 z¿h........ÿݨp
BC C1 08 AA 00 00 00 00 00 00 00 00 30 04 92 E1 ¼Á.ª........0.’á
CF 02 00 00 00 00 00 00 00 06 B7 B9 DF 57 53 4F Ï.........·¹ßWSO


000011: Bulk or Interrupt Transfer (UP), 22.10.2014 23:23:41.060 +0.002. (1. Device: USB Input Device) Status: 0x00000000
Pipe Handle: 0x842fcb8 (Endpoint Address: 0x81)
Get 0x40 bytes from the device
0B 00 00 02 B5 C0 7D 0C 39 11 DF 7C 00 0D 70 71 ....µÀ}.9.ß|..pq
6F C0 10 CC 00 00 00 00 00 00 00 00 FF 3F 68 7C oÀ.Ì........ÿ?h|
13 BF E6 FE 00 00 00 00 00 00 00 00 30 04 92 E1 .¿æþ........0.’á
CF 02 00 00 00 00 00 00 00 06 B7 B9 DF 57 53 Ï.........·¹ßWS

(An Infinite time loop no matter the HMD mode set).

joueur, not sure what to say or suggest here, I emailed support last friday, it's now Wednesday night now with no reply. I get that they are busy but I'd have thought they'd at least try to stick to their suggested reply times.

The Oculus VR Support team is the office and answering tickets Monday through Friday, 9am - 6pm PST/PDT. We plan to expand the days and hours of operation in the future.

Our typical response time is within 1 business day. If there is additional investigation required to resolve your issue, an additional 1-2 business days may be required.

Seems I've already missed the latter part of that without reply. :roll: 😞 Anyway, I'll continue sipping my peppermint tea whilst waiting for an email and trying to think of new ways to ignite this thing into life! 🙂

[ColinB]

"sneakyminky" wrote:


I find it doubtful that all of our units are faulty, man 🙂

Some may find it doubtful that all of the units are ok. man.

[ColinB]

"PacalB" wrote:

"ColinB" wrote:

"sneakyminky" wrote:
Add me to the list, folks.
Same thing. Orange light and no display.

Disappointed to say the least...

Would be interested in seeing the serial number of these units. Possibly there was a batch of (maybe) faulty headsets sent out?
Of course this pre supposes that the folk having this problem do actually have faulty rifts !
In my case I certainly did!

EDIT
my info. For the faulty one:

Sensor s/n 203Y1H04V7VB
Camera s/n 213Y1H04V7VB

Hey there ColinB, my info:

Oculus Configuration Utility
Version 1.4 Rev 1 (SDK 0.4.2)

------
Display Driver Version: 1.0.25.0
Camera Driver Version: 0.0.1.6

AMD Radeon R9 200 Series 4095MB
Connected to OVRService server.
------

Firmware: 2.12
Sensor s/n 205JBR04SBK3
Camera s/n 215JBR04SBK3

It would be interesting to hear what was the outcome of those returned units like yours? I wonder if anyone at Oculus tell us whether there were faults found in the return units with this problem? If so where/what was the fault and what was the method of finding it? I get that this could come across a bad PR but this is a dev unit, its going to have teething problems, I think most of get that when we signed up to experiment with the unit.

I was playing around with a USB analyzer last night, seems like the headset is not talking to graphics card as there seems to be no back and forth communication going on between the two things.




joueur, not sure what to say or suggest here, I emailed support last friday, it's now Wednesday night now with no reply. I get that they are busy but I'd have thought they'd at least try to stick to their suggested reply times.

The Oculus VR Support team is the office and answering tickets Monday through Friday, 9am - 6pm PST/PDT. We plan to expand the days and hours of operation in the future.

Our typical response time is within 1 business day. If there is additional investigation required to resolve your issue, an additional 1-2 business days may be required.

Seems I've already missed the latter part of that without reply. :roll: 😞 Anyway, I'll continue sipping my peppermint tea whilst waiting for an email and trying to think of new ways to ignite this thing into life! 🙂

Well there's certainly lots of info. for the team to look at !

I agree about a test method for the display. Just something to light up the rift so one would know if the display was faulty or not. But there doesn't seem to be one?

As far as support goes, I had the problems of delays with support. It seems a long time !
But later when things get going you tend to forget the waiting time.

And you are not waiting any longer than I did...yet 🙂

Just be careful with that peppermint tea. We don't want any ignitions !!

[joueur]

"sneakyminky" wrote:

"joueur" wrote:
Try another computer, nothing.
I wonder where everyone is now? Do we go for replacement process, we don't have any instruction. I agree we are developers, but hardware or software, do we have guide to open this thing to test the screen or something?
It's not clear if my Oculus is broken or not.

I find it doubtful that all of our units are faulty, man 🙂
More likely it's a software issue with certain hardware configurations.

We just have to wait for Oculus to fix it.

Wait? How you do that? :?

[sneakyminky]

"ColinB" wrote:

"sneakyminky" wrote:


I find it doubtful that all of our units are faulty, man 🙂

Some may find it doubtful that all of the units are ok. man.

Be 'that guy' if it makes you happy, dude.
I'll just wait.

[mcansler]

If you are having issues with video getting to your HMD in direct mode, try Bilago's VR Game Manager, viewtopic.php?f=26&t=12754

I was able to get the Tuscany demo working using that app.

I'm running the Rift on an Asus G75vw laptop.

I hope that helps someone.


Monte

[zakvt]

"cybereality" wrote:
@zakvt: Can you check for any error messages? Either in the Winodws event log or in the Config Util debug log?

hi yes have sent report to support no answer yet

[Pieter]

Is the Oculus staff following these forums at all?

There seem to be many many DK2 users/testers who can't get the device working at all. Are we stupid? There must be something seriously wrong if so many can't get it to work. And to test and provide feedback the least we need is for the DK2 to work.

I can get the desk demo to work most of the times, sometimes the other demo, but none of the other demos have worked for me thus far.

OCULUS STAFF: PLS. START COMMUNICATING ABOUT THIS PROBLEM

This is about your core business, the DK2...