Hi, I have MAMBA F722 + MAMBA F50 pro. Motors are T-Motor PACER P2208 kv1750



Recently I flashed ESC with 32.8 in BLHeliSuite32 and motors start stall. I tried to run motors from Betaflight but same problem.
I changed it back to 32.7 but still the same problem.

Before this flash motors worked.

Any ideas why its like that?

Thanks!

You mean they stall on the bench or mid flight?

Firmware should not cause motors to stall unless some settings have changed.

I have done 32.7–>32.8 on all me BLHeli32 ESC’s and so far not had any motor stalls.

(11-Feb-2022, 04:09 PM)kafie1980 Wrote: You mean they stall on the bench or mid flight?

Firmware should not cause motors to stall unless some settings have changed.

I have done 32.7–>32.8 on all me BLHeli32 ESC’s and so far not had any motor stalls.

On the bench. Here is some pic from BLHeli32

Here is link to the video how it looks.

https://drive.google.com/file/d/1pjPk0f0...sp=sharing

Your video is not public.

On the ESC try setting Motor timing to 23 deg and Demag compensation to Medium or High and see if this makes a difference.

Also check if you have any loose motor wires or connectors from FC to ESC.

Hope this link works.

There are two different firmware targets for the Mamba F50 PRO...

https://github.com/bitdump/BLHeli/tree/m...20testcode



It looks like you have the bottom "F50_PRO" version installed. It might be worth trying the top "F50PRO" version instead. Just one word of warning is that I think it's possible to brick the ESCs if you install the wrong firmware target on them, so keep that in mind because there might be an element of risk involved in trying that. But there is clearly a problem with the flashed firmware or the ESCs if everything was working fine before you started flashing any firmware to them, so you probably have nothing to lose. It's your call though.

(12-Feb-2022, 12:17 PM)SnowLeopardFPV Wrote: There are two different firmware targets for the Mamba F50 PRO...

https://github.com/bitdump/BLHeli/tree/m...20testcode


It looks like you have the bottom "F50_PRO" version installed. It might be worth trying the top "F50PRO" version instead. Just one word of warning is that I think it's possible to brick the ESCs if you install the wrong firmware target on them, so keep that in mind because there might be an element of risk involved in trying that. But there is clearly a problem with the flashed firmware or the ESCs if everything was working fine before you started flashing any firmware to them, so you probably have nothing to lose. It's your call though.

Thanks for the ideas.
Well it wont let me to chose that file only F50_PRO Rev32.8.3 and no other

---

You can manually download the HEX file you want to flash from the link I gave in my previous post, then press the "Ignore" button at the bottom of the Flash Assistant and manually browse / load the downloaded file, then flash it. You will get a warning message when you try to do it that way but it should let you flash the manually loaded file.

Maybe you are better off emailing Diatone support first before you risk bricking your ESCs to ask them what the BLHeli_32 firmware target is for your ESCs and also explain the issue you are having because they might know what is causing it (maybe an incorrect firmware target or some specific BLHeli_32 settings that need to be changed from defaults for that specific ESC board).

(12-Feb-2022, 04:03 PM)SnowLeopardFPV Wrote: You can manually download the HEX file you want to flash from the link I gave in my previous post, then press the "Ignore" button at the bottom of the Flash Assistant and manually browse / load the downloaded file, then flash it. You will get a warning message when you try to do it that way but it should let you flash the manually loaded file.

Maybe you are better off emailing Diatone support first before you risk bricking your ESCs to ask them what the BLHeli_32 firmware target is for your ESCs and also explain the issue you are having because they might know what is causing it (maybe an incorrect firmware target or some specific BLHeli_32 settings that need to be changed from defaults for that specific ESC board).

Thanks a lot for your help. I will try that and then see what they come back with.

(12-Feb-2022, 04:03 PM)SnowLeopardFPV Wrote: You can manually download the HEX file you want to flash from the link I gave in my previous post, then press the "Ignore" button at the bottom of the Flash Assistant and manually browse / load the downloaded file, then flash it. You will get a warning message when you try to do it that way but it should let you flash the manually loaded file.

Maybe you are better off emailing Diatone support first before you risk bricking your ESCs to ask them what the BLHeli_32 firmware target is for your ESCs and also explain the issue you are having because they might know what is causing it (maybe an incorrect firmware target or some specific BLHeli_32 settings that need to be changed from defaults for that specific ESC board).

The problem was that I  did set a battery protect in BLHeli_32. I took it off and it works.

Only now motors behave strange. When I speed up motors and lower the speed they seams to speed up by them self. I can even see in betaflight that they do that. I noticed this problem before this firmware update.

I completely missed the fact in post #3 that you'd changed the Low Voltage Protection value. I'm glad you managed to figure that out.

If you are testing the motors with props off on the bench then that speeding up by themselves behaviour is normal. Have a watch of the following video to understand why...



You just need to put some props on and take it outside for a proper test hover 

(14-Feb-2022, 08:57 PM)SnowLeopardFPV Wrote: I completely missed the fact in post #3 that you'd changed the Low Voltage Protection value. I'm glad you managed to figure that out.

If you are testing the motors with props off on the bench then that speeding up by themselves behaviour is normal. Have a watch of the following video to understand why...



You just need to put some props on and take it outside for a proper test hover 

Thanks, that's what I figured out as well. Need to wait for better weather to take it out for a spin.