just a question. The other day I was looking at blheli settings and noticed my esc's came up "not in sync" , 

motor 1 ppm min throttle        1.024 max was 1.824
Motor 2 ppm min throttle        1.024 max was 1.816
Motor 3 ppm min throttle        1.024 max was 1.820
Motor 4 ppm min throttle        1.020 max was 1.816

now I have always used Clean Flight Config to calibrate my esc's 1000-2000 then raised and lowered my Min/Max which ended up being 1040-1950. Since it has been raining for the past several days, I decided to update my esc's to blheli 14.5 and BetaFlight/LUX_RACE 2.6.2, that was when I saw my esc's didnt match.  my question should I still continue the esc's calibrate through CFC or use blheli suite ?  

Thanks in advance

I may well do it the long winded way, but have been doing it this way for ages and always works well for me.

I set up min throttle and max throttle in CF first, then do esc cal in CF, then I go into BLHeli suite and make note of all the esc's min and max.

If 3 are like 1024 and 1980 and 1 is at 1020 and 1960 for example I just make sure all 4 esc's in blheli are matched, so I adjust the lower one to match the others and save and exit.

(04-May-2016, 03:17 AM)BigglesFPV Wrote: I may well do it the long winded way, but have been doing it this way for ages and always works well for me.

I set up min throttle and max throttle in CF first, then do esc cal in CF, then I go into BLHeli suite and make note of all the esc's min and max.

If 3 are like 1024 and 1980 and 1 is at 1020 and 1960 for example I just make sure all 4 esc's in blheli are matched, so I adjust the lower one to match the others and save and exit.

Thanks Biggles, Im going to check that now, I was just curious, with the ability to use the FC to do this is great. So I have been flying with out of sync esc's for a while!

I think throttle calibration takes into consideration the possible inconsistencies between the hardware components on the escs. I know some are comfortable changing the values in blheli after calibration, but this has always had me sceptical. I would rather reduce max_throttle to match the lowest max rate you see in blheli. I guess I ask myself why blheli decided upon different values, then ask myself again if I am smarter than the software

(04-May-2016, 04:03 AM)Bandook Wrote: I think throttle calibration takes into consideration the possible inconsistencies between the hardware components on the escs. I know some are comfortable changing the values in blheli after calibration, but this has always had me sceptical. I would rather reduce max_throttle to match the lowest max rate you see in blheli. I guess I ask myself why blheli decided upon different values, then ask myself again if I am smarter than the software

Well after countless calibrations , I am no more smarter then last night. I tried your way Biggles and everytime I went to see what my motors spin at and 2 and 3 motors spin 1021 while 1 and 4 spun at 1017. Then I re flashed firmware and recalibrated. Spun my motors 2 and 3 1021 , one and 4 1021.I didnt even look in blheli, I don't want to know .   But I have a feeling they might be different settings in blheli

(04-May-2016, 04:03 AM)Bandook Wrote: I think throttle calibration takes into consideration the possible inconsistencies between the hardware components on the escs. I know some are comfortable changing the values in blheli after calibration, but this has always had me sceptical. I would rather reduce max_throttle to match the lowest max rate you see in blheli. I guess I ask myself why blheli decided upon different values, then ask myself again if I am smarter than the software

Joshua Bardwell in one of his recent videos about blheli settings mentioned about throttle deadband that ESCs have after callibration. He stated that it is a good idea to drop max throttle in FC firmware to avoid FC pushing into it.

(04-May-2016, 05:35 PM)Konrad Stepanajtys Wrote: Joshua Bardwell in one of his recent videos about blheli settings mentioned about throttle deadband that ESCs have after callibration. He stated that it is a good idea to drop max throttle in FC firmware to avoid FC pushing into it.

That's what I was saying. I have to do that now on blheli 14.5 and multishot, but have never read that its a good idea to change ESC settings in blheli after calibrating. Otherwise, what's the point of calibrating?

(04-May-2016, 07:32 PM)Bandook Wrote: That's what I was saying. I have to do that now on blheli 14.5 and multishot, but have never read that its a good idea to change ESC settings in blheli after calibrating. Otherwise, what's the point of calibrating?

You were saying that You *match* FC max throttle with blheli. Joshua claims that there is always a deadband before blheli max throttle (whatever the setting is) and advises to set it even lower in the FC. I tried it on one of my quads and indeed, the motor seems to stop accelerating before reaching max.

This is the video I'm talking about:

(04-May-2016, 08:27 PM)Konrad Stepanajtys Wrote: You were saying that You *match* FC max throttle with blheli. Joshua claims that there is always a deadband before blheli max throttle (whatever the setting is) and advises to set it even lower in the FC. I tried it on one of my quads and indeed, the motor seems to stop accelerating before reaching max.

This is the video I'm talking about:

thanks guys for the video , I must of have missed this episode. A few throttle punches in between rain drops and it looked and felt good.

(04-May-2016, 08:27 PM)Konrad Stepanajtys Wrote: You were saying that You *match* FC max throttle with blheli. Joshua claims that there is always a deadband before blheli max throttle (whatever the setting is) and advises to set it even lower in the FC. I tried it on one of my quads and indeed, the motor seems to stop accelerating before reaching max.

This is the video I'm talking about:

The point I was trying to make was that I don't believe changing values in blheli is a good idea. That's why I said "I would rather" match the max pwm value in blheli than change the blheli settings to be equal between escs. I'm a big proponent of calibrating max values as Joshua has described, and have been doing it even before he released his video due to the discussion in the Betaflight thread. Fly4props was asking if he should mess with the blheli values after calibrating in cleanflight, I say no. If anyone thinks otherwise I'd like to hear their reasoning.

the weather finally broke and I got some flying in! I followed Joshua's video and your advice, just amazing now that everything calibrated right. Thanks!

(07-May-2016, 05:21 AM)Bandook Wrote: The point I was trying to make was that I don't believe changing values in blheli is a good idea. That's why I said "I would rather" match the max pwm value in blheli than change the blheli settings to be equal between escs. I'm a big proponent of calibrating max values as Joshua has described, and have been doing it even before he released his video due to the discussion in the Betaflight thread. Fly4props was asking if he should mess with the blheli values after calibrating in cleanflight, I say no. If anyone thinks otherwise I'd like to hear their reasoning.

I see Your point, but consider this - when I first got my littlebees, I couldn't calibrate them (naze rev6 issue and no knowledge to solve the problem then), so I experimented and set throttle max manually to 1996 on all ESCs. It flew fine

While that doesn't really prove anything and is no reason to do it this or the other way, we should consider that whether it's set by CF or manually may not have so much impact in flight. (EDIT: but please tell me if You think otherwise)

But maybe I'll test it - looks like my left front motor pushes a tiny bit harder than the right. If the issue is in matching after callibration, leaving it untouched should solve it.