mirror of https://github.com/ArduPilot/ardupilot
c93dedc955
If you include airspeed, throttle or groundspeed changes in a mission then those should not be saved to EEPROM, as otherwise if you restart and re-fly the mission you will be starting with different parameters to the ones you used for the first flight. This is particularly important for setting the target airspeed when coming in for a landing. You typically set a low target, but if you fly again the next day I think it would be a real surprise to find that your loiter airspeed has then changed to the value from the landing part of your last mission. This one can be argued either way, but I think that not saving these changes is the more conservative choice, and better fits the 'principal of least surprise' |
||
|---|---|---|
| .. | ||
| APM_Config.h | ||
| APM_Config.h.reference | ||
| APM_Config_mavlink_hil.h | ||
| ArduPlane.pde | ||
| Attitude.pde | ||
| GCS.h | ||
| GCS_Mavlink.pde | ||
| Log.pde | ||
| Makefile | ||
| Parameters.h | ||
| Parameters.pde | ||
| climb_rate.pde | ||
| command description.txt | ||
| commands.pde | ||
| commands_logic.pde | ||
| commands_process.pde | ||
| config.h | ||
| control_modes.pde | ||
| createTags | ||
| defines.h | ||
| events.pde | ||
| failsafe.pde | ||
| geofence.pde | ||
| navigation.pde | ||
| planner.pde | ||
| radio.pde | ||
| sensors.pde | ||
| setup.pde | ||
| system.pde | ||
| test.pde | ||