Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Total Energy Control #251

Closed
wants to merge 3 commits into from

Conversation

dewagter
Copy link
Member

@dewagter dewagter commented Aug 3, 2012

pitch from airspeed, throttle from altitude, ... or maybe pitch from altitude and throttle from airspeed. Oh, no then we stall when the propulsion has a problem... then we do pitch from airspeed. Oh no, then the plane will dive into the ground during takeoff. Then we will takeoff with throttle from airspeed, then switch to pitch from airspeed for flight and landing. But then we must make sure we do not climb to hard to keep the speed within limits. Let's limit the MAX_CLIMB to 1m/s. Hmmm... Why can't it just do what it is supposed to do: climb and descend fast, fly at the correct airspeed all the time, not stall on motor problems and not crash on takeoff without any mode change?

Well now you can:

Total Energy Control for paparazzi-fixedwing with imu.

-throttle controls the lack of energy, and pitch the balance (airspeed/height)
-on total-energy saturation (e.g. engine failure or max climb) the energy balance lets loose of the altitude
-on takeoff the plane will not dive if the acceleration requirement is met
-you can climb with 100% and descend with 0% throttle
-full-speed climb loop (e.g. 100Hz in imu_aspirin) instead of old 4Hz

Test pilots are being searched.

@flixr
Copy link
Member

flixr commented Aug 3, 2012

I guess this should be merged into master, or do you really want to add new features like this to the stable v4.0 branch?

@gautierhattenberger
Copy link
Member

That's clearly not something that can go into the stable branch. I don't think the commit range can be changed now, so the pull request has to closed and reopened again.

@dewagter
Copy link
Member Author

dewagter commented Aug 4, 2012

Which is the next stabilisation branch? I thought it would be v4.1? I can change the merge request.

@dewagter dewagter closed this Aug 4, 2012
@flixr
Copy link
Member

flixr commented Oct 5, 2012

Merged into v4.1 for the next intermediate release.

@dewagter
Copy link
Member Author

update: save gains: 4268f05

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants