Question KIWI Link Cable Connection Issue

[kubrat]

Hello,

I recently purchased a Quest 3S and a KIWI Design Link Cable to connect it to my PC.

Yesterday, I had some time to set everything up. First, I connected the Quest 3S to my PC using the KIWI Design Link Cable to see if it worked. I plugged the cable into the front USB 3.0 port of my PC case, and the yellow light on the side of the headset lit up. After that, I removed the cable from the USB port and proceeded to download the Meta Quest Link app. I installed the app, logged into my account, and completed my profile settings until I reached the step to connect the headset to my PC.

I then connected the Quest 3S to my PC using the KIWI cable, but this time, a warning appeared stating that the USB device was not recognized. Additionally, another warning appeared saying, "The last USB device you connected to this computer malfunctioned, and Windows does not recognize it." I’ve included screenshots below.

https://imgur.com/a/TIfgJXs

View: https://imgur.com/a/TIfgJXs

I then connected the KIWI cable to the second usb port, which is usb 2.0- no error appeared but also it was not connecting the headset to the PC.
The third USB port is the second 2.0 port, where I have my headphones connected. I unplugged the headphones and tried connecting the KIWI cable there, but the same thing happened as with the first 2.0 port: no error message, but the headset still didn't connect to the PC.

Next, I decided to test the USB ports on the motherboard. I have two USB 2.0 ports, two USB 3.1 Gen 1 ports, and one USB 3.1 Gen 2 port on the motherboard. My mouse and keyboard are plugged into the two USB 3.1 Gen 1 ports, and the others are unused. I plugged the KIWI cable into the USB 3.1 Gen 2 port, but the same error message appeared: "USB device not recognized." I then tried the USB 2.0 ports on the motherboard, and again, the same error message occurred. Plugging the cable to the 3.1 Gen 1 port does nothing - no error but also not connecting the headset

Finally, I tested how the mouse and keyboard would behave if I unplugged them from the motherboard ports and tested the front USB ports. I plugged the keyboard into the front 3.0 and the first 2.0 port, and there was no error message, but I heard a constant USB connect and disconnect sound. The keyboard worked fine with no issues or sound errors when plugged into the second 2.0 port (which, as mentioned, I usually have my headphones plugged into). I then tried the mouse on the first 2.0 front port, and it worked fine with no error messages or sounds, despite the constant USB connect/disconnect sound when the keyboard was plugged in.

I'm not sure whether the issue is with my PC's USB port, the KIWI cable, or both. As mentioned above, some of the ports work fine with certain devices, while others do not. Generally I don't use the front USB 3.0 port and the 2.0 port next to it because, if I remember correctly, I had problems when plugging in USB sticks.

I would greatly appreciate any help in solving this problem. Thank you!

My current PC setup will be replaced with a new build in mid to late December, once the parts for the new system arrive. Until then, I have the current setup (all components were purchased brand new by me, with most acquired in mid-2019, except the GPU and CPU):

PC Components:

• CPU: Ryzen 5 3600
• GPU: RX 6600
• Motherboard: MSI B450 Tomahawk
• RAM: Corsair Vengeance LPX 16 GB
• Storage: Samsung 870 Evo 1 TB, SanDisk Ultra 3D 500 GB
• Power Supply: SeaSonic S12II 520 W 80+ Bronze
• Cooling: Noctua NH-U9S
• Case: Deepcool Kendomen

Peripherals:

• Monitor: Acer Nitro XV242Y
• Keyboard: Thor 303 TKL
• Mouse: Logitech G102 Lightsync
• Headset: Canyon Nightfall GH-7

 

[Paperdoc]

The problem could be the cable OR the Quest 3S headset. Do you have ANY other USB3 cable you can try? For example, the headset comes with a charging unit that includes a cable said to be able to work for data as well as just charging.

I expect that headset system needs the speed of USB3 to work. So it is possible that the driver supplied with that headset simply will NOT try to find or use it via any USB2 port. It may work ONLY on USB 3 Gen1 or Gen2 ports.

 

[kubrat]

The problem could be the cable OR the Quest 3S headset. Do you have ANY other USB3 cable you can try? For example, the headset comes with a charging unit that includes a cable said to be able to work for data as well as just charging.

I expect that headset system needs the speed of USB3 to work. So it is possible that the driver supplied with that headset simply will NOT try to find or use it via any USB2 port. It may work ONLY on USB 3 Gen1 or Gen2 ports.

I have an external hard drive enclosure, the ORICO 3588US3-V1-EU-BK (exact model), which has USB 3.0. I have one of my storage hard drives in it. The enclosure requires both the USB cable and the power adapter to be connected, as well as the power button to be switched on. I plugged it into my PC case's USB 3.0 port, and it worked perfectly. There were no errors, and I was able to access my hard drive files without any issues.

The Quest 3S charging cable has USB Type-C connectors on both ends. I initially charged the headset without issues, but to confirm, I just plugged the Quest 3S charger into a power outlet using the included power adapter. The orange light turned on, so it was charging. After about 5 minutes, the light turned green, so it must be fully charged (as I mentioned, I had already charged it the other day). I charged it directly through the power adapter and not via a PC.

Does that mean the problem is the KIWI Cable?

Edit: Going to check all my drivers again. Though, I have the latest (non-Beta) BIOS, and I have all drivers up to date, since I reinstalled Windows 2 months ago.

 

[Paperdoc]

Your last post tells us two things.

1. The case USB3 port works -at least for data, VERY probably for power.
2. The charger and its cable supplied with your Quest 3S system works for charging. That does not prove it will work for data; nor does it prove that the Quest 3S system itself works.

You should try this test. Take that charging cable that came with the Quest 3S system, disconnect from the charger module, and use it to plug into a mobo USB3 Type C socket. Does not matter whether Gen1 or Gen2. Now it is being used both to charge AND to move data. It is possible that Windows may pop up a window on your screen to say that a new device has been found and it is installing the required driver software.

1. See whether the the device is recognized. Go into Device Manager (use the search window on your screen bottom left to find that). Search through the listed devices for the Quest 3S system. If it is there but with NO flags beside it, Windows has found and recognized it.
2. If it has a yellow caution triangle beside it there is a problem. Very often this is simply that no driver has been installed. For that you have two choices. One would be to RIGHT-click on the device and choose to install its driver. The BETTER option might be to cancel that and back right out of Device Manager, then run the Meta Quest Link tool that came with the headset to install the driver they provided. Then go BACK into Device Manager to check that it is there with no problem flag.
3. If Device Manager does NOT have the Quest 3S system in its list, click on the very top main item of the list (your entire system). The in the top-line menu click on Action and choose Scan for Hardware Changers. This forces Windows to re-scan the entire system and find all devices that are working at a basic level. That should find your Quest 3S and add it to its list. If it has NO flags on it, it is probably OK with a connected driver and you can just back out. If it has a flag, see #2 above.
4. If even that re-Scan process does NOT find the Quest 3S, then that unit probably is faulty, OR the cable you are using is faulty.
5. With all that done back out of Device Manager. Try using the Quest 3S unit in Windows. If it works, you're almost there!
6. With all that done, switch back to using the KIWI cable system. See if it still works. If yes, total success! If no, then the Kiwi cable is faulty.