-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
AC_Autotune: Clean up Multi Variables and non functional changes #27370
AC_Autotune: Clean up Multi Variables and non functional changes #27370
Conversation
185332a
to
62b61bb
Compare
62b61bb
to
36c3f3a
Compare
36c3f3a
to
17c9baf
Compare
float start_angle; // start angle | ||
float start_rate; // start rate - parent and multi | ||
float rate_max; // maximum rate variable - parent and multi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
somewhat surprisingly AC_AutoTune_Heli also defines a "rate_max" variable but it is a parameter. I'm slightly surprised that the compiler didn't catch this "shadowing" but in any case it's good to get rid of it.
I think @bnsgeyer should confirm that Heli autotune seems to work OK
17c9baf
to
04a0bd0
Compare
Issue introduced in ArduPilot#27370 and partially fixed in ArduPilot#27762, though evidently not properly tested. Failing to track the maximum can result in a dangerously low value being calculated and the vehicle being unflyable. Make the variable a reference so that the maximum value is preserved between function calls.
Issue introduced in ArduPilot#27370 and partially fixed in ArduPilot#27762, though evidently not properly tested. Failing to track the maximum can result in dangerously low values being calculated for `ATC_ACCEL_[RPY]_MAX` and the vehicle becoming unflyable. Make the variable a reference so that the maximum value is preserved between function calls.
Issue introduced in #27370 and partially fixed in #27762, though evidently not properly tested. Failing to track the maximum can result in dangerously low values being calculated for `ATC_ACCEL_[RPY]_MAX` and the vehicle becoming unflyable. Make the variable a reference so that the maximum value is preserved between function calls.
Issue introduced in ArduPilot#27370 and partially fixed in ArduPilot#27762, though evidently not properly tested. Failing to track the maximum can result in dangerously low values being calculated for `ATC_ACCEL_[RPY]_MAX` and the vehicle becoming unflyable. Make the variable a reference so that the maximum value is preserved between function calls.
Issue introduced in ArduPilot#27370 and partially fixed in ArduPilot#27762, though evidently not properly tested. Failing to track the maximum can result in dangerously low values being calculated for `ATC_ACCEL_[RPY]_MAX` and the vehicle becoming unflyable. Make the variable a reference so that the maximum value is preserved between function calls.
Issue introduced in ArduPilot#27370 and partially fixed in ArduPilot#27762, though evidently not properly tested. Failing to track the maximum can result in dangerously low values being calculated for `ATC_ACCEL_[RPY]_MAX` and the vehicle becoming unflyable. Make the variable a reference so that the maximum value is preserved between function calls.
Issue introduced in #27370 and partially fixed in #27762, though evidently not properly tested. Failing to track the maximum can result in dangerously low values being calculated for `ATC_ACCEL_[RPY]_MAX` and the vehicle becoming unflyable. Make the variable a reference so that the maximum value is preserved between function calls.
Issue introduced in ArduPilot#27370 and partially fixed in ArduPilot#27762, though evidently not properly tested. Failing to track the maximum can result in dangerously low values being calculated for `ATC_ACCEL_[RPY]_MAX` and the vehicle becoming unflyable. Make the variable a reference so that the maximum value is preserved between function calls.
Issue introduced in ArduPilot#27370 and partially fixed in ArduPilot#27762, though evidently not properly tested. Failing to track the maximum can result in dangerously low values being calculated for `ATC_ACCEL_[RPY]_MAX` and the vehicle becoming unflyable. Make the variable a reference so that the maximum value is preserved between function calls.
I have moved the multi only variable declaration variables into the AC_AutoTune_Multi.h.
I removed the "f" from the floats.
I simplified a couple functions.
All these changes should be non-functional.
I am a little disgusted by some of the structures that I made here. This still has some work to do before it could be considered "clean".