KMBOX Guide — Understanding the KMBOX NET and KMBOX B Pro
Input Routing in Detection Research
You have two PCs, one keyboard, one mouse. How do you control both without physically unplugging and replugging cables? An input routing device handles this. It intercepts your keyboard and mouse, decides which PC should receive each input, and forwards accordingly. No driver installation on the target PC (which is critical for staying stealthy). Just hardware-level switching that anti-cheat software can’t monitor or block.
KMBox and Macku are the two most popular options in the research community. They solve the same problem but use different architectures. Here’s what you need to know.
KMBox NET vs. KMBox B Pro: Feature Comparison
Both are input routing devices, but they differ in network capability and speed specs.
| Feature | KMBox NET | KMBox B Pro |
|---|---|---|
| Polling Rate | 1000 Hz | 1000 Hz |
| Network Capable | Yes (100M Ethernet) | No |
| USB I/O | Dual USB (in + out) | Dual USB (in + out) |
| Cable Setup | USB + Ethernet | Dual USB |
| Best For | Remote or networked setups | Local dual-PC labs |
| Price Tier | Mid-range | Budget |
The NET version is built for flexibility—it can route inputs over a network, so your research PC and target PC don’t have to be sitting next to each other. The B Pro is simpler and cheaper, optimized for a tight dual-PC setup in the same room with USB cables.
Polling Rate and Input Latency
Both KMBox models poll at 1000 Hz, which means they check your keyboard and mouse 1000 times per second. That translates to a maximum latency of 1 millisecond per input. In practical terms, when you press a key, the target PC registers it nearly instantly. There’s zero perceptible lag.
This is critical for detection research because some anti-cheat systems measure input timing. If there’s a noticeable delay between key presses on your research PC and actions on the target PC, it can trigger suspicion. 1000 Hz polling keeps you under the radar.
Dual USB I/O and Device Chaining
Both KMBox models have two USB ports: one input (where your physical keyboard and mouse plug in) and one output (where the KMBox connects to the target PC). This is how it sits in the middle of the signal chain.
Your physical peripherals plug into the KMBox input. The KMBox reads them, decides which PC should receive each input, and either keeps it local (forwards to the research PC) or sends it to the target PC via the output USB port.
You can chain multiple KMBox devices if you’re running a larger setup with three or more PCs, though this is rare. Most people stick with one device.
Network Capability: When You Need the NET Version
The KMBox NET adds Ethernet connectivity. Instead of USB cables, you can route inputs over your local network. This is useful if your target PC is in a different room, on a different floor, or in a remote lab setup. Network speed is capped at 100M Ethernet, which is plenty for keyboard and mouse data—you’re only transmitting a few hundred bytes per second.
If your research PC and target PC are in the same physical location (typical), the USB-only B Pro is simpler and cheaper. If you need distributed flexibility, the NET justifies the extra cost.
Firmware and Customization
Like DMA cards, KMBox devices support custom firmware. Out of the box, they route inputs based on simple rules (keyboard to PC 1, mouse to PC 2, etc.). Custom firmware lets you build more complex behavior—conditional routing based on which window is in focus, macro recording and playback, dual-input simulation, and more.
Firmware customization requires C or assembly knowledge, but the community has pre-built options. Check DepShop’s Discord for shared firmware packages.
Integration with DMA and Fuser Setups
KMBox is the third leg of a complete detection lab. DMA card handles memory access. Fuser handles video. KMBox handles input. All three are independent and work together:
You sit at your desk with one keyboard and mouse. Everything goes to the KMBox. The KMBox decides whether each keystroke or mouse movement goes to your research PC or the target PC. Your research PC runs your detection tools. Your target PC displays on a merged monitor (via the fuser) and receives inputs from your KMBox. The DMA card in your target PC lets your research tools read and write memory over USB.
Clean, modular, independent. Each device does one thing well.
When You Actually Need a KMBox
If you’re running a single detection PC and occasionally testing software on a separate target machine, KMBox is overkill. Use it for serious research labs where you’re constantly switching between your tools and your target.
If you’re building a professional dual-PC setup or a multi-machine research environment, KMBox (or Macku) is essential. It saves you from unplugging cables, managing multiple keyboards, or dealing with software KVM solutions that add latency and require drivers.
The DMA Bundle includes a Macku board instead of KMBox (because Macku is cheaper), but both devices serve the same purpose. If you prefer KMBox’s network capability, you can swap it in easily.
KMBox vs. Macku: Which Should You Choose?
Macku uses an ESP32-S3 microcontroller and is more affordable. KMBox uses dedicated input routing hardware and adds network capability with the NET version. KMBox is faster, more feature-rich, and better for complex setups. Macku is simpler, cheaper, and sufficient for most users.
Think of it this way: if you’re just starting out, Macku gets you 90% of the way there at half the price. If you need network routing, high-end customization, or you’re building a professional lab, KMBox justifies the investment.
Firmware Updates and Community Support
Both KMBox and Macku have active community support. Firmware updates are released regularly to fix bugs, improve compatibility, and add new features. Updates are usually straightforward—download the firmware file, plug the device into your research PC’s USB port, run the update utility, and you’re done.
The DepShop Discord is the hub for firmware discussion, custom builds, and troubleshooting. If you’re stuck, someone in that community has solved it before.
Setting Up Your KMBox
For the B Pro (USB-only): Plug your keyboard and mouse into the KMBox input port. Plug the KMBox output port into the target PC’s USB. The KMBox powers on automatically (it draws power from the USB connection). Your research PC will detect the new USB device. On Windows, it may install drivers automatically. Once recognized, open your KMBox control software, set which inputs go to which PC, and you’re done.
For the NET version: Same USB setup, but also connect the Ethernet port to your network. The NET version will auto-assign itself a local IP address. Your control software can then operate over the network, giving you routing from anywhere on your LAN.
Troubleshooting KMBox Issues
If the target PC doesn’t recognize the KMBox output, try a different USB port on the target machine. Some USB ports have lower power delivery; the KMBox needs at least 500 mA. If you’re using a USB hub, make sure it’s powered.
If keyboard input works but mouse doesn’t (or vice versa), you may need a firmware update. Check the DepShop Discord for the latest version and the update procedure.
If the NET version isn’t routing over Ethernet, verify that your network switch or router has DHCP enabled. The KMBox will request an IP address on startup. If it doesn’t get one, it won’t be reachable on the network.
FAQ
Can I use a KMBox with a laptop?
Yes. If your target machine is a laptop, the KMBox output USB port connects the same way. Laptops have USB ports just like desktops.
What if I have three PCs?
You’d need multiple KMBox devices or a more complex setup. For three or more machines, consider an enterprise KVM switch, but those are expensive and require driver installation. Most research labs stick to two PCs and scale up only if necessary.
Is the KMBox detectable by anti-cheat?
The KMBox is a hardware device that looks like a standard USB hub to the OS. Anti-cheat software can’t detect it as a routing device because it presents itself as a normal input device. This is one of its major advantages over software-based input switching.
How fast is the Ethernet on the NET version?
100 Mbps, which is plenty for keyboard and mouse data. You’re transmitting maybe 100–500 bytes per second at most. Even 10 Mbps would be enough; 100 Mbps is overkill but ensures you never hit bandwidth limits.
Can I update firmware over the network?
Some NET firmware versions support OTA (over-the-air) updates, but USB update is the standard method. It’s more reliable and doesn’t require network configuration. Stick with USB updates unless you have a specific reason to do OTA.
Where can I get custom firmware?
The DepShop Discord has a firmware library with community builds. If you want to build your own, the KMBox hardware is well-documented and the community has example code. Start in the Discord if you’re new to customization. For DMA card firmware specifically, DepShop also stocks custom DMA firmware for BE/EAC/ACE bypass.
How does KMBox compare to a software KVM?
Software KVMs (like Barrier or Synergy) require drivers and software running on both PCs. They add latency, can be detected by anti-cheat, and don’t work if one PC crashes. Hardware KMBox is independent, requires no software on the target PC, and adds only 1 millisecond of latency. It’s the superior choice for detection research.