-
Notifications
You must be signed in to change notification settings - Fork 18.6k
Warn if using BLHeli 32.9 or lower #29820
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
Comments
Is there anyway to update BLHeli32 now that the servers are down? I thought
not…..
IE did someone find a workaround?
…On Sat, Apr 19, 2025 at 16:42 Ryan ***@***.***> wrote:
Feature request
*Is your feature request related to a problem? Please describe.*
BLHeli 32.10 has fixed a major issue with unintentional motor spoolups.
I've seen multiple instances of spoolups, or disarming and the motors not
stopping becuase they detect the wrong protocol.
This is a major safety issue for anyone using BLHeli 32.9 or less.
*Describe the solution you'd like*
On bootup, ArduPilot can try to communicate with DSHOT to retrieve the
blheli version. If the version is not 32.10, a warning can be issued.
ArduPilot could the version and warn users that if they fly 32.9 or less,
they need to throw their ESC's away and replace them with something safer.
*Describe alternatives you've considered*
Not warning users their ESC's are dangerous.
*Platform*
[ ] All
[ ] AntennaTracker
[ ] Copter
[ ] Plane
[ ] Rover
[ ] Submarine
*Additional context*
bitdump/BLHeli#743 <bitdump/BLHeli#743>
https://github.com/bitdump/BLHeli/releases/tag/Rev32.10
image.png (view on web)
<https://github.com/user-attachments/assets/4cfe2e09-8d5d-4b20-b01b-b5f8f318269f>
—
Reply to this email directly, view it on GitHub
<#29820>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQQEX5NDV346VQV5HD53ASL22KYMXAVCNFSM6AAAAAB3O5PRLSVHI2DSMVQWIX3LMV43ASLTON2WKOZTGAYDMNRUG43DQOI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
*Ryanf55* created an issue (ArduPilot/ardupilot#29820)
<#29820>
Feature request
*Is your feature request related to a problem? Please describe.*
BLHeli 32.10 has fixed a major issue with unintentional motor spoolups.
I've seen multiple instances of spoolups, or disarming and the motors not
stopping becuase they detect the wrong protocol.
This is a major safety issue for anyone using BLHeli 32.9 or less.
*Describe the solution you'd like*
On bootup, ArduPilot can try to communicate with DSHOT to retrieve the
blheli version. If the version is not 32.10, a warning can be issued.
ArduPilot could the version and warn users that if they fly 32.9 or less,
they need to throw their ESC's away and replace them with something safer.
*Describe alternatives you've considered*
Not warning users their ESC's are dangerous.
*Platform*
[ ] All
[ ] AntennaTracker
[ ] Copter
[ ] Plane
[ ] Rover
[ ] Submarine
*Additional context*
bitdump/BLHeli#743 <bitdump/BLHeli#743>
https://github.com/bitdump/BLHeli/releases/tag/Rev32.10
image.png (view on web)
<https://github.com/user-attachments/assets/4cfe2e09-8d5d-4b20-b01b-b5f8f318269f>
—
Reply to this email directly, view it on GitHub
<#29820>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQQEX5NDV346VQV5HD53ASL22KYMXAVCNFSM6AAAAAB3O5PRLSVHI2DSMVQWIX3LMV43ASLTON2WKOZTGAYDMNRUG43DQOI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Nope. It's my understanding that it's unrecoverable. I saw a translated-chinese-forum that some people are trying to crack the server keys, but they haven't achieved it yet. |
All I can say is that I have never encountered this problem myself, despite having multiple 32.9 ESC's. I am not sure what the difference is. |
Until I can come up with a reproducible way to cause a spool up, I'm considering this on hold as far as a code implementation. |
Ping @Hwurzburg on the Wiki concept. |
Added wiki warning |
Feature request
Is your feature request related to a problem? Please describe.
BLHeli 32.10 has fixed a major issue with unintentional motor spoolups.
I've seen multiple instances of spoolups, or disarming and the motors not stopping because they detect the wrong protocol.
This is a major safety issue for anyone using BLHeli 32.9 or less. Multiple users have posted to BLHeli complaining of injuries with unintentional spoolups too.
Describe the solution you'd like
On bootup, ArduPilot can try to communicate with DSHOT to retrieve the blheli version. If the version is not 32.10, a warning can be issued. ArduPilot could request the version and warn users that if they fly 32.9 or less, they could consider to throw their ESC's away and replace them with something safer (like AM32), or advanced users can reflash them.
Describe alternatives you've considered
Not warning users their ESC's are dangerous. Vendors could recall ESC's, but they won't.
We could also warn in the wiki, but most people won't connect the configurator or know their version.
Platform
[ ] All
[ ] AntennaTracker
[ ] Copter
[ ] Plane
[ ] Rover
[ ] Submarine
Additional context
bitdump/BLHeli#743
https://github.com/bitdump/BLHeli/releases/tag/Rev32.10
The text was updated successfully, but these errors were encountered: