LED key is mapping to caps lock

1

I just acquired a Model 01. Using the Arduino IDE, I updated and flashed the latest firmware.

I cannot figure out why, but the Key_LEDEffectNext toggles caps lock.

Any advice? Thanks in advance.

The Model01-Firmware.ino file indeed shows:

#define PRIMARY_KEYMAP_QWERTY
// #define PRIMARY_KEYMAP_DVORAK
// #define PRIMARY_KEYMAP_COLEMAK
// #define PRIMARY_KEYMAP_CUSTOM

and

#if defined (PRIMARY_KEYMAP_QWERTY)
  [PRIMARY] = KEYMAP_STACKED
  (___,          Key_1, Key_2, Key_3, Key_4, Key_5, Key_LEDEffectNext,
   Key_Backtick, Key_Q, Key_W, Key_E, Key_R, Key_T, Key_Tab,
   Key_PageUp,   Key_A, Key_S, Key_D, Key_F, Key_G,
   Key_PageDown, Key_Z, Key_X, Key_C, Key_V, Key_B, Key_Escape,
   Key_LeftControl, Key_Backspace, Key_LeftGui, Key_LeftShift,
   ShiftToLayer(FUNCTION),

   M(MACRO_ANY),  Key_6, Key_7, Key_8,     Key_9,         Key_0,         LockLayer(NUMPAD),
   Key_Enter,     Key_Y, Key_U, Key_I,     Key_O,         Key_P,         Key_Equals,
                  Key_H, Key_J, Key_K,     Key_L,         Key_Semicolon, Key_Quote,
   Key_RightAlt,  Key_N, Key_M, Key_Comma, Key_Period,    Key_Slash,     Key_Minus,
   Key_RightShift, Key_LeftAlt, Key_Spacebar, Key_RightControl,
   ShiftToLayer(FUNCTION)),
2

If this is a used Model01 the previous owner may have used Chrysalis to configure the keymap and assigned caps lock to the LED key. A Chrysalis defined keymap takes precedence over that defined in firmware.

So, checking with Chrysalis would be the first thing, then you can use Chrysalis to clear the EEPROM keymaps, if you want to use the keymaps defined in your firmware sketch. Alternatively, if you have a custom firmware sketch, you can also just get rid of the EEPROM-Keymap plugin by commenting the respective lines in the init plugins block.

2 Likes