Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MAVProxy sending invalid terrain data above 60N #709

Open
rmackay9 opened this issue Dec 2, 2019 · 3 comments
Open

MAVProxy sending invalid terrain data above 60N #709

rmackay9 opened this issue Dec 2, 2019 · 3 comments
Labels

Comments

@rmackay9
Copy link
Contributor

rmackay9 commented Dec 2, 2019

I think that MAVProxy is sending invalid terrain data to the vehicle for latitudes above 60N for which the ardupilot SRTM database has no data. This means that a user in finland (and many other places probably) could attempt to fly a terrain altitude mission and all would appear fine until the vehicle crashed into the ground.

This can be reproduced in SITL by doing the following:

  • edit the Tools/autotest/Locations.txt file and add finland as "62.23075, 25.6993,0,0"
  • ../Tools/autotest/sim_vehicle.py -L finland --map --console
  • create a short mission with a takeoff, waypoint (with an altitude of 10m AGL), RTL
  • fly the mission

The vehicle will fly the mission just as if it's a relative altitude. I.e. it will not climb over mountains.

Here is the issue on the vehicle side: ArduPilot/ardupilot#12923

@rmackay9 rmackay9 added the bug label Dec 2, 2019
@rmackay9
Copy link
Contributor Author

rmackay9 commented Dec 3, 2019

Just as a side note, Mission Planner (beta) has been fixed so that it no longer provides invalid altitudes if there is no SRTM data.

@Ryanf55
Copy link
Contributor

Ryanf55 commented May 8, 2024

Is this still an issue?

@rmackay9
Copy link
Contributor Author

rmackay9 commented May 8, 2024

@Ryanf55,

It should be fixed but we should test..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants