BLHeli_S configuration for 2212 motors and 8" or 9" props

Hello,

Can someone please tell me the ideal settings to use for a slow fly cruiser with 8” (maybe will move to 9” soon) drone using the 2212 (1000 kv),15A ESCs and 3s battery? I mostly need info on Startup Power, Low RPM Power Protect, Demag Compensation. I have since changes the PPM Min throttle to 1000, Max to 2000 and Center to 1500.

Thank you very much!

Default. Low RPM Power Protect is required to be disabled on lower kV motors. 1000kV is probably OK to leave it on but I would probably disable it. I would disable Temperature Protection too.
But what I would do 1st is flash Bluejay firmware to the ESC’s and then you won’t be using that configurator.

Great minds think alike :slightly_smiling_face:
Seriously though BLHeli_S with Bluejay is the best thing going with respect to cost, good enough performance and ease of configuration.

1 Like

Flash them to Bluejay so you can use BDshot for filtering.

1 Like

Well, if you remember, I have been trying to flash Bluejay to them and I have had a little conversation with you.

I’ll detail what I’ve observed now:

I am using a 2.4.8 and have connected the ESCs to AUX ports. Reading the ESCs, the software only identifies a single ESC out of the 4 using the cleanflight interface for passthrough. The rest are “unknown”. Now, I have flashed the latest blheli_s firmware to each of them individually using an Arduino Nano and 4-way or some other interface (both interfaces worked). Using and ARduino identifies the firmware in the ESCs, but yeah the passthrough doesn’t work. I am thinking it is because those ESCs don’t have the bootloader flashed.

Why do you suggest disabling temp protection though? Also I saw a video by Chris Rosser on the “Ardupilot methodic configurator” github guide where he suggested going lower on Startup Power for bigger props. Like 15% for a 7”

Startup power is important on larger props with AM32. On bluejay, the defaults will work just fine.

Right I recall that. I would call those ESC’s duds and replace them.

LOL, okay… But for now, as long as everything works, I’ll try to use these. I might try to flash the bootloader using the pads underneath the ESCs later though :slight_smile:

Yea, fair enough. I suppose they will work fine with PWM.

Okay so the firmware is just as important here. I wonder why there’s a difference when all its trying to do is limit current

They work with Oneshot and DShot, upto DShot 600. I can even get motors spinning at 2% throttle on any DShot. With Oneshot, the minimum throttle for smooth spinning was 3%

Also, can you tell me why you suggested disabling temp protection? 140C is a very high temp and I don’t think its a good indication if I ever reach those temps

I never trusted that feature on BLHeli_S. I would spec, build, configure and tune so the ESC’s don’t get flaming hot which is determined during that process. But sure, leave it enabled if you like.

1 Like

Different firmwares have different ideology on how they limit current and how quickly they will manage it.

1 Like

Hey, I have no idea what happened. I just decided to give the cleanflight passthrough one more go. And guess what? All ESCs detected as if they have the bootloader! I don’t know what it is but it is possible previously my USB connection was dodgy. I flashed Bluejay now (48 kHz, v0.21). First the motors didn’t spin but I later figured out that DShot150 didn’t work. So changed to Dshot600 and it works. I was planning on using DShot150 as I didn’t want to overload my FMU. Is it because DShot150 may not support 48 khz? Also should I bump it to 96 khz as I’ve read that it will increase my flight time?

Secondly, what is a bummer is I cant seem to get BDShot. I tried enabling esc3 RPM from the tuning options that let you plot a graph but it says 0 (yes, I did enable BDMASK). Sorry for bringing this topic into this thread as it is not really about the title of the thread.

Anyway, I’m super happy now. Can’t believe my luck :laughing:

It doesn’t really work that way. Go here Dshot ESC’s and page down to the section about higher rates. Dshot600 is generally the most stable. I would leave it at 48kHz unless someone else suggests a reason for 96kHz. Well, I give you that advice and then I see I’m running 96Khz on a BLHeli_S ESC’s.

Post the parameter file. Not getting Bdshot is usually a configuration error.

I think I may have found the cause for three ESCs not being identified previously: I was using 4.6.2 earlier and I saw it had some issues with passthrough. I now have 4.6.3.

Here is an Oscar Liang article claiming 30%: How to Flash Bluejay ESC Firmware and Best Settings - Oscar Liang. I guess this is when you jump from 24 to 96 khz.

Here are my current params:

DSHot.param (16.5 KB)

Configure for Dshot600 and you didn’t configure the Bdmask. Disable debug. Disable BLH_MASK (not needed).

Doesn’t work. Is it possible the ESC hardware doesnt support BDShot?

Also what do you mean it doesn’t work that way? SInce DShot600 is twice the bandwidth of 300, the CPU will definitely have to work harder. I have even read this from multiple sources. I think I once even skimmed past a Joshua Bardwell video on this