Commit 7e616472 authored by PX4BuildBot's avatar PX4BuildBot Committed by Daniel Agar

Update PX4 Firmware metadata Tue Oct 9 14:49:36 UTC 2018

parent defdcdc4
......@@ -1812,7 +1812,7 @@ This is the ratio of static pressure error to dynamic pressure generated by a wi
</parameter>
<parameter default="0.0" name="FW_DTRIM_P_VMAX" type="FLOAT">
<short_desc>Pitch trim increment at maximum airspeed</short_desc>
<long_desc>This increment is added to TRIM_PITCH when airspeed is FW_AIRSP_MAX.</long_desc>
<long_desc>This increment is added to TRIM_PITCH when airspeed is FW_AIRSPD_MAX.</long_desc>
<min>-0.25</min>
<max>0.25</max>
<decimal>2</decimal>
......@@ -1836,7 +1836,7 @@ This is the ratio of static pressure error to dynamic pressure generated by a wi
</parameter>
<parameter default="0.0" name="FW_DTRIM_R_VMAX" type="FLOAT">
<short_desc>Roll trim increment at maximum airspeed</short_desc>
<long_desc>This increment is added to TRIM_ROLL when airspeed is FW_AIRSP_MAX.</long_desc>
<long_desc>This increment is added to TRIM_ROLL when airspeed is FW_AIRSPD_MAX.</long_desc>
<min>-0.25</min>
<max>0.25</max>
<decimal>2</decimal>
......@@ -1852,7 +1852,7 @@ This is the ratio of static pressure error to dynamic pressure generated by a wi
</parameter>
<parameter default="0.0" name="FW_DTRIM_Y_VMAX" type="FLOAT">
<short_desc>Yaw trim increment at maximum airspeed</short_desc>
<long_desc>This increment is added to TRIM_YAW when airspeed is FW_AIRSP_MAX.</long_desc>
<long_desc>This increment is added to TRIM_YAW when airspeed is FW_AIRSPD_MAX.</long_desc>
<min>-0.25</min>
<max>0.25</max>
<decimal>2</decimal>
......@@ -3113,13 +3113,6 @@ Value 0 turns the functionality off</short_desc>
<unit>deg/s</unit>
<decimal>1</decimal>
</parameter>
<parameter default="0.1" name="LNDMC_THR_RANGE" type="FLOAT">
<short_desc>Multicopter sub-hover throttle scaling</short_desc>
<long_desc>The range between throttle_min and throttle_hover is scaled by this parameter to define how close to minimum throttle the current throttle value needs to be in order to get accepted as landed.</long_desc>
<min>0.05</min>
<max>0.5</max>
<decimal>2</decimal>
</parameter>
<parameter default="1.5" name="LNDMC_XY_VEL_MAX" type="FLOAT">
<short_desc>Multicopter max horizontal velocity</short_desc>
<long_desc>Maximum horizontal velocity allowed in the landed state (m/s)</long_desc>
......@@ -3516,7 +3509,6 @@ Used to calculate increased terrain random walk nosie due to movement</short_des
<value code="3">OSD</value>
<value code="4">Magic</value>
<value code="5">Config</value>
<value code="6">Iridium</value>
<value code="7">Minimal</value>
</values>
</parameter>
......@@ -3559,7 +3551,6 @@ Used to calculate increased terrain random walk nosie due to movement</short_des
<value code="3">OSD</value>
<value code="4">Magic</value>
<value code="5">Config</value>
<value code="6">Iridium</value>
<value code="7">Minimal</value>
</values>
</parameter>
......@@ -3602,7 +3593,6 @@ Used to calculate increased terrain random walk nosie due to movement</short_des
<value code="3">OSD</value>
<value code="4">Magic</value>
<value code="5">Config</value>
<value code="6">Iridium</value>
<value code="7">Minimal</value>
</values>
</parameter>
......@@ -4535,15 +4525,6 @@ towards MPC_ACC_HOR_MAX/MPC_ACC_UP_MAX with jerk limit</short_desc>
<unit>m/s</unit>
<decimal>1</decimal>
</parameter>
<parameter default="1.0" name="MPC_MANTHR_MAX" type="FLOAT">
<short_desc>Maximum manual thrust</short_desc>
<long_desc>Limit max allowed thrust for Manual mode.</long_desc>
<min>0.0</min>
<max>1.0</max>
<unit>norm</unit>
<decimal>2</decimal>
<increment>0.01</increment>
</parameter>
<parameter default="0.08" name="MPC_MANTHR_MIN" type="FLOAT">
<short_desc>Minimum manual thrust</short_desc>
<long_desc>Minimum vertical thrust. It's recommended to set it &gt; 0 to avoid free fall with zero thrust. With MC_AIRMODE set to 1, this can safely be set to 0.</long_desc>
......@@ -4583,10 +4564,18 @@ Temporary Parameter to enable interface testing</short_desc>
<value code="2">Sport position control</value>
</values>
</parameter>
<parameter default="0" name="MPC_THR_CURVE" type="INT32">
<short_desc>Thrust curve in Manual Mode</short_desc>
<long_desc>This parameter defines how the throttle stick input is mapped to commanded thrust in Manual/Stabilized flight mode. In case the default is used ('Rescale to hover thrust'), the stick input is linearly rescaled, such that a centered stick corresponds to the hover throttle (see MPC_THR_HOVER). Select 'No Rescale' to directly map the stick 1:1 to the output. This can be useful in case the hover thrust is very low and the default would lead to too much distortion (e.g. if hover thrust is set to 20%, 80% of the upper thrust range is squeezed into the upper half of the stick range). Note: in case MPC_THR_HOVER is set to 50%, the modes 0 and 1 are the same.</long_desc>
<values>
<value code="0">Rescale to hover thrust</value>
<value code="1">No Rescale</value>
</values>
</parameter>
<parameter default="0.5" name="MPC_THR_HOVER" type="FLOAT">
<short_desc>Hover thrust</short_desc>
<long_desc>Vertical thrust required to hover. This value is mapped to center stick for manual throttle control. With this value set to the thrust required to hover, transition from manual to ALTCTL mode while hovering will occur with the throttle stick near center, which is then interpreted as (near) zero demand for vertical speed.</long_desc>
<min>0.2</min>
<long_desc>Vertical thrust required to hover. This value is mapped to center stick for manual throttle control. With this value set to the thrust required to hover, transition from manual to Altitude or Position mode while hovering will occur with the throttle stick near center, which is then interpreted as (near) zero demand for vertical speed. This parameter is also important for the landing detection to work correctly.</long_desc>
<min>0.1</min>
<max>0.8</max>
<unit>norm</unit>
<decimal>2</decimal>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment