Preliminary support for new CX-10 #1122
Draft
Conversation
This file contains hidden or 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
1 participant
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.
Following my comment in #542, this adds preliminary working support for the new versions of the Cheerson CX-10 quadcopter with red PCB and
PAN2025B50XIC.Working
Missing
Advice needed
Advice is needed for the following:
How to add a new subprotocol for this:
The
CX10_nrf24l01.inofile is already used by both theCX-10andQ2X2protocols.Not sure if this is because there is a limit on the number of subprotols and it had to be split in two or other reasons.
If there is a limit and the
CX-10protocol is already full a new protocol might have to be created.Packet period and bind count constants values. I chose sensible values that work, based on the logs I collected from the original remote. If there is a better way to calculate these please let me know.
Algorithm to calculate channels from the TX ID.
Management of horizontal and vertical adjustments. More details about workings can be found in my comment in the original issue linked above.
Anything else you notice about the code.