#Wooting 60HE Keeps Doing Large Spaces

1 messages · Page 1 of 1 (latest)

bleak temple
#

I will send a video in 1 second

shy vortexBOT
#

Thanks for posting your support request!

Please note, the support center is only for community-based support with technical troubleshooting and general questions.

For official Wooting Customer Support, please use the Contact Us button on the Wooting Hub or email your request to social@wooting.io
note: use the email address associated with your order for fastest resolution

Looking for information about your specific order?
You can find that on the Wooting Hub! There you can also add upgrades, change/confirm 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!
https://hub.wooting.io/login

bleak temple
#

It did big spaces.

#

But now its doing it, its off and on

crisp roost
#

Stock cable? Plugged directly into pc?

bleak temple
#

And now when I click a key, sometimes it spams it

#

I've unplugged and re plugged it in

#

Please help @crisp roost.

As displayed in the video, it spams any key. Even backspace.

#

FYI: It just started doing this when I did the new update on the Wooting App

#

And its still doing this

#

Is it because I have this all on?

outer palm
#

same issue on the latest firmware, just updated

#

it's not tied to rapid trigger

#

tried reflashing as well, didn't help

analog hazel
#

The error on the Wootility indicate that you may use a RGB app to control the LEDs of the Wooting. If so that would be a bad idea. First you are using Tachyon and that disables the RGB for a reason. If you circumvent this by using a third party app which take over the RGB it will causes delays and so make Tachyon meaningless. The MCU of the device can't handle other things if it constantly needs to send new values to the LED controller. While static colors are fine a third party RGB app typically sends these again so the MCU likely sends them too even if nothing has changed.

#

The use of a RGB app likely also causes a higher power demand which may causes the phantom inputs.

#

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.
https://www.youtube.com/watch?v=U8ojU_8ASVE

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 while the actuation point is set to 0,1 mm 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.

Another cause can be a bad or unideal mod. For example when a tape mode is done or too much foam was added to the case or switch tripods are used. If something is pressing against the legs of the switches or there is a soft layer between the switch and the PCB the flex can cause that the magnet slightly bounces and so causing multiple inputs.

If you are experiencing your keyboard pressing random keys and opening programs, then you came to the right video. The issue is usually caused by an instable amount of voltage entering the board. Follow along to see what you can do about it.

➤ Follow our socials!
🧑‍🤝‍🧑 Discord https://wooting.io/discord
🐤 Twitter https://www.twitter.com/wooting...

▶ Play video
#

The reconnection issues are typically caused by third party RGB software. The Wootings can't handle if multiple apps try to communicate with it.
Even the Lian Li software L-Connect 3 don't support the Wootings it's known to cause issues.

outer palm
#

@analog hazel i know about the phantom inputs when using low quality 3rd party cables, i had no issues with mine before updating to the latest firmware (v2.6.19), i also tried the stock cable as well - didn't help, any idea what else i could try if i want to keep tachyon mode?

#

0% brightness on RGB, of course.

analog hazel
#

@outer palm Please create your own thread and don't hijack this one.

outer palm
#

why would i make a new thread? i have the same problem

analog hazel
bleak temple
#

Okay, will do. Thanks!

#

@analog hazel It's still occurring.

#

I've put down the brightness, etc nothing has changed

analog hazel
#

Are you using a thrid party app to control the RGB or not?

bleak temple
#

Do I use the website?

analog hazel
bleak temple
analog hazel
#

This isn't a third party app which takes over the RGB, this is the first party app because that is the official app from Wooting itself.

#

A third party app would be SignalRGB or Artemis.

#

As mentioned the Lian Li software L-Connect 3 is also know to cause issues even that only supports Lian Li products.

#

What's the current firmware version and when did you update? Like did the issues may start after the update?

bleak temple
#

Firmware v2.6.19
Wootility v4.5.5

analog hazel
#

Did you mean that the problem started after finishing the flashing?

bleak temple
#

The problem happened once It finished downloading the firmware

analog hazel
#

Again, what do you mean with downloading the firmware?

#

You can't really download the firmware. The app does that in the background and that has no effect.
When the Wootility performs an update it will put the device in the restore mode and then flash the firmware to the device. This is show with a progress bar. After finishing the device is restarted.

bleak temple
#

Hm

#

I updated it here

analog hazel
#

Yes but you mentioned a download and I don't get what you mean with that.

#

Updating the Wootility would not cuase changes to the device. If it's caused by a firmware issue only a firmware update would make an impact.

#

But regardless, to rule out a potential firmware issue please try out a dev firmware.

In the case you want to test the dev firmware please follow this link: https://beta--wootility.netlify.app/?test-builds=true
Then go to settings, then updates and click on "Get test firmware". Select "2.6.20-test.phantom-press.0 - Revised spacebar key repeat fix which should overall be more stable" to install it.

bleak temple
#

Okay thank you

analog hazel
bleak temple
#

Yes

#

Nvm it is working now. Sorry

analog hazel
#

I don't know what went wrong but it should be only greyed out if the site isn't connected to the device.

bleak temple
#

Okay, I downloaded the firmware.

analog hazel
#

Did you installed / flashed it? Again, there is no download.

bleak temple
#

Yes

analog hazel
#

So it is better or fixed?

bleak temple
#

It's still doing it, not as bad as before.

analog hazel
#

Hmm, please try the "2.6.16-test.usb-boot.0 - Fix for poor behaviour in pre-OS env" firmware.

bleak temple
#

Okay.

#

Still doing it, but only spamming 3-6 letters

#

Before it went crazy, spammed over 20+ of the same key I barely clicked

bleak temple
analog hazel
#

If click on update you would get the latest stable version again.

#

You may don't have a firmware issue or it's a combination. So please use the 2.6.20 dev firmware again.