Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Considerations:

  • Spin up to takeoff speed (Reduce current spikes/easier on ESC & motors)

  • Automated, but can be pilot overridden

  • Transition to hover at set height (3-5m) if no pilot input

  • If comms loss during takeoff transition to hover in place and if timeout passes transition to landing?

  • Uneven takeoff surface

The Plan:

  • First use Passby control to “spin up” motors to 20% throttle before takeoff, this reduces current spikes and increases motor longevity.

  • Next, add a takeoff state to path manager that calls the LandingTakeoffManager to figure out Path/speed targets

    • Either use waypoints or passby to set the throttle and move the drone.

Path Manager Component:

Call the LandingTakeoffManager to calculate the velocity at the current height. Feed that data into the waypoint manager

Landing Takeoff Manager:

Ideally calculate ascent speed using Gaussian Profile:

https://www.desmos.com/calculator/5pmkyu7h3t

To ascend to a set height (3-4m)

  • No labels