Thanks Tobi, have tried those things without luck and I bought a new ferrite/shielded cable and a new extra usb 3.1 card just to run only the sc2pro from… sadly the problem persists exactly the same and I feel like I am just wasting money now.
Hey Paul I never heard of a usb isolator but I will look into that and have a good read of that thread. I am feeling desperate to try anything. Do you guys think there is any chance the power brick itself could cause the wheelbase to disconnect or turn off & on again ? And how would I check that ?
Well, it was a desperate attempt for you to try to drive with very reduced FFB level to see if that had any effect on the issue you are having. But you didn’t report back any results.
Well yes I replied directly under what you wrote. I reported the FFB levels & settings I use and asked are they low enough ?
How do I test for fault in power supply ?
I am desperate to try anything and would very much appreciate your help.
You reported the levels you were using, but didn’t report if the problems persist with much lower levels than what you are using.
There is no particular test on PSU that a end-user can do, but running with reduced FFB level could rule out any issues with that, or any weird issues inside the device. But this is all blind speculation, there is no particular fault in my mind that we know of, that would cause this.
Ok I will try tomorrow with FFB at say 7 or 8nm. Is that low enough ?
Any setting lower than you have currently, is good. This is to try to find a relationship about your issues and FFB strength. I suspect there will be no relationship…
You can check the power-supplies with the old SC2 Pro by unplugging one. There should be still FFB.
Just had a 30 minute race and problems came back after 20 min. or so. The base was beeping a few times without any inputs after the race, but not during the race. I’m using 70% torque in TD, 70% gain in AMS2 and it didn’t get warm on the top where the sticker is. The FFB does not only go off for a split of a second, but also returns in a weaker mode for some seconds. Doesn’t sound like USB-related to me…
Ah very interesting info ! @Leynad - I have R2 sc2pro so only one 300w (tested/rated to 480w) power supply which is not a Meanwell but Phihong.
I need more time to test but I am running lower FFB strength set in TD as suggested by @Mika - I started at 8Nm and worked my way upto 14Nm.
So if I do not have any loss of FFB or disconnects at lower Nm force settings does that mean my psu has some problem that it cannot sustain higher Nm forces without disconnecting ? Or does it point to something else ?
What I have now notice is a strange feeling where FFB will suddenly very light for a second or lags a little, which I now recognise is a precursor to a full disconnect / reset of wheelbase, it goes off then on again. That seems to consistently happen some minutes after, while still racing.
Maybe some clue to what is happening there for much smarter people than me !?
I really have only basic to medium level understanding of this stuff but I am dedicated to find a solution. I would gladly pay for new power supply if that is the solution because I already invest over Aud $4000 in this sc2 Pro including my 2 x wireless wheels and I just want to race happily without these disconnects.
- The best way to clear if this is wheelbase problem is to test with different PC. Just borrow one for a day, even laptop will do.
- Try to capture event log when disconnect happens, on Advanced Info tab there is “Download debug event log”
- Try downgrading to 2020.10 FW, this is the last known release with truly stable USB.
1 Like
Thanks Andrew and I do not have access to another pc at the moment. I have gone back & forth to the 2020.10 fw many times and eventually gave up on it as the problems were exactly the same.
Today I have installed a new pci-e x4 card with 10gbs bandwidth which I have just my Reverb G2 connected to. My PT motion is now on my other pci-e x1 card by itself and with the sc2 pro direct to my mobo on a 3.1 gen2 port.
I have also moved my sc2 pro psu around to a different mains and running lower FFB torque from 8Nm upwards via TD to see if I can get the system stable. So far it is hanging on well without disconnects but I dont want to speak too soon as I thought I had it sorted couple times before only to have the disconnects start again.
Thanks heaps for all the suggestions and advice from you and other guys here including Mika - I am determined to get to the root of the issue and sort it - just keep plugging away !
@blanes This probably won’t rectify the issue but as a bit of a long shot and just to rule something out, could you try temporarily switching off XMP/DOCP and going back to the default 2400 ram speed, just to see if there is any noticeable change in reliability?
I’m not saying that it would point to PSU, it would just give us something (anything) to go on with troubleshooting your issue.
2021.4_4 is the latest stable with the known to be stable USB code. If he uses wireless wheels, it is very much recommended to use the latest version. There was a buffer overflow issue in the fimware, that could have caused literally all kinds of funny things in the previous versions, but the most typical manifestation was a wireless wheel buttons to stop working momentarily.
Hey @EsxPaul ~ Yeah Paul good idea, I try that early on and I do not have anything else overclocked. It did not change the situation unfortunately but was worth trying for sure.
@Mika ~ Ok for sure, I only asked could the problem be with the psu or lie somewhere else. It is logical to ask these questions to eliminate possibilities. I am not here to do battle with you - I apologise for any misunderstanding but I am not attacking your product, only trying to understand in working towards a solution.
I am using the 2021.4_4 FW and will stick with for sure. I am still testing with lower FFB working fine at the moment but I also fitted new usb hub and changed my power supply to different position. So far so good but time will tell.
I changed the USB-cable and (active) extension yesterday plus using another port and it just passed a stress-test with high torque FFB, so probably not related to the PSU or I my electricity-grid isn’t reliable thanks to ‘renewable energy’. Have you tried it without the Reverb G2? Crash here with a similar system couldn’t get it to run most of the time and I was reading about Reverb-G1-problems with people using motion. It could be some USB-priority-issue that might be Windows-related. Running True Drive as administrator might help, certainly doesn’t harm (an idea that just came up, so haven’t tested it). With GS-5, G-Belt, SimVibe, TrackIR, USB-audio and many other stuff I put quite some stress on my system as well.
Today I spent about 4 to 5 hours altogether racing … zero disconnects. I am pretty sure now that the source of the disconnects has been due to my VR headset, Reverb G2.
This morning I dialled FFB down to 8Nm in TD then over the day tested fully upto 25Nm 100% with no loss of FFB or disconnects. Then I set it back to 18Nm and raced few hours in VR with motion also turned on. 100% connected FFB.
My solution has been a $15 pcie x4 usb 3.1 gen 2 hub with 10gb bandwidth, sata powered. It has only 1 x usb a port and 1 x usb c port. I first tried the sc2 pro plugged to it, then my pt actuator motion but the disconnects continued. Finally I found success with only the Reverb G2 plugged to it, the pt motion to my other pcie x1 hub and the sc2 pro direct to my x570 Asus mobo usb 3.1 Gen 2 port - I only have 2 such ports on my mobo and the sc2 has to be plugged there or I get disconnects. They also are 10gb bandwidth. So it is very precise arrangement of devices to usb ports to 100% work. Nightmare but worth the time it took to discover.
I also have moved the psu to a better spot more isolated just in case there was some emi trouble. I will continue to test for a few more days and hopefully this will be the final solution with no more disconnects.
2 Likes
Have you updated to the latest FW?
https://support.hp.com/nl-nl/drivers/selfservice/hp-reverb-g2-virtual-reality-headset/33835976
1 Like
Hence the reason I proposed the Startech card earlier, it has 4 seperate controllers, which solved my issues on this AMD system for me.
How you did it might have the same end result via the hub, removing the USB high-bandwidth device to a seperate controller in some respects. As long as it’s a powered USB hub, you should be ok longer term.
But I still prefer to totally avoid the onboard AMD USB situation by running my gaming stuff and G2 through the Startech card. Glad you’re finally having some fun though 
Cheers,
Beano
1 Like
Thanks Beano, I investigated the Startech hub ($144 lowest price) but my only x16 port would place it covering my 3090 gpu fans.
Current config seems to be holding up well so far, no disconnects and yeah the little 3.1 card is sata powered. I think the bandwidth hog is the Reverb G2 and I guess followed by SC2 Pro then the PT Actuators.
Good Mate, glad you’re sorted
1 Like