#Iiyama KVM issue with 60HE+ (added troubleshooting in replies)

1 messages · Page 1 of 1 (latest)

zinc shale
#

Good day,

I am hoping that someone can help me troubleshoot an issue I have when using the Wooting 60HE+ keyboard with the built-in KVM ports.

This issue happens when connected to an Iiyama GCB3486WQSCP-B monitor with KVM functionality

Whenever I switch sources or enable the PIP or PBP modes to my computer and work laptop the USB peripherals connected (mouse and keyboard) get a short power cycle. With other keyboards this poses no issue at all, but when it does this with the HE+ caps lock turns on and the CTRL, SHIFT, ALT and Windows keys get triggered and stay actuated. To solve it I need to manually tap them all to turn them "off" again.

To add to this, it seems all buttons on the HE+ get triggered, opening a plethora of tabs for all Microsoft Office (and other MS product) apps which is a direct result of pressing CTRL-SHIFT-ALT-WIN-W for for example MS Word 365.

When I do this with focus on a text editor I get the following input:
ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°ÓÄÞ¦°

The only way to prevent these tabs from opening I need to either keep a text editor in focus, or disconnect the keyboard from the monitor before switching.

Additionally, the above was done on the previous firmware version.

I just installed the FW update to 2.12.5 and the input is different now.
This time the trick to keep a text editor in focus does not work completely as it also triggers a "save all" command which prompts to a confirmation window and after that it opens linkedin, outlook and a few MS365 tabs.

The little output that I did get from the text editor is: [øóäþ¦°¨á¢éí

Does anyone know if I can do anything about this in or outside of the keyboard settings through Wootility, or would this need to be looked at by Wooting themselves?

elder lilyBOT
# zinc shale Good day, I am hoping that someone can help me troubleshoot an issue I have whe...

Thanks for posting your support request!

Note: #community_support is only for answering general questions and for troubleshooting.
All order-specific and shipment-specific support must be handled via the Wooting Support Wizard*
(You need to create an account on the Wooting Hub, using the same email address as your purchase. The account is not created for you automatically!)

Troubleshooting your Wooting Keyboard? Try these steps first!
Basic Troubleshooting

Questions about shipping, or what to do if your shipment has a problem?
Possible Problems During Shipping (with Solutions)

Looking for information about your specific order?
You can find that on the Wooting Hub! There you can also add upgrades, update your shipping address, and much more.

Is your order about to ship and you need to pause it for any reason?
Place it on hold via the Wooting Hub!

Do you need to...

All of these types of requests need to be made via the Wooting Support Wizard!

zinc shale
#

I already did go through basic troubleshooting as outlined in the Wooting Bot's reply.

For extra info, I am using the default Typing profile with customized Fn2 sublayer.

I am doing a bit more testing on the go. It seems switching the 60HE+ to Tachyon mode does change the behavior a little, but after the update it seems the behavior seems to be completely random.

First off, the moment the USB power is cycled by the KVM and the keyboard goes dark my system inputs the x button held down for a while until the lights come on again.

Second, notepad++ seems to be getting a CTRL-SHIFT-S command to save all tabs

CAPS LOCK is not active anymore until I disable Tachyon mode again.

CTRL and SHIFT on both sides of the keyboard are permanently active until BOTH sides are pressed.

It doesn't seem to be opening any more apps though.

zinc shale
#

I just reset the keyboard through Wootility, but to no avail. After restoring my profile I tested the symptoms some more:

After the reset and Tachyon mode enabled:

Test 1 enabling PIP:
Input while the keyboard goes "dark" (*before the HUB turns the power back on):
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Input stops once the keyboard is online again.

No locked keys afterwards

Test 2 disabling PIP:
CTRL got stuck

Test 3 enabling PIP:
Input while the keyboard goes "dark":
Cursor is moved and CTRL-DEL is pressed, cleaning out the notepad++ notes word for word.
Input stops once the keyboard is online again.

No locked keys afterwards

Test 4 enabling PIP:
CTRL got stuck

This was all with Tachyon mode Enabled.

With Tachyon mode disabled the symptoms are significantly worse:

Follow-up tests Enabling and Disabling PIP with Tachyon mode disabled:

Input while "dark" on 1 test:
x[á¢á¢á¢éí

  • CTRL-S is triggered
  • ALT-TAB is triggered multiple times causing a "alt-tab party-time" on screen.
  • 45 tabs are opened in the facored browser with MS365 apps (Indicating all modifiers are stuck (CTRL-ALT-SHIFT-WIN) and random keys are pressed to open the corresponding MS365 apps or browser pages to the online apps if Office 365 is not installed.

After the keyboard comes back online:

Stuck keys: CTRL, SHIFT, ALT, WIN, CAPS-LOCK

The results after this are all similar, random keypresses and combinations and indicators of stuck modifyer keys like:

  • SHIFT stuck (text selection with the mouse is always active)
  • CTRL, SHIFT and ALT Gr stuck (letters like Á§ÐÄÅÉÐ can be typed without holding the modifiers down)
  • Actuating shift to release that modifier enabled letters like áßðäåé to be typed, indicating the CTRL and ALT Gr (right side ALT) being stuck.
  • Actuating ALT Gr to release that modifier enabled menu hotkeys like S for saving a document etc, indicating CTRL is still stuck.

After a mishap of CTRL-Q I lost testing notes, the above results should cover those

zinc shale
#

Iiyama KVM issue with 60HE+ (added troubleshooting in replies)

zinc shale
#

Also sent this in through a support form online. Keeping this post for reference.

gritty dragon
#

Ultimately it might just be a bad KVM - Meaning it's not designed properly, or doesn't fully pass through USB like it's supposed to.