-
Notifications
You must be signed in to change notification settings - Fork 2
/
Rotary.cpp
142 lines (124 loc) · 4.83 KB
/
Rotary.cpp
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
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
/* Rotary encoder handler for arduino. v1.1
Copyright 2011 Ben Buxton. Licenced under the GNU GPL Version 3.
Contact: bb@cactii.net
A typical mechanical rotary encoder emits a two bit gray code
on 3 output pins. Every step in the output (often accompanied
by a physical 'click') generates a specific sequence of output
codes on the pins.
There are 3 pins used for the rotary encoding - one common and
two 'bit' pins.
The following is the typical sequence of code on the output when
moving from one step to the next:
Position Bit1 Bit2
----------------------
Step1 0 0
1/4 1 0
1/2 1 1
3/4 0 1
Step2 0 0
From this table, we can see that when moving from one 'click' to
the next, there are 4 changes in the output code.
- From an initial 0 - 0, Bit1 goes high, Bit0 stays low.
- Then both bits are high, halfway through the step.
- Then Bit1 goes low, but Bit2 stays high.
- Finally at the end of the step, both bits return to 0.
Detecting the direction is easy - the table simply goes in the other
direction (read up instead of down).
To decode this, we use a simple state machine. Every time the output
code changes, it follows state, until finally a full steps worth of
code is received (in the correct order). At the final 0-0, it returns
a value indicating a step in one direction or the other.
It's also possible to use 'half-step' mode. This just emits an event
at both the 0-0 and 1-1 positions. This might be useful for some
encoders where you want to detect all positions.
If an invalid state happens (for example we go from '0-1' straight
to '1-0'), the state machine resets to the start until 0-0 and the
next valid codes occur.
The biggest advantage of using a state machine over other algorithms
is that this has inherent debounce built in. Other algorithms emit spurious
output with switch bounce, but this one will simply flip between
sub-states until the bounce settles, then continue along the state
machine.
A side effect of debounce is that fast rotations can cause steps to
be skipped. By not requiring debounce, fast rotations can be accurately
measured.
Another advantage is the ability to properly handle bad state, such
as due to EMI, etc.
It is also a lot simpler than others - a static state table and less
than 10 lines of logic. */
#include "Arduino.h"
#include "Rotary.h"
/* The below state table has, for each state (row), the new state
to set based on the next encoder output. From left to right in,
the table, the encoder outputs are 00, 01, 10, 11, and the value
in that position is the new state to set. */
#define R_START 0x0
#ifdef HALF_STEP
// Use the half-step state table (emits a code at 00 and 11)
#define R_CCW_BEGIN 0x1
#define R_CW_BEGIN 0x2
#define R_START_M 0x3
#define R_CW_BEGIN_M 0x4
#define R_CCW_BEGIN_M 0x5
const unsigned char ttable[6][4] = {
// R_START (00)
{R_START_M, R_CW_BEGIN, R_CCW_BEGIN, R_START},
// R_CCW_BEGIN
{R_START_M | DIR_CCW, R_START, R_CCW_BEGIN, R_START},
// R_CW_BEGIN
{R_START_M | DIR_CW, R_CW_BEGIN, R_START, R_START},
// R_START_M (11)
{R_START_M, R_CCW_BEGIN_M, R_CW_BEGIN_M, R_START},
// R_CW_BEGIN_M
{R_START_M, R_START_M, R_CW_BEGIN_M, R_START | DIR_CW},
// R_CCW_BEGIN_M
{R_START_M, R_CCW_BEGIN_M, R_START_M, R_START | DIR_CCW},
};
#else
// Use the full-step state table (emits a code at 00 only)
#define R_CW_FINAL 0x1
#define R_CW_BEGIN 0x2
#define R_CW_NEXT 0x3
#define R_CCW_BEGIN 0x4
#define R_CCW_FINAL 0x5
#define R_CCW_NEXT 0x6
const unsigned char ttable[7][4] = {
// R_START
{R_START, R_CW_BEGIN, R_CCW_BEGIN, R_START},
// R_CW_FINAL
{R_CW_NEXT, R_START, R_CW_FINAL, R_START | DIR_CW},
// R_CW_BEGIN
{R_CW_NEXT, R_CW_BEGIN, R_START, R_START},
// R_CW_NEXT
{R_CW_NEXT, R_CW_BEGIN, R_CW_FINAL, R_START},
// R_CCW_BEGIN
{R_CCW_NEXT, R_START, R_CCW_BEGIN, R_START},
// R_CCW_FINAL
{R_CCW_NEXT, R_CCW_FINAL, R_START, R_START | DIR_CCW},
// R_CCW_NEXT
{R_CCW_NEXT, R_CCW_FINAL, R_CCW_BEGIN, R_START},
};
#endif
// Constructor. Each arg is the pin number for each encoder contact
Rotary::Rotary(char _pin1, char _pin2) {
// Assign variables
pin1 = _pin1;
pin2 = _pin2;
// Set pins to input.
pinMode(pin1, INPUT);
pinMode(pin2, INPUT);
#ifdef ENABLE_PULLUPS
digitalWrite(pin1, HIGH);
digitalWrite(pin2, HIGH);
#endif
// Initialise state
state = R_START;
}
unsigned char Rotary::process() {
// Grab state of input pins
unsigned char pinstate = (digitalRead(pin2) << 1) | digitalRead(pin1);
// Determine new state from the pins and state table
state = ttable[state & 0xf][pinstate];
// Return emit bits, ie the generated event
return state & 0x30;
}