Fix Airport - TX module in Airport mode initialized to wrong baud rate #3167
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
…rport baud rate (TX only) and was fixed on the backpack baudrate.
pkendall64
approved these changes
Mar 26, 2025
MUSTARDTIGERFPV
approved these changes
Mar 26, 2025
205b559
into
ExpressLRS:3.x.x-maintenance
48 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
PR 2753 removed some code for Airport in tx_main.cpp/setupSerial() which led to Airport disregarding the TX WebUI Airport baud rate setting. Instead the TX module is initialized using the baud rate defined in hardware.html for the backpack. This sort of broke Airport because setting baud rates on the TX and RX to Airport compatible values, e.g. 9600/9600 and setting terminal programs/MCUs on both ends to the expected 9600/9600 doesn't establish Airport communication.