Wotitlity disconnect 80 he after changing rgbs

[wraith umbra]

After 5.1 wootility update I was trying to change my rgb color on my 80 he so I opened a chrome tab to select color from it and rpidetly move my cursor on my keyboard keys to change the keys colors but after that my keyboard gets disconnected from the wootility and I must to restart my pc to get it back it happens multiple times on my 4th profile

[unborn belfry]

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...

• Cancel an order?
• Return/Refund an order?
• Get assistance with placing an order?
• Change the items in your order?
• Change your shipping address to a different country?
• Return a recent purchase?
• Get warranty support?

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

[hybrid gorge]

can you open the console (f12) and show me what it displays?

[wraith umbra]

It also spams this errors

[hybrid gorge]

this is very useful, thanks

[hybrid gorge]

this is extremely weird

are you on the latest firmware version?

[wraith umbra]

Yes

It happens after that

[hybrid gorge]

what are your computer specs? (mostly interested in your motherboard because that's where the USB controller is)

[wraith umbra]

H410 mk r2

[hybrid gorge]

did you ever install any weird USB drivers or tweaks?

[wraith umbra]

No

Nothing new

[hybrid gorge]

is your Windows regular windows or do you have any of those windows tweaks for gaming?

[wraith umbra]

Normall win 11

Pro

[hybrid gorge]

have you tried restoring the keyboard? Backup your profiles first!!

[wraith umbra]

No i havent do u mean fully reset my keyboard or just reset it from wootility?

[hybrid gorge]

i mean put it in restore mode and reset it.

1. backup your profiles, you can share and save the profile codes somewhere
2. unplug the keyboard
3. Hold the right arrow and the Pause key (top right and bottom right keys), and while holding them plug the keyboard in
4. Those two keys should turn blue, and the keyboard is now in restore mode
5. in Wootility, go to the Help tab and follow the instructions

Thanks a lot for helping with this btw, it's really useful 😅

[wraith umbra]

Ok I will do it later🙏 also tnx for giving ur attention

[hybrid gorge]

also please turn this on and show me the logs again if you can (click where it says Verbose)

you can save the log like this:

[wraith umbra]

one after refresh one without

and also to mention chromes shows my device is paired

but wootility says its disconnected

and another thing sometimes it gets time for it to happend sometimes it happens right away

and only way i found to reconect it was to restart my pc

[wraith umbra]

let me know if u need more information

[hybrid gorge]

thank you, I'll look at these on Monday 😄

[supple hare]

@wraith umbra Hi, can you reproduce the issue? If so how often does it happen? How long does it take until it happens?

I guess a replug fixes it every time, or not?

If you can reliably reproduce the issue what happens when you downgrade back to the stable firmware via a restoring on the stable Wootility?

[wraith umbra]

Hi

Sometimes it happens very fast after 10 sec of changing color

Sometimes it takes time for it to happens

Like to 6 min

And unplug could fix it

The only 2 way to get it back on wootility is restart the pc or repluging the keyboard

[supple hare]

Do you mean changing colors by doing that manually via the Wootility?

[wraith umbra]

Yeah

It makes the keyboard disconnect from wootility

I have already shared a video about it

Idk if u can see it or not cause seem like icant reply to it

Let me know so ican repost it if u cant

[supple hare]

Please check if you can reproduce the issue after downgrading back to the stable version.

Beside that it would be nice if you can open the case and provide a close up picture of the back ob the PCB (the side you see when you turn the module up side down) and of both sides of the daughterboard which has the USB port. Also check if internal cable is properly attached.

Does the issue also happens when the polling rate is set to 1 kHz?

[wraith umbra]

How can I downgrade it can u share me the link

[supple hare]

Perform a restoring on the older Wootility.

Remember to save the share ID so you don't lose your profiles.

[wraith umbra]

Yeah I test it with tachyon mode off

[supple hare]

This isn't the same. Tachyon influences the scanning speed and disabled the RGB effects while the polling switch influences the used USB speed (Full-Speed vs. High-Speed).

You can change the polling rate in the keyboard settings section of the settings menu of the Wootility.

[wraith umbra]

Ok let me check it then

I test it for a while

And it seems like ok on 1k

Yeah then I switched back to 8k

And it happens exactly after 6 min

I would rather not to downgrade or restart my wooting since it isn't much important issue to me I just wanted to report it and also to mention I never had that experience ever on previous one 5.06

[supple hare]

It indicates a transfer issue. So as mentioned it would be helpful to provide pictures of the PCB and daughterboard and to check if the cable sits properly.

[wraith umbra]

So could it be a damge on pcb since i have already checked the cable

[supple hare]

Maybe, that's why pictures would be great.

For example corrosion or a scratch can lead to such issues.

[wraith umbra]

Ok I will check it tomorrow but I have never touched or opened it before since it was stock so it would be likley for it to have any scratches on it

Also I may try to use it on another system to check if anything wrong with my motherboard USB port

[wraith umbra]

I re test it on a laptop

For 10 minute and the issue didn't happend

Seems like something wrong with my motherboard

Are this blue usb ports different than balck ones?

[wraith umbra]

Maybe the issue was that

@supple hare

[supple hare]

USB 2.0 is independent from USB 3.X and 4.X and the later still support USB 2.0. Different USB controller might handle the connection a bit differently, meaning some are maybe more error tolerant that other if the signal isn't as great as it should be. Also it can be that the contacts port don't provide a good contact, like that dirt got in there or that they corroded.

So if it's fine on one port but not another it can be some minor differences but in general it should work.
USB Full-Speed is slower than High-Speed, so the later is more sensitive to issues, like if the connections isn't right.
For the keyboard the speed doesn't really matter as there isn't much data transferred but Full-Speed only supports a polling rate of 1 kHz while High-Speed supports up to 8 kHz.

[wraith umbra]

I didn't get any issue after switching to usb 2.0

But should I use usb 3 to get 8khz?

[wraith umbra]

And there might be still problem either with pcb or usb port?

[supple hare]

USB 3.X and 4.X ports contain USB 2.0 which is independent. So it should not matter where you connect it and it should work normally.

USB 1.0 only supports Low-Speed, Full-Speed got introduced in 1.1 and High-Speed got introduced in 2.0. But the version only specifies the protocol (so how the communication locks) not the speed (how the data signaling works). Meaning you can have a USB 2.0 Full-Speed device. USB 3.0 introduced SuperSpeed and SuperSpeed Plus, these later got renamed to Gen 1 and Gen 2. USB 4.X uses Gen 2 and Gen 3.

People get confused by the USB version as they think this refers to the feature set or speed while it actually only handles the protocol of the underlying device interaction. So the requests how a host talks to a device.

USB 3.X and 4.X has dedicated pins just for USB 2.0. So you can connect an older USB 2.0 to a USB 3.X and 4.X port and the device still works just fine. Meaning the later version only add things without really touching or changing the old stuff, so that the later is still compatible.

So it should not matter where you connect an old USB 2.0 device too. USB High-Speed is already kind of overkill for an input peripheral and only recently modern devices use the faster speed.

[wraith umbra]

As conclusion I understand does it mean that if I dont get any issue on my usb 2 my keyboard is fine and I can use 8khz but the USB 3 also shouldnt cause any problem?

And if it does it means that something is wrong with that port like dust or else?

[wraith umbra]

Also tnx for explanation

[supple hare]

If it doesn't work on one port while it's fine on all other it would indicate that there might be an issue with that port. If it doesn't work on a few specific ports it might indicate that the ports handled by a certain USB controller have an issue. But regardless it's hard to tell who is to blame for.

It can be a combination of things, for example maybe the signaling isn't as great for the Wooting and the port. So that's fine on another port or when a different device is used.

If you have the trouble on other systems too it would indicate an issue with the Wooting. So if you are able to test out different systems it's might worth to do it. The more test results of different device and port combinations you can provide the better the indication is who might causes the problem. But it's not really practical to do that for more than a few combinations.