mirror of
https://github.com/ArduPilot/ardupilot
synced 2025-01-09 09:28:31 -04:00
AP_Terrain: enable the terrain database by default
MissionPlanner now supports terrain data, and having terrain data in logs is useful even if users don't fly terrain missions
This commit is contained in:
parent
efa1d370fa
commit
642a07b6bd
@ -37,10 +37,10 @@ extern const AP_HAL::HAL& hal;
|
||||
// table of user settable parameters
|
||||
const AP_Param::GroupInfo AP_Terrain::var_info[] PROGMEM = {
|
||||
// @Param: ENABLE
|
||||
// @DisplayName: Terrain following enable
|
||||
// @Description: enable terrain following. This enables the vehicle storing a database of terrain data on the SD card. The terrain data is requested from the ground station as needed, and stored for later use on the SD card. To be useful the ground station must support TERRAIN_REQUEST messages and have access to a terrain database, such as the SRTM database.
|
||||
// @DisplayName: Terrain data enable
|
||||
// @Description: enable terrain data. This enables the vehicle storing a database of terrain data on the SD card. The terrain data is requested from the ground station as needed, and stored for later use on the SD card. To be useful the ground station must support TERRAIN_REQUEST messages and have access to a terrain database, such as the SRTM database.
|
||||
// @Values: 0:Disable,1:Enable
|
||||
AP_GROUPINFO("ENABLE", 0, AP_Terrain, enable, 0),
|
||||
AP_GROUPINFO("ENABLE", 0, AP_Terrain, enable, 1),
|
||||
|
||||
// @Param: SPACING
|
||||
// @DisplayName: Terrain grid spacing
|
||||
|
Loading…
Reference in New Issue
Block a user