You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/Terrain.md
+11-20Lines changed: 11 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,16 +21,20 @@ terrain data are unavailable or a read error occurs, the feature is automaticall
21
21
22
22
# SD Card Preparation
23
23
24
+
Use only quality SD cards from reputable brands. Note that some combinations of flight controllers and SD cards can cause issues,
25
+
so if you experience any problems, try a different card before troubleshooting further. Compatibility problems have been
26
+
observed especially with F4-based flight controllers.
27
+
24
28
For proper operation, the SD card must be prepared in advance. It is recommended to create a **partition with a maximum size
25
-
of 4 GB** and format it. Formatting should be done using the official
26
-
[**SD Memory Card Formatter**](https://www.sdcard.org/downloads/formatter/sd-memory-card-formatter-for-windows-download/) tool from the SD Association,
27
-
which ensures correct alignment and a compatible file system structure. Using this tool minimizes the risk of terrain data
28
-
read issues during flight and is considered the recommended method for preparing an SD card for iNav.
29
+
of 4 GB** and format it to FAT32.
29
30
30
31
# Data Generation and Copying
31
32
32
33
To generate elevation maps, use the terrain generator web tool available at https://terrain.ardupilot.org/
33
34
35
+
**Before copying any terrain data files, the SD card must be formatted. Always format the card before each new terrain data
36
+
installation to avoid file system errors.**
37
+
34
38
In iNav, **only 30 m resolution (SRTM1)** is currently supported, so this option must be selected during data generation.
35
39
The generated files are then copied to the SD card into the root directory structure.
36
40
@@ -45,10 +49,8 @@ SDCARD:\
45
49
├── N49E017.DAT
46
50
└── N50E016.DAT
47
51
```
48
-
Copying can be done via **iNav MSC (Mass Storage Class)**, but this method is very slow, so using an **external SD card reader**
49
-
is strongly recommended. Before copying the data, the file **`FREESPAC.E`** must be deleted from the root directory of the SD
50
-
card. iNav uses this file to track available disk space, and without deleting it, the card may appear to be full. After the
51
-
copying process is complete, iNav will automatically recreate this file on the next startup.
52
+
53
+
Copying can be done via **iNav MSC (Mass Storage Class)** is not recommended.
52
54
53
55
# Enabling and Displaying Terrain Data
54
56
@@ -70,15 +72,4 @@ them to display altitude above terrain.
70
72
Finally, it is **strongly recommended to use only high-quality, branded SD cards** from reputable manufacturers. The terrain
71
73
system is sensitive to SD card read speed and reliability, and low-quality or counterfeit cards may cause read errors,
72
74
display dropouts, or automatic disabling of the feature during flight. Using a quality SD card significantly improves the
73
-
stability and reliability of the terrain feature.
74
-
75
-
# TL;DR
76
-
77
-
-**H7/F4 flight controller** with SD card required
78
-
- Format SD card using [SD Memory Card Formatter](https://www.sdcard.org/downloads/formatter/sd-memory-card-formatter-for-windows-download/) (max 4 GB partition)
79
-
- Generate terrain data at https://terrain.ardupilot.org/ — select **SRTM1 (30 m)**
80
-
- Delete `FREESPAC.E` from SD card root before copying files to ROOT of SDCARD (use external card reader, not MSC)
81
-
- Enable via CLI: `set terrain_enabled = ON` + `save`
82
-
- Enable **Rangefinder distance** OSD element to see altitude above terrain
83
-
- ⚠️ Displayed value is **informational only** — not used for navigation or altitude control
0 commit comments