MOT_THST_EXPO setting from spreadsheet Ardupilot

Hello Friends
I am trying to adjust the MOT_THST_EXPO parameter for the h11 hobbywing motor using the motor thrust fit.excel found on this page.
I got the table information from Hobbywing website.
In the graph I calculated, Corrected thrust has the least difference with normalized thrust when MOT_THST_EXPO is 0.96 while the site explains that it should not be set higher than 0.8.
This graph corresponds to the value of 0.96:


This graph corresponds to the value of 0.8 :

This is my calculation file => Copy of ArduPilot Motor Thrust Fit - Google Sheets
Please check that my calculations are correct. @Leonardthall

I would not go over MOT_THST_EXPO,0.8
Make sure you also have:

MOT_PWM_MIN,1050
MOT_PWM_MAX,1950

The Hobbywing website has explained that MOT_PWM_MIN is 1100 and MOT_PWM_MAX is 1940 for H11 engine.
Untitled

Yes use that.
Some of the different models have the other range I gave.

Use the CAN connection if you are able to, instead of the old PWM/servo connections.

Can You explain Why we shouldn’t go beyond 0.8 even on such heavy Motors Like H11 ?!
I Read about it before from @Leonardthall but I Cant Find Why ?!

Hi @nrgs_barani,

Every time I use manufacture curves I get data I don’t believe. I have also never been able to get the same results myself. For example, the hobbywing data is below:
image

hobbywing H11M 54V (14S LiPo) 48*17.5"
Test Data : Expo : 1.1196 , Zero Thrust : 3460.8541 , Max_Thrust : 86283.8176
MOT_THST_EXPO : 1.1196
MOT_PWM_MIN : 1100
MOT_PWM_MAX : 1940
MOT_SPIN_MIN : 0.1
MOT_SPIN_MAX : 0.95

This matches an expo of over 1. That means the system is better than perfect as thrust increases.

My suspicion is that the Throttle(%) is not a ratio of PWM command but instead some non-linear relationship to PWM.

As to why I give the advice to not increase the expo over 0.8.

A perfect theoretical propeller provides thrust that is proportional to rpm. RPM is proportional to PWM with a relationship of kv * (pwm - MOT_PWM_MIN) / (MOT_PWM_MAX-MOT_PWM_MIN). This gives the perfect expo of 1.0.

A real system gets increasingly inefficient as the PWM increases. This reduces the expo below 1.0 because the slope of the upper end of the curve is reducing. Further we don’t start the range at zero thrust and again this reduces the expo. The end result is I have not seen measured data with an expo over about 0.8.

3 Likes

@Leonardthall Thank you very much for your reply :pray:

@Leonardthall,

Thanks very much for this. I also independently (and coincidentally) received thrust data from HobbyWing (in Japanese) and came to the same result of 1.1 which I knew could not be correct. Garbage in, garbage out I guess. Thanks for confirming this!

oh dear.

I have to use 0.99 for this drone using T-Motor MN2806 KV650 Hobbywing digital ESC (turned off Low RPM Power Protect) with Arducopter 4.2.x & 4.3.x.

Hello @Leonardthall

What would you suggest MOT_THST_EXPO for this propulsion system?

Currently I using the default value 0.65.

My formula in the spreadsheet and MissionPlanner Initial parameters gives 0.84 for 48" props, but I would definitely use maximum 0.8 as per Leonards previous recommendations.

1 Like

I am using it again on new UA design with MN2806 KV650.

By the way, I’ve recently updated the spreadsheet linked at the bottom of this wiki page (which is what we’re discussing above) to make it more robust.

I’ve also changed the colouring in the cells so that it’s slightly more clear which ones people should update (e.g. update the yellow cells)

1 Like

this MN2806 KV650 + 13x44 propeller + 4.5.4 drone, if I use the initial parameter

MOT_THST_EXPO,0.64
MOT_THST_HOVER,0.3066036

log MOT_THST_EXPO, 0.64.

If I use my previous experiment value

MOT_THST_EXPO,0.99
MOT_THST_HOVER,0.2258051

log MOT_THST_EXPO, 0.99

nothing change, drone weight, parameters, etc. except MOT_THST_EXPO
MOT_THST_HOVER turns weak under 0.64, in my view, Is it a normal expectation?

If the thrust expo has changed you should redo the MOT_SPIN_ARM and MOT_SPIN_MIN values in MissionPlanner motor test. The hover throttle will be different.
It’s more likely the hover thrust of 0.3 is more realistic.

thrust expo 0.99
hover throttle 0.23
PWM 1340 - 1400 approx

thrust expo 0.64
hover throttle 0.29
PWM 1490 - 1550 approx

With thrust expo 0.64 the attitude control looks better. There could be different conditions for the two flights, unsure.
There’s still some tuning to be done though, like an Autotune. Had you just done the VTOL Quicktune?

Noted.

No, only the thrust expo is different, or environmental wind conditions.
Maybe the flight profile is different.

Yes, the drone just completed a quick tune.

I am concerned thrust loss I experienced previously using default thrust expo with 4.2.3.

The thrust loss messages are a warning about a physical problem that has been detected. Say an ESC and motor is commanded to higher output for some manoeuvring, but the change in copter attitude does not match expectations (repeatedly) - so Arducopter is forced to assume that motor is not producing adequate thrust.
The thrust loss messages are not something you can induce by slight configuration changes.

if I remember correctly, that time was hovering and time-lapse flight endurance video recording with default thrust expo with v4.2.3.

MOT_THST_EXPO,0.66
MOT_THST_HOVER,0.3105014

0.99 or 0.64, the motor test spin arm, and minimum, there is no difference.

MOT_SPIN_ARM,0.03
MOT_SPIN_MIN,0.06
MOT_THST_EXPO,0.64


image