跳到主要内容
主页代理入口联系客服

Hardware guide

kmbox: USB HID Bridging in Two-Machine Setups

kmbox is a family of USB HID emulation devices — small boxes that present themselves to a computer as a keyboard and mouse, and receive input instructions over a network link from another machine. They solve a different problem than DMA hardware, which is why the two are often paired: one reads information, the other delivers input.

Last reviewed: 2026-11-14Published by Heino HMA Hardware Lab

Two halves of a two-machine setup

A DMA card reads host memory and sends it out. A kmbox receives instructions and presents them as USB input. Neither does the other job. Understanding that split explains most of the topology diagrams you will see.

TypeUSB HID emulation device
Presents asKeyboard and mouse (composite HID)
LinkEthernet (net) or USB (fusion variants)
RoleInput delivery, not memory access

What a kmbox actually is

At the hardware level it is a microcontroller with a USB device controller: it enumerates as a composite HID device — typically a keyboard and a mouse — and accepts commands over a second interface, usually Ethernet or a serial link.

Because it presents as a standard HID device, the host operating system loads its own generic HID driver. From the host's perspective there is nothing unusual: a keyboard and mouse were plugged in. That is the entire mechanism, and it is why the device class is so widely supported.

Why HID emulation is technically unremarkable

USB HID is a mature, well-documented standard. Every microcontroller vendor ships example code for a HID keyboard. There is no exotic capability here: an Arduino can do it, and the protocol has been open since the late 1990s.

What makes a commercial device different is the firmware around it: input timing, movement smoothing, command protocol and reliability under load. Those are engineering choices, not capabilities the standard grants.

AspectRealityMarketing claim to discount
USB identityStandard composite HID"Undetectable hardware ID"
Input pathHost driver receives HID reports"Bypasses the OS input stack"
TimingFirmware-dependent, millisecond scale"Zero latency"
DetectionBehaviour is visible to the game"Invisible to anti-cheat"

How kmbox pairs with DMA hardware

The two-machine topology separates reading from acting. The DMA card sits in the target machine and reads memory over an external link to an analysis machine. The kmbox sits on the target machine's USB bus and receives movement commands over the network from the same analysis machine.

That split exists for a practical reason: the analysis machine has the compute to process information, and neither device needs to run software on the target. The topology diagrams vendors publish are simply this arrangement.

Where the rules boundary sits

A kmbox is an input device. Using one to automate gameplay in a game whose Terms of Service prohibit automation is a rules violation regardless of how the device presents itself, because the prohibition is on the behaviour, not the hardware.

Legitimate uses exist: accessibility hardware that translates alternative input methods into HID reports is a well-established category, and HID emulation is standard in industrial test rigs and kiosk input simulation. The distinction is whether the resulting input is something the operator of the receiving system permits.

  • HID emulation itself is ordinary and widely used.
  • Automation in a game is prohibited by behaviour, not by device.
  • Accessibility and test-rig use are established legitimate categories.

What actually differs between devices

Firmware quality: how consistently movement commands are translated, and whether timing drifts under sustained input. This is the difference you notice in use, and it is not visible in a spec sheet.

Link stability: Ethernet-based units tolerate longer cable runs; USB-based units are limited by cable length and hub quality. Most "input lag" complaints trace to a hub in the path.

Firmware update path: same question as with any embedded device — who maintains it, and how do you recover a bad flash.

How the input actually reaches the game

A HID device sends reports over interrupt endpoints: a small packet containing button states and movement deltas, delivered at a fixed interval. The host controller receives it, the operating system's HID driver parses it, and the input is placed in the system input queue where the game reads it.

Every stage in that chain is ordinary. There is no side channel and no privileged path. What a game can observe is the same thing it observes from any keyboard: the resulting cursor movement and key state, timestamped by the OS.

This is why input devices are analysed behaviourally rather than structurally. Movement that is perfectly smooth at every scale, or corrections that land with machine precision, are visible in the input stream itself — no device inspection required.

Frequently asked questions

01What is a kmbox?

A USB HID emulation device that presents itself as a keyboard and mouse and receives input instructions from another machine over a network or serial link.

02Is kmbox the same as DMA?

No. A DMA card reads host memory. A kmbox delivers input. They solve different problems and are often used together in two-machine topologies.

03Can a kmbox be detected?

It presents as a standard composite HID device, which is entirely ordinary. What is visible is the resulting input behaviour, and that is what behavioural systems act on.

04Are there legitimate uses for HID emulation?

Yes. Accessibility hardware, industrial test rigs and kiosk input simulation all use HID emulation. The question is whether the receiving system permits the resulting input.

05Does a kmbox bypass the Windows input stack?

No. It presents as a standard composite HID device, so input flows through the normal HID driver and system input queue like any keyboard or mouse.

Official references

  1. USB-IF: HID class specification
  2. Microsoft: HID drivers
  3. Linux kernel: USB HID
HMA 安装支持

售后支持已迁移

IM 售后频道已关闭,售后服务已转移至 Discord。

前往 Discord