Model F F77 key registers on KeyUp

[gkaplan63]

I have a Model F Labs F77 that, for the most part, is working perfectly. However, a few keys often register on the release of the key instead of the press. Specifically, the "f" and the "j" keys are main offenders. The "f" key is certainly the most problematic - if I repeatedly press it, sometimes I will get two f's, one on the keydown, and one when I release it. If I press "f" and subsequently press "u" before "f" is fully released, the "u" will register first, resulting in uf instead of fu.

I've gone through the pandrew utility - I've removed keycaps and jiggled the spring as described in the troubleshooting portion of the video. After jiggling the spring for the F key, when it is at rest, the middle number is a solid green but is not close to the bottom number for that key. I did not remove the spring at this point, and I didn't open the case. I wanted to see if this is a typical issue and what the solution might be.

Thank you in advance for any help.

[Ellipse]

You may want to update to the latest firmware by following the manual. Not all keyboards are flashed with the latest factory firmware (only the classic and compact F104/FSSK, F15, and Round 1 beam spring boards currently are; the rest may not be). Generally, unless you can load the keyboard in Vial or the vial.rocks web site, it is likely older firmware.

The troubleshooting steps for the exact issue you describe are in the manual (transposed keys, delayed keypress signal, etc.). Tightening the 2 ground controller screws, replacing the spring with another spring (it is not required to take apart the keyboard to replace the spring), and testing with another keycap are all mentioned there - see the manual for additional details.

[gkaplan63]

I am able to use vial.rocks so I believe I updated the firmware sometime in the not too distant past. I attempted this repair when my new ultra compact case arrived - the controller screws were already plenty tight. I did replace the spring and fortunately that seems to have resolved the problem. Readjusting the spring for the "j" key seems to have resolved it doing the same issue. Thanks for the help.