Thank you for the feedback 
we are also testing these keyboards atm and we’ll update with any discoveries.
There is some progress… The KVMs support composite devices on the HID ports but the Wooting as a complex composite device has to many interfaces / endpoints than these can handle.
There is a dev build “v2.10.0-test.kvm” which can be tested on Wootility Web with dev flag which works when the gamepad feature is disabled. But while the device seems to operate fine the Wootility can’t be properly used. We still need to check that out.
PS: Can I please get the permission to share links. Thanks for granting…
3 Likes
Permission granted for posting links.
2 Likes
Thank you for checking this out!
1 Like
This worked for me!
Steps to reproduce:
https://v5.wootility.io/?test_builds=true
Ensured NKRO & gamepad were disabled.
Navigate to updates, selected test-kvm
Move from HID interface to USB interface, run update to “kvm build” … update firmware … move back to HID
Then it worked!!! Tested with ctrl + ctrl 1,2,3 etc…
I know this is preRelease but thank you everyone who did this!
@wendell @Level1_Amber @WootingKB.Markus
1 Like
This worked!
Let me know if I can test any other builds out for y’all!
1 Like
Awesome that’s great!
Short update…
With the mentioned dev build for the Wootings these should work fine as a keyboard on the Level1Tech products. Sadly there is an issue with how the OUT transfers are handled. Because of this the Wootility can’t be used properly. While it may works at the beginning as soon as changes where made in the Wootility or after a while the Wootility stops working completely.
I reported my findings to Wendell, if there is another Level1Tech dev interested in the information please contact me.
@WootingKB.Markus - I am using this build now and as you said it works fine as a keyboard.
Does your comment just mean that to update the keyboard or change settings, we should move it to the USB3 port first, then move back to the HID port once the changes are complete?
While I haven’t tested the update process the mentioned problem will likely also occur on the restore mode. Like to flash a new firmware the data for that need to be transferred to the device. This is done via multiple OUT transfers and these don’t work.
Because of the issues with the OUT transfers I do not recommend to try to update a Wooting on a HID port.
1 Like
The dev build “2.10.0-test.kvm” changes the interface handling of the Wootings so that they should work as a keyboard on the Level1Tech products when the gamepad feature is disabled. If the gamepad is not disabled an additional interface and endpoint is used and the Wooting exceed the capabilities of the KVMs. On this build the Wootility can only be used in a limited way. As soon as settings are changed it lead into problems. It seems to me that the KVMs don’t support data transfer over OUT endpoints. Would be nice if a Level1Tech representative can tell more on this.
The new dev build “2.10.0-test.kvm.2” removes the dedicated OUT endpoints of the Wootings. This avoids the issue with the OUT endpoints and the data is instead transferred over the control endpoint the same way as the lock indication data is handled. This allows that changes can be saved. But the communication only works at the beginning. After a while the communication breaks until the Wooting is replugged.
The bootloader mode of the Wootings can’t be changed. So the restore mode of the Wootings can’t be updated by firmware updates. This means that it’s not possible to improve the compatibility of the Wootings in the restore mode.
1 Like
@Jordan_Kail You mentioned that the Keychron Q1 HE works for you on the HID port. Does that mean that you are able to use the configuration tool to configure the device? If so what Level1Tech product do you have and does the Wootility work for you on the two mentioned dev builds with the Wooting?
1 Like
I think Wendell is the only one who works on the kvm but I could be wrong
2 Likes
The old AVR Wooting models seem to work fine on “2.10.0-test.kvm.2” while the newer ARM models trigger the issue. The difference is that on AVR all USB requests are done within an ISR. Because of this the device can immediately respond and so transfers don’t need to be delayed to the next poll. This is not the case on the ARM models which results that OUT packets are might not accepted right away. So it seems that NAKs causes the problem for the K(V)Ms.
1 Like
No it doesn’t, I have to do the same process to update my keychron’s profiles and configurations.
I’m still able to swap between onboard profiles on each, I’d say the firmware is at or above feature parity with the keychron.
Which all makes sense being that it’s a branch of open source software.
I don’t get what you mean but I guess what you mean is that you also can’t configure the Keychron.
At first I assumed it would work because it was mentioned that QMK works. On a quick search I didn’t found anything related if the configuration, like with VIA, works. Now I believe that it doesn’t work because of a limitation of the KVMs. It seems that they don’t support dedicated OUT endpoints on devices connected to the HID port.
I have the Level 1 KVM (Dual Video with DisplayPort) and looking at purchasing a Wooting Two HE.
Is the issue specific if you use the USB HID or other USB port on the KVM / like if use the Console USB port on the back of the KVM would this have the same issue?
Does this issue affect the newer 80HE keyboards?
@brink668 The HID ports are used to read the keyboard data and so to be able to toggle the output. The normal non HID ports are regular ports and work fine.
@Garbaeioux The W80HE as a new model has an ARM chip so the problem applies to that when used on a HID port.
1 Like
The two test version got updated to the latest beta.
So if you still want to test the KVM changes please update to v2.10.1-beta.4+kvm.1 or v2.10.1-beta.4+kvm.2 respectably.