-
Notifications
You must be signed in to change notification settings - Fork 16.8k
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
Move handling of parachute mission commands into AP_Mission_Commands #10385
Conversation
Thanks for this, makes a lot of sense. For support purposes though it's important that we know when the parachute has been deployed. I suspect this means that we need to move events into the dataflash log library? |
On Thu, 31 Jan 2019, Randy Mackay wrote:
For support purposes though it's important that we know when the parachute has been deployed. I suspect this means that we need to move events into the
dataflash log library?
tridge has already OK'd that IIRC.
|
3f87511
to
8cb5bca
Compare
@rmackay9 I've created a PR to move event logging up. |
bb0a537
to
8ab4d7f
Compare
@rmackay9 We now do events in the dataflash library, and parachute here takes advantage of that. |
Marked devcalltopic for attention |
redo - link in parachute instead |
8ab4d7f
to
eb8af80
Compare
I've changed the build to include AP_Parachute rather than using stub functions - as discussed on the devcall. |
eb8af80
to
81d482c
Compare
Tools: autotest: add test for triggering parachute via mavlink Tools: autotest: add Copter mission test for parachute release Tools: autotest: add Plane test for parachute deployment in auto
81d482c
to
3af2cb6
Compare
After discussion on the call I moved the text-message-sending into the library itself, and didn't log the parachute event if it's not enabled. |
Merged, thanks! |
Note that Copter logs will not get Event entries.