sskaug
sskaug
This is a really cool idea. When bidirectional dshot was defined, I advocated to also add codes for temperature, voltage, current etc, but the interest at that point was low....
BLHeli_32 implements the KISS compatible telemetry, where temperature is encoded as an unsigned byte. So negative temperatures are clipped to zero.
@damosvil, great that you are keeping track of a spec. We have started coding an implementation. I strongly disagree to remove current. Just for a statistics glimpse - out of...
@damosvil - great that you will include current. A range from 0-255A should be the best choice for an available byte of data.
@damosvil We now have an initial implementation ready for BLHeli_32. Please let us know which ESC code (the name of the firmware as shown in BLHeliSuite32) you would like to...
Testcode now posted here: https://github.com/bitdump/BLHeli/tree/master/BLHeli_32%20ARM/Dshot%20extended%20telemetry%20testcode
For BLHeli_32 there is no significant quantization of erpm period. And the accuracy of the averaging calculation is also good. What is left, is the accuracy of the internal RC...
For erpm period, the transmitted quantization is of course 1us. The internal is generally smaller, normally by the MCU clock frequency. But some MCUs only have 16bit timers, so for...
Sorry, typo, I meant 14pole motor. Then erpm is 14/2 times mechanical rpm.
No. The 475us is the number that is measured in BLHeli_32 (with the very fine MCU clock quantization). And then it is being sent back to the FC quantized to...