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

Mission Protocol - Clarifications on Geofence and Rally + Regular #95

Open
hamishwillee opened this issue Jul 30, 2018 · 0 comments
Open

Comments

@hamishwillee
Copy link
Collaborator

Mission Protocol covers regular missions in detail, and mentions how you set the two "new in MAVLink 2" types: - MAV_MISSION_TYPE_FENCE, MAV_MISSION_TYPE_RALLY

  1. For Rally Points, my assumption is:
    • A rally point is just like a flight plan mission except that you only use the MAV_CMD_NAV_RALLY_POINT as a command, and of course the mission_type
    • MAV_PROTOCOL_CAPABILITY_MISSION_RALLY should be set to specify support.

Is there anything else to them?

  1. For Geofence,
    • I assume that you can define a bunch of things about the fence using these messages: MAV_CMD_NAV_FENCE_RETURN_POINT, MAV_CMD_NAV_FENCE_POLYGON_VERTEX_INCLUSION, MAV_CMD_NAV_FENCE_CIRCLE_INCLUSION, MAV_CMD_NAV_FENCE_CIRCLE_INCLUSION, MAV_CMD_NAV_FENCE_CIRCLE_EXCLUSION
    • Also that you can turn it on and off at different points in the mission using MAV_CMD_DO_FENCE_ENABLE?
    • If you support the feature you enable MAV_PROTOCOL_CAPABILITY_MISSION_FENCE

Is that right? In PX4 can these be sent outside of missions?

How do you use FENCE_ACTION, FENCE_BREACH ?

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

No branches or pull requests

1 participant