airport: warn about USB routing DIP switches and jumpers - #552
Draft
MUSTARDTIGERFPV wants to merge 1 commit into
Draft
airport: warn about USB routing DIP switches and jumpers#552MUSTARDTIGERFPV wants to merge 1 commit into
MUSTARDTIGERFPV wants to merge 1 commit into
Conversation
Closes ExpressLRS#415. AirPort carries its serial data over the USB port of the TX module, but this page never mentions that several modules gate that port behind DIP switches or jumper pins. The page has a Required Hardware section and three warnings, and none of them cover it. The word "switch" did not appear anywhere on the page. On the Happymodel ES24TX and ES900TX families and the BetaFPV Micro modules, those switches select how the USB port is connected inside the module. AirPort needs the same position that is used for USB/UART flashing, not Normal Operation. With the switches wrong the COM port does not appear, or appears with no data, while the RF link still looks healthy, so the symptom points away from the real cause. The positions differ between modules, and even the meaning of a given switch differs, so the warning points at the per module flashing guide rather than naming positions. It also reminds the user to put the switches back, since the Backpack needs Normal Operation.
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.
Closes #415.
AirPort carries its serial data over the USB port of the TX module, but this page never mentions that several modules gate that port behind DIP switches or jumper pins. Before this change the words "switch" and "jumper" did not appear anywhere in
airport.md, despite the page having a Required Hardware section and three existing warnings.Why it matters
On the Happymodel ES24TX and ES900TX families and the BetaFPV Micro modules, the switches select how the USB port connects to the components inside the module. As the ES24TX guide puts it, "These TX Modules have switches to change how the USB port interacts with the different components in the module."
AirPort needs the USB port routed to the main microcontroller, which is the same position used to flash the module over USB/UART, and is not
Normal Operation.The failure mode is misleading. The COM port either does not appear or appears and carries no data, while the RF link itself looks completely healthy. That sends the user looking for a baud rate or configuration fault.
Why it does not name switch positions
The mapping differs per module, and the same switch numbers mean different things on different hardware. Compare:
es900tx.md: "Return the dipswitches to theNormal Operationposition (1 & 2 is On, 3,4,5,6 are Off)"betafpv900.md: for flashing, "Set switches 1 & 2 to On, set the rest of the switches to Off"So the warning points at the USB/UART flashing section of the per-module guide instead of naming positions, which also keeps it correct as modules are added.
It also reminds the user to return the switches to
Normal Operationafterwards, sincebackpack-tx-setup.mdnotes the Backpack "will NOT work properly" otherwise.