-
Notifications
You must be signed in to change notification settings - Fork 0
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
AP_ICEngine: don't allow engine run with safety on #118
AP_ICEngine: don't allow engine run with safety on #118
Conversation
Testing on PMU test unit: (Test by sending the crank signal from joystick) :
|
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.
Logic looks correct to me. If the test results are confirmed by @LachlanConn then I am good.
allow_throttle = ice->allow_throttle_disarmed(); | ||
} | ||
} | ||
request_was_sent = (allow_throttle) ? send_target_values(new_throttle) : false; |
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.
why this is set to false on failure and not calling the function which will set the throttle 0 like in master.
As I am not sure if calling send_target_values(0) could have any other impact
if (allow_throttle) {
request_was_sent = send_target_values(new_throttle);
} else {
request_was_sent = send_target_values(0);
}
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.
Agreed,
Reverted it back to original, since we do not have more time to test it fully
28c56b6
to
f67aaee
Compare
Cherry-pick source:
Cherry-pick was not sufficient, since the code has changed since 4.3.25. This code is tested after changes.