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

commander: fix takeoff and land CI test #15351

Merged
merged 1 commit into from
Jul 17, 2020
Merged

Conversation

julianoes
Copy link
Contributor

This fixes the takeoff and land CI test where we do a takeoff and land without RC connected.

In my opinion it does not make sense to go into RC lost failsafe if a datalink is still available.
Of course, this can be dangerous if someone has a companion computer connected which gets detected as "data link" but actually has no connection to the ground station.

This is required for the takeoff and land SITL test after #15316.

This fixes the takeoff and land CI test where we do a takeoff and land
without RC connected.

In my opinion it does not make sense to go into RC lost failsafe if
a datalink is still available.
Of course, this can be dangerous if someone has a companion computer
connected which gets detected as "data link" but actually has no
connection to the ground station.
@julianoes julianoes requested review from dagar and MaEtUgR July 16, 2020 12:08
@dagar
Copy link
Member

dagar commented Jul 16, 2020

This sounds right to me, if anything I'm wondering if this was intentionally not done in the first place.

@dagar
Copy link
Member

dagar commented Jul 17, 2020

I wanted to first lock down arming with manual control and data link (depending on configuration and mode), but it's not a small clean change. I'll merge this now and come back to that idea later.

@dagar dagar merged commit 9d97148 into master Jul 17, 2020
@dagar dagar deleted the pr-fix-loiter-rc-failsafe branch July 17, 2020 14:30
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.

2 participants