Skip to content
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

Matek f405 OSD INAV 2.0 regular plane servo mixer (same as #2912) #3909

Closed
zingaros opened this issue Oct 7, 2018 · 11 comments
Closed

Matek f405 OSD INAV 2.0 regular plane servo mixer (same as #2912) #3909

zingaros opened this issue Oct 7, 2018 · 11 comments
Labels

Comments

@zingaros
Copy link

zingaros commented Oct 7, 2018

Hello

it looks like on 2.0 for target matek F405 osd, using a third servo is not possible.
Works on 1.9 for pad S5. On 2.0 I did not suceed to use S4 S5 or S6 to drive a servo.
After looking to git hub, looks like the change referenced here #2912 was not moved to 2.0.

I would have loved to fix myself but not not feel confident into building the required dev env.

@shellixyz
Copy link
Collaborator

It has been disabled again following #3224. You will have to enable it yourself.

@zingaros
Copy link
Author

zingaros commented Oct 8, 2018

So it means per Matek request f405osd is for multi rotor or wings (2 servo) and only that?
@MATEKSYS it does not make sens

@MATEKSYS
Copy link
Contributor

MATEKSYS commented Oct 8, 2018

I am confused. LED pin should be on S5(PA15), it is right in master branch, but it was changed in development branch.

@zingaros
Copy link
Author

zingaros commented Oct 8, 2018

@MATEKSYS what I m looking for is that as for 1.8 and 1.9 I can use the matekosd to drive more than 2 servo for use in a plane. Looks that with the change in 2.0 we can only drive 2 servo. It’s fine for a wing but not anymore for a plane.

@MATEKSYS
Copy link
Contributor

MATEKSYS commented Oct 8, 2018

@zingaros not really sure what you mean. with 1.8/1.9/2.0. S1 is for motor, S2/S3/S4/S6 are for fixed wing servos, no changes.

@zingaros
Copy link
Author

zingaros commented Oct 8, 2018 via email

@MATEKSYS
Copy link
Contributor

MATEKSYS commented Oct 8, 2018

no difference on PWM output definitions between MATEKF405 & MATEKF405OSD target.
CLI "defaults" after reflashing it with 2.0

@shellixyz
Copy link
Collaborator

shellixyz commented Oct 8, 2018

@MATEKSYS I don't know why DE changed it again in dev. I can revert it.

EDIT: I saw Pawel already took care of it

@zingaros
Copy link
Author

For other users that might face the same trouble:
I confirm that despite test, re-test , reset re-config etc, no way to have more than 2 servo for wing with inav 2.0 on a matek f405osd. I this a way to sell the more shiny F405 wing?
I'm not a dev but thanks to the good doc, I was able to build the dev env, change the code myself (see change here #2912) in a local repo and build an image.

@stale
Copy link

stale bot commented Dec 13, 2018

This issue / pull request has been automatically marked as stale because it has not had any activity in 60 days. The resources of the INAV team are limited, and so we are asking for your help.
This issue / pull request will be closed if no further activity occurs within two weeks.

@stale stale bot added the Inactive label Dec 13, 2018
@stale
Copy link

stale bot commented Dec 27, 2018

Automatically closing as inactive.

@stale stale bot closed this as completed Dec 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants