SBUS Output in ports #1913
Merged
SBUS Output in ports #1913
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
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.
Hello.
When I enable sbus_output via the cli, it doesn't show up in the ports. It is not convenient, as well as the inability to select it there.
But, most importantly, if I change something in the serial port settings through the configurator and save it, the sbus_output setting is deleted and it must be done manually.
Of course, it would be great to put the servo_protocol in GUI: PWM, BUS or PWM+SBUS. But, unfortunately, MSP packets do not return and do not accept this value. I think it would be more correct to make it a separate PR for the next versions of INAV and the configurator.