sskaug
sskaug
There are some subtle changes between the revs, that will most often not be noticeable, but in extreme setups can make a difference.
Thank you for the info. Rev32.7 of TMOTOR_G0_01 now posted here: https://github.com/bitdump/BLHeli/tree/master/BLHeli_32%20ARM/Misc%20testcodes It's hard to say whether auto timing will prevent desyncs in your case. We have seen it to...
Click "Raw" on the code and then right click "save as" and save it in the BLHeli32_HexFiles folder of BLHeliSuite32. 
This sounds like it may be hardware related, you should probably contact your vendor.
Yes, the 32.9.9 testcode is not intended for multirotors. Have you tried the 32.9.3 testcode? It has some improvements for stalled motors. Some have also reported less risk of burning...
Sorry, at the moment we have no plans for adding seeeduino XIAO as an interface board
I have tried to reproduce this with a Rev32.9 ESC, without success. Motor spins down nicely undamped in both directions, both for regular 1-2ms input signal and sbus input signal....
The center value is given by the programmed (in BLHeliSuite32) center throttle value. And the deadband is about +-3% of total range around that value.
The 32bit source code is not published. The source code for 8bit MCUs is.
No, BLHeli_32 only operates with volume manufacturers and a small fee per unit. Check out the AM32 open source code: https://github.com/AlkaMotors/AM32-MultiRotor-ESC-firmware