-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
BL_heli temporarily knocks out motor #540
Comments
https://photos.app.goo.gl/FsRAbmyS8LkAeMyD9 little video of it |
@Ricky-Millar It's hard to guess, which BLHeliSuite32 and which Betaflight FC and version you are using. In order to better understand what's going on here, please enable the log function under "Options", repeat the steps you have done before, and post the log.tlg as zip file here. Also it maybe helpful to know, if there is anything special in the ESC settings (beside of reversed ESC 2 and 4). |
hey! I tried it on both 3.7 and 3.8 firmware as I was wondering if the update caused it, but it didn't. There were no other special ESC settings! |
@Ricky-Millar thanks for the log. As far as I can see, everything is just looking normal. Hard to say what causes the problem you are seeing. I could not reproduce the issue with my F4 board here. |
Hey, having some strange behaviour which im not sure is bl_heli's fault but it seems to be at the moment.
Essentially, if I use bl_heli to even read my ESC, motor 2 on my quad will just stop working. no errors, it can still talk to bl_heli. but it won't spin, in betalight or bl_heli itself
If I unplug and replug the battery then I can happily spin up the motors in betaflight and it works all fine, no errors still.
It's real strange because I can close bl_heli and the quad is still effected, even though I haven't tried to change any settings on the ESC. I don't understand it at all but I have done it a bunch of times to try and confirm that it is happening and I don't just have a dodgy connection somewhere, but it keeps happening as soon as I open and use bl_heli
The text was updated successfully, but these errors were encountered: