Add PINIO 3 & 4 plus MATEKF722PX_PINIO target #8401
Merged
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
There are plenty of flight controllers around now that use PINIO 1 and 2 internally for camera switching and switchable VTx power. This left no scope for user definable PINIO. A friend wanted to control a Caddx Peanut on such an FC. So I have implemented USER 3 and USER 4 PINIO options. Also in the PR is the target that was created for my friend.
…F722PX_PINIO-target
MrD-RC
deleted the
MrD_Add-USER-3-and-USER-4-PINIO-Also-MATEKF722PX_PINIO-target
branch
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.
There are plenty of flight controllers around now that use PINIO 1 and 2 internally for camera switching and switchable VTx power. This left no scope for user definable PINIO. A friend wanted to control a Caddx Peanut on such an FC. So I have implemented USER 3 and USER 4 PINIO options. Also in the PR is the target that was created for my friend. Said target works like a charm.
When rebasing to 6.0 master, I initially worked on 5.1.0 base, I saw that shellixyz had added USER 3 to master. But It had a box mode ID conflict. I fixed the initial problems with PR #8276, which negates the need for fixes #8346 and #8394. As USER 3 is not yet in a release (no milestone), changing the box ID for that makes the most sense. Due to this, no current box modes are disrupted at all. All diffs will work fine from 5.x to 6.x as far as box modes are concerned.
This will require a small Configurator update to correct the ordering on the modes page and add support for the LCs. iNavFlight/inav-configurator#1621