Projects

Designing a USB Auto-Clicker: From Hardware to Enclosure

By Eduardo Cortés Trujillo (Lalo Solo) · ~7 min read

AutoClick is a small USB device I designed that the computer sees as an ordinary mouse, but which clicks on its own at an interval you set. It is a tidy example of taking a project all the way from a circuit on the bench to a finished, enclosed product — and every stage taught me something worth sharing.

The idea: a hardware HID device

A software auto-clicker is just a program, and many applications and operating systems block or distrust them. A hardware auto-clicker sidesteps that entirely: it enumerates as a standard USB Human Interface Device (HID) mouse, so to the computer it is simply another pointing device sending genuine click events. No drivers, no software to install.

Choosing the microcontroller

The heart of the project is a microcontroller with native USB support that can present itself as a HID device. The firmware's job is small but precise: describe a mouse to the host during enumeration, then emit click reports at the chosen cadence. Keeping the descriptor correct is what makes the device "just work" the moment it is plugged in.

The circuit

Around the microcontroller the circuit is deliberately minimal: the USB connector and its data lines, decoupling capacitors on the supply, a button or two for control, and an LED for status feedback. A simple, well-decoupled board is a reliable board — and reliability is what separates a one-off hack from something you can hand to someone else.

The firmware and the circuit are only half the work. A project becomes a product when someone can use it without you standing next to it explaining how.

The enclosure

This is where my 3D-printing and CAD work meet the electronics. I modelled an enclosure sized to the board, with a cut-out for the USB connector, a hole for the status LED, and access to the control button. Designing the case around the real PCB — rather than the other way around — means the parts fit on the first print, and the finished device feels intentional rather than improvised.

From project to product

The difference between "I built a thing" and "here is a product" comes down to the unglamorous details:

Why these end-to-end builds matter

Projects like AutoClick are where the separate skills I enjoy — electronics design in KiCad, firmware, CAD, and 3D printing — come together into one object. That whole-stack practice is exactly the mindset I bring to my day job delivering IT projects: understand the requirement, design a solution, and ship something that actually works in someone's hands.

🛠️

Building your own HID device? Get enumeration and a single correct click working first. Everything else — timing, buttons, enclosure — is easier once the host trusts your descriptor.

← All articles