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

Mavlink terrain protocol support #8449

Merged
merged 4 commits into from
Mar 1, 2020
Merged

Conversation

DonLakeFlyer
Copy link
Contributor

@DonLakeFlyer DonLakeFlyer commented Feb 29, 2020

  • Currently only works with ArduPilot. PX4 firmware side support should be coming soon as well.
  • Not yet supported by Patterns. That will come soon in another pull.
  • I've done a bunch of testing myself flying over terrain, but best be careful when using this since it's a big pile of new code.

If you are using a firmware which supports it. You will now see the additional "Terrain Frame" option for altitudes.
Screen Shot 2020-02-29 at 3 45 48 PM

Fly view has a new indicator which shows the progress of uploading terrain heights to the vehicle.
Screen Shot 2020-02-29 at 10 23 54 AM

When all the terrain info the vehicle asked for has been uploaded you'll see it say Done. Then after 30 seconds it will disappear to get out of the way. if the Vehicle asks for more terrain data it will come back.
Screen Shot 2020-02-29 at 10 35 02 AM

So create Plans using Terrain Frame, wait for the data to upload to the vehicle and you can fly the mission which follows terrain and do thing like Terrain based RTL and so forth.

@DonLakeFlyer
Copy link
Contributor Author

Screen Shot 2020-02-29 at 3 58 50 PM

Note that it's a WIP to figure out what to do with the two terrain options. The old one which stuffs AMSL value direction into the waypoint altitude. And the new one where terrain data is uploaded to the vehicle and the vehicle handles it. Leaning towards it being an either/or option. If the vehicle supports mavlink terrain protocol then only show Terrain Frame (likely named something else) and hide the other one. And the reverse if the vehicle does not support the terrain protocol.

Knowing whether there is vehicle support is driven by the MAV_PROTOCOL_CAPABILITY_TERRAIN capability bit.

@DonLakeFlyer DonLakeFlyer merged commit 7d87020 into mavlink:master Mar 1, 2020
@DonLakeFlyer DonLakeFlyer deleted the Terrain branch March 1, 2020 21:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant