Commit 0a4fe0e4 authored by PX4BuildBot's avatar PX4BuildBot

Update PX4 Firmware metadata Tue Jan 29 09:14:20 UTC 2019

parent a43b8489
......@@ -4524,13 +4524,6 @@ is 90 degrees. It should be lower than MPC_XY_CRUISE</short_desc>
<unit>m/s</unit>
<decimal>2</decimal>
</parameter>
<parameter default="0.0" name="MPC_IDLE_TKO" type="FLOAT">
<short_desc>Delay from idle state to arming state</short_desc>
<long_desc>For altitude controlled modes, the transition from idle to armed state is delayed by MPC_IDLE_TKO time to ensure that the propellers have reached idle speed before attempting a takeoff. This delay is particularly useful for vehicles with large propellers.</long_desc>
<min>0</min>
<max>10</max>
<unit>sec</unit>
</parameter>
<parameter default="20.0" name="MPC_JERK_MAX" type="FLOAT">
<short_desc>Maximum jerk limit</short_desc>
<long_desc>Limit the maximum jerk of the vehicle (how fast the acceleration can change). A lower value leads to smoother vehicle motions, but it also limits its agility (how fast it can change directions or break). Setting this to the maximum value essentially disables the limit. Note: this is only used when MPC_POS_MODE is set to a smoothing mode.</long_desc>
......@@ -4609,6 +4602,13 @@ Temporary Parameter to enable interface testing</short_desc>
<value code="3">Smooth position control (Velocity)</value>
</values>
</parameter>
<parameter default="0.0" name="MPC_SPOOLUP_TIME" type="FLOAT">
<short_desc>Enforced delay between arming and takeoff</short_desc>
<long_desc>For altitude controlled modes the time from arming the motors until a takeoff is possible gets forced to be at least MPC_SPOOLUP_TIME seconds to ensure the motors and propellers can sppol up and reach idle speed before getting commanded to spin faster. This delay is particularly useful for vehicles with slow motor spin-up e.g. because of large propellers.</long_desc>
<min>0</min>
<max>10</max>
<unit>s</unit>
</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>
......
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