APM:Libraries
Classes | Functions | Variables
AP_Mission_test.cpp File Reference
#include <AP_HAL/AP_HAL.h>
#include <AP_Mission/AP_Mission.h>
Include dependency graph for AP_Mission_test.cpp:

Go to the source code of this file.

Classes

class  MissionTest
 

Functions

void setup (void)
 
void loop (void)
 
 AP_HAL_MAIN ()
 

Variables

const AP_HAL::HALhal = AP_HAL::get_HAL()
 -*- tab-width: 4; Mode: C++; c-basic-offset: 4; indent-tabs-mode: nil -*- More...
 
static MissionTest missiontest
 

Function Documentation

◆ AP_HAL_MAIN()

AP_HAL_MAIN ( )

Referenced by loop().

Here is the caller graph for this function:

◆ loop()

void loop ( void  )

Definition at line 1222 of file AP_Mission_test.cpp.

Here is the call graph for this function:

◆ setup()

void setup ( void  )

Definition at line 1218 of file AP_Mission_test.cpp.

Here is the call graph for this function:

Variable Documentation

◆ hal

const AP_HAL::HAL& hal = AP_HAL::get_HAL()

-*- tab-width: 4; Mode: C++; c-basic-offset: 4; indent-tabs-mode: nil -*-

The strategy for roll/pitch autotune is to give the user a AUTOTUNE flight mode which behaves just like FBWA, but does automatic tuning.

While the user is flying in AUTOTUNE the gains are saved every 10 seconds, but the saved gains are not the current gains, instead it saves the gains from 10s ago. When the user exits AUTOTUNE the gains are restored from 10s ago.

This allows the user to fly as much as they want in AUTOTUNE mode, and if they are ever unhappy they just exit the mode. If they stay in AUTOTUNE for more than 10s then their gains will have changed.

Using this approach users don't need any special switches, they just need to be able to enter and exit AUTOTUNE mode

Definition at line 9 of file AP_Mission_test.cpp.

◆ missiontest

MissionTest missiontest
static

Definition at line 53 of file AP_Mission_test.cpp.