paparazzi-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Paparazzi-devel] Reply to:"Re: small bug? (Reto B?ttner)"


From: Chris
Subject: [Paparazzi-devel] Reply to:"Re: small bug? (Reto B?ttner)"
Date: Mon, 18 Apr 2011 20:14:52 +0300
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8

Hi Reto.
Well i went up to 3000m and the glide angle was set exactly to "DESCENT_PITCH" which was far too much. I made some more tests and each time the glide angle was equal to whatever
the "DESCENT_PITCH"  was set to.
When i disabled the Aggressive mode everything was perfect and the glide angle was automatically set to 10 degrees which btw was the correct value for the intended glide slope. I implemented an emergency flight plan when the "fuel" level gets low which calls for a fast climb to an altitude calculated from the airplane's glide ratio and then a glide back home.
Obviously if i am 30km out the glide altitude can get as high as 5km.
(if this is possible as i check the climb rate vs the throttle setting)
I will see if i can solve the problem by increasing the "BLEND_START" alt error but i feel
that the aggressive mode should be disabled during gliding.
Anyway i found a workaround to this problem so my question was driven only from curiosity.
Here is my Aggressive section:
<section name="AGGRESSIVE"        prefix="AGR_">
<define name="BLEND_START"                value="30"/>
<define name="BLEND_END"                   value="10"/>
<define name="CLIMB_THROTTLE"          value="1.0"/>
<define name="CLIMB_PITCH"                  value="RadOfDeg(30)"/>
<define name="DESCENT_THROTTLE"      value="0.1"/>
<define name="DESCENT_PITCH"              value="RadOfDeg(-20)"/>
<define name="CLIMB_NAV_RATIO"           value="0.8"/>
<define name="DESCENT_NAV_RATIO"      value="1.0"/>
</section>

Chris




reply via email to

[Prev in Thread] Current Thread [Next in Thread]