Open vivian-zhou-skydio opened 1 month ago
Hi @hamishwillee sorry for the delay - just want to add you as a reviewer for this! :)
@vivian-zhou-skydio Thank you.
Your branch is not allowing me to push subedits. Can you please either allow that, or fetch my branch https://github.com/mavlink/mavlink-devguide/tree/skydio-add-parachute-protocol and cherry-pick these two changes into it:
pick 8832c63 prettier + add to sidebar
pick d76fd51 Reduce
What these do is cut back this document quite significantly. There is nothing wrong with it, except there is no point duplicating the docs in the messages - so this makes it much more high level.
Further, reading this has made me question some aspects of the naming in the mavlink PR, and the particular case of the drone trigger. Sorry to kick this off again, but that's what you get when you document stuff!
The first "flaw" in this is that it ignores the existing MAVLink command to enable auto triggering - https://mavlink.io/en/messages/common.html#MAV_CMD_DO_PARACHUTE
We need to clearly outline the way they interact, and what you've done here can't break the expectations on MAV_CMD_DO_PARACHUTE implementations.
adding parachute protocol microservice document and test suite