-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
FLYWOO F745 motor mapping incorrect in iNav version 7 #10018
Comments
Have the same issue. Flashed inav 7.1.2 today bug still exists. Reverted back to 6.0 don’t know how to solve that. |
To get the old mapping, set timer 1 and timer 3 to be motors, but not timer 8. The new mapping has S2 on what used to be S5. |
Having the same issue. EDIT: If there is a way to remap using the CLI I couldn't find instructions for it... |
Hello, I've had this issue and reported this to flywoo. Everything works fine after flashing this firmware. |
Thanks for the help in this thread - I actually ended up buying a new FC as I thought I'd damaged the ESC but then figured out it worked okay in BetaFlight. Hoping this can be fixed going into v8.... I'm working using the Flywoo provided hex from above. |
Current Behavior
One of Motor mappings with the target FLYWOOF745 uses port E13.
Steps to Reproduce
Expected behavior
The motors shall be mapped as follows according to the documentation. iNav 5 does it correctly.
https://flywoo.tawk.help/article/goku-f745-2-6s-16x16-stack
resource MOTOR 1 B00
resource MOTOR 2 B01
resource MOTOR 3 E09
resource MOTOR 4 E11
Suggested solution(s)
See the diff beneath
iNav version
7.1.1
Workaround / fix:
The text was updated successfully, but these errors were encountered: