sskaug
sskaug
Great to hear that it runs well for you. We count installs when BLHeliSuite32 or the BLHeli_32 app validates the serial number upon code flashing. 32.95 installs are increasing, not...
Not sure exactly which code you have, but hopefully it is one of these: https://github.com/bitdump/BLHeli/tree/master/BLHeli_32%20ARM/Misc%20testcodes
No, the name must be an exact match. F4 MCUs were added to BLHeli_32 at the Rev32.8 level, and unfortunately are not supported for earlier code revs.
Cases where the ESCs reboots are most likely related to hardware and not firmware. Besides, 32.7 is not available for F4 MCUs.
Sorry to see your loss. By now we do have thousands of installs of 32.9 and the testcode equivalent of 32.8.3 with very few reports of problems. So most likely...
This is most likely not directly related to BLHeli_32. At least it should be investigated by the Betaflight team first.
Ok, so that particular fix was in Rev32.8.
We have never heard of any such generic issue, so you should probably contact your vendor about this.
Testcode with additional protection against unintentional spoolups is now posted here: https://github.com/bitdump/BLHeli/tree/master/BLHeli_32%20ARM/Dshot%20extended%20telemetry%20testcode
Do you also set the telemetry bit in these command frames?