Reverb G2 Suddenly stopped working. HELP PLEASE!!!!

[parxuk]

On 5/23/2022 at 11:23 AM, Parrotnut said:

Another thing to try    Install the driver manually.

 

Download Windows Mixed Reality driver version 10.0.19041.2041 (Windows 10 Version 1903 or newer) from Official Microsoft Download Center

Thanks. Tried without success.

Colleague in work took my headset home. Headset works fine with his cable but not mine and vice versa, so have proved that the 6 month old v2 cable is faulty. Absolutely not caused by me, so it has just failed.

Service call was escalted to highest level but they have refused to help in ayway so I have to purchase a new cable.

Oh well, it's only money I suppose.

[edmuss]

Well the upshot is it's only the cable

As a matter of interest, do you run the cable above or below the frame and inside or outside?

The HP instructions videos show it routed over the top and outside of the frame, however every time you flex the frame hinge this then puts a dirty great big kink in the cable.  Route it under and inside the frame and it doesn't kink half as much.  I minimise the amont I flex mine as a matter of course but it's a terrible bit of cable management the way they show it should be routed.

Attached a photo of mine (with the leap motion fitted obviously) for reference.

edit: attached a screen crop straight from HPs setup guide

https://h20195.www2.hp.com/v2/GetDocument.aspx?docname=4AA7-5420ENW

Edited May 27, 2022 by edmuss

[Phantom711]

Have you tried to plug the G2 into a different display port yet?

I am still using the v1 cable and had less issues after I changed the display port. I get the same error sporadically but I can usually reset it by unplugging power from the G2.

[CaptBadTouch]

I had the same issue start about 1 week ago, 4-1 error no matter what. I found a fix for me, hope it works for you too:

1.) lower left search bar, search "USB"

2.) click on "USB settings"

3.) top left, "bluetooth and other devices"

4.) In there you should either find your headset, or an error item, which is your headset (unrecognized)

5.) right click you headset and delete (remove device).

Then plug and unplug you usb again to force it to re-install. Let me know if this works for you! GL

 

Edited May 27, 2022 by CaptBadTouch

[TylerPL666]

I bought my Reverb G2 about month ago, so also had my 5min of WTF, but this tutorial helps alot:

 

3:57 - U have to realy hard push the cable until u hear "CLICK". And the DOT on cable almost hide in the HMD. Second WTF was when I try (yeah - I know every tutorial says that shoult be default, but I had to try) the PIXEL DENSITY other than 1.0 - black screen immidietly.

[cordite]

I hope the cable is one of the things they improve for a potential G3. They solved the USB connectivity, but not the cable longevity.

The cables are too expensive for this nonsense. And they wouldn't even let people keep the rev1 cables as a (admittedly poor) backup, despite initially saying they would.

 

[edmuss]

Just looking at that video you can see the kink that is applied to the cable, route it inside and below the frame, there is no kinking that way.

[YoYo]

On 5/22/2022 at 1:47 PM, parxuk said:

As per the title. My HP Reverb G2 worked one day and not the next. All I get is Windows mixed reality attempting to start and then a message on screen that states:

CHECK YOUR USB CABLE. MAKE SURE THE USB CABLE IS PLUGGED IN TO THE SUPERSPEED USB3.0 PORT. ERROR CODE: 4-1.

Absolutley gutted because my whole PC/HOTAS is dedicated to DCS and without the headset I cant really use it (I gave my track-ir away).

The Reverb G2 is approx 15 months old and during this time I had the cable replaced with the V2. I am running WIndows 10. Am not aware of any software updates that would have occured to cause this. I have numerous different USB 3 ports and I have tried all of them as well as re-installing the lasest drivers, rescan for hardware changes in device manager etc. The device is visible in device manager as hollow lens sensor. I have unplugged power supplies, re-seated the cable in the headset, prayed etc but nothing has worked. The USB 3.0 ports appear to work fine with USB drives etc.

I have taken the PC apart and reseated power supply cables and the cables to the MOBO.

I have treated this headset like it's made of glass, and have annoyed the family by not even letting my teenage sons use it for VR. I also ensure that the cable is never trapped/bent and is well looked after.

The only thing I have done recently is swapped to openxr and removed steamvr and windows mixed reality for steamvr (or whatever it's called). Fairly sure I have used the headset since then, and dont really see why this would cause a problem anyway.

I have ordered a USB 3 PCI card to try just in case., but whilst waiting for delivery if you have any other suggestions they would be very gratefully received.

If the headset/cable is faulty I beieve the UK warranty is only 12 months. Cany anyone confirm? Once upon a time people used to state that in the UK you got 24 months regarless even though manufacturers would state only 12. Any comments to confirm or deny as I may contact HP? Dont exactly have a spare £600 for a new headset, and even if I did after this experience not sure I would buy another G2 if this one is faulty.

Thanks in advance.

 

So did you find a reason finally? It was the cable?