-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ESC firmware corruption during settings write with esc-configurator #76
Comments
what QS version did you run? 0.9.5? |
yes |
does not appear to be a general issue, i just ran through a couple of scenarios. |
I'll try to investigate this problem more this week. |
A similar thing happened to me with my Mobula 7 1S ELRS on their X12 board. ESC 2 got wiped out and it took me a bunch of tries via different methods to get BLHeli_S back on it, and then re-flashed to BlueJay. Scary! I thought my board was toast. |
Please keep me up-to-date if you were able to gain more insight into what is happening here. |
Also want to note that Jhemcu gsf405a and superbee f4 have the same esc S-H-50. |
And maybe someone with GOKU Versatile F405 1-2S 12A (FLYWOOF405S_AIO) could try to repeat the same steps, because this FC is very similar to jhemcu. |
I don't know whether there is a connection but in the case of my Beta F4 1S serial ELRS if I load the ESC info in the QS configurator, then it won't work. I receive only corrupt info. But for me the ESC works well. |
I've checked Betafpv f4 1S 5a aio (Spi elrs) on QS 0.9.5 (esc o-h-5) - no issue. |
i might have come across something. previously QS would feed the blheli response bytes as they came to the usb serial port, which, depending on the current state of the usb buffer, could lead to some time passing between bytes. i have now introduced some additional buffering which makes it so that the response is always sent in one go. if for nothing else, that seems to make the esc configurator much quicker to load the settings. |
This was tried 2 times.
The text was updated successfully, but these errors were encountered: