Using a fresh clone of this repository, I uploaded both kb.py and main.py from boards/gtips/reviung41 on my keyboard, a reviung41 using a boardsource blok controller.
I found out that coord_mapping were not consistent with key mappings in main.py, and also not consistent with the way they were organised to match the actual keyboard shape.
I tried to change it by mapping rows for the left part first, then for the right part and finally for the bottom row, which worked perfectly (w/o changing main.py).
TLDR: Rows in default coord_mapping are mapped as if they were wired for a 3X12 keyboard, while they are actually wired on the keyboard like a split 3X6, starting left hand then right hand.
I am pretty new to custom keyboards, and even newer to KMK so please be kind, I tried to understand what could have gone wrong before opening this issue!
Decription
Using a fresh clone of this repository, I uploaded both kb.py and main.py from boards/gtips/reviung41 on my keyboard, a reviung41 using a boardsource blok controller.
I found out that coord_mapping were not consistent with key mappings in main.py, and also not consistent with the way they were organised to match the actual keyboard shape.
I tried to change it by mapping rows for the left part first, then for the right part and finally for the bottom row, which worked perfectly (w/o changing main.py).
TLDR: Rows in default coord_mapping are mapped as if they were wired for a 3X12 keyboard, while they are actually wired on the keyboard like a split 3X6, starting left hand then right hand.
See https://reviung.com/wp-content/uploads/2020/01/reviung41-pcb-2.jpg
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Default mapping should match what is defined in main.py (alphas for exemple should match a qwerty alphas layout)
Solution (that worked in my case)
In order to have main.py mappings match the actual keyboard layout, I changed coord_mapping to
Additional context
I am pretty new to custom keyboards, and even newer to KMK so please be kind, I tried to understand what could have gone wrong before opening this issue!