-
Notifications
You must be signed in to change notification settings - Fork 0
Ardu copter 3.2.1 #1
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
Open
Strroke21
wants to merge
254
commits into
Copter-4.2
Choose a base branch
from
ArduCopter-3.2.1
base: Copter-4.2
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
headers were not always being written
the new GPS driver only ever needs a non-blocking port
the EKF check works reliably but attempts to check the inertial nav for errors has not been successful. I could not find a way to reliably catch flyaways without also introducing false positives (and thus unwanted LANDings)
… used for control pass-through.
… constructor. To be used for flybar passthrough.
reference to rc_1, rc2 are replaced with constant updates during acro_run
fixes pull #1320 thanks Arthur!
this saves a tiny amount of time by removing the memory copy of a Vector3f
this allows magfailed status to show on console via SYS_STATUS health bits
Made more strict by requiring 50 consecutive iterations where the climb rate is below +- 40cm/s. Previously it was 50 cumulative. Removed check of failsafe.radio when clearing the land flag because it could result in the vehicle taking off if the user picked it up.
Simulated copter is flying too high and causing the land to timeout
this prevents a "jump loop" from causing a firmware lockup. Thanks to dellarb for reporting this!
Protect against the GCS sending multiple arming messages close together which disrupts the gyro calibration
The alt limit is instead enforced when the target is set using the set_alt_target_from_climb_rate function Also updated comments
No changes from AC3.2.1-rc2
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.