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
Environment: latest stable version of Ardupilot Copter, RadioMaster TX16S, Crossfire
A few days ago while conducting Autotune flights, Yaapu gave repeated verbal warnings about "No Terrain Data."
I'd never heard or seen that warning before - and could not find it in the logs. I have the TERRAIN_ENABLE parameter set to "1" - but there was no internet access at this flying site to get data.
I'm guessing that I can defeat this warning by setting TERRAIN_ENABLE to "0" - but it would be preferable to leave it at "1" so terrain data will be loaded when it's available.
I don't suspect that Yaapu has the ability to defeat this one specific warning. As a compromise, perhaps it could be issued only once instead of repeated about every 30 seconds.
I'd appreciate any comments or suggestions. Thank you!
The text was updated successfully, but these errors were encountered:
As you suspected that warning comes from ardupilot, teh audio warning is indeed misleading, it should be "terrain unhealthy" but I have no visibility over the reason, it comes from the terrain engine
Environment: latest stable version of Ardupilot Copter, RadioMaster TX16S, Crossfire
A few days ago while conducting Autotune flights, Yaapu gave repeated verbal warnings about "No Terrain Data."
I'd never heard or seen that warning before - and could not find it in the logs. I have the TERRAIN_ENABLE parameter set to "1" - but there was no internet access at this flying site to get data.
I'm guessing that I can defeat this warning by setting TERRAIN_ENABLE to "0" - but it would be preferable to leave it at "1" so terrain data will be loaded when it's available.
I don't suspect that Yaapu has the ability to defeat this one specific warning. As a compromise, perhaps it could be issued only once instead of repeated about every 30 seconds.
I'd appreciate any comments or suggestions. Thank you!
The text was updated successfully, but these errors were encountered: