Air Mouse / open hardware

Air Mouse

A wearable Bluetooth mouse / ESP32 + MPU6050 / Open source

Curl two fingers, point at the screen, and the cursor goes where your hand goes. Let go and it stays put while you type.

Fig. 01 — The device, taken apart. Drag to turn it.

The 3D model needs WebGL, which this browser has switched off.

Fig. 02 — How it behaves

01 / How it works

Everything a mouse does, in the air.

Point

Hold the palm button by curling your middle and ring fingers. The cursor follows your hand: turn left and right, nod up and down.

Click

Three buttons on the side of the index finger, under your thumb. Left at the tip, then middle, then right.

Drag

Hold the palm button and left click together, then move your hand. Release the click to drop.

Scroll

Hold the middle button and tilt your hand up or down. A quick tap is a middle click.

Type

Let go of the palm button. Nothing moves, however much your hands do while you type.

Wear it

A plate on the back of the hand, two small control pieces on the index finger and the palm. A glove, a velcro strap or a splint all work. The firmware does not care.

[ See the parts → ]
  1. 01GyroHow fast the hand turns, 500 times a second.
  2. 02ZeroLearns the sensor drift whenever the hand rests.
  3. 03LevelUses gravity so a rolled wrist still moves straight.
  4. 04ShapeSlow is precise, fast crosses the screen.
  5. 05SendA Bluetooth mouse report every 8 ms.

It measures how fast your hand turns, not where it points, so the cursor never jumps when you press the palm button. It carries on from where it was.

Block diagram: the sensor and buttons feed the ESP32 firmware, which sends Bluetooth HID reports to the computer MPU6050gyro + accel Palm buttongates movement L / M / R buttonsindex finger ESP32 firmware 500 Hz sample loop Zero · level · shape · gate 125 Hz HID report BLE HIDmouse profile Computer
Fig. 03 — Signal flow, left to right.

Fig. 04 — Exploded assembly

02 / Anatomy

Take apart

Drag to turn it, pull the layers apart, tap a label or a part. Every board is drawn at its real proportions.

The 3D model needs WebGL, which this browser has switched off. The part list on the right still works.

Selected

Raid your drawers first

03 / Shopping list

Parts list

Everything you need, and why.

Tools: soldering iron, multimeter, breadboard and jumper wires, a small screwdriver for the boost module.

Skip power-bank style charge-and-boost boards (the IP5306 kind). They switch off when the load is light, which will randomly kill the mouse.

Fig. 05 — The bench

04 / Wiring

Wire it up

    Pin map
    WhatESP32 pinNote
    Power chain: battery, charger, switch, boost set to 5 volts, ESP32 VIN pin Li-po cellTP4056SwitchMT3608ESP32 VIN 3.0–4.2 Vcharges, protectshard offset to 5.0 V first5.0 V in
    Fig. 06 — The power chain.
    Three ways to fry it. Don't.
    1. Set the MT3608 to 5.0 V with a multimeter before it touches the ESP32.
    2. Never connect the battery straight to the 3V3 pin. A full cell is 4.2 V.
    3. Slide the switch off before plugging USB into the ESP32 to flash it.

    Also leave D0, D2, D5, D12 and D15 alone: they decide how the board boots.

    Each one works before the next

    05 / Build order

    Build order

      06 / Firmware

      Flash it

      Install PlatformIO, plug the ESP32 into USB, then:

      git clone https://github.com/JeyaVardhan-L/Air_Mouse.git
      cd Air_Mouse/firmware
      pio run -t upload
      pio device monitor

      Open your computer's Bluetooth settings and pair Air Mouse. The on-board LED blinks while it is looking for a host and goes dark once connected.

      If the LED blinks fast and never stops, the sensor was not found: check the four MPU6050 wires. If the upload will not start, hold the BOOT button on the board while it connects.

      Make it yours — firmware/src/config.h
      SettingDefaultWhat it does

      The numbers

      10–20 msHand to cursorDesign target
      500 HzSensor loopIn firmware
      125 HzReports to the computerIn firmware
      4–5 hPer 500 mAhEstimate

      Honest status: the firmware was written ahead of the first finished build. Measured latency, battery life and weight will replace the targets above once it has been built and tested.