-
-
Notifications
You must be signed in to change notification settings - Fork 40.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] GMMK Pro ISO support #13524
Comments
I've created a PR adding an ISO layout #13532 |
Thanks for putting the PR together! :) I wasn't sure if a new keyboard needed to be created since it's a new PCB or if a new layout sufficed. Mostly because I don't have any clue about how the RGB configuration works. We'll probably have to see about RGB once the Glorious PR gets merged or rejected. RGB is secondary anyways, at least to me. |
If someone with an ISO PCB and a multimeter can probe the ISO specific LEDs to figure out which rows/columns they belong to it shouldn't be that hard to get those LEDs lit up. I just need to know:
Presumably the ISO specific keys correspond to one of the |
I just measured it: LED 83 (that's the label on the PCB) belongs to the key to the right of Left Shift (<> in ISO-DE, \ in ISO-UK) and is mapped to K45, so SW1_1 and CS4_1 - CS6_1. I didn't test it yet but maybe it helps. |
Fix provided, this can probably be closed now. |
Key- and RGB matrix is in. Cheers guys. Thanks for stepping in where glorious should have. |
Now that the GMMK Pro ISO hit the market, I'd like it to be supported by QMK, too
Feature Request Type
Description
The GMMK Pro ISO PCB works very similarly to the ANSI one.
Going by the matrix currently available for the ANSI version, Backslash is ka2 and no longer needed, since it does not exist on the ISO board.
The new keys needed are k23 (KC_NUBS) and k84(KC_NUHS).
Copying the proposed AW20216S RGB implementation into my experimental ISO firmware results in good behavior, except for NUBS and NUHS not being lit. Have not tried the competing one.
I have some codework on my end, but I am very inexperienced with the project and github, so I'd love if someone more experienced could do what glorious should have done 2 weeks ago.
cheers.
The text was updated successfully, but these errors were encountered: