Comment on page
Reprogramming Encoders
So you've decided that you'd like to reprogram/remap your encoders to do something different? Sounds good, but be forewarned, the process can be a bit complicated.
First of all, at the moment, you won't be able to reassign the encoders using QMK Configurator. The only methods right now is through a standard QMK build environment or by using an updated version of firmware that includes encoder remapping support for VIA: VIA Firmware Upgrades.
Physically adding an encoder to a PCB that doesn't have support for it is beyond the scope of this guide. On the firmware side, if your board doesn't already support for encoders, then you will need to add that in yourself. See the Encoders section of the QMK Docs.
All Keebio boards have encoders pre-configured in QMK, so you don't need to enable support for it.
A rotary encoder can be rotated clockwise and counter-clockwise. Some models of rotary encoders (including the ones sold at Keebio) can also be pressed down like a switch.
Here's some ideas on what you can use this functionality for:
- Volume control - Turn volume up or down, press to mute
- Media control - Play previous or next track
- Scrolling - Page up or down, home/end, left/right
- Window/Tab switching
- Macros
- Change RGB/Backlight modes
- Regular keystroke
First, you need to make sure that you have you own keymap directory setup if you don't already have one. For example, if you have an Iris keyboard, go to
keyboards/keebio/iris/keymaps and copy default to your own name/username. If you want to retain VIA functionality, then copy the via keymap directory.There are two methods of defining the mapping of your encoders:
- 1.
- 2.
Encoder map is the newer method of encoder mapping and is recommended if you are just sending keycodes like a keyswitch. It is also easier to set the mappings for different layers.
Using callbacks is the older method, and most of the code in the QMK repository uses this method since it's been around much longer.
First, you will need to enable the encoder map feature by adding the following line to your keymap's
rules.mk:ENCODER_MAP_ENABLE = yes
Next, open up the
keymap.c file that's in your keymap folder. Go down to the bottom of the file and add the following code:#if defined(ENCODER_MAP_ENABLE)
const uint16_t PROGMEM encoder_map[][NUM_ENCODERS][2] = {
[0] = { ENCODER_CCW_CW(KC_PGUP, KC_PGDN), ENCODER_CCW_CW(KC_VOLD, KC_VOLU) },
[1] = { ENCODER_CCW_CW(RGB_HUD, RGB_HUI), ENCODER_CCW_CW(RGB_SAD, RGB_SAI) },
[2] = { ENCODER_CCW_CW(RGB_VAD, RGB_VAI), ENCODER_CCW_CW(RGB_SPD, RGB_SPI) },
[3] = { ENCODER_CCW_CW(RGB_RMOD, RGB_MOD), ENCODER_CCW_CW(KC_LEFT, KC_RIGHT) },
};
#endif
The first parameter of
ENCODER_CCW_CW() is what the counter-clockwise rotation of the encoder will be, while the second parameter is the mapping for the clockwise rotation of the encoder.This snippet above assumes that there are 2 encoders. Here's a commented version of the same code that explains what it does, so you can change things accordingly:
#if defined(ENCODER_MAP_ENABLE)
const uint16_t PROGMEM encoder_map[][NUM_ENCODERS][2] = {
// Mappings for 1st Encoder // Mappings for 2nd Encoder
[0] = { ENCODER_CCW_CW(KC_PGUP, KC_PGDN), ENCODER_CCW_CW(KC_VOLD, KC_VOLU) }, // Mapping for Base layer
[1] = { ENCODER_CCW_CW(RGB_HUD, RGB_HUI), ENCODER_CCW_CW(RGB_SAD, RGB_SAI) }, // Mapping for Layer 1
[2] = { ENCODER_CCW_CW(RGB_VAD, RGB_VAI), ENCODER_CCW_CW(RGB_SPD, RGB_SPI) }, // Mapping for Layer 2
[3] = { ENCODER_CCW_CW(RGB_RMOD, RGB_MOD), ENCODER_CCW_CW(KC_LEFT, KC_RIGHT) }, // Mapping for Layer 3
// You can add more layers here if you need them, or you can also delete lines for layers you are not using
};
#endif
Open up the
keymap.c that's in your keymap folder. Go down to the bottom of the file and add the following code:bool encoder_update_user(uint8_t index, bool clockwise) {
if (index == 0) {
if (clockwise) {
tap_code(KC_VOLU);
} else {
tap_code(KC_VOLD);
}
}
else if (index == 1) {
if (clockwise) {
tap_code(KC_PGDN);
} else {
tap_code(KC_PGUP);
}
}
return false;
}
This snippet above assumes that there are 2 encoders. Here's a commented version of the same code that explains what it does, so you can change things accordingly:
// Commented version of the previous block of code
// This piece of code is run anytime the encoder is rotated
bool encoder_update_user(uint8_t index, bool clockwise) {
if (index == 0) { // Index 0 is the first encoder
if (clockwise) {
tap_code(KC_VOLU); // Volume Up is sent if the 1st encoder is rotated clockwise
} else {
tap_code(KC_VOLD); // Volume Down is sent if the 1st encoder is rotated counter-clockwise
}
}
else if (index == 1) { // Index 1 is the second encoder
if (clockwise) {
tap_code(KC_PGDN); // Page Down is sent if the 2nd encoder is rotated clockwise
} else {
tap_code(KC_PGUP); // Page Up is sent if the 2nd encoder is rotated counter-clockwise
}
}
// If you have more encoders, add more `else if (index == ...)` blocks here
return false;
}
The QMK documentation has info about what keycodes can be used. Basic keycodes are prefixed with
KC_, while other types of keycodes have different prefixes, such as BL_ for backlighting controls, RGB_ for RGB lighting controls, and KC_MS_ for mouse keys.Find the keycodes that you would like to use, and replace the example ones used in the code blocks above.
If you are using modifier keys in combination with a keycode, such as
C(A(KC_DEL)) (Ctrl-Alt-Delete), then you will need to replace tap_code with tap_code16, like this: tap_code16(C(A(KC_DEL))).Once you have made your changes to
keymap.c, go ahead and compile your keymap. The following example is for Iris Rev. 6 with keymap directory of misterjuice:make keebio/iris/rev6:misterjuice
You can then flash using this command, or take the .hex/.bin file generated with the previous command and flash using QMK Toolbox:
make keebio/iris/rev6:misterjuice:flash
This section has some info on more advanced usage of programming the encoder functions.
If you'd like to have different keycodes sent depending on what layer you are on, add
layer_state_is(...) to determine if you are on a particular layer and change functionality based on that.Example:
bool encoder_update_user(uint8_t index, bool clockwise) {
if (index == 0) {
// Base layer (you can also use the enums in `enum layer_names` instead of 0, 1, 2, etc.)
if (layer_state_is(0)) {
if (clockwise) {
tap_code(KC_VOLU);
} else {
tap_code(KC_VOLD);
}
} else if (layer_state_is(1)) {
if (clockwise) {
tap_code(KC_MPRV);
} else {
tap_code(KC_MNXT);
}
}
}
else if (index == 1) {
if (layer_state_is(0)) {
if (clockwise) {
tap_code(KC_PGDN);
} else {
tap_code(KC_PGUP);
}
} else if (layer_state_is(1)) {
if (clockwise) {
tap_code(KC_HOME);
} else {
tap_code(KC_END);
}
}
}
return false;
}
Mouse keys is a QMK feature that allows you to emulate a mouse using your keyboard. You can move the pointer at different speeds, press 5 buttons and scroll in 8 directions.
If you want to use mouse keys, you will need to make sure that it is enabled by adding the following line to your keymap's
rules.mk if it not already enabled in the keyboard's rules.mk:MOUSEKEY_ENABLE = yes
Last modified 11mo ago