Closed ilbalta closed 1 year ago
Turns out I had botched the soldering and short-circuited the pins for row 3 and row 4 of the arduino. Using qmk console and this snippet in my keymap.c helped me easily identify the issue.
#include "print.h"
bool process_record_user(uint16_t keycode, keyrecord_t *record) {
// If console is enabled, it will print the matrix position and status of each key pressed
#ifdef CONSOLE_ENABLE
uprintf("KL: kc: 0x%04X, col: %2u, row: %2u, pressed: %u, time: %5u, int: %u, count: %u\n", keycode, record->event.key.col, record->event.key.row, record->event.pressed, record->event.time, record->tap.interrupted, record->tap.count);
#endif
return true;
}
Sorry for the bother
Describe the Bug
I have a custom ortholinear split keyboard with Serial communications based off 40percentclub's 5x5. Left (master) half works fine, right half works fine on the first 3/5 rows; the last two rows produce double key presses on any of the 10 columns so if the mapped keycode is
KC_Q
I getq
on any key of the left half and any key of the right half's first 3 rows andqq
on any key of the last 2 rows of the right half. It would seem to me like a debouncing issue were it not for the systemic nature of the issue affecting only the last 2 rows.Keyboard Used
Custom ortholinear split based off 5x5 by 40percentclub
Link to product page (if applicable)
No response
Operating System
Windows
qmk doctor Output
Is AutoHotKey / Karabiner installed
Other keyboard-related software installed
Logitech g hub
Additional Context
rules.mk
config.h
5.5h
keymap.c
As a side note, this is my very first experience actually writing stuff for QMK, I had previously built a "classic" 5x5 and a 15x5 using 40percentclub's 5x5 boards and the "off the shelf" firmware flashing method. This build is me using the leftover pieces I had; sorry if there's something blatantly wrong, I tried sticking to the split keyboard guide as much as I could. ♥