#Wooting Two HE

1 messages · Page 1 of 1 (latest)

cobalt geode
#

Good evening,

I've been having trouble with my wooting two he. Switching profiles via the keyboard itself has proven buggy, alt+tab, windows key, etc refuse to work until I unplug the keyboard. It also seems like a key gets "stuck" while I play osu! because it constantly lowers my volume, hitsounds, and music. It even persists when I unplug it and swap over to another one of my keyboards until I ultimately have to just restart my computer. Not sure if the one I got is just part of a bad batch or something, but trying to use the lekker software and make profiles using rapid trigger and 0.4mm just causes issues.

prime rampart
#

Make sure you're plugging the keyboard directly into the back of the computer using the included USB cable, since this sounds like the keyboard is struggling to get enough voltage.
If you must use a 3rd party cable or an unpowered hub, reduce your LED brightness to 70% to compensate and it should be fine

vale flume
#

During the first two seconds after the keyboard gets power it calibrates the keys. If you are pressing a key during that the key detection will be off later on for sure.
It's recommended to only start typing after the LEDs went on. This only happens after a power loss, so there is no calibration for a normal restart.
In the case you pressed a key accidentally during the calibration phase a simple replug will fix it.

#

Phantom / multiple inputs often occur due to to low or unstable voltage from USB. This often happens when third party cables are used which aren't up to the standard (like a lot of coiled cables). It can also happen when another device is used in-between and so the overall power consumption would be too high on the USB port. So it's recommended to use the provided stock cable and either directly connect the Wooting to an I/O port on the back of the system or to an active USB hub (externally powered). In general USB 3.X ports should work better than USB 2.0 ports because 3.X ports typically can handle more power than 2.0 ports. A port on the case can also sometimes causes issues because the cable from the case to the mainboard header adds length and so resistance. If so the device should typically still work fine on a low power demand with 0% brightness and Tachyon off.

#

Besides that EMI can also cause issues. Like any magnet or electric device especially direct above or under the device. For example some fancy desks have magnets in it to clamp on accessories. Or the device don't work reliable when it's placed on top of a laptop. To test for that you can use the trail RGB effect and move the keyboard around and pushing it on the side without pressing any key. If keys get activated and especially when their spot compared to the ground / desk moved accordningly.

cobalt geode
#

I have tried using both the included cable and my own cable just to see if it made a difference.

#

I have the wooting plugged in directly to the back of my computer, my other peripherals, camera, mouse, tablet, etc are plugged into a usb hub and that hub is powered by a it's own power cable as well.

#

There is no EMI that could interfere, I"m on an old wardrobe like wooden dresser.

prime rampart
#

Does the issue still present if your LEDs are turned off? If not, is there a certain LED brightness above which it does happen?

Have you tried a few different USB ports in case the specific one is problematic?

Is the cable loose or wiggly in the connection at the keyboard?

vale flume
#

To be honest I don't really get the problem. If it happens again please record a video of it.

#

If I know what is going on I can maybe help.

#

So far I assume you change to a profile with Tachyon on, very sensitive settings and maybe even a high brightness and that this causing phantom inputs.

It would also help if you would share the profile via the ID where the issues happen.

cobalt geode
#

The ID I use is literally either the default typing profile or the rapid trigger profile that come with the wooting lekker software

#

I have not tried using tachyon anymore and the problem still happens. I just got home not too long ago, plugged my keyboard in and the QWERTY keys didn't work until I plugged it back in. Made sure I didn't tap any keys before it connected. Also terrible placement for the usb-c.

vale flume
#

Not sure why the USB C port has a bad placement when you can use three different positions. You mentioned that you are using the W2 HE which uses a cable guiding.

Without providing the requested info there is likely nothing we can do.