KVM Model:
SQ8415090
USB Interface (5-gigabit or 10-gigbit):
5-Gigabit
Problem:
The Wooting 60HE does not work on the HID port. It simply will not power on or react in any way, it’s as if it is not plugged in at all. I have tried disabling NKRO on the keyboard and that had no effect. I know that it is stated that the keyboard must be fully HID-compliant and I assume that is the root of the issue here. I believe this is probably a general problem with Wooting products, the only other post in this forum that references Wooting states that they can’t get their Wooting 2 to connect on the HID ports and had to move it to the USB 3 ports (they believed it was a power supply issue, I don’t believe that it is).
I guess my question is basically do you have any experience with Wooting keyboards, and would there appear to be any path to getting them to work as HID inputs to the/a KVM? Is there any information I can give you about the Wooting 60HE I have and how the system recognizes it that would be of any help?
As a seperate question, on a thread that dealt with keyboard issues on the HID ports (“glorious-gmmk2-not-working-on-hid-port-of-dp1-4-kvm”) I see it mentioned that the USB-HID ports are “soft cut over” and the USB 3 ports are “hard cut over.” Is it possible to have USB 3 ports “soft cut over,” or does that not make any sense?
I think I will ultimately keep this KVM (its performance switching the HID ports between machines is insanely good). I was hoping to utilize keyboard switching and also leverage the ability to have the K&M ports and USB 3.2 ports not follow each other, but I think I’m willing to compromise on both. (I also understand that I could find a different keyboard to use, but I don’t think I’m ready to do that quite yet.)
Other Notes:
Thanks in advance for the help!
One other finding, the newest Logitech Lightspeed that ships with the Logitech G PRO X SUPERLIGHT 2 shows a lot of stuttering at all reporting rates (125 Hz - 4000 Hz) when plugged into the HID port. The older Logitech Lightspeed receivers have no issues though - the one that shipped with all of their previous Lightspeed mice.
I see other people have mentioned issues with really high report rate mice. Thought it was interesting that turning down the report rate had no impact on stutterting.
I have no question related to this I guess this is just an FYI.
If you can flash qmk itll proably resolve the issue as long as it doenst have a built in usb hub inside the keyboard.
Can you post pics of the serial/item#? For rhe reciever. Also uninstall all logitech software from both pcs to see if that makes a difference. Usually software polling rate mismatch bwtwen hosts can be a source or percieved stutter but genrtally 4khz polling is fine.
Logitech had one run of bad hardware caught in qc they never actually sold, but showed up on ebay with srial #s scratched out. And those were not fun to try to support…but that was years ago
1 Like
No built in USB hub on the keyboard, but it (and other Wooting keyboards) is one of those analog Hall Effect switch keyboards. As far as I can tell no one’s attempted and documented flashing QMK on a Wooting - their main selling point is the fancy stuff they can do with the analog switches and the on-board controller. Their firmware is actually open-source at GitHub > WootingKb > wooting-analog-sdk as it turns out.
Popular brand in gaming, but I don’t think there’s a huge volume of these keyboards out in the wild. Not sure if it’s worth your time to look into, but thought I’d throw my observation out there. I’m using the keypad specific HID port for control now and am happy enough with that work flow at this point.
Here’s photos of the front and back of the Logitech Lightspeed Receiver I was using that had stuttering (I believe the text is as legible as it is to me looking at it in person, but if you’re not sure on a character let me know):
EDIT: Also forgot to add - no Logitech software running (G Hub, Options, or Options+)
Thanks for the info I’m not sure about this one, but thank you for point this information out!
For now, we have had success creating a KVM hotkey switcher out of a macropad.
You’re welcome!
Also, re: the Superlight 2 receiver - one thing I think that’s worth pointing out is Logitech designed those Ligthspeed receivers to have a keyboard and mouse paired to one receiver. I know you guys got Unifying receivers to work, but this at least is the major difference from the old Lightpseed Receiver (other than the increased available polling rates).
And yeah I ended up using small programmable keypads as switcher devices, that works very well!
For the sake of someone finding this thread in the future and looking for ideas/closure, my setup is:
-
A G Pro Superlight (instead of the Superlight 2 which had stuttering issues) plugged into one of the mouse/keyboard HID ports.
-
The Wooting 60HE plugged into the USB3 header on the KVM.
-
A MK321-Pro (3-key pad sold under various brandings) hooked up to the other mouse/keyboard HID ports and I used its software to program keyboard hotkeys to it.
-
A Vaydeer “One-Handed Macro Keyboard - 4 Programmable Keys” hooked up to the keypad-specific HID port and I used its software to program keypad hotkeys to it.
Basically the only drawbacks are slightly slower switching over of the Wooting 60HE in comparison to the mouse (talking about a second or two) and you can’t utilize the ability of this specific KVM model to have your USB3 header stick to one machine while the KM/Audio/Network swap around.
Even with those drawbacks I have not seen a KVM that works this well to sync “gaming” peripherals between computers without sacrificing device performance - really struggled to find any that were fit-for-purpose.
1 Like
Does this mean the wooting 60he is not hid compliant and will not work in the hid ports?
I had someone tell me that it works fine when you disable nkey rollover, so try it
I have tried it with both NKRO enabled and disabled on USB HID ports with no luck. I am using the Wooting Two HE on version “v2.9.1-beta.0” with the PAAG-ET3124B KVM (4 port 8K Dual Displayport 1.4 KVM with USB 3.2 gen 2).
can you flash it to qmk and disable nkey? after you disable nkey try rebooting the kvm
I just tried disabling NKRO with the Wooting One and it doesn’t even light up in the HID port. Works fine in USB 3 though. I’m assuming this is a problem with the Wooting firmware since a couple other keyboard I tried all worked fine. Flashing the Wooting to QMK would ruin its main selling point of analog switches. Forgive my ignorance but is there any technical terms that I could forward to Wooting that would help them understand what their firmware needs in order to work in the HID ports?
id probably have to look at it. ideally nkey rollover being disabled makes it show up as a hid device
qmk handles composite functions really cleanly too so that’s why it works with qmk. if you verify it works on qmk but not their firmware its gotta be some wacky thing in their firmware about how they’re triggering the events.
there’s even a patch on here to make qmk smart enough to manage nkey rollover even with a a kvm. so you can have nkey you just have to send both the kvm leading keys and hotkeys from the same virtual hid endpoint in key scenarios.
No, I can’t find anyway to flash qmk firmware to the keyboard. It seems qmk has no support for any Wooting keyboard.
I sniffed the USB traffic between the Wooting keyboard and the KVM. The Wooting Keyboard claims the HID class, but not the Keyboard protocol in the initial configuration response descriptor. The initial descriptors are identical with NRKO enabled or disabled. I can also provide the pcap files if there’s interest.
Wooting
CONFIGURATION DESCRIPTOR
bLength: 9
bDescriptorType: 0x02 (CONFIGURATION)
wTotalLength: 166
bNumInterfaces: 6
bConfigurationValue: 1
iConfiguration: 0
Configuration bmAttributes: 0xa0 NOT SELF-POWERED REMOTE-WAKEUP
bMaxPower: 200 (400mA)
INTERFACE DESCRIPTOR (0.0): class HID
bLength: 9
bDescriptorType: 0x04 (INTERFACE)
bInterfaceNumber: 0
bAlternateSetting: 0
bNumEndpoints: 1
bInterfaceClass: HID (0x03)
bInterfaceSubClass: No Subclass (0x00)
bInterfaceProtocol: 0x00
iInterface: 0
Ducky One 2 (Working keyboard)
CONFIGURATION DESCRIPTOR
bLength: 9
bDescriptorType: 0x02 (CONFIGURATION)
wTotalLength: 91
bNumInterfaces: 3
bConfigurationValue: 1
iConfiguration: 0
Configuration bmAttributes: 0xa0 NOT SELF-POWERED REMOTE-WAKEUP
bMaxPower: 50 (100mA)
INTERFACE DESCRIPTOR (0.0): class HID
bLength: 9
bDescriptorType: 0x04 (INTERFACE)
bInterfaceNumber: 0
bAlternateSetting: 0
bNumEndpoints: 1
bInterfaceClass: HID (0x03)
bInterfaceSubClass: Boot Interface (0x01)
bInterfaceProtocol: Keyboard (0x01)
iInterface: 0
1 Like
Hey Team,
I’ve been running into the same issue and tried nearly everything. NKRO, Additional Voltage USB power supplies and cables, different computers (windows & mac), bootleg software and drivers etc.
I currently have an the
- 4port KM - h-ttps://www.store.level1techs.com/products/p/4-port-km-switch-with-usb-32-gen-1-mouse-roaming-function
- wooting 60he (only works via USB3)
- keychron q1 HE (works with HID but software doesn’t register via hid) h-ttps://www.keychron.com/products/keychron-q1-he-qmk-wireless-custom-keyboard
Here is the github issue that i’ve come across as relevant.
h-ttps://github.com/WootingKb/wootility-issues/issues/293#issuecomment-2368891405
Happy to help and or try things to help make peoples lives easier!
Myself and another user tried with the new Wootility v5 software & newest beta firmware [v2.10.0-alpha.9] and still nothing.
The keyboard’s lights don’t even turn on.
More updates are over on the github issue for Wooting.
I am stumped of what to try next.
Being that the Wooting KBs are typically regarded as best in class for gaming would be amazing if we could find a way to make them work with the Level1 Tech’s best in class KMs.
I am rather stumped on this issue. Hopefully we can figure this out
1 Like
Ditto
I’m by no means an expert on this but willing to help and learn!
Let me know what I could try or experiment with. Those in the gitHub issue seem to have a better technical comprehension of HID than I do, maybe some of that info could help?
Hey @Level1_Amber & @wendell ,
I ran my own comparison between my Keychron that works and my Wooting that doesn’t.
My script as well as a detail of my results are attached to this github issue:
h-ttps://github.com/WootingKb/wootility-issues/issues/293
ChatGPT found a few differences:
Functionality:
- Wooting 60HE (ARM): Appears to be a more feature-rich keyboard with multiple interfaces and endpoints, possibly supporting analog input, advanced lighting effects, and other proprietary features.
- Keychron Q1 HE: Focuses on providing standard keyboard functionality with some customization, indicated by the large HID descriptor on Interface 0.
Power Consumption:
- Wooting 60HE (ARM): Consumes more power (400 mA vs. 100 mA), likely due to additional features like per-key RGB lighting and analog key switches.
Interface Complexity:
- Wooting 60HE (ARM): Has a more complex interface structure with five interfaces.
- Keychron Q1 HE: Has two interfaces.
Endpoint Configuration:
- Wooting 60HE (ARM): Uses various endpoints with different packet sizes and intervals, indicating diverse data transmission needs.
- Keychron Q1 HE: Uses fewer endpoints with consistent configurations.
Device Classes and Protocols:
- Both devices implement the standard HID class for keyboards but differ in how they structure additional functionalities.
Raw Results for y’all:
Device: Keychron Q1 HE
- Vendor ID: 0x3434
- Product ID: 0x0b10
Configuration Descriptor:
- bLength: 9
- bDescriptorType: 2
- wTotalLength: 0x0042
- bNumInterfaces: 2
- bConfigurationValue: 1
- iConfiguration: 0
- bmAttributes: 0xa0 (Bus Powered, Remote Wakeup)
- MaxPower: 100mA
Interface 0:
Interface 1:
Device Status:
- Power: Bus Powered
- Remote Wakeup: Enabled
Device: Wooting 60HE (ARM)
- Vendor ID: 0x31e3
- Product ID: 0x1312
Configuration Descriptor:
- bLength: 9
- bDescriptorType: 2
- wTotalLength: 0x008d
- bNumInterfaces: 5
- bConfigurationValue: 1
- iConfiguration: 0
- bmAttributes: 0xa0 (Bus Powered, Remote Wakeup)
- MaxPower: 400mA
Interface 0:
Interface 1:
Interface 2:
Interface 3:
Interface 4:
Device Status:
- Power: Bus Powered
- Remote Wakeup: Enabled