Device topology
One box. Two different kinds of connection.
An input bridge is a small box that sits between your mouse and your PC. To the computer it looks like an ordinary USB mouse. To software running somewhere else, it looks like a serial port. Those are two genuinely different things, and understanding why is the whole of this page.
The hardware
Three ports, and the box is really two devices.
Dual RTS5411 controllers (MAKCU) or native 8,000 Hz isolated dual-USB-C hardware (Ferrum One) share the enclosure. One path speaks HID to your PC; the other carries the control link to the second computer. Pick a controller model and a path below to see which connections are involved.
Illustrated signal flow. Click the controller node or toggle above to swap between MAKCU (1K) and Ferrum One (8K).
MAKCU Hardware Port Architecture
Native 1,000 Hz Realtek PassthroughGoes to the PC you play on. The bridge presents itself here as an ordinary USB HID mouse — a standard mouse descriptor on a normal port at 1,000 Hz. Nothing about it looks unusual to the operating system.
The path your hand takes. It never leaves the hardware — the mouse is read and re-emitted as ordinary USB HID reports.
How it works
The two-computer relay, step by step.
This is the architecture the hardware was built for. Five steps, and every one of them is something you can check against the box in front of you.
The networking accessory
A “USB hub with Ethernet” is not a hub.
It reads like it should be: take a hub, add a network port, done. What is actually in the case is two unrelated things sharing an enclosure.
A USB hub
One upstream USB port fanning out to several downstream ports. It knows how to enumerate devices and hand them to the host. This is the half that carries your mouse.
A USB-to-Ethernet bridge
A network card on one side, a USB device on the other, and a chip in the middle translating between them. Nothing about the Ethernet jack is connected to the hub function — they are neighbours in the same box, not a chain.
And that is where VLANs come in
Once commands travel over IP rather than over a cable, they are ordinary network traffic — which means they can be placed on a separate VLAN, routed, or blocked by anything in between. A VLAN is just a separate logical network on the same physical wiring; routing is what lets a packet cross from one to another. That gives you real control over the path: which subnet the device appears on, what can reach it, and what it can reach. It also means the path can leave the machine if you route it that way, which is the honest thing to know before you build on it.
Choosing a transport
Ethernet, Wi-Fi, or BLE.
The three ways the command channel can be carried. They are not interchangeable and none of them is best for everyone — this is the trade-off, stated plainly.
Wired Ethernet
- Latency
- Lowest and most consistent
- Range
- Whatever cable you run
- What it costs you
- A bridge plus a cable, plus a switch if nothing is nearby
- Reliability
- Best — a wired link does not renegotiate
The sensible default whenever a socket is within reach.
Wi-Fi
- Latency
- Higher and variable
- Range
- Room to building
- What it costs you
- A wireless module only
- Reliability
- Good, but the radio shares the air with everything else on it
Fine when cabling is genuinely awkward; latency varies with the network.
Bluetooth LE
- Latency
- Highest of the three, and bursty
- Range
- Short — room scale
- What it costs you
- A wireless module only
- Reliability
- Power-saving reconnects mean gaps, not smooth streaming
Built for control surfaces and battery devices, not for continuous input.
Moving the commands does not change what the device is.
On two computers, the control link lands on the second machine — not on the one running the game. On one computer, there is nowhere else for it to land. The board's second port still has to plug into that same machine, and security software running on it can see the connection. Putting the commands on the network instead changes where they travel. It does not make the setup sanctioned, and it does not change what any of these games consider cheating.
If your input device is being driven by software in a competitive online multiplayer game, that is against those games’ terms of service and it will cost you the account. This holds whatever transport you use. The two-computer topology is the one the hardware was designed around, and it is the one worth building on.
Nothing on this page is a bypass, and we do not sell one. If you are looking for that, this is the wrong product.
What you need
Start from what you are doing.
Not from a parts list. The bridge is the same in all four cases; what changes is where the control software runs and how honest the answer is about the rest.
Two-computer relay
VerifiedThe documented topology. A second computer runs the control software and talks to the bridge over the serial link on USB 2.
Input remapping / accessibility
VerifiedControl software on one machine, your input device on the bridge, your PC on USB 1. Nothing needs to leave the room.
Input testing and automation
VerifiedA repeatable command path into a device you can drive from software. Useful for hardware QA and for testing your own setup.
One computer, no second machine
Needs thinkingTechnically reachable with a networked accessory. Read the honesty note below before you build anything around it.
Passthrough coverage varies by device and firmware. Mouse support is the reliable path; keyboard and gamepad support depends on the model — check before you buy on the assumption it will work.
Troubleshooting
The five faults we actually see.
Most reports that arrive as “the hardware is broken” are one of these.
The second computer does not see the control link
Check the cable and the port first: re-plug the control-link connection, try another USB port on the second machine, and confirm the board is powered over USB. If the link stays down across cables and ports, that is a hardware fault and it falls inside the replacement window.
My mouse shows up as a keyboard, or stops working entirely
A recurring fault with high-polling devices: some 8000 Hz mice are parsed with the wrong HID report descriptor and enumerate as a keyboard-class device. It is a parser limitation, not a dead port, and it is resolved by firmware. Check whether your exact model is listed before you assume the hardware is faulty.
A port stopped responding
Re-plug that connection and try another cable and USB port before assuming the worst — most dead ports are cables. If a port stays down across cables, ports and machines, that is a hardware fault and it falls inside the replacement window.
It works after a warm restart but not on a cold boot
A timing race at enumeration: the bridge is being polled before the PC has finished bringing the USB bus up. Replug the host connection after boot and it will resolve; if it happens on every cold boot, that is a hardware fault and it falls inside the replacement window.
My keyboard does not pass through
Passthrough coverage is not universal. Mouse support is the well-trodden path; keyboard and gamepad parsing depends on the device and the firmware version. Confirm your specific model is supported before buying on the assumption it will work.
Next step
Now you know what the thing is.
Compare the controllers side by side, or tell us what you are building and we will say whether this hardware fits it. Every hardware order carries 30 days of TRUE Support, and defective units are replaced inside the warranty window.