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

Kakute F4 V2 use motor 2 as servo #3999

Closed
holoduke opened this issue Nov 8, 2018 · 6 comments
Closed

Kakute F4 V2 use motor 2 as servo #3999

holoduke opened this issue Nov 8, 2018 · 6 comments

Comments

@holoduke
Copy link

holoduke commented Nov 8, 2018

I want to use motor 2 as a servo, but this is not working somehow. In the mixer screen you can see id:2 not having a servo assigned.
Motor 3 and 4 are working ok. But if you want to fly a plane with additional elevons you need that extra servo. Is there a way to remap motor 2 to work as a servo?

@shellixyz
Copy link
Collaborator

Short answer: you can't

Long answer: it is possible by making a custom build with M2 reconfigured as a servo output but then you need to use 50Hz for all the outputs

Best solution: Use a PCA9685 board for driving up to 16 more servos through I²C or just use a FC suitable for your application.

@Tygrys-1
Copy link
Contributor

Best solution: Use a PCA9685 board for driving up to 16 more servos through I²C or just use a FC suitable for your application.

Can we really have 16 servo channels that way? Some time ago it was limited to 8 AFAIK.

@shellixyz
Copy link
Collaborator

@Tygrys-1 Should be. The chip and drivers supports 16 servos

@Szpero
Copy link

Szpero commented Nov 20, 2018

Outputs are related to servo ID's and are affected by mixer?
Or it is just direct pass through RX channels to controller?

@shellixyz
Copy link
Collaborator

Goes through the mixer. According to the source code the chip outputs replaces the FC's servo outputs.

@stale
Copy link

stale bot commented Jan 19, 2019

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 Jan 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants