-
Notifications
You must be signed in to change notification settings - Fork 22
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
Add BLHeli_32 ESC telemetry support #122
Comments
I added some code in version 2.11.8 (in test branch on github) in order to process blHeli frames (based on the doc you provided). I did not tested the code. |
I put 2.11.10 on github. At this stage, I do not plan to combine 2 data into one telemetry fields. It is a quite big change and should not be valid for other protocols. |
That did it - thanks.
You are right, the ESC sends 100rpm values. I assume EdgeTx multiplies the values internally when the sensor IDs I mentioned above are used. I get plausible values when I enter "7" for Blades/Poles for a 14-pole motor and a multiplier of "60" (although I don't understand the "60" because I want to stick with minutes as the basis).
I understand, thanks for clarifying.
The % seem to be 100 :-(
This is a real data logging from BLHeli (HTerm), last byte per line is the checksum: Frank |
It seems that there are quite many frame errors. |
Ok, I got it! I had 1k in series with BlHeli Tx from the beginning, that causes the problem.
valid Blheli frame: 46100 21 4 fc 0 4 0 1a 0 0 b0 Thank you very much for your efforts. Tomorrow I want to test with iBus. Good night |
Thanks for the feedback. |
I hope it is now fixed in 2.11.12 version. |
It is! Thank you. |
Hello!
I would be very happy if BlHeli_32 telemetry could be implemented. Even if this would make my own converter ( https://www.franksteinberg.de/BLHeliTelemetryFeeder.html ) more or less superfluous. BlHeli_32 ESCs are cheap and widely available. In the meantime, the first models with BEC for fixed-wing airplanes are also on the market.
The protocol is very simple and documented here:
http://ultraesc.de/downloads/KISS_telemetry_protocol.pdf
Other than described there, the ESCs can be configured to auto-telemetry since version 32.6, so that only reception via one line is necessary. Since firmware 32.8 BlHeli can also output FrSky S.Port directly, but S.Port only and not for all ESCs (not every cpu used, can output the inverted signal). Auto-telemetry (Kiss) in uninverted and works always.
Regards
Frank
The text was updated successfully, but these errors were encountered: