DataFlash_MAVLink.cpp File Reference

#include "DataFlash_MAVLink.h"
#include "LogStructure.h"
#include <GCS_MAVLink/GCS.h>

Include dependency graph for DataFlash_MAVLink.cpp:

Go to the source code of this file.

Macros
#define	REMOTE_LOG_DEBUGGING   0
#define	Debug(fmt, args ...)

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

Macro Definition Documentation

Debug

#define Debug	(		fmt,
			args ...
	)

Definition at line 17 of file DataFlash_MAVLink.cpp.

Referenced by DataFlash_MAVLink::handle_ack(), and DataFlash_MAVLink::periodic_1Hz().

REMOTE_LOG_DEBUGGING

#define REMOTE_LOG_DEBUGGING   0

Definition at line 11 of file DataFlash_MAVLink.cpp.

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.