#Phantom Key Presses for specific keys

1 messages · Page 1 of 1 (latest)

charred crow
#

I have a 60HE and unforunately, some of my number keys are now reading as actuated .16mm. This is causing phantom keys costcojudge.
I've been using the Wootility(V5) to update my profiles and firmware. I am hoping to hear if there are others who maybe have a similar issue and what caused it 😄

I've attached the analog monitor. I've worked around it in the software tweaking my actuation points. Is this a switch defect issue?

Thanks!

modest viperBOT
# charred crow I have a 60HE and unforunately, some of my number keys are now reading as actuat...

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!

plush imp
#

Have you tried replugging the keyboard?

charred crow
#

Thanks for the advice, yes I did.

Actually surprisingly, turning it back on today seemed to resolve the issue.

I think there may be noise from the power cable or my PCs USB port. Not sure if that is a design oversight. The keys are over/near the power port. Noise from the PC may not be mitigated well.

timber lion
# charred crow Thanks for the advice, yes I did. Actually surprisingly, turning it back on to...

With how stable the analog values are, and given that these sensors are all located on the corner of the keyboard grouped together, this may be related to external influences, typically from a magnet being close to the keyboard and throwing off the calibration during the initial power-up.

For example, if I place a magnet near the top of the keyboard and then power it on, this will calibrate the resting positions of each sensor with that external interfances. Then, when I move the magnet away, the magnetic strength decreases, causing the keyboard to register the raised value and will stay like that until next power up

(that or you learned on the keyboard during power up)

charred crow
#

I was unaware of the calibration at warmup, I have had my phone near it and a boom mic placed above my keyboard. Nothing with a strong magnet, maybe iphones magsafe charger

#

This makes sense though, I was worried the sensors were defective in those keys. Is there shielding in the case ? the KB I have is direct from Wooting

timber lion
#

Certain cases can mitigate external magnetic effects, but it's really hard to isolate this without going into expensive materials

Most of the time it is caused by the switch being slightly pressed or from deskmats that have magnets to attach to a metal desk or metal desks that have been magnetised by strong magnets (LTT cable management is a common one or the cable management puck)

as thius just happened the once may just a single case

charred crow
#

Fair enough, would it be possible to have a keybind to recalibrate after power up?

timber lion
#

That is a bit hard to do. You would need to press a certain key combination to trigger this, and most likely the act of pressing this when powering back up would cause the keyboard to calibrate the values of the keys being pressed.

Another method would be to change a setting to cause the keyboard to restart, like "gamepad," "NKRO," or "polling," as that restarts the keyboard to change the device ID.

I'm not sure of a method to send the command to soft restart without Wootility in dev mode.

charred crow
#

I see, very interesting! I will check it out