summaryrefslogtreecommitdiffstats
path: root/docs/feature_encoders.md
blob: dd12c91ce34e07a3cea177c08ccf40e389c17a35 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
# Encoders

Basic encoders are supported by adding this to your `rules.mk`:

    ENCODER_ENABLE = yes

and this to your `config.h`:

    #define NUMBER_OF_ENCODERS 1
    #define ENCODERS_PAD_A { B12 }
    #define ENCODERS_PAD_B { B13 }

Each PAD_A/B variable defines an array so multiple encoders can be defined, e.g.:

    #define ENCODERS_PAD_A { encoder1a, encoder2a }
    #define ENCODERS_PAD_B { encoder1b, encoder2b }

If your encoder's clockwise directions are incorrect, you can swap the A & B pad definitions.

Additionally, the resolution can be specified in the same file (the default & suggested is 4):

    #define ENCODER_RESOLUTION 4

## Callbacks

The callback functions can be inserted into your `<keyboard>.c`:

    void encoder_update_kb(uint8_t index, bool clockwise) {
        encoder_update_user(index, clockwise);
    }

or `keymap.c`:

    void encoder_update_user(uint8_t index, bool clockwise) {
      if (index == 0) { /* First encoder */
        if (clockwise) {
          tap_code(KC_PGDN);
        } else {
          tap_code(KC_PGUP);
        }
      } else if (index == 1) { /* Second encoder
        if (clockwise) {
          tap_code(KC_UP);
        } else {
          tap_code(KC_DOWN);
        }
      }
    }

## Hardware

The A an B lines of the encoders should be wired directly to the MCU, and the C/common lines should be wired to ground.