APM:Libraries
Classes | Macros | Variables
DataFlash_MAVLink.h File Reference
#include <AP_HAL/AP_HAL.h>
#include "DataFlash_Backend.h"
Include dependency graph for DataFlash_MAVLink.h:
This graph shows which files directly or indirectly include this file:

Go to the source code of this file.

Classes

class  DataFlash_MAVLink
 
struct  DataFlash_MAVLink::dm_block
 
struct  DataFlash_MAVLink::dm_block_queue
 
struct  DataFlash_MAVLink::_stats
 

Macros

#define DATAFLASH_MAVLINK_SUPPORT   1
 
#define DF_MAVLINK_DISABLE_INTERRUPTS   0
 

Variables

const AP_HAL::HALhal
 -*- tab-width: 4; Mode: C++; c-basic-offset: 4; indent-tabs-mode: nil -*- More...
 

Macro Definition Documentation

◆ DATAFLASH_MAVLINK_SUPPORT

#define DATAFLASH_MAVLINK_SUPPORT   1

Definition at line 8 of file DataFlash_MAVLink.h.

◆ DF_MAVLINK_DISABLE_INTERRUPTS

#define DF_MAVLINK_DISABLE_INTERRUPTS   0

Definition at line 18 of file DataFlash_MAVLink.h.

Variable Documentation

◆ hal

const AP_HAL::HAL& 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 14 of file AC_PID_test.cpp.