-
-
Notifications
You must be signed in to change notification settings - Fork 354
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
fix(AFHDS3): V0 ibus option and failsafe malfunction #3793
Conversation
@pfeerick I think this is good for merge, for now. There are some historical problem about V0 receivers and need more time for Flysky to resolve in their TX firmware first. |
Sounds good to me... if there are no further concerns from @raphaelcoeffic @gagarinlg I'll review and try this shortly. |
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.
Tested on FTr12B w/ EL18, both iBUS IN and failsafe settings now runtime configurable rather than bind time (or perhaps not at all in some instances).
I think line 924 is wrong (compiler complains).
should probably be assignment not comparison.
|
* Fixed failsafe function and sync output of V0 version * Make the code more readable. Co-authored-by: Xy201207 <yaoxu@flysky.com>
@richardclli I haven't pushed the commit for this on the 2.9 branch yet, so can make that change before pushing it if that is the only change required edit: ouch... managed to misattribute another commit to this PR ... bad VSCode! |
* Fixed failsafe function and sync output of V0 version * Make the code more readable. Co-authored-by: Xy201207 <yaoxu@flysky.com>
Yes, that is the only change needed. |
Fixes #3791
Fixes #3792
Summary of changes: