Fix for Sensor Disconnection Issue

[cybereality]

We've just started rolling out a possible fix for the repeated sensor disconnection issue. This is a problem that could cause the sensor to disconnect while idle on certain hardware configurations. Although we had some trouble reproducing the exact problem in our lab, we have a good idea of what the core issue was and believe it may be resolved.

Some customers have already received the update, and everyone else should have it within a few hours. The update should happen automatically, but you'll have to just unplug and replug the sensor to reset its state.

I'd recommend people wait until later this evening to test and see if the fix actually resolves their issue. Either way, please report back so we can understand if the fix was a success. Thanks.

[jpmera]

Windows 10 aniversary and a z97 motherboard. I have hdmi ands sensor disconnect.

[Hornet_F4C]

XMerc said:

Yes some apps definitely cause more frequent sensor disconnects than others.

Yes, that's definitely something to look into. For me one particular app was unusnable because of this... while all others still work fine (never had a single sensor disconnect before or after). Thats why the issue feels so touchy, just as if it could break any moment... that feeling makes it hard to spend money on apps or periphals (Touch).

My logs along with an explanation of the incident were posted here:

https://forums.oculus.com/community/discussion/42305/sensor-fault-disconnect-caused-by-software-even...

It reported 26 "Hardware health is BAD." messages for the sensor between 12:59 and 14:00 while I tried to run the application in question. I tried without success as it constantly exited to home telling me the sensor was disconnected. The logs seem to say clearly that the sensor is wrecked.

I uninstalled that stuff and played pinball for a while. Everything worked fine and none of those messages is reported anymore after 14:00 until 15:54 (when those logs were created).

However: Reviewing those logfiles, I also found 4 of those "Hardware health is BAD." - messages being reported the day before, Aug 31st at 22:15. I cannot remember of having experienced any problem or drop out, but still those messages are there...

Does that mean the sensor is really broken? So this single expierence was not the cause of the issue but merely made it show up more frequently?

If I don't actively experience problems such as drop outs or disconnects, should I still keep generating those log files to activiely look periodically if these "Hardware health is bad" -  messages persist?

[XlordB]

Well after my reinstall im still going with no disconnect. Bear in mind my usb 3.0 ports are intel but i didnt install any drivers at all from asus website i only let windows itself install all needed drivers and I didnt update to anniversary.. so for now im happy.

[TC1999]

I've had issues with sensor disconnecting after the 1.7 update and the rift affecting other usb devices. 

The fix update resolved the disconnects for me but the rift was still affecting other usb devices. Here is what i did and my two tuppence worth of experience with this.

I've had issues with my hotas stop working while on Elite but if I took my rift off and put it back on the hotas would start working again. This was also happening with the xbox controller. 

I had my hotas, xbox pad and mouse attached to a usb hub that was attached to the usb 3 port next to the sensor port. 

so the rift is affecting anything attached to the usb 3 ports. 

On my my motherboard I have intel usb 3 ports - asmedia usb 3.1 ports and front usb 2 ports. 

I disabled the asmedia 3.1 hub in device manager so only the usb 3 and 2 ports working. 

To fix the issue with my hotas and xbox being affected by the rift I moved them to the front usb 2 port and so far no issues with losing the hotas and hub. 

Now the only thing on the usb 3 is the rift and so far after about 10 hours of no issues with disconnects, sensor or hotas / hub. 

It looks to me some power management issues within the way the sensor and rift communicate their state to the OS. The ERDY and ERD method of readiness is not used with usb 2 and I feel this is where possible the issue is. 

Basically the rift does not play well with others on the usb 3 bus and I feel this is regardless of internal or add on cards. 

Lastly avoid the windows update this is sure to have an impact on the sensor as its bugged many webcams and other devices on the usb bus. I rolled my windows update back to 1511.

Not sure if this will help with any of the issues others are experiencing just wanted to share what I did to resolve mine. 

I've come to the conclusion owning a rift is like having two Faberge eggs and every day you take them out and learn to juggle ...... scary and exciting at the same time until you drop one......oh the tears...... oh the tears  

 

[Turranius]

cybereality said:

@Ryder35 and @Turranius , it looks like you two are having issues with the USB 2.0 mode. In this case, USB 3.0 may side-step the issue (assuming you can use USB 3.0). Also, do you have any bright windows behind you or something that would interfere with the sensor?

I have tried both the USB 2.0 and 3.0 ports. No difference.

I do have a window in front of the sensor. Sensor is not quite pointing towards it but almost. I can try the blinds on the window, but I fail to see how that can cause the USB connection to lose contact. But I will give it a go with the window blinds down.

[flynsqrl]

Hi all,

I had sensor disconnects when idle (for example putting it on my desk, out of view of the sensor).  After a short while it would always seem to disconnect.  I reinstalled Windows 10 and for the past few days it's been great.  No sensor disconnects at all.

I have been keeping track of what has been installed since in case this happens again.

So, I can't confirm if this is related, yet, last night I installed another game that has nothing to do with Oculus.  I noted that it prompted me for VC 2012 redist EULAs.  Today, the first time I used the Rift since installing the game, it started disconnecting again (just like before).  I checked out my Add/Remove programs and noted that there were actually 3x 2012 redistributables (2 for x64 and 1 for 32 bit) which was strange.  Maybe there were there before or not, but this seemed to coincide pretty well.

The suspicious one was 11.0.60610.  And the two others were 11.0.61030 (the latest).  I uninstalled all of them to be sure, then went to Microsoft to get the latest 2012 redistributables (11.0.61030) and freshly installed them.  I then Started Oculus (sensor still showed disconnected), and then restarted via Beta -> restart, and was back in business.  No disconnects for the last few hours, so fingers crossed.

Again this could be totally unrelated, but it seemed suspicious enough to mention and so far, and it is working for me.

[Reversa]

I have the same issue with sensor, i have a ASUS Maximus VIII Hero and with the last firmware (2001) sensor work better with less disconect issues but it still happen (like every 20 minutes), with (1902) the sensor disconnect every second.
Here is my log

[Speeder]

Ryder35 said:

Posted mine already in this thread. Interestingly I notice a number of people having problems are on z97 motherboards, do the logs give you hardware info. Also I and I think most others are having the disconnects when the rift is in use, I get the impression most people were having the disconnects when the rift was idle so it might be a different issue

Not me. I have an ASUS X99S Gaming 7 and I also suffered the damn bug.
This feels bad for the reputation of the oculus team to suffer so long this problem blocker.

[cybereality]

Thanks for sharing the logs. I'll see if we can find anything.

[Ryder35]

cybereality said:

@Ryder35 and @Turranius , it looks like you two are having issues with the USB 2.0 mode. In this case, USB 3.0 may side-step the issue (assuming you can use USB 3.0). Also, do you have any bright windows behind you or something that would interfere with the sensor?

Tried USB 2 and 3 ports; same issues. Nothing behind me but the sensor is about 45 degrees to my left as the stand is so short it won't poke above my monitor.