[Draft] {Sponsored by Intelliterra} Sets OPEN_DRONE_ID_LOCATION status to emergency on MAV_CMD #21959
+11
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Solved Problem
The GCS Operator is unable to manually set the OPEN_DRONE_ID_LOCATION status to emergency. This change adds a MAVLink command that I added in this PR here and sets the OPEN_DRONE_ID_LOCATION's status to emergency when the command is received.
This change also allows the "Declare Emergency" button in QGC to work.
According to the accepted MOC ASTM docs, specifically F358
This change is targeting specifically 7.7.1.1.
Context
Associated PRs can be found here:
mavlink/mavlink#2027
mavlink/qgroundcontrol#10770