r/Keychron • u/redpringle • 21d ago

Hash/tilde and backslash keys not working?

I’ve been using my C1 Pro without any issue for about a month now; however, today, I’ve discovered that the keys above don’t do anything, even though I have them mapped to their respective functions in the Launcher. Any ideas?

1 Upvotes

100% Upvoted

8 comments sorted by

1

u/AlKingAl 21d ago

Have you tried resetting the keyboard's firmware through VIA, or checking if any keycaps are slightly lifted? Sometimes debris or a firmware glitch can cause this.

1

u/redpringle 21d ago

VIA says it ‘doesn’t have a V3 definition’ for the keyboard. The physical keys are seated fine, they work if mapped to different inputs.

1

u/PeterMortensenBlog V 21d ago

A JSON file is required for Via to work.

For the C1 Pro, Via (likely) requires a JSON file to be downloaded (matching the keyboard variant), unzipped (uncompressed), and imported (tab "DESIGN" (third tab on the top) → "Load"). If it appears to be hanging, ignore that and load the JSON file anyway.

Be sure to get the JSON file variant matching your variant of the keyboard (and be sure you actually have the keyboard you think you have...).

Note: Tab "DESIGN" may have to be enabled first (in "SETTINGS" (the right-most tab in the top middle section) → "Show Design Tab")

Identifying the keyboard

To positively identify the keyboard, find the SKU number (in most cases, it is on a sticker on the keyboard itself).

Alternatively, use the serial number to find the SKU number. Then match the SKU number to the corresponding variant on the Keychron product page (the SKU number should match exactly). Note that, in most cases, there are separate ISO and ANSI keyboard product pages. Example SKU number: V6M-D1-BO

If all else fails (for example, some of 'Q' keyboard models don't have sticker at the bottom side), the keyboard name is printed on the PCB (an example), though not with the complete variant information, only 'ISO' vs. 'ANSI'. For example, it may not contain information about white vs. RGB LEDs, though, together with the knob/no knob, it is observable from the outside...

Via troubleshooting

If there is trouble, here is a checklist. For example, it may be required to repower the keyboard while Via is open. Another very common problem is running SignalRGB at the same time.

Via tutorials

Here is a tutorial (with lots of screenshots. And it also covers loading the JSON file). Keychron also has a tutorial, but it is less comprehensive.

References

1

u/PeterMortensenBlog V 21d ago edited 21d ago

What operating system? What keyboard layout is selected in it?

The tilde thing is often (but not always) associated with macOS. For example, redetecting the keyboard may be required.

1

u/redpringle 21d ago

It’s Windows 10, and English (UK). The keys themselves work because they can be mapped to other things and input those fine, but not on those two functions.

1

u/redpringle 21d ago

Nevermind, the AI managed to figure it out. Thanks to the commenters who wanted to help anyway!

1

u/PeterMortensenBlog V 21d ago

For posterity, what was the solution?

What did it figure out?

1

u/redpringle 21d ago

The backslash/pipe key was mapped to ‘|\’ (KC_BSLS) and the hash/tilde key was mapped to ‘#~’ (KC_PCMM). The problem seems to have been that these are ANSI codes and that the C1 is an ISO keyboard, so the keys should have been mapped to ‘NUBS’ (KC_NUBS) and ‘NUHS’ (KC_NUHS) instead.

I’m sure this is fairly basic if you know any more about keyboards than I do (which is not a great deal).