This is a custom ESP32S3 prototyping board i built to troubleshoot the issues. It Started With a Simple Problem I was testing the EvilCrow Cable Wind — a USB HID device built around the ESP32-S3 that executes keystroke injection payloads over WiFi. Everything seemed fine: the keyboard HID was typing correctly, the web interface loaded, basic commands like RunWin worked. But ServerConnect and ShellWin did absolutely nothing. No error. No feedback. Just silence. Digging Into the Code The first thing I found was this pattern — repeated across four commands: ORIGINAL — DANGEROUS if (!clientServer.connect(serverIP, serverPort)) { while(1); // hangs forever if TCP fails } ⚠ Critical Bug If TCP connection failed for any reason, the device entered an infinite loop with no timeout, no error output, and no recovery path. Ever. But there was more. The bugs were stacking: critical TCP failures were environmental: listener ...
After a little modifications done to circuit and to the RX and TX code, i manage to use it as a remote controller. I fixed four buttons in TX side and receiver will detect which button is pressed and taddaaaa i can switch on an off anything that is connected to receiver board. I took some pictures so you guys can have a look at it...still planes are in my mind to design a cool thing..........
Transmitter modified
Receiver got command to switch on these 2 LED's
Transmitter modified
Receiver got command to switch on these 2 LED's
Comments