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 ...
During the last trial runs the boat just flipped over by an wave and sunken, but with help from a friend i was able to rescue it. When it was rescued almost all the electronics was under sea and started to corrode. With lots of cleaning and soldering i was able to run it again. But with new motor, ESC, SD card and battery. So after that i modified the boat a lot and the final result was very successful. Earlier the propeller was bit high and it don't cut enough water. Now the shaft and everything is lowed around 1 half inch. New brushless motor and ESC was tested for two weeks for speed controlling and finally a bit more water proofing. Old shaft coupler removed and made my own coupler for shaft and motor. Most of the firmware also cleaned up ;) After all these modifications i finally did a wonderful trial run. :) Early morning checked the tide table and it was perfect for test so packed everything and went to testing area. Today i have done continuous for ru...