i had my hmd running with a 5m usb 2.0 extension last year (no eye tracking) and it did fine (including audio)
also i got my 8m kit for using the eye tracking directly connected to the computer, works at 120Hz as with my short cable, so testing some games with eye tracking can begin
USB2 only has a maximum of 480Mb/s, so 1Gb of Bandwidth couldnât be reserved. So, even if there was only 1Gb reserved for the USB-C ports with a USB3 interface, that would still be double the maximum bandwidth of what the USB2 could do and that is neglecting all the other stuff thatâs also plugged into the USB2 interface. USB3 has about 10 times the capabilities of USB2.
And why anyone would think that was enough when even long before the kickstarter development eyetracking AND handtracking both individually already had problems with the bandwidth of even one undivided USB port. And the whole modular approach was supposed to host both and potentially more.
The interface in the HMD is still just one USB2 Hub that is not capable of more than 480mb, no matter what cables or connections go there. There is no way for the connection from the USB2 Hub to the PC to ever exceed 480mb/s. The only important connection is the connection of the one USB2 hub to the PC, no matter whatâs inbetween or around it or anything.
And even if there was a second USB2 hub it would still not change the fact that USB3 would have had a lot more bandwidth and should have been seen as a requirement early on.
Edit: So I just checked my top USB C port to check if it goes to another hub or just another port and apparently it doesnât do anything at all. No connection with any device that works with the bottom port. So I guess I donât even have a top port. Never had a reason to check that before.
As far as I know thatâs usb2 only, so even though pimax advertise the HMDâs as usb3 ports itâs irrelevant. There is only 1 version of cable available I believe so all performance limits end there for anything except the X and its different cable.
Ăhhhmm , ernsthaft?
Shift.
I take everything back and claim the opposite. This is a 7port 2.0 controller.
Then the eye tracker can not even hold the 30 Hz, because the rest is still running. Will the lighthouse still function without lag at all?
only now do I get the excitement. The whole time I assumed that it was the other IC and that you only used two of the separate 2.0 outputs for the sockets.
This is the chip that replaced the 2137b chip. Depending on what kind of device is plugged into the 8kX it will show as the 5537b usb 3 hub in the usb c port or a 2137b if the deivice is usb 2.
As the document lists it has 5Gbs cs usb 2 which has 480mbs. The usb 2 parts of the controller could be utilized for Audio, imu sensors. Leaving the bulk of the usb 3 lanes for bidirectional for tracking and modules that require high bandwidth.
@Raujok tested the usb-c cable from the ET on a usb-c NVME drive. This cable is wonky as he needed to roatate tge straight connector to have it show as a usb 3 device on both his pc and 8kX usb-c port.
The cable when used caused it to not function when used with this cable.
This chip should have been used in the earlier pimax headsets with an all in one cable on these headsets. Then yes it maybe fixed with firmware updates.
I would recommend you checking your 8k+ plug to see if it is a usb 2 or usb 3 cable.
I could be considerably different as the old chip is not available. Clearance of old obsolete models often sell for considerably less than manufacturing prices to get rid of stock from sitting taking up space and is more coat effective than scrapping remaining stock.
Apples and oranges. But I usually buy last yearâs work boots as a $300 boot can often be bought for $100 or less new.
The 5537 costs maybe $2/piece for 1000 here in europ. (Edit $4 ohh, expensive)
In China maybe 50cent, I mean. (Edit, then the twice)
BTW, the Color of the usb connector is a good note, but not all adhere to it. On my Asus mainboard, the blue sockets are usb 2, the black ones are usb 3. One of the employees was color-blind. (was a B-ware)
Unfortunately, I donât have a C to C cable here, otherwise I would have measured the throughput with a smartphone. Maybe next week.