A MOUSE YOU CONTROL WITH YOUR LIPS, FOR PEOPLE WHO CANNOT USE THEIR HANDS
A small mouthpiece on a sensor board that moves a cursor and clicks with lip movement and breath, presenting to any computer as an ordinary USB mouse.
Open-hardwareHealth
Built withArduinoRaspberry Pi Pico / RP20403D printing
- difficulty
- ●●●○○
- time
- a weekend
- license
- CC-BY-SA-4.0 (hardware, docs, images), GPL-3.0 (firmware and GUI)
- repo
- repo ACTIVE43 stars
●●●○○ · a weekend · CC-BY-SA-4.0 (hardware, docs, images), GPL-3.0 (firmware and GUI) · 43 stars · repo ACTIVE
WHAT YOU’LL NEED
Jump to section
COMPAREE VERDICT
FLipMouse is a genuine assistive device that replaces a mouse and keyboard entirely, designed for people with no hand function. Lip movement drives the cursor in all directions, and a light sip or puff of air clicks. It presents itself to the computer as an ordinary USB mouse, keyboard and joystick, so there is no software to install and it works with any operating system. The AsTeRICS Foundation made this to be reproducible: the repository has KiCad schematic and PCB files, the enclosure design, a full part list and a photographed construction manual, and the Foundation also sells the official DIY kit. The board uses an Arduino Nano RP2040 Connect; strain gauges measure the tiny forces on the mouthpiece and a pressure sensor catches sip and puff. The real work is tuning: in the web-based Configuration Manager you adjust sensitivity and assign actions to each person's range of movement, so if you are building this for someone else, plan time to sit with them. Hardware files are CC BY-SA 4.0 and the code GPL v3, both permitting commercial use. There is a companion FLipPad touchpad in a separate repository.
IN THE REPO
GOOD TO KNOW
- —KiCad PCB design, enclosure files and part list are in this repository; current firmware lives in the separate FabiWare repository.
- —Step-by-step assembly guide with a photograph of every stage.
- —BOM lists every component with supplier part numbers and alternatives.
- —Licence is CC BY-SA 4.0 for hardware design files, documentation and images, and GPL v3 for the source code — both stated in the repo and both permit commercial use.
- —The FLipPad touch version is in a separate repository with the same structure.
- —No driver installation on the host computer — presents as a standard USB HID mouse and keyboard.
Parts to buy
6 itemsFrom our check of the build. Exact quantities and part numbers are in the creator’s BOM.
Can I build this?
Build at your own risk. Projects involve tools, electronics and sometimes mains voltage — follow the creator’s safety notes.
More builds like this
All projectsGallery
Start here
Navigation into the creator’s own docs — we don’t rewrite the guide, we route you to the source.
- 1.Read the Construction Manual (ConstructionKit/ConstructionManual.pdf) (Every assembly step is photographed — start here to see what the build actually involves)
- 2.Order the PCB using the KiCad PCB source files in the Hardware folder (Export Gerbers from the KiCad files first, then order from any PCB fab; minimum quantity is usually 5 boards)
- 3.Order components from the BOM(The part list is FM3_BOM.xls in the Hardware folder; the strain-gauge sensor and the Arduino Nano RP2040 Connect are the parts to get exactly right.)
- 4.Print the enclosure parts (case base, front, lid and the Luer spacer)(The mouthpiece is not printed: it is an acrylic pipe glued to a Luer Lock adapter, with a filter, as described in the mouthpiece fabrication note (or included in the kit).)
Resources
Documentation, files and community threads for this build — we link straight to the original sources and never rehost the creator’s files.
KNOWN ISSUES
- The calibration step is harder than the assembly - plan an evening with the actual user adjusting sensitivity and actions in the Configuration Manager, using the user manual as your guide.
- The strain-gauge sensor under the mouthpiece is the delicate part — handle it carefully during assembly, because a damaged gauge gives drifting, erratic cursor movement.
- The mouthpiece is exposed to saliva: clean or replace it (or its filter) regularly, following the cleaning instructions in the repo. If you build for someone else, keep a spare mouthpiece and filters.
- The pressure sensor tubing must remain unobstructed or the sip-and-puff click will not register — test it before final assembly.
- PCB minimum order quantity is usually 5 boards, so the per-unit cost drops sharply if building multiples or sharing an order.
- Firmware since v3.7 lives in the separate FabiWare repository; the web Configuration Manager can update it, so you only need Arduino tooling if you want to modify the code.
Does this need special software on the computer it plugs into?
No. It presents itself as a standard USB HID mouse and keyboard, so any operating system recognises it immediately with no drivers.
Can I build the FLipPad touch version instead?
Yes, it is in a separate repository with the same documentation structure. The FLipPad is for people who can still use a finger but not a standard mouse.
How do I calibrate the sensors for a specific person?
Open the FlipMouse Configuration Manager (flipmouse.asterics.eu) in Chrome or Edge: it sets sensitivity, sip/puff thresholds and actions, and stores several profiles on the device. The user manual explains each setting.
Is this a certified medical device?
No. It is an open-source assistive technology project, not a certified medical device, and it carries no regulatory approvals.
Can I sell these?
Yes. The hardware files are CC BY-SA 4.0 and the code GPL v3, both of which permit commercial use as long as you credit the AsTeRICS Foundation and share modifications under the same licence.
Community builds
No community builds yet — be the first, we feature the best ones.
Discussion1
FROM THE COMPAREE TEAM
A full construction manual and a browser-based configuration tool make the build approachable, but every user needs their own settings. If you have set one of these up for an actual user, which sensitivity and action settings worked?
AsTeRICS Foundation
The AsTeRICS Foundation develops open-source assistive technologies for people with disabilities. FLipMouse and FLipPad are part of a broader ecosystem of adaptive input devices, all built to be reproducible at home with standard fabrication tools.
DISCLAIMER
- Comparee is not the author of the projects featured here. All rights to each project belong to its creator — every page links to the original source, and we never host creators’ files.
- Information is provided without warranty and may become outdated as projects evolve. Prices are indicative bands only — always check the creator’s parts list for current costs.
- Building and operating any project is at your own responsibility. Protective equipment, safe workshop practice and compliance with local regulations are the builder’s responsibility.
CompareeTEAM2mo agoedited
Practical notes from our verification: the repository is actively maintained (pushes in September 2026), the FLipPad companion project is in a separate repository under the same organisation, and newer firmware (v3.7 onward) lives in the separate FabiWare repository. The construction manual is a PDF in the repo, with a full parts list in the Hardware folder, and the official kit is sold by the AsTeRICS Foundation. Mouthpiece movement is measured with strain gauges and sip/puff with a pressure sensor; all tuning to a person's range of movement is done in the web-based Configuration Manager (Chrome or Edge), which can also update the firmware. The README does not link any official video walkthrough. Licensing: hardware design files, documentation and images are CC BY-SA 4.0, the code is GPLv3. Correction 21 August 2026: this page previously said the mainboard uses an ESP32 and that the repository ships Gerber files. The FLipMouse V3 mainboard uses an Arduino Nano RP2040 Connect; an ESP32 appears only as an optional Bluetooth add-on module. The repository contains KiCad schematic and layout sources, not exported Gerbers - you generate those yourself. Correction (4 October 2026): we re-checked this page line by line against the project's own repository, documentation and videos, and fixed errors in earlier versions.