Anyone had -8609 when plugging in their new sensor?

[steveoz32]

I had it at first, kept retrying and it went away, seems it comes back though?

Not really sure what a -8609 exactly means.

I've tried other USB ports and even the same port the original one is plugged into and same issue, my original however is fine.

[Jamesparker_1]

I had to keep swapping USB ports. Eventually the screen just told me they were ok.

[steveoz32]

Hmmm same. Even unplugging and plugging it back into the same one, or just leaving it along and keep retrying sometimes works.

I noticed this though in device manager:

USB\VID_2833&PID_3031&REV_5000

That's a rift sensor, it has a yellow exclamation, it shows as Generic Superspeed USB Hub, and I do not know why it shows that it has an error. It is in a working USB 3.0 port. Even tried swapping with the original sensors location.

Something isn't right with it.

[steveoz32]

Hmmm, weird, so I have another device ID the same, could be the other sensor, it shows fine as just a generic USB hub, when I disable the one above, the sensor still works so could be a red herring.

[Anonymous]

got the same but im using inateck pci 2 usb 3.0 nothiing works pulld out all other tryd every usb port still say  8609

[steveoz32]

Biomodse said:

got the same but im using inateck pci 2 usb 3.0 nothiing works pulld out all other tryd every usb port still say  8609

It's odd, I also left the PC on and the sensor plugged in on the sensor detection in oculus touch, kept trying and eventually it just works!

[MrWonderstuff]

I have issues with the Inatek drivers so uninstalled them (tracking and no USB 3.0) - am using the Microsoft ones now which seem better (less hiccups when tracking and it says USB 3.0 now). I still have a 'warning' saying If I get any tracking issues to update the drivers.

[kogermax]

i got the same problem. 😞

[HoIIywood]

In my experience, -8609 is indicating poor tracking, which has often been down to USB bandwidth or some USB related error due to drivers.

For the latter, and example would be that some people have tried using the Windows 7 Microsoft USB extensible driver instead of the default version 1.0 which is used in Windows 8 and 10. While it works for some, the downside for others is it causes previously working USB device connections to go haywire and in the case of the sensors, spits out -8609 tracking errors.

You'll also most likely have a notice in Oculus Home about updating your drivers.


In the former, where bandwidth is a concern, you can try another USB controller if your motherboard has one, or a USB 2.0 slot instead. 


Do not be fooled by the fact that sometimes you can replug the sensors and it works for a while or passes the sensor tracking test. If there's any issue with it, it will rear it's head in due time.

Your alternative options are to buy the popular Inatek or similar Fresco chip based PCI/PCI E USB card and or an external powered USB hub.

If at that point (and with no extension cables being used) the sensor still fails, then I would request an RMA.

Make sure to get your logs prepared and then open a support ticket. They need all the feedback they can get as there are some serious issues with the sensors and the software which they are aware of - more reports coming in help them get closer to a resolution for everyone.

• Logs can be generated in C:\program files\Oculus\support\Oculus-diagnostics
• Run the OculusLogGather and click All Logs
• It will auto zip the files which you can attach to your support ticket.

[steveoz32]

Thanks for the info, have also already provided oculus with the logs a couple of weeks back, still waiting a response.