Ports
The three USB ports and how to cable themInside are two ESP32-S3 microcontrollers and a CH343 USB-serial bridge. Your program only ever speaks to the CH343 serial port; the two chips talk over an internal 5 Mbaud link you never touch, separate from the 4 Mbaud control link.
| Port | Connects to | Role |
|---|---|---|
USB1 | Game PC | The clone (device chip), a copy of the mouse's USB identity, so the PC enumerates the same device it would if the mouse were plugged in directly. |
USB2 | Control PC | CH343 serial control, the /dev/ttyACM* port your program opens |
USB3 | Mouse | Real mouse (host chip) |
USB3 power hazard
The one wiring pairing to avoid⚠️ USB1 and USB3 must never both connect to the same machine.
The USB3 5V rail can't be pulled low in firmware, so wiring both to one machine back-feeds power and can force a shutdown or drain the battery.
Disconnecting
No power switch, just unplugThe box is USB bus-powered: no battery, no power button. Unplugging it is safe at any moment, and injected input never outlives the program that sent it, so a button or move can't get stuck.
| You unplug | What happens |
|---|---|
USB2 (control), or the program stops | After 1 s of silence the box clears all injection and falls back to pure passthrough. The real mouse keeps working. |
USB1 (clone) | The game PC gets an ordinary device detach; the box drops its injection state. |
USB3 (mouse) | The box tears down the captured mouse cleanly and reports it detached. |
To return to passthrough instantly instead of waiting out the silence timeout, send a RESET before unplugging (the library's reset). Dropping the Device stops its threads, after which the same timeout clears the box. Port order otherwise does not matter.
The one rule: USB1 and USB3 must not share a machine at any point, plugging in or unplugging. See the power hazard.