- Status
- Offline
- Joined
- Mar 3, 2026
- Messages
- 421
- Reaction score
- 7
Anyone else digging into the KMBox B+ and hitting a brick wall during the handshake?
I've got a dual-PC DMA setup running, and things seem fine until the moment the cheat software attempts to initialize the connection to the KMBox. As soon as that serial port is opened by the software on the second PC, the output from the box just dies.
The Symptoms:
Technical Troubleshooting:
I've already double-checked the VID/PID and the COM port numbers. If you're running into this, it's usually not a 'broken' box but a protocol hang or a firmware deadlock. In my experience with these Chinese controllers, they can be extremely finicky about how the serial handle is managed.
It is a massive headache when the hardware is verified but the software init kills the output. It feels like a serial buffer overflow or the controller firmware is crashing on the first packet.
Anyone else had their KMBox B+ just ghost them the moment the software starts talking to it?
I've got a dual-PC DMA setup running, and things seem fine until the moment the cheat software attempts to initialize the connection to the KMBox. As soon as that serial port is opened by the software on the second PC, the output from the box just dies.
The Symptoms:
- HID passthrough works perfectly during normal use (mouse/keyboard movement through the box).
- The COM port is correctly detected on the second PC.
- Everything suddenly stops—zero mouse output—the moment the DMA cheat tries to connect.
Technical Troubleshooting:
I've already double-checked the VID/PID and the COM port numbers. If you're running into this, it's usually not a 'broken' box but a protocol hang or a firmware deadlock. In my experience with these Chinese controllers, they can be extremely finicky about how the serial handle is managed.
- Baud Rate Mismatch: Most B+ setups expect 115200, but some custom firmware builds might be picky about the buffer size or parity bits.
- USB Power: If the KMBox is drawing power through a low-quality hub, the controller can brown out or reset when the serial chip starts active communication.
- Firmware Version: Verify if you are flashed with the standard B+ serial firmware. Some 'Pro' versions use different command sets that cause a crash if the software sends an unhandled opcode.
- Driver Conflict: Ensure the CH340/CP2102 drivers on the second PC aren't being intercepted by another process.
It is a massive headache when the hardware is verified but the software init kills the output. It feels like a serial buffer overflow or the controller firmware is crashing on the first packet.
Anyone else had their KMBox B+ just ghost them the moment the software starts talking to it?
