Skip to content

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

Open
Ryanf55 opened this issue Apr 19, 2025 · 6 comments
Open

Warn if using BLHeli 32.9 or lower #29820

Ryanf55 opened this issue Apr 19, 2025 · 6 comments
Labels

Comments

@Ryanf55
Copy link
Collaborator

Ryanf55 commented Apr 19, 2025

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

Image

@Ryanf55 Ryanf55 added the Safety label Apr 19, 2025
@hendjoshsr71
Copy link
Member

hendjoshsr71 commented Apr 20, 2025 via email

@Ryanf55
Copy link
Collaborator Author

Ryanf55 commented Apr 20, 2025

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.

@andyp1per
Copy link
Collaborator

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.

@Ryanf55
Copy link
Collaborator Author

Ryanf55 commented Apr 20, 2025

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.
We could at least update the wiki.

@peterbarker
Copy link
Contributor

Ping @Hwurzburg on the Wiki concept.

@Hwurzburg
Copy link
Collaborator

Added wiki warning

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants