New to the forums? Click here to read the "How To" Guide.

Developer? Click here to go to the Developer Forums.

Oculus Link fried my motherboard?

AfroHyenaAfroHyena Posts: 6
NerveGear
I had PTC activated and I dont know if that was the issue, but Im pretty sure i fried some USB ports on my motherboard.

When I connected the Quest windows gave me Power Surge warnings a couple of times and i could never get it to work.

Suddenly my keyboard stopped working. I disconnected the quest and restarted my PC.

Now 2 USB ports and my keyboard are not working anymore -.-

Is there anything I can do?

Comments

  • vargabloodvargablood Posts: 75
    Hiro Protagonist
    this only comes from shorting circuits of the connector, never from software like oculus ptc ....
    you can try to get your pc AC less for some minutes, unplug all power cables from your power supply.
    With some luck it will work again or you will have burned your usb chip.
  • DaftnDirectDaftnDirect Posts: 5,574 Volunteer Moderator
    edited November 2019
    If USB 3 can deliver power in both directions, I guess it has the potential to cause problems if there's a cable or connector fault. Maybe if the device being plugged in has power on-board, there's additional risk. No idea though if the Quest has the ability to output power.

    If it can, I wonder if this is something that Oculus are considering when designing their cable (or firmware)... only have power delivery in one direction. The other thing to consider when choosing cables is avoid where possible adaptors as every additional connection introduces a potential for fault.

    Whatever the cause, I hope your problem gets resolved.

    Edit: I'd hope though that USB hubs have protection built-in, for all these types of problems, am I hoping too much?
    Intel 5820K [email protected], Titan X (Maxwell), 16GB Corsair Vengeance DDR4, ASRock X99 Taichi, Samsung 500Gb 960 Evo M.2, Corsair H100i v2 Cooler, Inateck KTU3FR-4P USB 3 card, Windows 10 Pro v1903 (18363.720)
  • dingofoxvrfoxdingofoxvrfox Posts: 43
    Brain Burst
    I can tell you why your usb took a dump. 

    There are 2 types of usb 3.0 ports powered and non powered if you installed the quest onto a non powered port you will pull to much voltage and burn out your usb connection 
  • AfroHyenaAfroHyena Posts: 6
    NerveGear
    so after disconnecting all usb devices and powering off / switching off the psu, i got all functionality back. phew
    i still get the "power surge on usb port" message but if the oculus software successfully pairs with the quest the message goes away.

    still kinda scary and i am not sure what's causing it. I also dont know anyhting about powered or non powered usb ports. Aren't they all powered on the motherboard?
  • enigma01enigma01 Posts: 661
    Neo
    edited November 2019
    AfroHyena said:
     I also dont know anyhting about powered or non powered usb ports. Aren't they all powered on the motherboard?
    Yes they are... I think what DaftnDirect is saying is that because the Quest also has an internal battery there is the potential for it to push an electrical signal back down the cable. I guess this potential isn't there with the Rift as it doesn't have onboard power. 
  • kojackkojack Posts: 6,165 Volunteer Moderator
    This is actually a common problem with poorly designed cables. If you buy a cheap one, it may do this.

    The problem is the USB port on the motherboard identifies itself as being able to handle maybe 2 amp draw max. The Quest identifies itself as accepting up to 3 amps. The cable should allow them to negotiate. But a cheap cable will just let the Quest draw whatever it wants regardless of what the motherboard says it can handle.




  • AfroHyenaAfroHyena Posts: 6
    NerveGear
    kojack said:
    The problem is the USB port on the motherboard identifies itself as being able to handle maybe 2 amp draw max. The Quest identifies itself as accepting up to 3 amps. The cable should allow them to negotiate. But a cheap cable will just let the Quest draw whatever it wants regardless of what the motherboard says it can handle.




    ok I think I will return the cable then and try another one. thanks!
  • enigma01enigma01 Posts: 661
    Neo
    AfroHyena said:
    ok I think I will return the cable then and try another one. thanks!
    What cable was it?
  • AfroHyenaAfroHyena Posts: 6
    NerveGear
    enigma01 said:
    AfroHyena said:
    ok I think I will return the cable then and try another one. thanks!
    What cable was it?
    it was a 3m USB A - USB C  cable from "mumbi". got it from german ebay
  • adaptogenadaptogen Posts: 1
    NerveGear
    Did a new cable fix your issue? I'm trying to connect to my quest to PC just for simple media transfers, and am getting the surge warning. That being said, I'm using a China cable that is undoubtedly not super high quality. My USB port gets disabled until I restart my computer.
  • DaftnDirectDaftnDirect Posts: 5,574 Volunteer Moderator
    adaptogen said:
    Did a new cable fix your issue? I'm trying to connect to my quest to PC just for simple media transfers, and am getting the surge warning. That being said, I'm using a China cable that is undoubtedly not super high quality. My USB port gets disabled until I restart my computer.
    For media transfer I've been using the cable that came with the Quest... have you tried that and does that trigger a warning on your PC?
    Intel 5820K [email protected], Titan X (Maxwell), 16GB Corsair Vengeance DDR4, ASRock X99 Taichi, Samsung 500Gb 960 Evo M.2, Corsair H100i v2 Cooler, Inateck KTU3FR-4P USB 3 card, Windows 10 Pro v1903 (18363.720)
  • AfroHyenaAfroHyena Posts: 6
    NerveGear
    edited January 5
    Did a new cable fix your issue? I'm trying to connect to my quest to PC just for simple media transfers, and am getting the surge warning. That being said, I'm using a China cable that is undoubtedly not super high quality. My USB port gets disabled until I restart my computer.
    In case this will help someone: Yes, changing to another cable ended up fixing my issue
Sign In or Register to comment.