#firmware bug

1 messages · Page 1 of 1 (latest)

random brook
#

2.13.0

lucid garnetBOT
# random brook 2.13.0

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!

cosmic mantle
#

What?

lucid kelp
dry compass
#

oops sorry forgot to check on discord

lucid kelp
dry compass
#

yea i saw that post not sure if related (mentions issues before they updated the firmware)

dry compass
# random brook 2.13.0

So to start, I think we should get a baseline.

Could I check what firmware you currently have and perform the following tests?

Tools
To better understand what is occurring at a sensor level, can you use our analog monitor tool and take pictures of the results?
https://analog-monitor.wootility.io/

Note:
I recommend disabling the keyboard brightness to 0% to rule out power as a cause.

Test 1
With the analog monitor open:

  • Disable Tachyon mode
  • Slowly press the switch and release
  • Take a picture of the result

Test 2

  • Enable Tachyon mode
  • Slowly press the switch and release
  • Take a picture of the result

Firmware 2.13.0
Update back to the stable firmware

Test 3

  • Disable Tachyon mode
  • Slowly press the switch and release
  • Take a picture of the result

Test 4

  • Enable Tachyon mode
  • Slowly press the switch and release
  • Take a picture of the result
random brook
dry compass
#

Yea that perfect

random brook
#

alright thats test 1

dry compass
#

and that is with the rollback right?

random brook
#

yep

dry compass
#

the last 2 was with the latest 2.13.0 firmware?

random brook
#

yep

dry compass
#

hmm look pretty normal when you experince phantom presses could you try to take a picture ?

random brook
#

alright

dry compass
#

Thanks

random brook
#

it only happens when im typing fast or like randomly spamming tho

#

like hitting the 3rd row keys randomly somehow

#

triggers enter

#

lol

dry compass
#

hmm that makes it a bit more complicated

random brook
#

i didn't press the number keys here

#

oh also this onl

#

only happens with like 0.1 actuation

dry compass
#

that is wired let me see how these are scanned or if there is any patten

vernal stump
# random brook

Turn on browser hardware acceleration for more accurate results, it doesn't seem to be enabled

dry compass
#

ohh yea that too

random brook
#

i was only spamming a d and s here

#

ok i got it to trigger

image.png
dry compass
#

doesn't look like a mux but more a physical issue like hitting the switch causes the nearby keys to react/detect the vibration or maybe flex of the switch plate (causeing the slike spike)

bu no spikes when held down

random brook
#

oh it was fine before updating tho

dry compass
#

hmmm maybe the update detects the slight vibrations better or dosnt filter it out as well

random brook
#

oo

dry compass
#

will give the software team a heads up

#

for a clean result could you try taping the key lightly then with a bit more force to confirm the theory

random brook
#

i think that might be it

dry compass
#

Thanks for the help

we added a new firmware "2.12.5-rollback" that was the previous firmware if you wish to use that instead

random brook
dry compass
# random brook np

Any chance you would be interested in trying a test to see if this is linked or related to the friction fit or switch plate

The test would involve removing the module from the case, placing it on the desk, then trying to replicate the spikes again

The reason behind the request was the image above shows switch's pretty far away (R-alt) and the theory is that the fraction fit is pushing up the switch plate while the pressing the switch push the pcb down

image.png
random brook
#

oh that sounds kinda troublesome ngl

#

i am using the tofu redux case tho

dry compass
#

no worry the case information helps

is this friction fitted or tray mounted?

random brook
#

friction fitted

random brook
#

@dry compass ok i just did it