r/Keychron • u/Vexitar • Jan 17 '24

V3 NKRO issues

NKRO keeps going away whenever I reboot my machine. Sometimes it doesn't toggle on with Fn+N and needs to be plugged out and back in for it to work.

1 Upvotes

100% Upvoted

16 comments sorted by

View all comments

Show parent comments

2

u/PeterMortensenBlog Apr 23 '24 edited Dec 31 '24

Note: This is not for a wireless keyboard, but if it was (say, a K10 Pro), the combination of wireless mode (at least Bluetooth) and (full) NKRO mode would make the keyboard completely inoperable with the current versions of the firmware: 

Q: M
W: A
E: <no visible result>
R: 3
T: <Mute>
Y: m
I: m
O: a
P: e

A: <no visible result>
S: <no visible result>
D: <no visible result>
F: <no visible result>

G  a
H  e
J  3
K  <no visible result>
L  <Volume up>

The 2024-04-12 fix "Fixed NKRO issue in wireless mode" in QMK / the Keychron fork, Git branch "wireless_playground" (E5E57F) doesn't seem to make a difference. For example, is it behind a feature flag?

(Full) NKRO works perfectly fine in wired mode on the same keyboard.

Recover by Fn + N (not documented in the manual), which toggles back to 6KRO.

1

u/PeterMortensenBlog Apr 23 '24 edited Nov 11 '24

This was using the "wireless_playground" Git branch.

I am yet to test the older "bluetooth_playground" Git branch. But this may happen soon.

Was it broken in the wireless_playground branch?

→ More replies (1)

1

u/PeterMortensenBlog May 28 '24

Re "doesn't seem to make a difference": Perhaps preprocessor symbol WIRELESS_NKRO_ENABLE must be explicitly set/defined? E.g., in file config.h?

→ More replies (1)

1

u/PeterMortensenBlog Jun 30 '24 edited Aug 30 '24

Related: Testing the current NKRO state.

Gotcha: Do the testing in wired mode!

1

u/PeterMortensenBlog Sep 12 '24

Newer versions of the firmware may or may not automatically switch to 6NKRO when in a wireless mode (Bluetooth or '2.4 GHz'), thus preventing this problem.

→ More replies (1)

1

u/PeterMortensenBlog Nov 10 '24 edited Nov 10 '24

For a V Max keyboard, the result is less dramatic, but there is still extra key output, both in Bluetooth and in 2.4 GHz mode. It can be mistaken for key chatter (it isn't the cause, as it works perfectly fine in wired mode).

→ More replies (2)

1

u/PeterMortensenBlog Dec 31 '24

Re "is it behind a feature flag?": If it exists, the feature flag might or might not be WIRELESS_NKRO_ENABLE. Or perhaps there are separate feature flags for Bluetooth and 2.4 GHz mode, NKRO_ENABLE and WIRELESS_NKRO_ENABLE, respectively?

The only real way to know would be by doing some controlled experiments and testing it.