77 lines
4.0 KiB
Markdown
77 lines
4.0 KiB
Markdown
|
Rotary Encoder Arduino Library
|
||
|
|
==============================
|
||
|
|
|
||
|
|
Arduino library for reading rotary encoders that output a 2-bit [gray code](http://en.wikipedia.org/wiki/Gray_code).
|
||
|
|
|
||
|
|
Rotary r = Rotary(2, 3);
|
||
|
|
|
||
|
|
void setup() {
|
||
|
|
r.begin();
|
||
|
|
}
|
||
|
|
|
||
|
|
void loop() {
|
||
|
|
result = r.process();
|
||
|
|
if (result) {
|
||
|
|
Serial.println(result == DIR_CW ? "Right" : "Left");
|
||
|
|
}
|
||
|
|
}
|
||
|
|
|
||
|
|
This is a repackaged version of Ben Buxton's excellent [rotary library](http://www.buxtronix.net/2011/10/rotary-encoders-done-properly.html) organized for the Arduino 1.x IDE, keyword highlighting, polling example, Arduino library capitalization conventions.
|
||
|
|
|
||
|
|
Features
|
||
|
|
--------
|
||
|
|
* Debounce handling with support for high rotation speeds
|
||
|
|
* Correctly handles direction changes mid-step
|
||
|
|
* Checks for valid state changes for more robust counting / noise immunity
|
||
|
|
* Interrupt based or polling in loop()
|
||
|
|
* Counts full-steps (default) or half-steps
|
||
|
|
* Supports use with pull-up (default) and pull-down resistors
|
||
|
|
|
||
|
|
Installation / Usage
|
||
|
|
--------------------
|
||
|
|
1. Download and unzip to Arduino\\libraries\\Rotary. So for example Rotary.h will be in Arduino\\libraries\\Rotary\\Rotary.h.
|
||
|
|
2. Restart Arduino IDE
|
||
|
|
3. File -> Examples -> Rotary
|
||
|
|
|
||
|
|
Note: Resistor usage is specified through `void begin(bool internalPullup=true, bool flipLogicForPulldown=false)`.
|
||
|
|
* `r.begin()` enables the Arduino's internal weak pull-ups for the rotary's pins
|
||
|
|
* `r.begin(false)` disables the Arduino's internal weak pull-ups for the given pins and configures the rotary for use with external _pull-ups_
|
||
|
|
* `r.begin(false, true)` disables the internal pull-ups and flips the pin logic for use with external _pull-downs_
|
||
|
|
|
||
|
|
Background
|
||
|
|
----------
|
||
|
|
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. In Rotary.h, uncomment `#define HALF_STEP` to enable half-step mode.
|
||
|
|
|
||
|
|
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.
|
||
|
|
|
||
|
|
License
|
||
|
|
-------
|
||
|
|
GNU GPL Version 3
|