Hi Everyone! I just wanted to pin a comment here following some discussions I've had regarding BLHeli32.8 over the last few hours. A few days ago a bug was discovered in the RPM reporting through Bidirectional Dshot on BLHeli32.8: github.com/bitdump/BLHeli/issues/546 This negatively affects RPM filtering and may cause motors to get hotter than on 32.7 There is a tested fix for it here: github.com/bitdump/BLHeli/tree/master/BLHeli_32%20ARM/Rev32.8.1%20testcode My recommendation: If you have been having issues or are concerned consider rolling back to 32.7 for now I'm sure an update will be released officially soon If you want to keep using 32.8 features and are comfortable flashing testcode through BLHeliSuite32 then that is also an option.
I can't repeat this often enough: You are a true gift to the FPV community. No procedural bla bla bullshit. Just academic and straight to the point knowledge with practical tips! I downloaded all your videos and put them on my field laptop so I can watch your videos when tuning my quads on the field. Thank you so much!
Gotta appreciate the fact that Mr. Rosser acknowledges that he doesn't know EVERYTHING and asks for folks to help translate BLHeli32 settings to other firmwares.
One video answers 3 years of questions. The original beta95x came with a 2 board AIO with blheli 32 ESC. The default ramp up power was 150. That thing would smoke motors if it bounced off the ground landing. Someone told me to turn it way down and it was fine after that just never knew why, now I do thankyou
Important DIY quad builder reference. Soldler-up, smoke check, plug in usb to check f/c (may as well calibrate the IMU/Accelerometer) and obtain passthrough to the esc, then WATCH THIS. Setting up your esc properly is much easier after watching this effective overview of BL-Heli_32. Others may do a deep dive into specific settings, but this video is the best overall explanation of this critical firmware that I have found! Thanks AGAIN Mr. Rosser!
Great video! This is how to be confident about no desync's and losing a long range quad. I've been playing with this on my long range quads for a couple of years. These are exactly the same settings I use on my ESC's for my long range quad. Only difference is I use reg 24khz PWM rate. Very clearly explained, nice work.
Great video! I'll be a Patreon member soon. Appreciate all the new videos. Your detailed explanation of everything is exactly what I've been looking for!
I love your videos. They're incredibly informative. My only suggestion is I wish you had described the function of the last three or four Blheli32 items versus only suggesting a desired setting.
Thanks again for this exelent explanation of blheli32 parameters , now I know a little but more about what these parameters are for and hope to play with them once I finished to apply all previous knowledge you thought me about filters an pid tuning
Thanks! I was really hoping you'd do an ESC video - after the fine tuning one that's the major topic that was still missing ;) I put the timing on 23° already - but learned quite a bit about ramp-up power and also didn't know that variable PWM is a linear curve but thought there is a switching point somewhere. Gonna make a few adjustments I guess!
What do you mean you can not figure out why?. BlheliS is a free, open source firmware, it doesn't use the larger stm32 chip and it came before Blheli32. As a result more older esc's tend to use it because it came out earlier, manufacturers don't have to shell out license fees so it is cheaper, and it uses a smaller chip.
Yes, I see the point but the price difference really justifies the performance downgrade and tuning limitations? Do you think that a few more dollars on top of a 500$ build would make that difference? Even on smaller quads the benfits are higher than the extra costs…in my humble opinion.
@@francescomaria8524 Yeah the price really does justify the performance. The licensing fees alone was one of the reasons why certain manufacturers don't run Blheli32, based on their volumes they produce. And I am not sure what you mean by tuning limitations - there are differences yes, but limitations no. Most pilots can't even tune properly let alone feel the difference between Blheli32 and BlheliS - you only know there is a difference because of the increased processing demands on betaflight which has slowly evolving to demand more and more processing power. Arguably some of the best flying esc behavior by 'feel' and pilot feedback was KISS - which ran on something close to BLheliS level of computation demands and it ran on a 1k loop for a lot longer than most people realize. And relative to smaller quads - the size limitations on 20x20 and whoop boards limit the processor dimensions and mosfets that can run Blheli32 - that is why if those boards have them they don't have as many peripherals.
Oh, the translation to other escs is really easy. First, read the code if available. Then, randomly change various settings and finally go back to the defaults after failing miserably.
Another great video Chris! I had a bad experience when flashing to BlHeli32 32.8. I tried it when it was first released on two quads. On one, my (2306) motors got a lot hotter than I'd like and on the other (1204) I was experiencing what seemed like arm dips or wobbles. Once back to 32.7 everything was back to normal.
Thanks for sharing! A couple of other pilots have reported strange behavior with 32.8 although I've never experienced hot motors. You 100% did the right thing to go back to a version that was working for you.
Mamy thanks Chris, very well explained. It's time to do some testing. My quad started acting up, I'm not certain if it's desync but I will try some of the steps you have described.
Great roundup of Blheli_32 features that I never understood haha. I feel a little smarter now. If you ever dive into Blheli S ESCs with Bluejay, that would be a great topic to cover.
This is super helpful. I have built a 9" quad and found the motors really overpowered on 3 or 4 S. I suspect it's actually because I haven't tuned the ESC (running multishot). Look forward to more experiments this week!
@@Thewiruz1 iNav doesn't have full DSHOT support as far as I can see. When I choose DSHOT and save, it reverts to multi. On Betaflight, DSHOT600 works fine with the same ESC.
@@unicron000I think it depends on the ESC, in my experience on a speedybee 50A ESC that supported DShot300/600 it had that behavior (returning to multishot) while on a Mamba 65A ESC Dshot worked with no issues
Very informative video, thank you ! :) Betaflight 4.3 provides the ability to reverse motors very easily. Which was already possible with SpeedyBee (and FalcoX). I gave a try to BLHeli32 32.8 with variable PWM, but like many others pilots, it was not satisfying : it gave untunable bounce back on snappy moves, so I rolled back to 32.7.
Thank you for explaining all this. I'm trying this approach on a 7" build: auto timing, 24-48khz, high demag, 20% ramp up on 2806.5 1800kv motors. Hope all goes well.
@@dennismatovich8411 good to know these esc settings worked. I flashed my esc with bluejay to 48khz and my 2807 motors freaked. On 24khz they are a charm
Rosser thanks you for your input into the comuminity and educating us with everynsingle ciseo you make . I bought your novas the guys on the track make fun of me for that but they dont understand science! Can you do is a favor Mr Rosser , could you please make a video on the best AM32 settings or an explanation the way you have here . I have all your equipment good sir i advocate for your frames "raceing" motors and stacks you recommend. I hope this reaches you well . Clear skies !
hi Chris. I have an old motor emax RS2205S. it ran ok with multishot, motor temp was manageable. couple or so years later, was used with dshot300(and 600). motors ran HOT! seen some info regarding heating motors, quick remedy was change from stock 24KHz to 48KHz + motor timing + demag. it solved the problem. newer esc fw gives problem to older motors w/c ran fine on multishot. *newer* motors ARE -sort of- designed for dshot and 24KHz ... just an info.
Very interesting. There is no obvious reason why the protocol used to communicate between ESC and FC would change motor performance. I'm glad you were able to solve the problem.
I took his day to watch many of ur videos because tomorrow is a hlday so i dont nd o go o bed early lol hak u for he explanation on blheli 32 I id njoy watching it
Excellent roundup of the topic! The only aspect you are missing out on is deadtime (although it's hard-coded in the firmware there are a lot of wrongly tagged BLHeliS ESCs out there)
Dead time is an interesting one to be sure. Not something I think people should be tuning though as if you get it wrong your ESC can get super hot and let the magic smoke out!
Great informative video 👍 Thanks Chris ☺️ Perhaps in the future you could run through BlHeli_S as there are still many quads old and new that run this firmware
thanks this was a big help i just took a crap flying drone and now it feels good on line of sight next test will be in fpv. i dont know what it is maybe im doing something wrong but i notice when i change to betaflight 4.3 i now have to go into blheli and tweek settings to get my drones flying good. befor i went to bf4.3 my new drones would fly good out of the box with just changing a few filters to make it perfect
I have a newb question regarding motor direction: Most set-up videos/guides say you should just swap two connectors on an ESC to change rotation direction. On this video you suggest that using the BLHeli set up is the only proper way to do this. Can you (or someone else here knowledgeable about the subject) clarify this for me? Thanks! BTW, loving this video and the in-depth explanations!
Hmm, that's one of the most tempting patreon promotions I've seen. Look forward to hearing about the racing frame and new carbon. A question; did that 2nd BLheli32 update just after they brought out the variable PWM function, fix the issue with the variable PWM? And.... Would flying 4s mean that you may need more 'ramp up power', seen as it's less voltage, or does the ESC auto adjust for less volts?
28:49 Except in the case of F4 equipped ESCs, leave temp protection set to off. If you turn it on the ESC will actively limit how much throttle the motors get no matter what you do. Not sure if that's a bug issue in current BLheli32 32.9 or not but something to keep note of.
thank you for this great video. But i have a question. Is the Motor timing a static value? If so, why electric motors do not use dynamic values? Wouldn't it be better if the Motor timings also behaved dynamically to the demanded rpm? Similar to variable ignition timing adjustment in an internal combustion engine?
The auto setting does this but many people prefer the extra torque and power they get from a more aggressive static value. It would be cool to have an adjustable auto setting where you could tweak the "aggressiveness" of the auto timing if that makes sense.
Yeah I damn sure had the exact opposite idea on a couple of those. Well I would respond to them in the exact opposite way that I should have apparently.
This was an exceptional explanation of this stuff. Thank you so much! One thing that is problematic for “recommended” settings based on the size of a quad is that the pilots who stand to gain the most from understanding these settings (top tier racers) the demands put on the Esc are likely an order of magnitude more extreme than the average freestyle or long range pilot. Dsyncs are very common in the first few seconds of flight for racing pilots. What would your recommendation be to combat that? Many of us have noticed that slightly raising ramp up power helps along with raising demag compensation. What are the negative effects of running higher demag compensation? How does the motor timing affect dsyncs? Do you have any additional recommendations for racing pilots who are spending the majority of a flight near 100% throttle?
So if you are a racer who is getting Desyncs in the first few seconds of a race that is likely because your motors are cool and your battery is full so that will deliver the maximum current into the motor windings and create the most noise for detecting the zero crossings on the inactive phase. A few things to check: 1. I've very recently learned BLHeli32.8 may have a susceptibility to desync so roll back to 32.7 2. Make sure your timings are quite aggressive 23-25 degrees that will be more robust against desync 3. Try 24 and 48kHz PWM. 24kHz gives more torque to control the motor but 48kHz may produce less noise so its hard to know which will be better for a given setup. 4. If get a desync from rapidly increasing the throttle try *reducing* ramp-up power slightly to 30% and see if that helps. 5. Demag to high as a last resort
@ChrisRosser Hi Chris, i just wanted to know what i need to tweek if i wish to have a good soft start.. What values should I approach if prop is more than a 7"
I just got a new iflight nazgul 5 V2 6S, everything is setup and it arms but none of the motors spin when I throttle.. Just random stutters here and there
Note: when using the latest betaflight configurator 10.8.0 and betaflight 4.3 builds, it IS possible to change motor direction in betaflight. I know because I did so. There is a special new dialogue on the motors tab specifically for this.
Hi Chris, Thanks so much for this content, it really helps explain things at this technical depth so that we're not just relying on "Betaflight" voodoo... question about ESC tuning, where does ESC tuning fit into the "progression" for tuning your Quad that you have shown in the other video? Should this be done before tuning PIDS and filters? After? Or is it separate entirely?
@@ChrisRosser There is an interesting discussion to be had about variable PWM (as well as just different frequencies) and frame resonance BTW. Also I'm pretty sure I remember it right and dev of AM32 firmware (opensource one for BLheli32 hardware) was quite critical about how variable PWM was implemented in BLHeli32.
Hi chris, is Rampup Power only a limit for accelerating the Propeller from 0 speed or is it also limiting the power for accelerating in normal flight from one rpm to an higher rpm? I used 12% for rcinpower 1506 4100kv to reduce the risk of smoking motor during turtelmode. I know it helps, but if it also affects the agility of the quad i have to think about that trade again.
I strongly doubt, that there are cw and ccw wound couls in the motor. I took several apart already and rewound some. Having north and south poles only originates from the polarity the 3 leads are connected to by the FET bridges. All windings are the same. Every third coil is wound from one wire, with three wires for the three groups.
If you check the bottom of a factory wound motor you will see that some of the coils are wound clockwise and some counterclockwise. The animation in the video shows how when the A winding is north the a winding is always south. That is accomplished by winding A CW and a CCW. You are correct that the FET bridge also changes the direction of current swapping north and south poles as shown in the animation.
Hi Chris! Great content, a question to you if you have time to answer; how is active breaking working? The reason I ask is because the FC only tell the esc what "power" the motors to have and not what rpm. How can the esc then decide on for how much to break or for how long? Best regards, Martin
Hi mr.Chris . i have a question . i use 3D Fly Mode rather than acro mode on my 5 inch quad. On that case, i must increase Motor RampUp up to 100% so the motor can rotate on Low Throtle otherwise it will desync. And like you said, it make the motors got more heat . Do i have any option to make the motor rotate on low throttle ? i like to sent you the bench video,if you have discord or instagram.
Thank you Chris your videos are very in-depth I have a question about rampup power you say 25-30% for 5in does that apply To all 5in including 6s with a 60a 4in1
My 2810 1500KV motors are ticking (like a lightning discharge) with 8060 2-blade props, not with 3-blade ones. 23 degree, 24-48kHz, 25% rampup. Does anyone have an idea to avoid this?
I've been having an issue with my legacy KISS setup, I've done lots of troubleshooting, and also lot's of part swaps. New motor, new flight controller, new ESC, swapping the wires between the FC and ESC, monitoring Rx link quality, etc. Sometimes I think both of my 4in1 ESCs have the same issue, but then I think it's the flight controller, because both of them exhibit the issue too. The problem seems to be with ESC #4 on the KISS 25A 4in1. No dead shorts exist through the mosfets. in fact the ESC functions fine unless it's accelerating quickly. It can hover, and I can do maneuvers on any axis, but if I jam the sticks, the quad spins out and falls out of the sky, and won't re-arm. Does anyone have experience diagnosing the kiss 25A 4 in 1 or KISS in general?
Hey Chris ... great video btw ... learned something today ^^ ... i very rarely do stuff with BL-s or BL-32 ^^ .. KISS user xd anyway ... the "Current Protection" and "Current Sens Cali" is only a thing if the "ESC for one Motor" got a Current shunt on it ... 99% of the 4in1's only got one A/D Current shunt on it .. and reports that value to the FC ... the ESC itelf doesn't do anything with it as far i know
Thanks, that's good to know. I've always used ESCs with an analogue current sensor so I typically don't have ESC telemetry enabled just bidirectional Dshot.
