Dual band binding happening on wrong rate #3446
Merged
+1
−1
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.
Resolves Team2.4-only RXes not being able to traditional bind with a Dual Band TX, due to the TX being on the wrong packet rate.
The TX actually switches to RATE_MAX which is RATE_LORA_DUAL_100HZ_8CH
Backport
This does NOT need a backport to 3.x as 3.x mixes the references such that the first binding uses
enumRatetoIndex(enum)and the second uses a direct index. Although we could backport it to use enums both places if we want to get our PR count up!