Medius - Native APIArchitecture

How it fits together

Mouse, box, and PC

The box has two chips joined by an internal link, plus a third port for your program. The clone is a copy of the real mouse's USB identity.

PartRole
Host chipReads the real mouse.
Device chipPresents the clone to the PC and merges your input into what it reports.
LinkPasses data between the two chips.
   real mouse                     game PC
        |                            ^
        | USB3                       | USB1
        v                            |
  +-----------+                +-----------+
  | host chip | ---- link ---> |device chip|
  +-----------+                +-----------+
                                     ^
                                     | USB2 (CH343 serial)
                                     |
                                control PC

Three connections:

PortConnects to
USB3The real mouse.
USB1The PC receiving the mouse.
USB2The program driving the box, over a CH343 serial link.

That program speaks the binary protocol, sending movement, button, and scroll commands.

What the PC sees

A real mouse, plus your input

To the PC the clone is the same model of mouse, with the same buttons and capabilities. Your input adds to the real mouse's input rather than replacing it (Injection Model), so the physical mouse keeps working either way.

When your programThe box
Sends inputLayers your movement, scroll, and button state onto the real mouse.
Goes quietReturns to plain passthrough, just a wire, per the safety rule.

Two computers

A separate driver host

Your program on USB2 runs on a different computer from the one receiving the mouse on USB1.

See Hardware for the ports and how to wire them, including the one pairing to avoid.