Closed c3r63ru5 closed 2 years ago
Thanks, I can reproduce this.
It happens only with DShot-600 and was introduced by https://github.com/mathiasvr/bluejay/commit/1670ce2b1089c18e8502224be733e52c1276a81d which adjust timing for 24Mhz mode used by BB1 (L ESC) but also is used by BB2 (H ESC) when idle.
The update should improve telemetry protocol timing for BB1 but looks like it makes it worse for BB2 (idle only). I will look into if this can be improved more generally but otherwise will make BB2 targets revert back to old behaviour.
I have released v0.16 as a small fix for this.
Describe the bug
Flashed 0.15 48kHz onto a iFlight F7 Beast AIO and checked RPM telemetry in BF. With BLheli_M all looks normal, with BlueJay Error shows 100% until motors start spinning. When motors start spinning, error goes down to 0%.
Expected behavior
Even with motors not spinning, I would expect 0% telemetry errors.
Configuration: