Servo midpoint as first servo command on initialization #6499
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DzikuVx
approved these changes
Jan 14, 2021
Closed
DzikuVx
pushed a commit
that referenced
this pull request
Feb 23, 2021
Servo midpoint as first servo command on initialization
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have a camera on a tilt mechanism where 1000 is up and 2000 is down (sticking out from under the fuselage), and it is very annoying that it jerks to 1500 on power up before the LC's that drive the servo kick in. This PR makes it so that the first command sent to the servo's is the servo midpoint from the outputs tab, instead of 1500us regardless of servo midpoint. I cannot think of any situation where this is not desirable, but if there is I can make this a configurable option instead.