Motion
Interfacing KY 040 Motion with STM32 Blue Pill
What is the KY 040?
KY 040 practical reference
A rotary encoder with a push-button, widely used for volume knobs, menu navigation, and precise incremental control input.
Key specifications
- Type: Incremental mechanical rotary encoder with integrated momentary push-button
- Resolution: 20 detents (clicks) per full revolution, 20 pulses/rev quadrature output
- Output type: 2-bit quadrature (Gray code) on CLK/DT, direction derived from their phase relationship
- Operating voltage: 3.3V–5V DC
- Mechanical life: ~30,000 rotation cycles typical for this class of encoder
- Interface: Digital — 2 GPIO for rotation (CLK, DT) + 1 GPIO for the push-button (SW), no bus protocol
- Debounce requirement: Mechanical contacts bounce for a few ms on both rotation and button press — needs software or hardware debouncing
Pinout and connection notes
Decode direction from CLK+DT phase, not CLK alone — reading CLK by itself only tells you that the knob moved, not which way. Standard quadrature decoding compares the current and previous state of both CLK and DT to determine clockwise vs counter-clockwise.
Use an interrupt on CLK, not polling — polling in loop() is unreliable at typical rotation speeds and will miss steps. Attach a hardware interrupt (attachInterrupt) on the CLK pin and read DT's state inside the handler to catch every transition.
Debounce in software — mechanical contacts bounce for a few milliseconds; a naive interrupt handler will often register 2-4 counts per physical click. A simple time-based debounce (ignore transitions faster than ~1-5ms apart) or a state-machine decoder fixes this — don't rely on the raw interrupt count.
Direction feels backwards? Swap CLK/DT in code, not wiring — if clockwise rotation decreases your counter, it's almost always just a CLK/DT swap; flipping the two variable names in your decode logic is easier than re-wiring the module.
SW is a separate mechanical switch, not electrically related to the encoder — it needs its own pull-up (INPUT_PULLUP is fine) and its own debounce handling, independent of the rotation logic.
- GND: Ground
- +: Power, 3.3–5V DC
- SW: Push-button output — LOW when pressed (active LOW, needs pull-up if board doesn't include one)
- DT: Quadrature channel B — read alongside CLK to determine rotation direction
- CLK: Quadrature channel A — the primary channel to trigger an interrupt on for reliable counting
Integration checklist
- Confirm the exact part number and breakout-board revision.
- Verify supply voltage, current demand, logic levels, and signal direction against the datasheet.
- Check controller pin assignments and bus address or interface mode against the example code.
- Power up with external loads disconnected, then test signals before full integration.
- If readings or communication fail, check power and ground first, then pin mapping, interface settings, and library initialization.
Troubleshooting and reproducibility
Record the board used, wiring, library/version, supply arrangement, and measured behavior. Use the selected board-specific wiring example as the source of truth. Never assume visually similar modules share identical voltage tolerance or pin order.
Setting Up KY 040 with STM32 Blue Pill
Wiring
| Component pin | STM32 Blue Pill pin | Note |
|---|---|---|
| + | 3.3V | |
| GND | GND | |
| CLK | PA1 | All Blue Pill GPIOs support external interrupts |
| DT | PA2 | |
| SW | PA3 |
Swipe sideways to see every column →
- Every GPIO on the Blue Pill supports external interrupts, same flexibility as the ESP32 — no fixed-pin limitation like the Arduino Uno.
- Same button-is-separate and cheap-encoder-bounce caveats as the other boards.
- Usual Blue Pill Serial-over-USB caveat applies if you don't see output.
Related Components
Related Guides & Projects
STM32 Low-Power Modes: Sleep, Stop, and Standby Explained (With Working Code)
A practical guide to STM32's three-tier low-power system — Sleep, Stop, and Standby — with working STM32duino code, measured current draw on a Blue Pill, and a battery-powered project example.
STM32 Blue Pill Pinout: Every GPIO, ADC, and Alternate Function Explained
A complete STM32F103C8T6 Blue Pill pinout reference: every GPIO port, ADC channel, timer, and communication bus mapped, plus the 5V-tolerance and clone-board considerations that affect wiring decisions.
STM32 Black Pill Pinout: Every GPIO, ADC, and Peripheral Explained
Complete STM32 Black Pill (STM32F411CEU6) pinout reference: GPIO ports, 12-bit ADC, timers/PWM, USART, SPI, I2C, and the 3.3V-only pins to watch out for.
STM32 Nucleo Pinout: Arduino Headers, Morpho Connectors, and GPIO Explained
Complete STM32 Nucleo pinout reference: Arduino-compatible headers vs ST Morpho connectors, the built-in ST-LINK debugger, ADC voltage limits, and every peripheral pin mapped.