ExpressLRS is a high-performance, open-source radio control protocol built from the ground up to be an extremely fast (Express), extremely sensitive (Long Range) System. ELRS uses Semtech SX12xx LoRa transceivers and a lightweight, highly optimized over-the-air (OTA) protocol to provide superior performance compared to legacy RC links. While ExpressLRS started with DIY and repurposed hardware, a large number of manufacturers are now producing high-quality, low-cost transmitters and receivers to make it easy for anyone to get started!
"},{"location":"faq/#how-does-expresslrs-compare-to-other-systems","title":"How does ExpressLRS compare to other systems?","text":"How does ExpressLRS compare to other systems?
ExpressLRS is capable of extremely high packet rates (up to 1000 Hz) and extreme sensitivity (ranges well over 100+ km have been achieved with 2.4 GHz hardware), making it extremely competitive with any commercially available system. And since ExpressLRS is open-source, it costs much less than other systems too!
"},{"location":"faq/#which-opentxedgetx-version-do-i-need-and-why-should-i-update","title":"Which OpenTX/EdgeTX version do I need and why should I update?","text":"Which OpenTX/EdgeTX version do I need and why should I update?
ExpressLRS requires OpenTX 2.3.12 or newer, as it depends on CRSFShot (a.k.a mixer sync) to work properly. However, as OpenTX is no longer being maintained, it is strongly recommended that you update to EdgeTX in order to take advantage of the latest performance improvements and bug fixes.
Click here to read more about radio firmware requirements and setup.
"},{"location":"faq/#how-do-i-flashupdate-my-receivermodule","title":"How do I flash/update my receiver/module?","text":"How do I flash/update my receiver/module?
See Getting Started for a Quick Setup guide and detailed instructions on flashing, features, hardware, and troubleshooting.
"},{"location":"faq/#will-x-receiver-work-with-y-tx-module-from-z-manufacturer","title":"Will x Receiver work with y TX Module from z Manufacturer?","text":"Will x Receiver work with y TX Module from z Manufacturer?
Any Receiver and TX Module from the same Band (e.g. 2.4 GHz or 900 MHz) will work together. For example, a 900 MHz receiver from BetaFPV will work with a 900 MHz TX module from HappyModel. Likewise, any 2.4 GHz receiver will work with any 2.4 GHz TX Modules, from any manufacturer (including DIY ones). This of course assumes the hardware is working properly, flashed with the same major ELRS version (e.g. 3.x), and is using the same binding phrase and configuration options (e.g. Regulatory Domain).
"},{"location":"faq/#whats-the-difference-between-the-different-24-ghz-receivers-pp-ep1rp1-ep2rp2-ep1-dual-rp3-rp4td-tcxo","title":"What's the difference between the different 2.4 GHz receivers (PP, EP1/RP1, EP2/RP2, EP1 Dual, RP3, RP4TD, TCXO)?","text":"What's the difference between the different 2.4 GHz receivers (PP, EP1/RP1, EP2/RP2, EP1 Dual, RP3, RP4TD, TCXO)?
Early ELRS receivers like the HappyModel PP used an STM32 MCU, while later designs EP1/EP2/etc use ESP MCUs. All offer firmware updates via UART or Betaflight Passthrough, but the ESP-based hardware also support firmware update and configuration over WiFi. The EP1/RP1 receivers use u.fl (external) antennas, while the EP2/RP2 receivers use on-board ceramic antennas. Receivers like the RP3 and R24D have two antennas for antenna diversity, while receivers like the EP1 Dual, RP4TD, and SuperD add a second parallel RF path to provide full receiver diversity.
See here for more about different antenna configurations.
"},{"location":"faq/#what-is-required-to-achieve-a-1000-hz-update-rate-on-24-ghz","title":"What is required to achieve a 1000 Hz update rate on 2.4 GHz?","text":"What is required to achieve a 1000 Hz packet rate on 2.4 GHz?
In order to achieve the fastest packet rate, your radio must be running a supported firmware, set to a minimum hardware baud rate of 921000, and be connected to a serial ELRS receiver (SPI receivers do not support the FLRC modes required). Also make absolutely sure ADC filter is disabled on your radio, and that you have applied the appropriate RC Link Preset in Betaflight.
You can use the ELRS lua to check your current packet rate and ensure the radio mixer sync is working properly. See Using the Lua Script for more details.
"},{"location":"faq/#how-many-channels-does-elrs-support","title":"How many channels does ELRS support?","text":"How many channels does ELRS support?
ELRS supports up to 16 channels*. Channels 1-4 are always sent at full-resolution (10-bit). The resolution and update rate of the remaining channels can be configured as follows, based on your requirements:
4x full-resolution (10-bit) channels for sticks (CH1-4) with either:
HYBRID Mode 1x 2-position channel, AUX1 (CH5; Must be used for Arming), 6x 2-position/3-position/6-position (AUX2-7) and 1x 16-position (AUX8), OR
WIDE Mode 1x 2-position channel, AUX1 (CH5; Must be used for Arming), 7x 64 or 128-position channels (AUX2-8). Available via the Lua Script since 2.0.
8x full-resolution (10-bit, ext-limits) with 1x 2-position channel, AUX1
16x full-resolution (10-bit, ext-limits, all half rate) with 1x 2-position channel, AUX1
12x full-resolution (10-bit, ext-limits) with 1x 2-position channel, AUX1, channels AUX2-9 run at half rate.
See Switch Modes for more details on switch modes and how they work.
"},{"location":"faq/#is-my-binding-phrase-a-secret","title":"Is my binding phrase a secret?","text":"Is my binding phrase a secret?
No, just like what channel your VTX is on is not a secret. If everyone kept their VTX channel a secret, the chances of you blasting someone out of the sky accidentally is high. The binding phrase is not used for security, it is used to prevent collisions. Specifically, the binding phrase is hashed and used to seed the random number generator that determines the frequency hopping pattern. Thus, each binding phrase results in a unique hopping pattern, minimizing the likelihood of collisions with other users. To provide the best chance of not interfering with other pilots and them not interfering with you, be sure you're not using the same dumb bind phrase as someone else. Express your style with a hilarious or saucy bind phrase.
"},{"location":"faq/#what-does-rqly-tqly-rssi-x2-snr-x2-mean","title":"What does RQLY, TQLY, RSSI x2, SNR x2 mean?","text":"What do RQLY, TQLY, RSSI x2, SNR x2 mean? Datapoint Description Range Info RQly Uplink - link quality (valid packets) 0 - 100 The number of successful packets out of the last 100 from TX. TX \u2192 RX 1RSS Uplink - received signal strength antenna 1 (RSSI) -128 - 0 First antenna RSSI dBm as reported by the RX. Values vary depending on mode, antenna quality, output power and distance. TX \u2192 RX 2RSS Uplink - received signal strength antenna 2 (RSSI) Second antenna RSSI dBm, for diversity receivers. TX \u2192 RX ANT RX active antenna 0 - 1 Active receiver antenna for diversity RX. RSNR Uplink - signal-to-noise ratio SNR reported by the RX. Value varies mostly by radio chip and gets lower with distance (once the agc hits its limit). TX \u2192 RX RFMD Uplink - packet rate 0 - 7 RF Mode Indexes TPWR Uplink - transmitting power 50mW reported as 0, as CRSF/OpenTX do not have this option TQly Downlink - link quality (valid packets) 0 - 100 An LQ indicator of telemetry packets received by TX. RX \u2192 TX TRSS Downlink - received signal strength (RSSI) RSSI dBm of telemetry packets received by TX. RX \u2192 TX TSNR Downlink - signal-to-noise ratio SNR reported by the TX for telemetry packets. RX \u2192 TX
See the Signal Health page for more info on interpreting link stats.
If you have other questions or concerns, or maybe you need further help that is not covered by this Guide, head over to our Discord Channel or Facebook Group!
ExpressLRS Discord ExpressLRS Facebook
"},{"location":"gsod/","title":"Google Season of Docs: Project Page","text":"
Review and Expand ExpressLRS User Documentation - expresslrs.org
"},{"location":"gsod/#about-the-organization","title":"About the organization","text":"
ExpressLRS (ELRS) is an open source project focusing on developing a radio control (RC) link. The link is primarily designed for first-person view (FPV) crafts (e.g Multicopters, Planes). ELRS aims to provide the best completely open source, high refresh radio control link, minimizing latency while maximizing range. A vast range of hardware in both 900 MHz and 2.4 GHz frequencies is available.
FPV is a community built on top of open source projects such as flight controller firmware Betaflight and RC handset firmware EdgeTX. ELRS fills a void for an open source and high performance RC link with an active development team of about 20 volunteers.
github.com/ExpressLRS was created nearly 4 years ago and in the past 12 months has experienced significant growth. Not only in code contributions, but also users and commercial manufacturers releasing ELRS compatible hardware.
"},{"location":"gsod/#about-the-project","title":"About the project","text":""},{"location":"gsod/#the-projects-problem","title":"The project\u2019s problem","text":"
During early ELRS development users were required to Do It Yourself (DIY) and build their own hardware. This tended to attract tech savvy users. However, in the past 12 months a number of commercial manufacturers have released ELRS compatible hardware. A much wider user group now exists of varying knowledge and initial setup of ELRS can be troublesome. More so for users who are also new to FPV.
A review of the existing user documentation by a technical writer, who has not previously been exposed to FPV, will bring a fresh pair of eyes to the project and help identify knowledge gaps.
Introduce the Technical Writer to the FPV community and teach them about flying a FPV multicopter\u2026 Lets try and have some fun first
Introduce the Technical Writer to our troubleshooting procedures.
This experience will help to identify any knowledge gaps in existing user ELRS documentation.
Devs and Advanced Users will provide information on general user queries from project volunteers and assist with documentation on recurring issues.
Review documentation used to assist manufacturers where English may not be their first language.
Hopefully assist in a major release (ELRS V3) and release notes.
We estimate that this work will take 4-6 months to complete.
Work that is out-of-scope of ELRS project: - In-depth PID Tuning of RC vehicles (Multicopter, Fixed - Wing, Boat, Rover). - Auxiliary function of RC vehicles (Mapping, Package Delivery, Pest Control Drone, Weaponry).
The ELRS project runs a Facebook group (8.4k users at time of application) and Discord Server (8.1k users at time of application) to help users troubleshoot setup issues. A milestone of this work will be to see the number of users posting setup issues reduced, and to have documentation for all common issues presented in a user first perspective and mindset.
The project would be a success if we could provide a link to users for 90% of new user questions.
ELRS Developers also volunteer a lot of time communicating with commercial manufacturers. For a majority of the manufacturers English is not their native language and current ELRS documentation may be confusing. A long term goal of the project is to minimize design errors in commercial hardware releases.
The documentation project will take approximately four to six months. It is expected the initial learning about FPV, Multicopters and ELRS may take 4 - 8 weeks. During which time the existing documentation can be used and reviewed. The remaining time will be used updating and expanding existing user, manufacturer, and developer documentation. ELRS has set its next major release goal before November to include release notes coordinated from this project.
Dates Action Items May - June Learning FPV and ELRS from scratch July - August Updating and expanding current User and Manufacturer documentation September - October ELRS V3 release notes and new feature documents November Project Completion"},{"location":"gsod/#proposed-budget","title":"Proposed Budget","text":"Budget Item Amount Running Total Notes Technical Writer 10,000 10,000 26 wk, 6 hrs/wk Technical Writer Hardware 2,000 12,000 FPV Hardware Volunteer stipends 500 14,500 2 ELRS Devs + 3 Adv User Total 14,500"},{"location":"gsod/#additional-information","title":"Additional information","text":"
The ELRS development team includes a range of expertise, from software professionals, academics, researchers, scientists, and university students. And we love nothing more than nerding out on all things FPV in our free time
ExpressLRS (ELRS) is an open source project focusing on developing a radio control (RC) link. The link is primarily designed for first-person view (FPV) crafts (e.g Multicopters, Planes). ELRS aims to provide the best, completely open source, high refresh radio control link, minimizing latency and maximizing range. A vast range of hardware in both 900 MHz and 2.4 GHz frequencies is available.
FPV is a community built on top of open source projects such as flight controller firmware Betaflight and RC handset firmware EdgeTX. ELRS fills a void for an open source and high performance RC link with an active development team of about 20 volunteers.
github.com/ExpressLRS was created nearly 4 years ago and in the past 12 months has experienced significant growth. Not only in code contributions, but also users and commercial manufacturers releasing ELRS compatible hardware.
Problem Statement / Proposal Abstract
During early ELRS development users were required to Do It Yourself (DIY) and build their own hardware. This tended to attract tech savvy users. However, in the past 12 months a number of commercial manufacturers have released ELRS compatible hardware. A much wider user group now exists of varying knowledge and initial setup of ELRS can be troublesome, especially for users who are new to FPV.
A review of the existing user documentation by a technical writer, who has not previously been exposed to FPV, will bring a fresh pair of eyes to the project and help identify knowledge gaps.
Project Description
Creating the proposal
The proposal idea was pretty easy for us, as we like to keep it simple. GSoD is fundamentally about improving documentation and also supporting technical writers, so we collectively decided we needed the support to hire a writer to review & write better documentation. The exploding ELRS users base meant we could not continue to provide 1 on 1 support to new users, unlike in the beginning of the project. The demand for more and better documentation is and will be ongoing during the ELRS growth period. However, the community appears to have reached a critical mass and the user base is great at supporting new users.
Budget
Of the initially deposited $5800:
$3000 was invoiced by our Technical Writer.
$1,849.42 of the proposed $2000 hardware budget has been spent.
$600 of the proposed $1000 volunteer stipend has been claimed.
The project was able to stay within the initial budget. Some ExpressLRS hardware manufacturers were even able to help with additional hardware and we thank (in alphabetical order) BETAFPV, Happymodel, and RadioMaster for their assistance in providing hundreds of dollars of free hardware to our technical writer.
Participants
The project had 5 volunteers that were either developers or long term users who were integral community members with their insight: deadbyte, maybenikhil, StonedDawg, YeOldePirate, and commanderguy3001.
We selected our writer Agha Saad after reviewing many resumes and cover letters. He offered an incredibly detailed set of goals and timeline & had previous season of docs experience with Arduino.
While no one dropped out of the project, there were personal issues that arose during the period that made it difficult for some volunteers to be available. This did significantly impact the project's timeline and delay hardware delivery.
Selecting a writer with a pre-existing interest in RC or similar hobby that aligned with the projects, and not focus solely on writing experience, may also have assisted with keeping to the timeline, due to hardware being more accessible to them.
Timeline
Our initial timeline has been heavily delayed through the delivery of hardware to our Writer and the eventual confiscation of said hardware. More details are provided below.
Results
A number of PRs were merged by the Technical Writer, which include major technical topics/issues such as Crystal Oscillator (XO) Frequency Error. However key beginner documents were difficult without hardware for our writer to have hands on experience with.
Metrics
A key metric for the success of the project was to address common user issues in the documentation. Another key metric is the project's user base & growth: at the time of the proposal the Facebook group had 8.4k and Discord 8.1k users. These groups have now grown to 12.4k and 13k respectively!
Therefore, we can say that we observed significant growth as a project & organization within the months of Google Season of Docs, but have no strong metrics correlating to use of documentation, as compared to the beginning of the project.
Analysis
A number of challenges were met during this project. With the final hurdle being the import of FPV hardware to the Technical Writer. In the end the hardware required for learning FPV, building, and flying were confiscated by the country's Ministry of Defense. This massively limited what could/can be completed during the project.
In good faith, the ExpressLRS devs can not call this project a success, as without hardware to write about the documentation that most affects new users did not see many significant improvements.
Summary
A number of PRs were merged by the Technical Writer, which is to be commended without access to hardware. If ELRS was to participate in GSoD again in the future there are a couple major conditions that require checking before hiring a writer:
Is FPV legal in their country?
Is the import of FPV/RC hardware legal in their country?
Hot tip for other organizations participating in GSoD and dealing with hardware (especially within the RC & FPV communities). Potentially look to hire someone in a country, or in close proximity to one of the participating developers or volunteers. Local expertise to help with delivery and hand up assistance will be invaluable, as well as an existing understanding of complex regulations surrounding the project.
"},{"location":"hardware/crystal-frequency-error/","title":"Crystal Oscillator (XO) Frequency Error","text":""},{"location":"hardware/crystal-frequency-error/#principle","title":"Principle","text":"
ExpressLRS TX and RX modules generate RF signals based on an external clock source, such as a crystal oscillator (XO). For example, an ExpressLRS 2.4GHz module has an SX1280/1281 RF transceiver chip with a 52 MHz XO. Theoretically, XO is desired to be 52 MHz exactly to generate an accurate 2.4GHz RF signal. However, a real-world XO has deviation for various reasons, such as manufacturing error and ambient temperature.
Real-world TX and RX modules deviate from the reference frequency, depending on the quality of XO used and circuit design. Despite that, if the frequency difference is within a certain threshold, they can communicate with each other (working pairs #1 and #2 in the picture). However, the last malfunctioning TX/RX pair will not communicate. In ELRS 2.4GHz@500Hz, the threshold is around 190 kHz.
This issue may affect both 2.4GHz and 900MHz units. To compensate for this, 900MHz modules do online frequency correction, which tunes the RX frequency automatically to the TX unit once connected. Even in this case, if the TX/RX frequency error is too large to make any connection, the frequency correction won't help. 2.4GHz modules are more vulnerable to frequency error because they can't do frequency correction due to some technical issues, which has risks of a connection drop due to frequency drift from the change of unit temperature.
"},{"location":"hardware/crystal-frequency-error/#recommendation-to-elrs-hardware-manufacturers","title":"Recommendation to ELRS hardware manufacturers","text":"
For SX1280/1281, USE 52 MHZ XO RATED 10 PPM TOLERANCE, 10 PF LOAD CAPACITANCE.
Do not add unnecessary extra load capacitors. If you add the extra caps for the frequency fine-tune, please VERIFY THE FREQUENCY ACCURACY WITH YOUR FINAL PRODUCT (for every new batch). The detailed procedure is described in this document.
TCXO (Temperature Compensated Crystal Oscillator) is a special kind of crystal oscillator, which equips a temperature-compensation circuit inside the package. Unfortunately, TCXO could not be a drop-in replacement for a normal XO, as it requires additional circuitry and needs a redesign of the module. Please refer to SX1280 reference design (part 15.2, Application Design with optional TCXO) to apply.
The advantage of TCXO over a normal XO is its frequency accuracy and stability. Usually, the frequency tolerance of a TCXO is <2 ppm, while the error of a good XO is limited to about 10 ppm. While a good XO is totally fine for ELRS operations (it can tolerate up to 50 ppm relative errors), a TCXO could be a silver bullet to eliminate the frequency offset issue entirely.
So far, we have established two ways of measuring the XO frequency error:
Absolute
Relative
"},{"location":"hardware/crystal-frequency-error/#measuring-absolute-xo-error-not-for-everyone","title":"Measuring absolute XO error (not for everyone)","text":"
Note
This procedure requires a special instrument, which is not expected of a regular ELRS user.
The current ELRS master branch (after PR #1785) equips a test-tone mode. After flashing a TX/RX unit with master branch, get into WiFi update mode, and access http://10.0.0.1/cw.html which should look like the figure below:
By clicking the START CONTINUOUS WAVE button, the unit will generate a continuous wave at 2440 MHz. By measuring the output frequency with a spectrum analyzer (e.g., HackRF SDR), you can determine how the XO deviates from the reference frequency (2440 MHz). Within 20 ppm (=~50 kHz) absolute error over the entire working operating temperature (from -20 to 85 degC) is expected for a good unit. Up to 40 ppm error (=~100 kHz) is acceptable.
Caution: don't use Continuous Wave mode for longer periods of time to avoid excessive heat up of the RF unit.
"},{"location":"hardware/crystal-frequency-error/#measuring-relative-xo-error-between-a-tx-rx-pair","title":"Measuring relative XO error between a TX-RX pair","text":"
You'll need to use \"Manual mode\" in the configurator to enable a special debug mode. In addition to this debug mode flag, you should add any other user defines you need to get your TX/RX to connect (check the user defines section).
For example, this might look like (which is safe to just copy-paste in general):
Using the configurator and user defines, include the -DDEBUG_FREQ_CORRECTION define for BOTH TX AND RX builds of any version of ELRS past v3.0.0 (i.e. V3.0.0 RC2)
After loading the new firmware on both TX and RX, go to the telemetry screen in your model settings on the TX side. Note the \"RSNR\" value. This is the relative difference between your TX and RX clocks.
The closer this value is to 0, the better!. Negative means the RX clock is slower than TX, and positive means that it is faster.
\u00b1 20 ticks (~30 kHz offset) is nearly perfect. \u00b160 ticks (~95 kHz) will still likely be completely fine, though not ideal. \u00b170 ticks and further is marginal and might be fine, but you should be careful.
The TX-RX pair can communicate up to about 110 ticks (~170 kHz). However, because you'll want some safety margin, DO NOT USE the gears with \u00b190 ticks of error.
The tick value that appeared in the RSNR field is a scaled value of the frequency offset, and here is the conversion formula:
\\(Freq_{kHz} = Tick \\times 1.575\\)
For example, if you got the tick value of 30, the frequency offset between your TX and RX is \\(30 \\times 1.575 = +47.25_{kHz}\\), and this means your receiver is generating 47.25 kHz higher frequency than your TX.
When one unit in the measured pair uses TCXO with good error tolerance (desirably <1 ppm) as the SX1280 clock source, the measured ticks will represent the absolute error of the counterpart unit.
We measured the frequency deviation of RX modules from various makers and samples, using the absolute method mentioned above. In the graph, 0 is the reference frequency, and the amount of frequency deviation is shown as the bars. Closer to zero is better. More than 200 kHz deviation is considered to be out of tolerance. Please note that they are only a few samples acquired by the devs, which may not represent the entire product batches.
There are a few interesting points in the graph.
1 All three samples from JHEMCU have significantly deviated more than other makers. A TX module at the reference frequency will not bind to JHEMCU #3 (yellow bars). Also, a TX module with a slight positive frequency deviation will not bind to JHEMCU #1 and #2 as well. 2 Ambient temperature changes the operating frequency of a module. In the graph, Jumper Aion RX (blue bars) and JHEMCU #3 (yellow bars) were chilled and heated, and their operating frequencies were changed around +- 50 kHz. 3 A few makers added extra load capacitors to XO, which lowered their operating frequencies. In this graph, Matek (pink and green bars) and Jumper (blue bars) modules were shipped with the extra load caps. Removing them shifted the frequency to the higher side. 4 Overall frequency errors tend to shift toward the negative side. This might be caused by using XO designed for 8pF load, while the internal load capacitance of SX1280 is 10 pF.
To conclude, XO frequency error is unavoidable. However, a careful circuit design and good-quality parts can control the error within the tolerable amount.
Just to note, we've had some mismatching cases as follows:
JHEMCU (which are rebranded and sold as Flywoo, HiYounger as well) SP24S and EP24S units have frequently reported not being able to bind. (Their units tested here are bad as well)
A few cases were reported that Matek R24-D, R24-S, and Jumper Aion RX Mini units were not able to bind with some TXes (e.g., HappyModel ES24TX Pro). Removing the additional caps around 52 MHz XO solved the issue.
Caps to be removed Jumper Aion Caps Flywoo Caps"},{"location":"hardware/crystal-frequency-error/#how-to-video","title":"How-to-video","text":"
You can also follow the below video which helps to fix ELRS RX Frequency Error by removing extra caps.
The Crystal Oscillator error documentation would not have been possible without the work and huge effort from the @SunjunKim
"},{"location":"hardware/fan-mod/","title":"R9M Fan Mod","text":"
Initially, this mod is brought to life by Niklas Voigt and Seba112PL as a beta tester and is still a work in progress.. if you have suggestions don't hesitate to contact.
DISCLAIMER
Users have experienced temperature issues on R9M that degrades the link quality. We recommend you use the lowest power setting required for your flight and turn on dynamic power at all times (ELRS v2.0+)
Hot Tip
It might seem counterintuitive, but using less power might help for longer flight times and more range by reducing the heat. ELRS does not require a lot of energy and looking at the long-range leader board
You need a 20x20mm or 25x25mm fan in 5V version. Both sizes are supported. To secure the fan into the cover you can use 2x M2 screws, a thread is already in the print. You can solder the pins of the fan directly to the 5v port of the R9M or use the Controllable Fan Mod which can control the fan out of software (fan blows only at >250mW).
R9M Fan Mod Cover is built out of four Parts and a Sticker:
"},{"location":"hardware/fan-mod/#controllable-fan-mod","title":"Controllable Fan Mod","text":"
Additionally to the fan, you'll need one NPN Transistor (e.g. 2N4401) or N-Channel MOSFET (e.g. BS170 has built-in Schottky-Diode) and a resistor (200-3k7)
The PB9 pad location on the R9M2019 module is a bit different. Please see the photo.
PB9 pad location"},{"location":"hardware/fan-mod/#2w-mod","title":"2W Mod","text":"
WARNING
Only do this if you are comfortable with modding hardware
In addition to the 3D printed Cover & the Controllable Fan Mod you'll need:
Fan + Heatsink \"2507 25MM 25x25x13MM Hydraulic bearing Graphics card Cooling fan with heat sink 5V 12V m.2 SSD Fan with 2pin\"
Thermal Pad 0.5mm \"1pc 100mmx100mmx0.5mm GPU Northbridge IC LED Chipset Heatsink Cooling Conductive Silicone Thermal Pad,100x100x0.5mm w/ 3.2W/M-K\"
The screw heads are cut off to reduce height.
As you can see in picture 3, the 5v fan is connected to the power source of the module, so the fan is used with some overvoltage and spins with higher rpm... tested for a long time and should not be a problem for the fan. If you don't know how to allow the 2W in the firmware, don't do this mod!\ud83e\udd26\u200d\u2642\ufe0f
"},{"location":"hardware/fan-mod/#here-are-some-makes","title":"Here are some makes","text":""},{"location":"hardware/hardware-selection/","title":"Hardware Selection","text":"
ExpressLRS is #blessed with the benefit of there being many options of transmitters and receivers available from a variety of manufacturers. This begs the question \"what is the best?\" There is no best option for hardware, only one that has the features you want for the price you want to pay in the size you want it. ExpressLRS does not recommend a specific brand or model, but provide the information to help you select the right ELRS hardware for your needs. The following page will list manufacturers and features to look out for on their hardware.
Note
This list will list primarily 2.4GHz hardware with 900MHz only listed in the frequency category, as 2.4GHz has become a significantly larger portion of the ELRS market.
This section exists to list some common features of receivers and will give some examples of receivers with these features.
Each build is different, but these are recommended things to look for when selecting a receiver:
Whoops / Toothpicks / Light aircraft: Size is probably the most important feature, with a light small receiver and an onboard antenna being the best choice.
Racing Quads: Size is again most important. Ceramic antennas could be less easily damaged, and the reduced range of tucking them inside the frame is fine due to the short flight range. An external 2.4GHz antenna dipole is still pretty easy to fit and can be tucked away for a small improvement over the ceramic, but comes with a chance of Choppage.
Freestyle Quads: Minimum size is no longer an issue so Nano-sized receivers are the best bet here. An LNA is going to give you better reception behind obstacles. External antennas are a benefit as well, but you need to trade off how unobstructed the antenna will be versus getting it chopped. Diversity can be of major benefit in medium-range scenarios to prevent antenna nulls from pointing towards transmitters and carbon or concrete blocking one antenna.
Long Range: For sure you need an LNA, an external antenna, and a PA to extend the telemetry range. This isn't to say these are required for long range, 5km is achievable on a ceramic antenna receiver with no LNA/PA at 250Hz/100mW with a clear line of sight. Diversity can be useful for longer-range quads, to prevent carbon from blocking antennas or antenna nulls from pointing toward the transmitter in certain flight orientations. For planes without a flight controller, PWM receivers will work great. For absolute maximum range, 900MHz can do more but 2.4GHz can still do 50+km.
Frequency
ExpressLRS offers both 2.4GHz and 900MHz systems, with each only working with receivers and transmitters of the same frequency. 2.4GHz is the currently most popular frequency given its legality, features and cost. 2.4GHz links offer the fastest packet rates allowing for a more locked-in feel while piloting and still offering massive amounts of range. 900MHz is the original long-range frequency and still can be great for high wifi pollution environments with slightly better penetration.
For new users, unless you plan on flying hundreds of kilometers or in a high-noise environment we recommend 2.4GHz hardware such as:
Happymodel EP Series
Radiomaster RP Series
NamimnoRC Flash Series
If you have an R9 system or similar or plan on flying beyond reasonable ranges, some great 900MHz receivers include:
BetaFPV Nano900
Happymodel ES900RX
GEPRC Nano 900MHz
Antenna Type
Antennas are where the radio waves come and go from the receiver. ExpressLRS offers many different antenna types, with dipoles and ceramic antennas (see SMD Antennas) being the most common types of reciever antennas. In terms of range: Ceramic antenna < Mini Dipole (\"Minimortal-T\" style) < sleeved dipole < Half-wave Dipole. A diagram of the antennas and their sizes for the 2.4GHz band is shown below:
Unless otherwise noted, most receivers will have a U.FL/IPEX connecter which supports external antennas. Some receivers with ceramic antennas are:
Happymodel EP2
Radiomaster RP2
MatekSys R24-S
Diversity
Diversity improves reception compared to standard receivers by using multiple antennas. A standard receiver has a single antenna, while antenna diversity uses two antennas and a switch to route the signal from one or the other. True diversity takes it a step further by using two radio chips, each connected to a different antenna, and choosing the one with the strongest reception at any given time. This provides a level of redundancy which is particularly beneficial for flight where the antenna nulls can point towards the pilot (e.g. freestyle flight)
Some receivers with antenna diversity include:
Radiomaster RP3
Namimno Flash Diversity
Matek R24-D
Some receivers with true diversity include:
Happymodel EP1 Dual
BetaFPV SuperD
PWM
PWM is used for crafts that do not have flight controllers and allow for direct control of ESCs and Servos. See the page on PWM for more in-depth information on using PWM.
Some PWM receivers include:
MatekSys R24-P6
Happymodel EPW6
Radiomaster ER5A/C
PA/LNA
A Low Noise Amplifier (LNA) directly adds to your incoming RSSI. Typical gains are in the ballpark of +12dBm which will be observed in the RSSI as being 12dBm higher than it would have been without the LNA. This is because the LNA amplifies the incoming signal coming from the antenna before going to the RF chip, which increases the sensitivity of the receiver by boosting the incoming signal. An LNA also boosts the noise by the same amount so the sensitivity limit will likely be lower than the value quoted by the Lua.
A Power Amplifier (PA) boosts the outgoing signal strength and extends the telemetry range back to the TX. Without a PA, the power output is limited by the RF chip's max power output itself (around +13dBm 20mW). It works the same way as turning up the power output on the transmitter module, however it is not adjustable. The receiver's output can be ran at adjustable power levels given range needs. Most PAs are 20dBm/100mW, meaning the telemetry transmit power can be adjusted to 10, 25, 50 or 100mW.
Receivers with a PA/LNA will have a listed telemetry output power in dBm or mW
Some receivers with a PA & LNA are the following:
Radiomaster RP3 (100mW)
Skystars Nano SS24D (20dBm)
MatekSys R24-D (23dBm)
BetaFPV SuperD (20dBm)
Size
The FPV world shook when ELRS released receivers that were half the size of \"nano\" sized receivers, included the antenna onboard, and still had kilometers of range at 250Hz/100mW. A small receiver can fit in tight places, but remember that tucking a tiny receiver's ceramic antenna deep inside a stack behind carbon reduces its performance, which was already compromised by the elimination of amplifiers to make it that small. Larger ELRS receivers regain these amplifiers offering better reception and telemetry range at the cost of size and weight. The common size classes are shown below, but there are other receivers with slightly different sizes:
PP Sized Receivers (absolute smallest, lowest range regardless of antennas):
Happymodel EP/PP
Radiomaster RP
BetaFPV Lite
Nano Sized Receivers (medium sized, can have PA/LNA but tends to lack some features):
BetaFPV Nano
iFlight RXes
Namimno Flash Diversity RX
Axisflying Thor RX
Namimno Flash RX
Larger Receivers (most feature rich but also significantly larger)
This section lists out some common features of transmitters and some examples of transmitters with those features
Everyone has different needs for a transmitter but the main needs come down to size, range and integration.
Built-In Transmitters
Certain manufacturers have made handsets with built in ELRS modules, which offer tighter integration with ELRS. These can be updated through the handset as well as generally over WiFi as is standard.
Some handsets with built-in ELRS include:
RadioMaster TX16S ELRS
RadioMaster Zorro ELRS
BetaFPV Lite Radio 3 Pro ELRS
Jumper T-Pro
Jumper T-Lite v2
A notable exception to this list is the iFlight Commando, which, while including a TX built into the handset is simply wired as an external module, and put within the casing. It does support an external module and notably has both 868/915MHz and 2.4GHz options available
Frequency
ExpressLRS offers both 2.4GHz and 900MHz systems, with each only working with receivers and transmitters of the same frequency. 2.4GHz is the currently most popular frequency given it's legality, features and cost. 2.4GHz links offer the fastest packet rates allowing for a more locked-in feel while piloting and still offer massive amounts of range. 900MHz is the original long range frequency and still can be great for high wifi pollution environments with slightly better penetration.
For new users unless you plan on flying hundreds of kilometers or in a high noise environment we recommend 2.4GHz hardware such as:
Axisflying Thor
RadioMaster Ranger
HappyModel ES24TX Pro
Namimno Flash
If you want to push the limits of range, a 900MHz system might fit within your needs. Some off the shelf 900MHz transmitters include:
Namimno Voyager
Happymodel ES900TX
BetaFPV Micro 915/868MHz
Size
Most ExpressLRS Transmitter modules fit into one of two classes - Micro and Nano. There are some exceptions that fit into multiple or have interesting features that may make them work better for your needs.
Micro modules will fit into the JR bay of a standard transmitter such as a TX16s or QX7, with some examples including:
RadioMaster Ranger Micro
Namimno Flash
HappyModel ES24TX
Nano modules will fit into a lite module bay such as that on a Zorro, T-Pro or X-Lite with some examples including:
HappyModel ES24TX Slim Pro
RadioMaster Ranger Nano
Jumper AION Nano
BetaFPV Nano
Some notable exceptions that can fit into multiple or very specific module bays include:
HappyModel ES24TX Lite - Fits onto Jumper T-Lite
Axisflying Thor - Has a wire system to be able to plug into any radio with a CRSF output
Radiomaster Ranger - includes Micro & Nano mounts and wiring for any CRSF compatible radio
Power
Most ELRS Transmitters have a 250mW or 500mW power cap, but if you need to go a bit further, a select few 1W modules exist (see the Inverse-square law for info on why 1W does not double the range over 500mW), packing that punch needed to go even further. These transmitters include large heatsinks, fans and sometimes temperature-sensing to cool the RF components. Some of these 1W transmitters are:
HappyModel ES24TX Pro
RadioMaster Ranger (Full Size, Micro and Nano all are 1W)
Axisflying Thor
BetaFPV Micro TX 1W
RadioMaster Boxer
Jumper T-Pro Internal
NamimnoRC Flash (both OLED & non-OLED models)
Screens
Some transmitters include a small screen that displays useful information and pairs with a small joystick to quickly change settings on the go. This can be useful when paired with handsets running firmware that does not support lua scripts. The two main types of screens are TFT and OLED:
The only transmitter with a TFT screen on the market at the moment is the Axisflying Thor TX.
Some transmitters with an OLED include:
Namimno Flash OLED
RadioMaster Ranger
BetaFPV Micro TX
Jumper AION Nano
Backpack
Most current transmitters will include a backpack, which enables communication with accessories such as a VRX allowing for tighter integration with the transmitter and drone. Transmitters with a built-in backpack include:
HappyModel ES24TX Pro
HappyModel Slim Pro
NamimnoRC Flash
AxisFlying Thor
RadioMaster Zorro
BetaFPV Micro TX 1W
Antennas
Besides handset integrated transmitters, all ELRS TX modules support many antennas so this serves as a guide to antenna types and connectors.
ELRS TX Modules have two connecters, which are visually similar - SMA and RP-SMA
These connecters mount many types of antennas which have different types of radiation patterns. The first figure depicts the types of antennas commonly sold with transmitters:
The most common antennas sold besides simple dipoles are moxons and folded dipoles, which visually look similar which helps distinguish the two:
The radiation patterns of a moxon and folded dipole are depicted below in a isotropic, lateral and top view
Bling Features
Certain transmitters have \"bling features\" which are less important than the other listed features. Some of these include RGB LEDS, Temperature Sensors and G Sensors.
RGB LEDs are included on many modern TXes, and also serve as a useful status indicator.
Temperature sensors are useful for higher power transmitters, to turn on the fan only when needed instead of constantly running while transmitting which reduces noise. Currently the only transmitter with this feature is the Axisflying Thor.
G Sensors/Motion sensors use a 3 axis linear accelerometer to detect the orientation of the transmitter and also can use bump to handoff for loan model. The transmitters that ship with this feature is the Axisflying Thor & RadioMaster Ranger
To benefit from the higher bitrate of 400 kilobits per second using OpenTX/EdgeTX you need to add a pull-up resistor to the inverter of the serial port on the R9M 2018\ud83d\uddfb\ud83c\udd99
Strongly suggested being done for anybody looking for higher than standard packet rates using ExpressLRS \ud83d\udd2e
ExpressLRS now supports direct PWM output from receivers. This documentation refers to only receivers with native PWM output, not receivers attached to external CRSF to PWM converters such as the CRServoF or Matek CRSF-PWM-C.
"},{"location":"hardware/pwm-receivers/#channel-mapping-and-failsafe","title":"Channel Mapping and Failsafe","text":"
The default channel mapping is straight through: CH1 from the TX goes to PWM Output 1, CH2 to Output 2, etc. To change this on ESP-based receivers, allow the receiver to go into WiFi mode then use the WebUI to configure the mapping. Any input channel can be mapped to any output channel, and the same input can be used for as many outputs as desired. AUX1/CH5 is always 1-bit, so you'll likely want to change this mapping to a channel with more resolution.
PWM Output WebUI
Failsafe values are set using this UI as well with values that can range from 988us to 2012us. Failsafe is entered if the receiver is connected and Link Quality (LQ) drops to 0, or 1 second has passed without a valid channels packet being received, whichever comes first. On startup, no pulses are generated until a transmitter connects, allowing ESC throttle calibration with the standard \"raise the throttle before connecting\" method. The default failsafe value is 1500us for all channels except Output 3, which defaults to 988us.
PWM output is still subject to the resolution of the ELRS protocol, which means by default there are still only 4x full resolution channels (10-bit CH1-CH4) and 8x switch channels (CH5-CH12). For the best resolution on the switch channels, use Switch Mode: Wide and a TLM Ratio of 1:8 to 1:256 for 7-bit (128 pos) switch channel resolution. Higher TLM Ratios (1:2 and 1:4) are reduced to 6-bit (64 pos) resolution. Remember that switch channels are sent one per packet in Wide mode, taking 8 packets to send all 7 channels (e.g. 150Hz mode 1:64 = 18.657Hz updates to CH6-CH12). AUX1/CH5 is sent in every packet in all switch modes but is only 1-bit (2-pos). See Switch Configs for more information.
Full-Resolution Switch Modes
ELRS v3 now supports full-res switch modes, which provide 8, 12, or 16 full-resolution (10-bit) channels at 100Hz (900MHz and 2.4GHz) or 333Hz (2.4GHz only). For PWM receivers with more than 4 channels, it is recommended that you use one of the full-res modes for best performance.
Normal pulse width (988-2012us - center 1500us), extended pulse width (885-2115us - center 1500us), and also half pulse width servos (494-1006us - center 750us)
10kHz Duty Cycle 0-100% PWM (e.g. for driving a brushed motor FET)
On top of this, outputs can also be set to:
Binary On/Off (High/Low signal output)
DSHOT300 (for driving brushless motor ESCs; ESP32-based receivers only)
PWM receivers can also output any supported serial protocol, such as CRSF or SBUS. Select the desired output protocol using the ELRS lua, or on the Model tab in the receiver's WebUI. The default pins used for serial output vary by receiver. If your receiver has a dedicated serial port (e.g. RadioMaster ER6, ER8, ER8G(V)), serial output will be over this port. Otherwise, check the Model tab in the receiver's WebUI to see which pins can be mapped to Serial TX and RX (usually Ch2 and Ch3).
JST-GH Serial Port on RadioMaster ER6 PWM Receiver
Advanced Output Mapping
Advanced users can remap serial, I2C, and PWM outputs to any available pin using the hardware.html page in the receiver's WebUI. Please ask on the ELRS Discord if you need help configuring non-standard receiver output mapping.
Have you ever been frustrated that you can't finish a race because your receiver antenna got chopped? Have you ever wished you could build a quad without worrying about how to mount your antenna? If so, the SMD Antenna is for you!
SMD Antenna
This perky little fellow is worse at receiving signals than his snaky brothers, but don't let that deter you! Because of the amazing range of ExpressLRS, he still gets all the range a racer could ever need. The SMD Antenna is available now on Happymodel PP/EP hardware and other 2.4GHz receivers. Take a look at the videos below to see what Mr. SMD can do for you.
The antenna is sort of fragile and can break off or be melted by a stray soldering iron. If this happens, you can save your receiver by soldering a U.FL/IPEX1 connector onto the pads as shown here. Just make sure the center pin has continuity with the filter at the other end of the trace, and no continuity with the ground.
Conversely, the SMD antenna can be soldered to regular U.FL footprints if you're brave.
SPI receivers DO NOT support D(D250, D500), F(F500, F1000) and Full Res(100Hz Full Res, 333Hz Full Res) Modes (Packet Rates) and thus will not bind or sync with a TX module in any of these modes.
You must use one of these packet rates with an SPI receiver: 50Hz, 150Hz, 250Hz, 500Hz.
Update Betaflight 4.5.1 and newer now support FLRC modes (F500,F1000) for SPI receivers. F1000 is not recommended for FCs with F411 MCUs.
A few Flight Controllers and AIOs have been released with ExpressLRS receivers on-board using SPI instead of a regular UART. This means you can build a more compact and lightweight whoop or nano long range rig without the need for an external receiver. More of these flight controllers are coming into stores.
Because the ExpressLRS code is \"baked-in\" to the flight controller firmware instead of using a second microcontroller, these can not be updated the same way external UART-based receivers are updated.
NOTE
You cannot use the ExpressLRS Configurator to update these FCs. You must update the flight controller software, e.g. Betaflight.
SPI receiver compatibility with ExpressLRS v3.x requires your flight controller be flashed with Betaflight 4.4.0 or newer. If you are running Betaflight 4.3.0 or Betaflight 4.3.1, your receiver will only work with ExpressLRS v2.x. Please update to Betaflight 4.4 or newer for ExpressLRS v3.x compatibility.
In preparation for updating, you should save a copy of your diff all dump. Simply go into the CLI Tab of the Betaflight Configurator and execute the command diff all then press enter. A bunch of text will show up on the screen. At the bottom of the page, click the Save to File button and navigate to the folder you want the file to be saved. Finally click Save after taking note of the folder and filename of the text file. You will need to navigate to this file later on, moreover if you already have customized your settings on the flight controller, like rates, PID tune, OSD.
Using the latest Betaflight Configurator, navigate into Firmware Flasher and select the latest Betaflight release. Depending on your AIO board, the target will differ. Betaflight targets for FCs with SPI receivers will usually end in SX1280. Examples:
Happymodel AIO: CRAZYBEEF4SX1280
BetaFPV AIO: BETAFPVF4SX1280
If your Flight Controller model is not in the list above, consult your Flight Controller manufacturer for details.
NOTE
The Happymodel Mobula6 900MHz AIO with the CrazyF4 ELRS FC (Target: CRAZYBEEF4DX) doesn't use an SPI ExpressLRS receiver. Check the page for ES915RX instead.
Likewise, the v2.0 BetaFPV F4 1S 5A comes with an on-board UART-based ExpressLRS Receiver and doesn't use the SPI ExpressLRS implementation. Use the BETAFPV AIO 2400 RX Device target.
If you're using Windows and flashing fails to start, you may need to correct the drivers using a tool like ImpulseRC Driver Fixer. These tools and other drivers are also linked in the Welcome tab of Betaflight Configurator.
Once flashed, you will need to connect and restore settings from the diff all you have saved. Go into the CLI Tab of the Betaflight Configurator and press the Load From File button. Select the diff all file you made previously and press execute. If there were any errors, you will need to manually type in the save command and press enter. Betaflight Configurator should disconnect. After reconnecting, review your Betaflight settings (for example the Receiver Type and Protocol in Receiver tab; it should be set to SPI Receiver, with Provider as ExpressLRS).
As of Betaflight 4.4 (with Betaflight Configurator version 10.9.0 or newer), your ExpressLRS Binding Phrase can be set directly on the receiver tab in Betaflight Configurator.
Proper configuration of the Betaflight Receiver tab for ExpressLRS SPI Receivers. Receiver Mode (1) should be set to SPI RX. SPI Bus Receiver Provider (2) should be set to EXPRESSLRS. Enter your binding phrase in the box (3) and it will be converted to UID bytes (4) and saved to your Betaflight config. You can also take this opportunity to enable Telemetry (5) if desired, and make sure RSSI_ADC (6) and RSSI Channel (7) are disabled as shown.
Put the receiver into bind mode using any of these procedures:
\"Bind\" button in the Betaflight Configurator, Receiver Page (if can't be found, update the Betaflight firmware).
Using the CLI, type in bind_rx and press enter once.
Press the bind button on the flight controller.
Using the CLI, type in set expresslrs_uid = 0, press enter once, then save and reboot
Once the SPI receiver is in Bind Mode (indicated by two immediate blinks followed by a short pause), execute the ExpressLRS Lua script in your handset and press the Bind option. The RX and TX should be now bound (indicated by a SOLID LED on the Flight Controller).
Please mind the order, RX first, TX second.
Video Tutorial (thanks to @JyeSmith):
"},{"location":"hardware/spi-receivers/#binding-phrase-via-cli","title":"Binding Phrase via CLI","text":"
The binding phrase is hashed into 6 bytes represented as numbers. These 6 bytes are referred to as the UID bytes. UID bytes are entered into the Betaflight CLI for binding. Please look below for instructions.
NOTE
When building via ExpressLRS Configurator or via VS Code, note down the UID bytes from the build log. You can also use the generator below to retrieve your UID bytes from your binding phrase.
In order to set or retrieve current Model ID through Betaflight you need to use CLI: - Set new Model ID: set expresslrs_model_id = N - Get current Model ID: get expresslrs_model_id
Go to Betaflight CLI and enter the following commands.
As shown above, Betaflight Configurator 10.9.0 also supports entering the Binding Phrase directly in the Receiver Tab. It will generate the UID bytes for you. Clicking Save and Reboot will save the Binding Phrase into the flight controller configuration.
Supported RF Modes
SPI receivers DO NOT support D(D250, D500), F(F500, F1000) and Full Res(100Hz Full Res, 333Hz Full Res) Modes (Packet Rates) and thus will not bind or sync with a TX module in any of these modes.
The SPI ExpressLRS implementation would not have been possible without the work and huge efforts from the following developers:
Pawe\u0142 Stefanski (@phobos-)
Dominic Clifton (@hydra)
Hans Christian Olaussen (@klutvott123)
Steve Evans (@SteveCEvans)
ctzsnooze (@ctzsnooze)
"},{"location":"hardware/x9d-troubleshooting/","title":"Troubleshooting the X9D(+)","text":"
For quite some time we had the impression that the X9D(+) radio works well with the high baud rates, needed for ExpressLRS. However, some users report it's not working as it should with ExpressLRS. For example:
ExpressLRS Lua script just shows Loading...
ExpressLRS Lua script shows unstable behavior, especially on the higher packet rates, showing values different from 0/[SELECTED PACKET RATE]
It is possible that the X9D(+) radio also suffers from a slow inverter circuit that messes up the 400000 baud UART signals.
As you may know, for the Taranis QX7(S) you can do the Crossfire inverter mod or select a lower baud rate in the Hardware menu (Page 6/7) of OpenTX to fix the issue.
Well, the final verdict is not out yet, but the following may help to resolve the issue:
Do a hardware mod as well on your X9D(+) as you can read all about here in PR# 59 for EdgeTX. This requires changing the 10k resistor R82 to a 1k resistor.
Download a OneBit_Status firmware using this OpenTX version, based on OpenTX(2.3.12 or 2.3.14) and enable ONEBIT Sample Mode (System Menu -> Hardware). One Bit Sample Mode is also available on EdgeTX.
Sample Mode: Normal Sample Mode: OneBit
Select 115200 baud using the above OpenTX version. (ExpressLRS will lock you out of 500Hz packet rate with 2.4GHz, but any packet rate below that should be stable now.)
The nice thing about the OpenTX build above is that it also adds two additional Sync lines to show the current OpenTX/UART behavior. This will show in your Model Setup (Page 2/11) where you select the external module type (where you selected CRSF to enable ELRS):
The first Sync line shows something like L00002R04000u. L and R indicate the microseconds of Lag and Rate.
The L is how much OpenTX is trying to compensate to nail the rate you selected. (The closer to 0 the better)
The R is just the Packet Rate you selected using the ExpressLRS Lua script.
The second Sync line shows something like G11 C00 F00. This stand for G (good packets), C (CRC error), F (Framing error). The goal is to have zero errors here. (Don't forget to power your receiver so a link is established!)
If this has helped you in any way (good or bad) with your X9D(+) radio, let us know on the ExpressLRS discord!
Most of the ESP-based ExpressLRS modules come with the TX Backpack. A \"TX Backpack\" refers to an additional WiFi-capable microcontroller inside the TX module, which can communicate wirelessly with \"Backpack receivers\". This allows the TX to communicate with other devices such as your Goggles (to change VRX channel), race timers, antenna trackers, ground control stations, etc.
Open the ExpressLRS Configurator and select Backpack in the left hand menu bar.
Select the latest Backpack Release version from the Releases dropdown.
Select your device target. If there is a target that matches your hardware, use it. If you can't find a target that matches your TX module, use the Generic backpack for any TX module targets.
Enter your Binding Phrase and your Home WiFi SSID and Password (Optional).
Choose your Flashing Method based on your hardware (choose from the options below):
"},{"location":"hardware/backpack/backpack-tx-setup/#flashing-via-usbuart-for-older-tx-modules-with-dip-switches-jumper-pins","title":"Flashing via USB/UART (for older TX modules with DIP switches / jumper pins)","text":"
Applies to: Older TX modules that have DIP switches or jumper pins, e.g. Happymodel TX modules. Recent transmitter modules do not required any preparation prior to flashing the TX-Backpack firmware. If your TX module does not have any DIP switches or jumper pins, you can skip this step, and proceed to flash via Passthrough or WiFi.
For older TX modules like the Happymodel TX Modules, you will need to move the jumpers or DIP switches into the correct position before flashing the firmware. Please see the USB/UART Flashing section of your particular TX Module for the jumper or DIP switch position.
ES24TX Jumpers
ES900TX Jumpers
You need to activate the Backpack Flashing jumper or DIP switch (middle pair). Opening up the module enclosure will be needed as well to access the Buttons on the modules. Make sure your computer recognizes your TX module as a USB to UART Bridge. Windows drivers are linked in the Flashing Guides.
For the NamimnoRC Flash and Voyager TX Modules without an OLED screen (Gen 1 STM-based), make sure you're able to access the Backpack Web Update page (see Flashing Guide) via WiFi.
For the Happymodel TX modules, connect to your computer via USB. As stated above, the module should be detected as a USB to UART Bridge and the jumper/DIP switches are set in the correct position (middle pins/switches should be On).
Button Dance: A few buttons are needed to be pressed on the module while the firmware is compiling. Press and Hold the GPI0 button then the RST button (GPIO is still pressed) then release the RST button and then the GPIO button.
Module Buttons
In the Configurator, select the UART option under Flashing Method.
Ensure you have completed the steps in the Setup section above, then click Flash on the ExpressLRS Configurator.
Wait for the process to complete and you should see the green Success notification.
Unplug the USB and change the position of the jumpers/DIP switches for the Normal Operation (refer back to the module's Flashing Guide page for the correct position).
Put back the cover of the module and attach it to your module bay.
"},{"location":"hardware/backpack/backpack-tx-setup/#flashing-via-passthrough","title":"Flashing via Passthrough","text":"
Applies to: Newer TX modules that do NOT have DIP switches / jumper pins, e.g. Radiomaster Ranger Series
Plug a USB Data Cable into the TX module.
In the Configurator, select the Passthrough option under Flashing Method.
Ensure you have completed the steps in the Setup section above, then click Flash on the ExpressLRS Configurator.
Wait for the process to complete and you should see the green Success notification.
"},{"location":"hardware/backpack/backpack-tx-setup/#flashing-via-wifi","title":"Flashing via WiFi","text":"
Applies to: All TX modules that have a Backpack (this method assumes that the Backpack firmware has been flashed in the past and is functional).
Using the ExpressLRS Lua script, navigate to WiFi Connectivity and select Enable Backpack WiFi.
The LUA script will briefly show Sending, then return to the WiFi menu.
The Backpack WiFi Access Point (or Home WiFi, if you enabled it) will activate.
Home WiFi
With your Home Network SSID and Password set, when you activate the WiFi mode via the Lua script (WiFi Connectivity -> Enabled Backpack WiFi), the Backpack will try to connect to your Home WiFi Network. Once connected, you can access the Web Update page via http://elrs_txbp.local/ and upload your firmware there.
If you are NOT using Home WiFi, connect to the ExpressLRS TX Backpack WiFi access point (password is expresslrs) and navigate your browser to http://10.0.0.1/.
If you ARE using Home WiFi, navigate your browser to http://elrs_txbp.local/.
In the Configurator, select the WIFI option under Flashing Method.
Ensure you have completed the steps in the Setup section above, then click Flash on the ExpressLRS Configurator.
Wait for the process to complete and you should see the green Success notification.
Alternatively, you can build the firmware file, then drag it to the WebUI. To do this, ensure you have completed the steps in the Setup section above, then click Build on the ExpressLRS Configurator.
Grab the built firmware.bin.gz (do NOT extract it) and drag-and-drop it into the File Upload section of the webpage. If you are using an ESP32 based Backpack, the filename may be firmware.bin. Drag-and-drop it into the File Upload section of the webpage.
Click Update. Wait a bit (~10s) for the \"Update Success! Rebooting...\". The AP should automatically disappear and disconnect.
WiFi ESP"},{"location":"hardware/backpack/backpack-tx-setup/#flashing-via-wifi-older-namimnorc-gen1-tx-modules","title":"Flashing via WiFi (older NamimnoRC Gen1 TX Modules)","text":"
For the First Generation NamimnoRC TX modules (No OLED), you will have to first Build the Backpack firmware. Once built, grab the backpack.bin file from the folder that the ExpressLRS Configurator opened. Open the URL http://elrs_tx.local on your browser and scroll down to where the WiFi Backpack Firmware Update section is (shown in the image below). If the page isn't loading, make sure you have followed the Wifi Flashing guide for these modules (see Flashing Guide).
Wifi Backpack
Wait for a bit (~10s) after the message \"Update Success! Rebooting...\" appears before you power-cycle the module. Your TX Backpack should now be ready.
"},{"location":"hardware/backpack/backpack-tx-setup/#flashing-via-etx-passthrough","title":"Flashing via ETX Passthrough","text":"
Applies to: Internal ExpressLRS TX modules, e.g. RadioMaster Zorro TX Backpack, RadioMaster TX16S Backpack, etc.
FYI
This method is the result of the collaborative effort between EdgeTX, RadioMaster, and ExpressLRS.
With your handset turned on, connect a USB data cable to the USB data port of the Radio.
Select USB Serial(Debug) or USB Serial(VCP) in the options window that pops up.
In the Configurator, select the EdgeTXPassthrough option under Flashing Method.
Ensure you have completed the steps in the Setup section above, then click Flash on the ExpressLRS Configurator.
Wait for the process to complete and you should see the green Success notification.
Unplug the USB from the handset and you're set!
"},{"location":"hardware/backpack/backpack-tx-setup/#how-to-check-you-have-updated-the-tx-backpack-firmware","title":"How to check you have updated the TX Backpack Firmware?","text":"
Make sure you set the jumpers or DIP switches on your modules (if required, e.g. the Happymodel TX Modules) to the Normal Operation position (refer to the top of this page). This allows the main ESP32 chip to talk to the Backpack chip. The Backpack will NOT work properly if the DIP switches or jumper pins are not in the Normal Operation position.
Attention
Change the position of the DIP switches or jumper pins to Normal Operation if required for your module (e.g. Happymodel TX modules).
Navigate to the WiFi Connectivity folder of the ExpressLRS Lua script and select Enable Backpack WiFi. Scan for Access Points, and ExpressLRS TX Backpack should appear. Connect to it and point your browser to http://10.0.0.1/.
If you have set your Home Network SSID and Password, point your browser to http://elrs_txbp.local/.
The main banner will show you what kind of device it is and the firmware version that's flashed into it.
"},{"location":"hardware/backpack/backpack-tx-setup/#setup-your-vrx-backpack","title":"Setup your VRX Backpack","text":"
Proceed to the VRX Backpack Setup section to setup your VRX Backpack, if desired.
The Backpack Usage section provides further details on ExpressLRS Backpack Operation, including Binding, LED Status codes, and more.
"},{"location":"hardware/backpack/backpack-vrx-setup/","title":"VRx Backpack Setup","text":""},{"location":"hardware/backpack/backpack-vrx-setup/#flashing-methods-for-backpack-device","title":"Flashing Methods for Backpack Device:","text":"
Before wiring up your VRX Backpack into your VRX Module, you MUST first flash the VRX Backpack firmware, either via WiFi or UART/FTDI.
Good VRX Backpack candidates are the EP1 or EP2 receivers from Happymodel as these have Boot pads instead of Boot buttons. The Boot pad will be repurposed for the SPI Clock signal from the VRX module.
The VRX firmware you will flash into your Backpack Device will depend on what VRX module you want to connect it to. If you do not flash the correct firmware, it will not work properly.
"},{"location":"hardware/backpack/backpack-vrx-setup/#flashing-via-wifi-esp-based-expresslrs-receivers","title":"Flashing via WiFi (ESP-based ExpressLRS Receivers)","text":"
Power up your selected VRX Backpack device (connect 5v and GND pads to any 5v power source). Let it go into WiFi Update mode (fast blinking LED) and load up the WiFi Update page. In the Address bar of your browser, add ?force=true to ensure it will accept the VRX Backpack firmware. The resulting URL should read http://10.0.0.1/?force=true (if you connected via Access Point) or http://elrs_rx.local/?force=true (if your device has connected to your local WiFi network).
Note
The ?force=true is not needed for ESP-based receivers with factory firmware. It is only required if you have previously flashed the receiver and want to repurpose it as a VRX Backpack.
Go to the Assets section of the Backpack Release on GitHub, Download the binary suited for your VRX module. Upload this binary into the VRX device using the Web Update page. Wait (~30s) until the LED on the VRX device has turned on again.
Alternatively, you can use the ExpressLRS Configurator to create your binaries for you. Build your binary, with the set binding phrase (Optional) as well as Home Network SSID and Password (Optional; available starting 0.2.0). Upload the resulting binary on the WiFi Update page as outlined above.
"},{"location":"hardware/backpack/backpack-vrx-setup/#flashing-via-uartftdi","title":"Flashing via UART/FTDI","text":"
Note
This method is best used for the DIY ESP01F VRX Backpacks, as these devices do not have any firmware from the factory.
Connect your FTDI RX pin into the TX pad of your VRX Device, and the FTDI TX pin into the RX pad of the VRX Device; then the 5V and GND pads. The Boot pad needs to be bridged with the Ground pad. Connect your FTDI, with the connected VRX device, into a free USB port (VRX Device's LED should light up SOLID). Using the ExpressLRS Configurator, select your VRX module, select the via UART method and set your binding phrase (Optional) and the Home Network SSID and Password (Optional; Available starting 0.2.0). Click Build and Flash and the compiling and flashing should commence. If done right, the Success bar should appear and your VRX Backpack should now be ready for wiring into your selected VRX Module.
"},{"location":"hardware/backpack/backpack-vrx-setup/#flashing-tbs-fusion-for-the-first-time","title":"Flashing TBS Fusion for the First Time","text":"
You will need an FTDI dongle (USB to UART Bridge) to flash the VRX Backpack firmware into your TBS Fusion module for the first time. You will also have to follow the TBS Fusion WiFi Module Unbricking Guide but instead of uploading the WiFi Firmware file from TBS, you will upload the VRX Backpack Firmware that the ExpressLRS Configurator compiled from Build.
Any subsequent firmware updates can be done via WiFi.
"},{"location":"hardware/backpack/backpack-vrx-setup/#starting-with-020-you-can-also-update-via-your-home-wifi","title":"Starting with 0.2.0, you can also Update via your Home WiFi","text":"
With your Home Network SSID and Password set, when you activate the WiFi mode via the Lua script (WiFi Connectivity -> Enabled VRX WiFi), the Backpack will try to connect to your Home WiFi Network. Once connected, you can access the Web Update page via http://elrs_vrx.local/ and upload your firmware there.
The ExpressLRS Configurator will also detect the device after it has been connected. It will be listed in the \"Device List\" section, and you can press SELECT, so that the correct target is automatically selected for Build.
Alternatively, you can also Build and Flash via the Configurator through WiFi without having to access the Web Update page (just like any ESP-based ExpressLRS receiver).
"},{"location":"hardware/backpack/backpack-vrx-setup/#vrx-module-setup-before-wiring-it-all-up","title":"VRX Module Setup Before Wiring It All Up","text":"
IMPORTANT: You will need to set your VRX module to the highest band and channel it can go, usually Race 8 (5917MHz) before wiring up any VRX Backpack. This is to ensure the VRX Backpack knows \"where it is\" in the selectable channels.
"},{"location":"hardware/backpack/backpack-vrx-setup/#connecting-the-vrx-backpack-to-your-vrx-module","title":"Connecting the VRX Backpack to Your VRX Module","text":"
Currently supported VRX Modules include:
ImmersionRC Rapidfire
SkyZone SteadyView
Generic RX5808 Module
FENIX Module
Shark Byte RX5.1 HDZero Module
VRX Backpacks communicate with these modules via SPI, and require 3 signal lines: CLK, DATA, CS. Additionally, depending on your VRX Backpack, they will either need 5v (ExpressLRS ESP-based Receiver) or 3.3v (ESP01F module) and of course the GND line.
For the ESP01F Module, you will have to source out a voltage regulator such as an AMS1117 (1A Low Drop-out Voltage Regulator) which will lower the 5V voltage from the VRX module to the needed 3.3v.
The VRX has an easily accessible UART on the main board, which is accessed by removing the 4 screws which secure the back plate. Use the goggle mount to pull the back plate from the housing.
Solder your VRX backpack as shown below:
It is unlikely that you can close the back plate with the backpack module between the plate and the main board. There are two solutions:
Route the wires out of the cooling vents and mount them externally
Mount the backpack in the front patch, routing the wires through the goggle mount as shown below:
Make sure that your RX5808 is running in SPI mode. Then wire it up as shown below:
"},{"location":"hardware/backpack/backpack-vrx-setup/#how-to-check-you-have-updated-the-vrx-backpack-firmware","title":"How to check you have updated the VRX Backpack Firmware?","text":"
Navigate to the WiFi Connectivity folder of the ExpressLRS v3 Lua script and select Enable VRX WiFi. The LED will begin blinking rapidly. Scan for Access Points and ExpressLRS VRX Backpack should appear. Connect to it and point your browser to http://10.0.0.1/.
If you have set your Home Network SSID and Password, point your browser to http://elrs_vrx.local/.
The main banner will show you what kind of device it is and the firmware version that's flashed into it.
"},{"location":"hardware/backpack/backpack-vrx-setup/#setup-your-tx-backpack","title":"Setup your TX Backpack","text":"
Proceed to the TX Backpack Setup section to setup your TX Backpack.
The Backpack Usage section provides further details on ExpressLRS Backpack Operation, including Binding, LED Status codes, and more.
"},{"location":"hardware/backpack/esp-backpack/","title":"Backpack Info","text":""},{"location":"hardware/backpack/esp-backpack/#what-is-a-backpack","title":"What is a Backpack?","text":"
A Backpack is an add-on device that facilitates wireless communication between an ExpressLRS module and another device (e.g. a Video Receiver on your goggles) using the ESPnow protocol.
Communication between an ExpressLRS module and a Video Receiver"},{"location":"hardware/backpack/esp-backpack/#usage-scenario","title":"Usage Scenario","text":"
You are setting up to fly with others, and your favorite video channel is already in use. You're asked to use R2 as that's the vacant one. Using the ExpressLRS Lua script, you change the setting into R2 (this while your aircraft is still unpowered). You power up your goggles equipped with a VRX Backpack. Then plug in your aircraft. Upon the establishment of the connection, the VTX and the VRX are automatically set to R2. You're now ready to fly. No fiddling with channels on the OSD or your goggles.
"},{"location":"hardware/backpack/esp-backpack/#okay-im-sold-what-do-i-need-to-get-this-working","title":"Okay, I'm sold. What do I need to get this working?","text":"
You already have the majority of the hardware needed. Most of the ESP-based ExpressLRS modules come with the TX Backpack. For the VRX Backpack, you can reuse any ESP-based ExpressLRS receiver (recommended are the EP1/EP2 receivers as they have boot pads, instead of boot buttons), or for a complete DIY route, you'll need an ESP-01F module.
An off-the-shelf VRX Backpack has also appeared from Happymodel: the EP82
See the tables below for a partial list of supported devices:
Backpack Requirement
All new ExpressLRS TX releases after October 10th, 2023 require a TX backpack to be integrated into the hardware
"},{"location":"hardware/backpack/esp-backpack/#supported-tx-backpack-targets","title":"Supported TX-Backpack Targets","text":"TX Module Support Happymodel ES24TX Pro \u2714\ufe0f Fully supported Happymodel ES24TX \u2714\ufe0f Fully supported Happymodel Slim Pro \u2714\ufe0f Fully supported Happymodel Slim Ironman \u2714\ufe0f Fully supported Happymodel Slim T-Lite \u2714\ufe0f Fully supported Happymodel ES900TX \u2714\ufe0f Fully supported Happymodel ES915TX (STM32 version) \u274c Not compatible FrSky R9M \u2714\ufe0f Supported with the addition of an ESP8285 FrSky R9 (all others) \u274c Not compatible NamimnoRC Flash (STM32 version) \u2714\ufe0f Fully supported NamimnoRC Flash OLED(ESP version) \u2714\ufe0f Fully supported NamimnoRC Voyager (STM32 version) \u2714\ufe0f Fully supported NamimnoRC Voyager OLED(ESP version) \u2714\ufe0f Fully supported Axis Flying THOR \u2714\ufe0f Fully supported HGLRC Hermes \u274c Not compatible BETAFPV 2.4 Micro TX 1W \u2714\ufe0f Fully supported BETAFPV 2.4 Micro TX 500mW \u274c Not compatible BETAFPV 900 Micro TX \u274c Not compatible RadioMaster Zorro \u2714\ufe0f Fully supported RadioMaster Pocket \u2714\ufe0f Fully supported Jumper Aion T-Pro Internal \u274c Not compatible Jumper Aion Nano \u274c Not compatible Vantac Lite \u274c Not compatible ImmersionRC Ghost TX \u274c Not compatible QuadKopters 2.4 TX \u274c Not compatible SIYI FM30 \u274c Not compatible DIY TX \u2714\ufe0f Fully supported with the addition of an ESP8285"},{"location":"hardware/backpack/esp-backpack/#supported-vrx-backpack-targets","title":"Supported VRX-Backpack Targets","text":"Backpack Target Compatibility Tested? Happymodel EP1/EP2 \u2714\ufe0f Compatible Yes Happymodel ES900RX \u2714\ufe0f Compatible Yes Happymodel EP82 \u2714\ufe0f Compatible Yes BETAFPV Nano 2.4 \u2714\ufe0f Compatible No Flywoo EL24E \u2714\ufe0f Compatible No Flywoo EL24P \u2714\ufe0f Compatible No Ghost ATTO \u274c Not compatible N/A HappyModel PP \u274c Not compatible N/A HGLRC 2400RX \u2714\ufe0f Compatible No JHEMCU / HiYOUNGER EP24S \u2714\ufe0f Compatible No JHEMCU / HiYOUNGER SP24S \u2714\ufe0f Compatible No JHEMCU / HiYOUNGER RX24T \u2753 Unsure No Matek R24-S \u2714\ufe0f Compatible No Matek R24-D \u2714\ufe0f Compatible No Jumper Aion RX \u2714\ufe0f Compatible No Vantac 2.4GHz RX \u2714\ufe0f Compatible No Namimno Flash (ESP) \u2714\ufe0f Compatible No QuadKopters Nano \u2714\ufe0f Compatible No SIYI FR Mini \u274c Not compatible N/A"},{"location":"hardware/backpack/esp-backpack/#video-receivers-currently-supported-include","title":"Video Receivers currently supported include:","text":"VRX Module Support ImmersionRC Rapidfire \u2714\ufe0f Fully supported (Versions 1.2.5 of the rapidFIRE firmware and later) SkyZone SteadyView \u2714\ufe0f Fully supported TBS Fusion \u2714\ufe0f Fully supported (FTDI needed) Generic RX5808 Module (some) \u2714\ufe0f Fully supported FENIX Module \u2714\ufe0f Fully supported HDZero VRX4 \u2714\ufe0f Fully supported HDZero Goggles (built-in, no mods required) \u2714\ufe0f Fully supported"},{"location":"hardware/backpack/esp-backpack/#im-ready-to-proceed-what-do-i-do-next","title":"I'm Ready to Proceed. What do I do next?","text":"
If your TX module is already equipped with a TX backpack (see list above), your next step is to update the firmware of the backpack. Proceed to the TX Backpack Setup page for more details.
If you're using a DIY TX module and want to add a backpack to it, proceed to the Backpack Wiki.
For the VRX Backpack, you will need to first update the firmware on the ESP device. The firmware will highly depend on which VRX module you will use it on. Proceed to VRX Backpack Setup page for more info.
"},{"location":"hardware/backpack/esp-backpack/#backpack-usage","title":"Backpack Usage","text":""},{"location":"hardware/backpack/esp-backpack/#led-status-codes","title":"LED Status codes","text":"
Solid - The backpack is powered up and ready to receive packets.
Fast Continuous Blinking - WiFi Mode is active, and either the Access Point is ready for connection or the Backpack has connected to your Local WiFi Network (0.2.0; Home Network SSID and Password have been set).
Double Blink, Pause - The Backpack is in Binding Mode. Using the ExpressLRS Lua Script, press Bind, and the TX Backpack should bind with the VRX Backpack.
Pressing and Holding down the button during Power Up puts the device into Bootloader mode. From here, you can flash the firmware via UART using an FTDI dongle (USB to UART Bridge). The LED on the Backpack device will be SOLID when in this mode.
A Single Press during Normal or Binding mode will put the device into WiFi Mode.
A Single Press during WiFi Mode will put back the device into Normal Mode.
Just like any ExpressLRS device, you can set a Binding Phrase for both the TX Backpack and VRX Backpack so they automatically bind with each other during power up. This Binding Phrase can be the same as what you used with your other ExpressLRS devices or can be entirely different. The concept is the same.
Should you choose to bind manually, the procedure is as follows:
Make sure you didn't flash the VRX firmware with a Binding Phrase.
Power Cycle the VRX Backpack 3 times every ~30s. This interval gives ample time for your goggles and VRX module to power up and down more gracefully. If your VRX Backpack has a button, it can also be used to power-cycle the device by cycling between WiFi Mode and Normal mode 3x (as WiFi mode reboots the device).
The LED on the Backpack should now blink twice followed by a brief pause, then repeats, indicating it is in Binding Mode.
Using the ExpressLRS Lua script, navigate into the Bind option. Press it once, and the LED on both Backpacks should blink once and stay SOLID thereafter.
Your Backpacks are now bound and connected, and you can now use VTX Administrator on the ExpressLRS Lua script to sync your VTX and VRX modules.
When in Binding Mode (Double Blink & Pause) and no Bind packets have been received within 120s, the VRX Backpack will switch into WiFi Mode. This provides the users a means to enter WiFi Mode when their VRX Backpack doesn't have a Button.
"},{"location":"hardware/backpack/hdzero-goggles/","title":"HDZero Goggle VRx Backpack","text":""},{"location":"hardware/backpack/hdzero-goggles/#flashing-the-hdzero-goggles-backpack","title":"Flashing the HDZero Goggles Backpack:","text":"
After building the VRX firmware, copy the following 4 files into a folder named ELRS on the root of the SD card: - firmware.bin - partitions.bin - bootloader.bin - boot_app0.bin
Insert the SD card into the goggles and boot the goggles as normal.
The first step is to ensure that you have the backpack enabled in the Connections page in the goggles.
Scroll down to the Firmware page and select the Update ESP32 option.
The 4 firmware files will be flashed to the ESP32 backpack, and you should see a progress bar with the name of the current file being flashed at the start.
When the upload has completed, the page will display the version (or branch) of backpack firmware that is installed next to the update button.
To start the WiFi endpoint on the backpack, navigate to the Connections page of the goggles UI and select the Start Backpack WiFi option. If you have configured your backpack with your home WiFi credentials, it will attempt to connect to that and will fallback to creating an access point if it cannot connect, with the name ExpressLRS VRX Backpack and password expresslrs. The web UI will be available as http://elrs_vrx or http://elrs_vrx.local.
"},{"location":"hardware/backpack/hdzero-goggles/#binding-to-your-transmitter","title":"Binding to Your Transmitter","text":"
Attention
Since the goggles have a bind button in the Connections page in the UI, the option to enter binding mode by power-cycling 3x to bind has been disabled.
If you entered the same binding phrase as on your TX module and TX backpack when building the goggle backpack firmware, your device will connect automatically. You can validate this looking at the UID next to the Start Backpack Binding button on the Connections page in the goggle UI.
If you have NOT entered your binding phrase into ExpressLRS Configurator when building your backpack firmware, you can use the Start Backpack Binding option in the Connections page in the UI. Once you have selected this option, the goggles will wait for a bind message from your transmitter. To perform the bind from the transmitter, load the ExpressLRS Lua Script on your radio handset and select the [Bind] option there. When the message is sent and the goggles have received the bind message, they should display Success in place of the button text. If they do not receive a bind message, they will timeout after 2 minutes and display a Timeout message.
You can validate the binding by navigating to the Connections page and verifying that the correct UID is displayed next to the Start Backpack Binding button.
20x20 footprint and uses 0805 size SMD components. SMD components have been positioned on the PCB in a soldering iron friendly way. \ud83d\udeb8
ELRS Nano
The ELRS Nano RX is 18mm x 11mm and uses the same pinout as the Crossfire Nano RX. This allows for direct mounting to compatible flight controllers. \u26a0\ufe0f This PCB uses 0402 SMD components and will require a hot air rework station and probably a microscope. \ud83d\udd2c
Uses the ESP-01F for WiFi and a RFM95 for our business \ud83d\udd74\ufe0f
Requires ordering PCBs from Gerber files, a regulator chip, a few passives, a ESP-01F and a RFM95 (915/868MHz)
Multiple RX PCB designs are available \u2705
20x20 RX
discrete SMD antenna for Wifi and RF directly soldered to PCB
Target DIY_900_RX_ESP8285_SX127x_via_UART
20x20 RX 0805 - easier to build due to bigger SMD parts. PCB antenna for Wifi and u.fl connector for RF
Mini RX - the smallest form factor, lightest weight and lowest cost per PCB
If you need help soldering, please check out this video
"},{"location":"hardware/special-targets/diy-rx/#flashing-custom-rx","title":"Flashing Custom RX","text":""},{"location":"hardware/special-targets/diy-rx/#before-you-start","title":"Before you start","text":"
The steps for building are in each individual README.md for the RX of your choice
If you are using an ESP-12F instead of ESP-01F it is recommended to follow this tutorial but use the appropriate RX target \ud83e\uddd1\u200d\ud83c\udfeb
"},{"location":"hardware/special-targets/diy-rx/#get-it-flashed","title":"Get it flashed","text":"
Connect the serial adapter to GND, TX, RX, and the appropriate 3V3 or 5V.
Additionally, connect IO0 to GND to activate the bootloader and enable flashing
Quite some serial adapters have TX and RX swapped, mislabeled, or both \ud83d\ude38. Please double-check!
Finally, select the appropriate RX target, make sure your user defines are correct, and press Upload in PlatformIO
Possibly one of the biggest benefits of using ExpressLRS is custom hardware!
\ud83d\udcf6 Custom ESP 2.4 GHz TX
\ud83d\udce1 Custom Super Slim ESP 2.4 GHz TX
\u26a1 Custom 900 MHz TX
"},{"location":"hardware/special-targets/diy-tx/#custom-esp-24-ghz-tx-for-jr-module-bay","title":"Custom ESP 2.4 GHz TX (for JR module bay)","text":"
All of the info on this topic can be found here
"},{"location":"hardware/special-targets/diy-tx/#custom-super-slim-esp-24-ghz-tx-for-lite-module-bay","title":"Custom Super Slim ESP 2.4 GHz TX (for lite module bay)","text":"
The super slim is an evolution of the slim. It uses the same base hardware as the JR size one. It's the same size as an R9M Lite, and fits in all handsets with a lite module bay such as the X-Lite, X9 Lite, and Tango 2 (with the proper adapter). The rest of the info can be found here
"},{"location":"hardware/special-targets/diy-tx/#custom-900-mhz-tx-not-built-anymore","title":"Custom 900 MHz TX (not built anymore)","text":"
In the beginning, 900 MHz transmitters were sometimes built DIY. Today they're not. If you have one, the max output power defaults to 100mW, but with UNLOCK_HIGHER_POWER, that can be increased to 250mW.
PlatformIO is a prerequisite for developing custom hardware.
The hardware pinouts for ExpressLRS are kept at ExpressLRS/targets. Clone this repo within src/ of your ExpressLRS/ExpressLRS repo - or, if you run a build, it'll happen automatically.
In the RX and TX directories, you can find the pinouts and configuration for different layouts stored as JSON files.
Within targets.json, there are listed all the possible build targets for ExpressLRS.
To access your target's configuration, you must add a new entry to the targets.json file - mimic the closest existing one and change the values to match your hardware. It's critical the firmware field match your processor.
Select the matching build target from PlatformIO:
After you run a build, you should be met with a hardware configuration selector and your new configuration!
The Nuclear RX is designed to be as small as possible, using the same software target as the DIY Nano RX, and assembled by JLCPCB. It uses the 2400MHz band and the ExpressLRS firmware.
20x20 stack mounting with break-off tabs for compact applications
SMD Antenna
WiFi updating
Up to 500Hz packet rate
When you get your Nuclear RX, it will likely be on the latest release firmware. You'll probably have to update it to work with your TX. To update, follow the steps in the WiFi updating page. Alternatively, you can use betaflight passthrough should work, but the boot jumper must be bridged while applying power to the RX.
When building, use one of the DIY_2400_RX_ESP8285_SX1280_via_X targets. To use via_wifi, put your RX in binding mode, connect your computer to the RX WiFi, and hit upload.
LED Status Blinking Slowly Waiting for Connection Fast Double Blink Binding Mode Super Fast Blink WiFi Updating Mode Solid On Connected
If for some reason the RX needs to be in boot mode, bridge the jumpers as shown here:
The Nuclear TX is designed to be the same size as a FrSky slim module and use the same software target as the DIY Slim TX. It uses the 2400MHz band and the ExpressLRS firmware. There is also a case that fits a full size JR module bay with the same PCB.
If you ordered a Nuclear TX that wasn't fully assembled, these steps should help you finish it.
"},{"location":"hardware/special-targets/nuclear-hardware/#print-a-case","title":"Print a case","text":"
The latest version of the Nuclear TX STL files can be found here. Print the pieces in the orientation in the image and use support. Tree support in Cura works great. Keep in mind that PLA may melt if left in a hot car or in direct sunlight.
Slap it together as seen below. Solder the wires to the pin header in the order in the picture, then slide it in from the outside. The header should press in with a little force. Add some glue on the inside to keep it from sliding out when removing it from your handset. Put the SMA pigtail in the hole in the top and screw it down. Use a wrench to make sure it doesn't come loose when you screw on your antenna. Plug the U.FL into the module and route it under, and loop up around the side.
When you get your Nuclear RX, it will likely be on the latest release firmware. You'll probably have to update it to work with the RX you have. To update, follow the steps in the WiFi updating page. If your transmitter module ever becomes bricked from a bad upload, connect it with a serial adapter as shown here. MAKE SURE THE ADAPTER IS SET TO 3.3V; 5V WILL KILL THE MODULE! Use tweezers or solder to bridge the boot jumper while you power on the module to put it in boot mode. Use the target DIY_2400_TX_ESP32_SX1280_E28_via_UART.
Note
The version of the boards with the 6-pad layout for programming has the TX and RX named backward. The actual order of the pins is TX, RX, 3V3, GND, GND.
In normal state, the top right corner of the LUA will display - or C for RX connection status. in Warning or Critical Warning, the top right corner of the LUA will display a number to debug. As the LUA title will only show the current most critical warning only.
Converting the number on the top right corner to bits, you can decode the on going warnings.
Bit Status Solution 0 RX connection status connect a RX with TLM ratio other than Off 1 Reserved Status 2 Model Mismatch Warning set ModelMatch to Off or Select/Set the correct Model ID 3 Armed Status LUA should be closed to maximize sent Stick Command 4 Reserved Warning 5 Not While Connected Do not change this parameter when connected to a RX 6 Reserved Critical Warning 7 Reserved Critical Warning"},{"location":"info/advance-technical-info/#debug-logging","title":"DEBUG Logging","text":"Defines Description -DDEBUG_LOG Turn on debug messages, if disabled then all debugging options (starting with DEBUG_) are disabled -DDEBUG_LOG_VERBOSE Use DEBUG_LOG_VERBOSE instead (or both) to see verbose debug logging (spammy stuff) -DDEBUG_RX_SCOREBOARD Print a letter for each packet received or missed (RX debugging) -DDEBUG_CRSF_NO_OUTPUT Don't send RC messages over UART -DDEBUG_BF_LINK_STATS These debugging options send extra information to Betaflight in the LinkStatistics packet"},{"location":"info/glossary/","title":"Glossary","text":""},{"location":"info/glossary/#technical-words-with-explanations","title":"Technical words with explanations","text":"
Below you can find a list of terms you might not be sure about, as well as some common abbreviations:
BL: Bootloader, loads the FW
CRSF: TBS Crossfire, more specifically in our case most often referring to the communication protocol between TX and TX module and RX and FC respectively
ESC: Electronic Speed Controller
FC: Flight Controller
FW: Firmware
LQ: Link Quality, percentage of expected packets received. Our preferred method of measuring the quality of the control link
Lua: Means \"Moon\" in Portuguese. As such, Lua is the correct way to write and not all uppercase. The ExpressLRS Lua script can be installed on a OpenTX radio, to easily alter TX parameters like Packet rate, Telemetry ratio and Output power. But also shows if the radio (OpenTX) is communicating correctly with the module. ( e.g. 0:50, 0:150, 0:200 and so on.)
MCU: Micro Controller Unit, generally denotes an embedded system controller as opposed to big iron CPU
OSD: On Screen Display, refer to this page for instructions for setup in BF
OTA: Update your device Over The Air (WiFi)
OTX: OpenTX
RSSI: Received Signal Strength Indicator, \"arbitrary\" scaled version of RSSI dBm or LQ. Signal Health: LQI and RSSI Explained
RSSI dBm: Measure of power level measured in dBm. Basically, how strong the signal being received is
S.Port: SmartPort, sometimes referred to as sport. FrSky \"telemetry\" protocol. The S.Port also gets used for updating FrSky receivers.
To be continued.
"},{"location":"info/init-rate/","title":"Init Rate","text":""},{"location":"info/init-rate/#what-happened-to-the-lua-init-rate-option","title":"What happened to the Lua Init Rate option?","text":"
The Init Rate receiver Lua option was removed in ExpressLRS 3.4 in favor of automatic Init rate storage.
"},{"location":"info/init-rate/#what-is-init-rate","title":"What is Init Rate?","text":"
On boot, the receiver will listen for the Sync Packet starting with the fastest RF Mode or Packet Rate, down to the slowest, then cycles, until it finally Syncs and Binds. The Initialization Rate controls the packet rate that the receiver will start checking for the Sync Packet which can allow for near-instant connection when the receiver is powered up.
However, when the receiver is connected, it can not save its configuration without failsafing, which leads to a problem of how to store the connected rate as the Init Rate for use next power up. Unfortunately, this means you must failsafe the receiver once to configure its Init Rate.
"},{"location":"info/init-rate/#setting-init-rate","title":"Setting Init Rate","text":""},{"location":"info/init-rate/#method-1-switch-to-rate","title":"Method 1: Switch To Rate","text":"
Power on both a receiver and transmitter and wait for them to connect on any packet rate.
On the transmitter, select the packet rate to set the receiver's Init Rate to.
NOTE the packet rate must actually change for the setting to be sent. This means changing away from, then back to the desired packet rate if already connected at the desired rate.
The receiver briefly failsafes when changing packet modes and will save the target rate.
The receiver will now boot at the selected rate on next boot.
"},{"location":"info/init-rate/#method-2-transmitter-power-off","title":"Method 2: Transmitter Power Off","text":"
Power on the transmitter and select the packet rate to set the receiver's Init Rate to.
Power on the receiver and wait for it to connect. The LED on the receiver should be on solid / not blinking.
Power off the transmitter with the receiver still connected, bypassing any EdgeTX warnings along the way.
The receiver should failsafe and the LED will start blinking again.
The receiver will now boot at the selected rate on next boot.
"},{"location":"info/long-range/","title":"Long Range Competition","text":"
One of the most frequently asked questions that are asked by people who are interested in, but haven't yet tried ELRS is \"How far does it go, and at what power level?\"
The following table is a leaderboard of the current record holder for each packet rate, and the longest distance from home. Note that not every flight resulted in a failsafe at max range, so the link could go further in some cases. The leaderboard is separated into two different tables: 2.4GHz, and 900MHz. A leaderboard entry will only stay if it is the \"best\" for any specific packet rate, be it via power, range, or craft type.
To enter, press the pencil in the upper right corner of this page, and enter your record's info into the table, sorted by distance, and then PR it into the docs repository,
Anyone can add an entry to the table, and entries should include the:
Max distance from home
RF freq (900MHz / 2.4GHz)
Packet rate
Power level
If the link failsafed at max range
The pilot name
A link to your DVR on youtube
2.4 GHz Rankings900 MHz Rankings Max Dist. (km) Packet Rate (Hz) TX Power (mW) Type Failsafe at Max Range? Pilot Handle Link to DVR 101.3 50 2000 Wing No Snipes Link 43.7 150 250 Wing No Slickshot Link 40.6 50 25 Wing No Shawn U Link 35.0 250 100 Wing No Snipes Link 20.0 150 100 Wing Yes Pairan Link 18.9 150 50 Wing yes TitanDynamics Link 17.1 50 10 Wing No Denks Link 12.2 500 250 Wing No B\u00f6rner Link 10.2 500 10 Quad Yes mrscythe Link 10.0 50 250 Quad No Disnator Link 7.1 500 100 Wing No Bri'ish Link 7.0 150 50 Quad No Taufik Link 5.0 250 500 Quad No ZoFPV Link 4.6 50 25 Quad No febbyeka Link 3.0 150 25 Quad No Taufik Link Max Dist. (km) Packet Rate (Hz) TX Power (mW) Type Failsafe at Max Range? Pilot Handle Link to DVR 50.1 25 500 Wing No Yarillo Link 40.7 50 10 Wing No Leslie Yagin Link 13.1 50 100 Quad No Taufik Link 10.0 100 100 Wing No Flight Cub Link 6.0 100 50 Wing No Snipes Link 5.0 200 50 Quad No S0L4R Link 2.2 50 10 Quad No Mike Malagoli Link"},{"location":"info/signal-health/","title":"Signal Health","text":"
RSSI has become somewhat a generic term for how good a signal is, and every manufacturer can have their own scale, with most agreeing that \"100\" is the best, less than that is bad, and expect have RXLOSS at ???. This is an explanation of the signal metrics provided by ExpressLRS and how to understand their values.
"},{"location":"info/signal-health/#two-types-of-signal-health","title":"Two Types of Signal Health","text":"
There are two main types of signal information available from ExpressLRS: RSSI and LQI
RSSI - Received Signal Strength Indicator, this value indicates how loud \ud83c\udfba the reception is. RSSI must be above the sensitivity level to be understood. Units are dBm and start from 0 and go down as the volume gets lower (-130dBm hard limit).
LQI - Link Quality Indicator, this value indicates how much of the conversation is being understood and ultimately all that matters. Units are percent, with 100% being every packet is received, and 0% means no packets are being received.
Consider you're having a conversation in a quiet room. Your partner speaks loudly enough for you to hear, so the RSSI of their voice is above the sensitivity of your ears. You're going to understand the conversation because you're hearing every word. That's a 100% LQI-- you're receiving 100% of the words. Now imagine someone blows an air horn right in the middle of a sentence. The RSSI is still the same level, you still hear what you could make out at the same volume, you missed a word so the LQI is lower. The closer the volume of the conversation is to the background noise level in the room, the greater the chance is that you'll miss a word due to it getting mixed in with the background noise and lowering your LQI. Remember, LQI is all that matters. Your partner could shout as loud as they want but if you could hear every word anyway, the volume doesn't matter, you always heard every word.
"},{"location":"info/signal-health/#which-do-i-care-about","title":"Which do I care about?","text":"
Both really. LQI is most important because you can't fly if you're not getting packets. RSSI is important because it tells you how close you are to the radio receiver not being able to receive packets at all. I'd say if you have just one, pick LQI, because that tells you what percentage of packets are getting through and you get to make the decision if it isn't enough. What you can't tell from LQI alone is when that number is going to drop off a cliff, and it could happen extremely fast because you hit the RSSI sensitivity limit.
This is the lowest theoretical RSSI value that can be distinguished by the radio receiver. It is displayed next to the packet rate in the ELRS.lua script, as different packet rates and frequency bands have different sensitivity limits. Lower rates are more sensitive, -123dBm for 25Hz 915MHz up to -105dBm for 500Hz 2400MHz. This gives you the limit you know you can't fly below.
A sensible warning value is 5-10dBm higher than the sensitivity limit shown in the RF Mode Indexes (e.g. 250Hz=-108dBm, so -103dBm to -98dBm for the alarm).
RSSI and LQI are included already in the protocol used to communicate to the flight controller, so the \"RSSI Channel\" on the Receiver tab should be set to Disabled. RSSI_ADC / \"Analog RSSI input\" on the Configuration tab should also be disabled.
RSSI dBm - This is the true RSSI value we've talked about here, and is available on Betaflight after 4.1 (?) and iNav after 2.6 (?)
Link Quality - This is LQI discussed here, and has the same version requirements. Betaflight and iNav (LQ TYPE2 option) display add the RF Mode to this as well, e.g. 7:100 means mode 7 = 250Hz and 100% LQI.
RSSI Value - Or sometimes just RSSI. This is the old undefined units of Signal Strength value that everyone is used to with no idea what value is good or what value is too bad. What value you'll actually see here varies, even on ExpressLRS, and is covered in the RSSI Value OSD field section. It is not recommended to use this field unless you have to (e.g. DJI).
"},{"location":"info/signal-health/#rssi-value-osd-field","title":"RSSI Value OSD field","text":"
What appears in the RSSI Value field is based on what is selected as the RSSI Channel as ExpressLRS also sends LQI and RSSI as channels (AUX11/ch15 and AUX12/ch16 respectively). It is better to use the dBm or LQ OSD fields instead of this one if you can. DJI users are forced to use this due to it being the only field supported by their OSD. Changes to RSSI Channel in Betaflight requires a reboot to take effect.
Disabled is set as the \"RSSI Channel\" field in Betaflight - Displays RSSI dBm scaled as a percentage from -130dBm to 0dBm. Not recommended since what percentage of 130 is the Sensitivity Limit for your selected rate? Math!
AUX11/ch15 is set as the \"RSSI Channel\" - Simply LQI although the value might be slightly off due to rounding.
AUX12/ch16 is set as the \"RSSI Channel\" - Displays the RSSI dBm scaled as a percentage from the current Sensitivity Limit to -50dBm and is a decent indicator of how much range is left before the LQI cliff (0 here = Sensitivity Limit).
In iNav, the RSSI Value on the OSD is called RSSI (Signal Strength), and will always display 0. To show a filtered (by iNav) LQI in that field, set the rssi_source to protocol using the CLI with set rssi_source = PROTOCOL.
OSDs report the packet rate using an index instead of the actual rate, either as a RATE:LQ% or with rate in the hundreds digit such as 799 where 7 is the RATE and 99 is the LQ%. Handsets display the rate using the RFMD telemetry item.
SNR stands for Signal to Noise ratio and compares RSSI dBm to the RF background noise level and is in dB units (not dBm), higher is better. Notice it compares the background noise level and not the Sensitivity Limit. The reported value changes quite a bit from packet to packet and what values are good depend on what packet rate is being used. The RF chip can only approximate the noise level and only registers a value so high above the noise floor leading to this value getting clipped. Add to that, LoRa modulation can actually receive data below the noise floor to some degree.
All FLRC modes (F1000, F500, D500, D250) always report 0 for SNR.
TBS Crossfire I believe reports SNR * 4-- their values can be much higher.
ExpressLRS uses an averaged SNR to control dynamic power, with the following low/high values. The lowest possible SNR a packet can still be received is 5-10dB lower than the \"Raise Power\" limit.
"},{"location":"info/signal-health/#team24","title":"Team2.4","text":"Packet Rate \"Raise Power\" (bad) SNR \"Lower Power\" (good) SNR 500Hz 5.0dB 9.5dB 333Hz Full 5.0dB 9.5dB 250Hz 3.0dB 8.5dB 150Hz 0.0dB 8.5dB 100Hz Full 0.0dB 8.5dB 50Hz -1.0dB 6.5dB"},{"location":"info/signal-health/#team900","title":"Team900","text":"Packet Rate \"Raise Power\" (bad) SNR \"Lower Power\" (good) SNR 200Hz 1.0dB 3.0dB 100Hz Full 1.0dB 3.0dB 100Hz 1.0dB 2.5dB 50Hz 1.0dB 1.5dB D50 1.0dB 3.0dB 25Hz -3.0dB 0.5dB"},{"location":"info/signal-health/#how-far-can-i-go-on-x-mw","title":"How far can I go on X mW?","text":"
Very far? This question is usually used in place of the actual question \"Will I get good signal where I fly?\" which is impossible to answer.
ExpressLRS 2.4GHz can go over 40km at 250Hz 100mW on omnidirectional antennas with excellent LQI, or it can go 400m with less stellar LQI. By far the biggest factor in determining maximum range is direct line of sight. Blocking line of sight reduces RSSI dBm. A few trees or a building isn't going to keep you from flying due to ExpressLRS's excellent sensitivity even when line of sight isn't available, but range is reduced a bit for every physical object between you and the receiver. Piloting from an elevated position can eliminate some ground obstacles and provide a measurable boost in range.
The second largest factor is interference. Interference is the clobbering of our packets by outside sources, such as WiFi on 2.4GHz or other ISM transmissions on 868/915MHz, and is seen as a drop in LQI well before the sensitivity limit. Increasing TX power output is usually not the solution you'd expect, where each doubling in output power only might only add 10% to the usable range due to interference.
"},{"location":"info/signal-health/#team868team915-or-team24","title":"#Team868/#Team915 or #Team2.4","text":"
Unfortunately, there is a misconception about the 2.4GHz range thanks to other radio protocols on the market. ExpressLRS uses LoRa, which has had some amazing results on 2.4GHz. Again, 40km on 100mW 250Hz on 2.4GHz. The advantages of 2.4GHz is that the antennas are 2.5x smaller than 915MHz antennas, and there's more spectrum for ExpressLRS to hop around in, opening up the air for more pilots at once. 868/915MHz does have increased penetration and is the ultimate king of long range flying, but penetration difference may not be as great as you think. The high sensitivity of ExpressLRS receivers allows them to fly places you wouldn't dream of flying FSK-based 2.4 receivers such as FrSky ACCST/ACCESS, FlySky AFHDS2A, Spektrum DMX, or Redpine.
We have all heard the stories of racers powering up his TBS crossfire full module at 2W and causing people to fail-safe during a race. This happens because the 868/915MHz band has limited bandwidth. The solution for this is to use a low power mode during races, so you do not blast anyone out of the sky. 2.4GHz does not have this issue. Flite Test has a world record of having 179 RC airplanes in the sky using 2.4 GHz.
2.4GHz LoRa can also handle WiFi noise very well. Studies have been conducted with the coexistence of WiFi and LoRa bands.
868/915 does not have to worry about WiFi signal but it does have to worry about cell towers and other RF noise. You are fighting against thermostats, fire systems, burglar systems and any other device running on that band.
Telemetry Burst describes the allocation of telemetry packets in ExpressLRS added in #472. There are two types of packets, LINK and DATA. LINK is the standard link statistics and is always available, and DATA is \"Advanced Telemetry\" which is telemetry coming from the flight controller and shares bandwidth with MSP transfers. Burst mode attempts to maintain a minimum rate of LINK packets and use the rest of the available telemetry slots for DATA.
The LINK rate chosen was one every 512ms, roughly 2 per second but slightly higher to allow more rates to have an additional burst packet at lower ratios.
"},{"location":"quick-start/ardupilot-setup/","title":"Ardupilot Setup","text":""},{"location":"quick-start/ardupilot-setup/#ardupilot-serial-setup","title":"ArduPilot Serial Setup","text":"
ArduPilot Firmware must be 4.1 or higher to run CRSF protocol. As with any serial-based receiver, you need to attach the TX/RX pads to a UART on your flight controller, then enable Serial RX in the corresponding UART in ArduPilot. In mission planner, you will need to go to the config tab -> parameter tree
Our packet rate is different from the ArduPilot CRSF packet rate, and ArduPilot will keep on reporting the mismatch, but recently they have an option to suppress the report. Currently ArduPilot provide a way to suppress this notification with the parameter below. (this will not cause any effect to RC link or telemetry Link.)
RC_OPTIONS turn on Bit 9th which is \"Suppress CRSF mode/rate message for ELRS systems\".\n
Another bit you should enable on RC_Options is the use of 420K baud rate. ExpressLRS receivers use 420K Baudrate to talk to flight controllers.
Once you have set the parameter above, power-cycle the flight controller by disconnecting and reconnecting your battery and USB. ArduPilot should automatically run with ELRS, but if it fails, set RC_PROTOCOL parameter 9th bit to 1 (CRSF option) and set the other parameter as below:
ArduPilot default flight modes channel is channel 8, but ELRS 8 position channel is on channel 12 (in hybrid switch mode). you will need to set your handset to use channel 12 as flight modes and set ArduPilot parameter:
FLTMODE_CH=12\n
if you are using Wide Switch mode (only available in ELRS V2 and above), you can use any channel for your 8 flight mode selection (beside channel 15 which is LQ and channel 16 which is RSSI)."},{"location":"quick-start/ardupilot-setup/#ardupilot-rssi-and-link-quality","title":"ArduPilot RSSI and Link Quality","text":"
To get RSSI and LQ shown in OSD (in %) set:
RSSI_TYPE = 3 (ReceiverProtocol)\n
and go to your OSD tab, and place your RSSI and LQ element where you want them to be.
If you feel any delay or lag in the control, check the RX connection to the Flight Controller. On some Flight Controllers you have to use full DMA supported input pin.
You can select a short and simple Binding Phrase for your devices before flashing or updating using the field in the ExpressLRS Configurator.
Binding Phrase Field
Alternatively, you can also change the Binding Phrase via the WebUI if your device has WiFi capabilities and is already updated to ExpressLRS 3.0 or newer. See this page for the WebUI User's Guide.
Binding Phrase Field in the WebUI
We recommend using a unique phrase with at least 8 alpha-numeric characters. The best candidate is your Pilot Handle. This phrase need not be complicated or super-secret as it isn't a password or encryption key.
Is my binding phrase a secret? (click/tap to expand)
No, just like what channel your VTX is on is not a secret. The binding phrase is not for security, it is for anti-collision. If everyone kept their VTX channel a secret, the chances of you blasting someone out of the sky accidentally are pretty high. To provide the best chance of not interfering with other pilots and them not interfering with you, be sure you're not using the same dumb bind phrase as someone else. Express your style and some creativity with a hilarious or saucy bind phrase.
For traditional binding to work, a Binding Phrase must not be set, at least for the Receiver.
Updated on 3.4.0
Any Receiver flashed with 3.4.0 or newer can be put into Bind Mode, even with a set Binding UID.
Notice
A Receiver flashed or set with a Binding Phrase WILL NOT initiate Manual Binding mode, however many times you try the procedure below. You must first reflash the receiver with the Binding Phrase field disabled and/or unset. Why would you not use a bind phrase though if you're already having to flash the RX anyway?
The Receiver LED should also be blinking when powered up.
Receiver LED doesn't Blink (click/tap to expand)
Here are the things you can do if the Receiver is in Bootloader Mode:
Check if the Boot button on the Receiver is being pressed or if it's damaged.
If the button is being pressed or pinched, remove the cause of the pressing or pinching. Heatshrink can sometimes press a button on the receiver.
If the button is damaged, remove the button or replace the receiver with a better one. Consider asking the seller for a replacement.
If the receiver doesn't have a Boot button and instead has a Boot pad, check if the Boot pad is not connected to a Ground pad.
If the Boot pad is connected to a Ground pad, disconnect or remove the connection.
Disconnect the RX and TX wires of the Receiver from the Flight Controller. Reconnect power to the drone or aircraft. Observe the LED on the Receiver once again.
If it starts Blinking Slowly (500ms Blink Pattern), you will need to move the receiver wiring to a different UART.
If the other UART is occupied by another peripheral, disconnect it and swap places with the Receiver.
If there is no other Full UART, you can try wiring a Pull-up Resistor: Connect a Resistor (300 Ohm to 1k Ohm value; a lower value is more effective) between this UART's RX pad and either a 5v or 3.3v pad as shown below:
If you are using any of the Digital FPV systems like the DJI FPV Air Unit, Caddx Vista or DJI O3 Air Unit, and you wired or connected all six wires to your Flight Controller, you will need to remove the SBUS/DJI HDL wire.
The procedure is as follows:
Power off your transmitter/radio.
Power-cycle the receiver 3 times.
Supply power to the receiver.
The receiver LED lights up.
Turn it off within 2 seconds.
Repeat 2 more times.
Caution
This step is best done using a LiPo flight pack, so make sure you've wired your flight controller properly and checked for any shorts. You don't want to let out the blue smoke!
Make sure the LED is doing a quick double-blink, which indicates the receiver is in bind mode.
Power up your transmitter/radio and use the [BIND] button on the ExpressLRS Lua script, which sends out a binding pulse. The Popup will briefly show up and then disappear.
If the receiver LED turned into a solid light, it's bound!
"},{"location":"quick-start/binding/#updated-binding-procedure-since-expresslrs-340","title":"Updated Binding Procedure since ExpressLRS 3.4.0","text":"
With PR#2542 being part of the 3.4.0 update, users now have the following methods to bind an ExpressLRS receiver with a TX module:
Binding Phrase, flashed or set (via the WebUI) into both devices.
3x Power Cycle.
Bind Receiver button in Betaflight Configurator 10.10 (or newer) Receiver Tab (bind_rx CLI command also works). This will ONLY work if your flight controller is flashed with Betaflight 4.5.0 or newer.
1.5s Button Press on the Receiver itself (or Boot pad shorting to Ground).
With the last 3 methods, the Receiver LED will blink twice, pause then repeats, until the Bind is established indicated by a solid LED light. Pressing [Bind] in the ExpressLRS Lua Script should establish the Bind, per the Traditional Binding Procedure above.
After a Receiver is bound using any of the methods above, users can put the Receiver back into Bind Mode anytime following any of the last 3 methods above. The Bind will persist or stay with the receiver until another Binding Procedure is initiated, with any of the methods above.
To cancel Bind Mode, a reboot or power-cycle is needed, or Binding the receiver with a Transmitter. The old Binding Info will be used if the receiver is rebooted without the new Bind.
A Lua Script or WebUI option can be toggled to make the Bind volatile upon power-cycle or reboot. Volatile Bind means that the Bind is only valid while the receiver is powered up. Once the receiver is power-cycled or rebooted, the Bind information is wiped and the receiver will boot up in Bind Mode.
Using the ExpressLRS Lua Script, look for a C in the top-right corner of the screen which indicates TX module and Receiver are Connected and Communicating.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, go back to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
A C in the top-right corner should be visible indicating TX module and Receiver are connected and Communicating.
Model Mismatch (click/tap to expand)
If the ExpressLRS Lua Script is showing a C in the top-right corner alright, but then that line disappears and is replaced with a line saying \"Model Mismatch\", do not worry. ExpressLRS has detected that the set Model ID in the Receiver is different from the Receiver ID set in the current Model in your Radio Model Configuration.
This is also indicated by the Receiver LED as 3 fast blinks then a pause:
If you've deliberately set up Model Matching following this page, make sure your settings are correct.
If the Model Match item in the ExpressLRS Lua is set to On, and you do want to use the Model Matching Feature, briefly set it to Off, then set it back to On to assign the current Receiver and Model ID to the Receiver.
Otherwise, simply set the Model Match item to Off.
If Model Match is set to Off, briefly set it to On and after a second or so, set it back to Off. This should clear the Model Match ID in the receiver.
This must be done while the TX module and Receiver are both powered up and connected/bound.
This page aims to explain only the key options in ExpressLRS Configurator you may need for your initial setup. For a full description of all the options available, see the User Defines page.
Some of these options are present on both the TX and RX Targets. It is important that these options match to both the TX module and receiver in order for them to bind. team2400 and team900 also share a few options and some options are unique to that frequency band. Shown below are common options available on team2400 and team900 TXes respectively.
Entering a binding phrase allows you to skip the binding step with your receivers-- you want this set. Any transmitter using the same binding phrase will connect to any receiver with the same binding phrase, so be unique. Limit to alphanumeric phrases conforming to the Latin alphabet. Receivers flashed with firmware builds that do not have binding phrase enabled will require binding with the traditional binding method.
Set these to have the \"WiFi Update\" mode try to connect to an existing WiFi network using these credentials. Configure them with the WiFi settings for where you'll be flashing your firmware, to save the step of switching WiFi networks on your computer or phone during the flashing process. If the device is unable to connect to this network, it will create its own network."},{"location":"quick-start/firmware-options/#other-options","title":"Other Options","text":"
UNLOCK_HIGHER_POWER \n
Enables higher output power for devices that support it but will possibly melt themselves to give it to you. Do not enable it without first updating your cooling setup or verifying the device isn't overheating when running at your chosen power.
UART_INVERTED\n
This only works with ESP32 based TXes. Almost all handsets require UART_INVERTED on, such as the FrSky QX7, TBS Tango 2, and RadioMaster TX16S. For T8SG V2 or Deviation firmware turn this setting off."},{"location":"quick-start/firmware-options/#receiver-only-options","title":"Receiver Only Options","text":"
Note
Configuration of Receivers should match the configuration of the Transmitter Module for Sync/Binding to happen between devices.
Most of the options listed above for the Transmitter Modules also apply to Receivers. The following are options specific to receivers that you might need.
If using an a flight controller that only has an RXI / SBUS (RX inverted) pad, turn on this option to invert the CRSF output from the receiver to be able to use that pad. This does not convert the output to SBUS, it is inverted CRSF, so CRSF should still be the receiver protocol selected in the flight controller software. ESP-based receivers only.
USE_R9MM_R9MINI_SBUS\n
On the R9MM/R9Mini only, this changes the pin used to output CRSF from the receiver the two side pins (A9 and A10) to the pin labeled \"SBUS\" on the RX, which is inverted. Similar to RCVR_INVERT_TX this does not convert the output to SBUS protocol, so CRSF should still be the receiver protocol selected in the flight controller software."},{"location":"quick-start/firmware-options/#should-i-turn-these-offon","title":"Should I turn these off/on?","text":"
NO_SYNC_ON_ARM\n
Sync packets are one packet out of every 5 seconds when armed. Leave this off unless running telemetry ratio Off because you won't be able to reconnect after a failsafe while armed if this is on.
LOCK_ON_FIRST_CONNECTION\n
Keeps the receiver on the last packet rate it was on if it failsafes, instead of trying every packet rate to reconnect. Should be left on."},{"location":"quick-start/firmware-options/#full-list","title":"Full List","text":"
For a complete list of User Defines, head over to the User Defines page.
Done! It's time to flash the firmware on your transmitter
The ExpressLRS team works closely with manufacturers to review and test hardware. It isn't until after testing that a specific ExpressLRS Configurator Target is added.
Hardware not found in the ExpressLRS Configurator means the hardware did not pass requirements, or the manufacturer has chosen not to collaborate. In this case, the manufacturer should be contacted for tech support.
Generic targets are meant for pre-production or DIY hardware. Off-the-shelf Hardware should be using Hardware-specific targets.
TL;DR: Check the Configurator before purchasing, and support manufacturers that support open source and the ExpressLRS project.
"},{"location":"quick-start/getting-started/#welcome-to-the-quick-start-guide","title":"Welcome to the Quick Start Guide","text":""},{"location":"quick-start/getting-started/#prerequisites","title":"Prerequisites","text":"
You should be comfortable navigating through your Radio Handset firmware (OpenTX/EdgeTX) and setting up models, as the guide on this website mainly covers setting up your radio for you to be able to use ExpressLRS.
Likewise, you should also be comfortable with your Flight Controller firmware (Betaflight, INAV, etc), as the guide only covers setting up your ExpressLRS receiver to work with your flight controller firmware.
"},{"location":"quick-start/getting-started/#what-should-i-do-first","title":"What should I do first?","text":"
So you got your ExpressLRS Hardware, be it a new Radio Handset with an Internal ExpressLRS module, or an External ExpressLRS Module; and a set of ExpressLRS Receivers in a bundle or a Bind-and-Fly drone with the Receiver already wired up. Where do you start?
Here's our recommendation:
Transmitter SideReceiver Side
Setup your Radio
Check the TX Firmware Version
Update the TX Module
Wire your Receiver
Configure your Flight Controller
Check the Receiver Firmware Version
Update the Receiver Firmware
After both of these, you can then proceed with the following:
Bind
Do the Bench Test
Other Radio and Flight Controller Configuration
Fly!
"},{"location":"quick-start/getting-started/#how-to-use-or-navigate-through-the-guide","title":"How to Use or Navigate through the Guide","text":"
This User Guide is organized to cater to both new and seasoned users of the system. The navigation menu on the left is arranged to start with getting the ExpressLRS Configurator installed, an Explanation of the Options available, Steps concerning the Radio and TX module, FC and Receiver setup, a \"Before you Fly\" page and a Troubleshooting page.
You can also use the Footer Navigation shown below to go through these steps:
For a specific hardware flashing guide, the pages are either in the Updating Receivers or Updating Transmitters sections organized semi-alphabetically.
You can also use the Search Bar for any topic or info you are after:
Longer pages have a Table of Contents menu found on the right-hand side of the page.
Each Updating Method available for a device can be accessed by clicking on their respective Tab.
We hope these pages will help you get started with ExpressLRS and experience one of the best and most innovative RC links in the hobby.
If you have other questions or concerns, or maybe you need further help that isn't covered by this Guide, head over to our Discord Channel!
ExpressLRS Discord
"},{"location":"quick-start/getting-started/#where-are-the-video-guides","title":"Where are the Video Guides?","text":"
Due to the current fast pace of development, video guides often end up outdated faster than intended. Specific hardware guides sometimes use pre-release firmware targets or targets intended for different hardware which can confuse when specific firmware targets are added.
We will be adding a separate videos section soon, but for now, until we find high-quality, relevant and applicable guides, you are on your own. Please take note of the publication date for these videos to make sure they are still relevant.
"},{"location":"quick-start/installing-configurator/","title":"Installing the Configurator","text":"
Download the latest ExpressLRS Configurator application for your platform, following the instructions written by jurgelenas.
ExpressLRS Configurator
The targets for each of the supported hardware can be seen on the individual device pages. Use the navigation menu on the left to get to the specific hardware page.
On the next page, you will find the different Firmware Options you can set along with their explanations.
"},{"location":"quick-start/led-status/","title":"LED Status","text":""},{"location":"quick-start/led-status/#receivertransmitter-led-status","title":"Receiver/Transmitter LED Status","text":"
ExpressLRS uses the LED to communicate the status of the transmitter/receiver.
The conditions and status LED are as follows:
Receiver Single Color LEDReceiver RGB LEDTransmitter RGB LED LED Indication Status Solid on Connected to a transmitter, or bootloader mode enabled Double blink then pause Binding mode enabled Slow blink 500ms on/off Waiting for connection from transmitter Triple blink then pause Connected to transmitter but mismatched model-match configuration Medium speed blink 100ms on/off Radio chip not detected Fast blinking 25ms on/off WiFi mode enabled LED Indication Status Rainbow fade effect Starting Up Green heartbeat Web update mode enabled Slow blink 500ms on/off Waiting for connection from transmitter Red flashing 100ms on/off Radio chip not detected Orange Double blink then pause Binding mode enabled Orange Triple blink then pause Connected to transmitter but mismatched model-match configuration Solid single color Connected to a transmitter, color indicates packet rate No Light Off or in Bootloader Mode LED Color 2.4GHz Packet rate (Hz) 915/868MHz Packet rate (Hz) Red F1000 200 Yellow F500 Yellow-Green D500 100 Full Green D250 100 Cyan 333 Full Light Blue 500 50 Blue 250 25 Blue-Purple 150 Purple 100 Full D50 Magenta 50 LED Indication Status Rainbow fade effect Starting Up Green heartbeat Web update mode enabled Blue heartbeat Bluetooth joystick enabled Red flashing 100ms on/off Radio chip not detected One Orange flash every second No handset connection Solid single color Connected to receiver, color indicates packet rate Fading single color No connection to receiver, color indicates packet rate LED Color 2.4GHz Packet rate (Hz) 915/868MHz Packet rate (Hz) Red F1000 200 Yellow F500 Yellow-Green D500 100 Full Green D250 100 Cyan 333 Full Light Blue 500 50 Blue 250 25 Blue-Purple 150 Purple 100 Full D50 Magenta 50"},{"location":"quick-start/pre-1stflight/","title":"Before First Flight","text":"
Prior to your first ExpressLRS flight, you may want to do a few tweaks to your setup to ensure a fun and trouble-free ExpressLRS experience!
By default, ExpressLRS uses limited bits for AUX switches (1-bit for AUX1, and 3-4 bits for other AUX channels), which results in very coarse resolutions up to 8 or 16 positions to Betaflight/INAV on the AUX channels. In most cases, it is enough (especially on a multirotor), but if you need finer resolution, enabling the Wide Switch Mode option expands the resolution of AUX2-AUX8 up to 128 positions. For more information, read the switch modes page.
One important thing to keep in mind is that Aux1 should be used as your Arming switch, with LOW (~1000us) as disarmed and HIGH (~2000us) as armed. AUX1 is the low-latency switch, sent with every packet, and only supports on/off (2-position) operation. ExpressLRS uses AUX1 to determine if your model is armed and this is the most reliable way to be able to tell your model to disarm. If your arm switch is in another aux channel, it may be several packets before that switch is transmitted, and there's no guarantee that the Receiver will receive that packet.
WARNING
Please make sure your ARM mode is on the AUX1 channel, and the armed state is set ~2000.
"},{"location":"quick-start/pre-1stflight/#rssi-and-link-quality","title":"RSSI and Link Quality","text":"
To get RSSI and Link Quality displayed in the OSD, set both RSSI Channel and RSSI_ADC to Disabled. Both settings can be found in the Receiver Tab.
On the OSD Tab, use the Link Quality and RSSI dBm value elements (not \"RSSI Value\"). INAV has put this in the CRSF RX Statistics section.
If you wish to enable the RSSI dBm warning, you'll have to change the alarm level using set osd_rssi_dbm_alarm = -100 in CLI. A sensible value is 5-10 higher than the sensitivity shown in the ELRS.lua for the packet rate (e.g. 250Hz=-108, so -103 to -98 for the alarm).
Likewise, if you want to change the LQ Alarm level, you can use the CLI command set osd_link_quality_alarm = x with x as your LQ Alarm level. 60 is a good value to start with.
If you're using DJI Goggles V1 or V2 (unrooted/unmodded), you're required to use \"RSSI Value\" as the OSD element. Therefore you have to decide between LQ or RSSI, by selecting either AUX11 (LQ) or AUX12 (RSSI) as RSSI Channel on the Receiver tab (see images above).
For digital FPV systems with \"Canvas Mode\" or full native OSD support via MSP DisplayPort (Walksnail Avatar, HDZero, DJI O3), you can treat the config as any analog FPV setup. Therefore, you do NOT have to set RSSI Channel (leave it at disabled).
More information about signal metrics can be found in this great article on signal health.
"},{"location":"quick-start/pre-1stflight/#bench-test","title":"Bench Test","text":"ExpressLRS Bench Test
Shown above is a Bench Test to determine if you're getting a good signal from your radio. This aims to provide you with information on whether you should check your antennas (particularly the R9's Super 8) or if you have good hardware overall.
Set your ExpressLRS module to the lowest power level using the Lua script. The packet rate doesn't matter much here.
Put your radio 1m (3ft) from your receiver and power it up. Make sure the receiver and TX module antennas are oriented in the same way. (You might want to disconnect your VTX/Air Unit temporarily, put VTX in pit mode, or have a fan blowing on it).
Using your OSD or the Telemetry Page of your radio, take note of the RSSI dBm or the 1RSS telemetry data.
On the 900MHz hardware, a value of -20dBm or thereabouts is a good indication your hardware is in working order. On the 2.4GHz hardware, around -40dBm up to -25dBm should be good. If you're getting lower numbers than these (closer to 0 is higher and better), here are a few things you could check:
The ExpressLRS module antenna could be loose. On some 3D printed module cases, the print may be too thick at the part where the pigtail's RP-SMA/SMA end would be attached; if so, tighten the nut on the RP-SMA/SMA to give the antenna some more space to get tightened up.
The antenna pigtail may be damaged or not connected properly to the module's mainboard.
On receivers using SMD antennas, expect lower values than those equipped with wire antennas. If the receiver with the SMD antenna has heat shrink, enclosed in a whoop canopy, surrounded with carbon parts or buried inside a plane/fixed wing, expect some more attenuation of the signal.
The Super 8 antenna from FrSky, which most of the R9Ms came with is notorious for being faulty or would degrade from just a few weeks of use. Replace it or as a temporary fix, solder all around the junction where the coax shielding and the RP-SMA meet. Another failure point is the connection of the coax to the active elements itself. It would seem okay, but due to the twisting of the antenna, the connection could be severed.
Super8 Antenna's common points of failure
Check if there aren't any missing components in your receivers, like the RF filter (can be found near the antenna or UFL). Also check if the SMD antenna is not broken or damaged and it's soldered in properly.
Most DIY modules require moving the 0-ohm resistor on the E28 from the PCB antenna side towards the UFL side. A solder bridge will work just fine as well, but make sure it is on the correct pads.
Swap out antennas on the receiver and/or the TX module; Most ExpressLRS receiver antennas use IPEX 1/UFL connectors and as long as the frequency tuning of the antenna is appropriate for the frequency you're in, it should work. You can also use old 2.4GHz WiFi Router antennas for your 2.4GHz modules, but avoid those that are dual-band. Also, make sure that the connector on the antenna is the appropriate one (RP-SMA on R9 modules; SMA on most off-the-shelf ExpressLRS modules)
Blackbox is handy for evaluating the performance of the RF link for a flight. Set your BB to debug mode RC_SMOOTHING_RATE, which will capture the rate that Betaflight is receiving RC Packets from the RX.
The RX transmits a subset of telemetry it receives from the flight controller. Disabling certain messages only works if the flight controller firmware does support it. For Betaflight this is possible with the telemetry_disabled_* CLI settings:
Since telemetry messages are sent with low priority it may take some time to transmit the data. The telemetry rate in the Lua settings script controls how often a telemetry message should be sent. So a ratio of 1:2 means that every second message is a telemetry message, so the telemetry data is transferred very fast. A ratio of 1:64 means that only one of 64 messages is a telemetry message and so the transfer happens much slower.
The refresh rate also impacts the transfer speed. 50 Hz is slower compared to 200 Hz. So if you need a fast telemetry update rate choose a high refresh rate, and a ratio that favors telemetry messages e.g. 200 Hz and 1:16 usually works well. For detailed information on telemetry bandwidth at different rates and ratios, see this page on telemetry bandwidth.
To finish the telemetry setup open the telemetry page on your transmitter and select \"Discover new sensors\" and wait for the list to fill.
* Indication
Notice, that there is a * sign for each row. This star indicates that this telemetry sensor was just updated.
[ ] Indication
If you see a row that does not change, and the name of the row is in square brackets it means that this sensor was not updated for some time.
The first values (including RSSI and link quality) should always be updated (flashing stars). If this does not happen multiple times per second the transmitter will issue a \"telemetry warning\". To prevent this warning use the setting TLM_REPORT_INTERVAL_MS.
It should look like this (and if it does not there is something wrong with your setup):
The remaining values are updated at a different rate (depending on refresh rate and telemetry ratio). So if you use 50 Hz and 1:64 it will happen slowly, and the update takes multiple seconds for each sensor:
If you use 200Hz and 1:2 Tlm ratio the stars will not even blink because the update happens so fast:
To configure Betaflight from your transmitter it's possible to use the Betaflight lua scripts. This requires the telemetry feature enabled for the RX+TX. If the telemetry page of OpenTX does not show regular updates for all sensors the LUA script will also not work.
To get a responsive UI configure ExpressLRS for fast data transfer so make sure to use something like 200Hz/500Hz with 1:2 Tlm and a serial baud rate of 400000. Currently, MSP is limited to 50Hz on 115200 Baud and does not work with a 500`` Hz refresh rate. The initial VTX tables download does take some time - but is cached after that.
If you get a \"retrying\" message while saving changes it means that the Lua script did not receive a response fast enough. But the change usually still goes through so try reloading the page to check if the change was saved. With the recommended settings this does not happen but with slower settings, it could happen.
"},{"location":"quick-start/troubleshooting/","title":"Troubleshooting","text":""},{"location":"quick-start/troubleshooting/#general-troubleshooting","title":"General Troubleshooting","text":""},{"location":"quick-start/troubleshooting/#my-rx-and-tx-are-bound-but-fc-is-not-responding-to-inputs-and-i-can-only-see-10-telemetry-sensors","title":"My RX and TX are bound, but FC is not responding to inputs, and I can only see 10 Telemetry sensors","text":"My RX and TX are bound, but FC is not responding to inputs, and I can only see 10 Telemetry sensors
Check whether you have wired the receiver correctly and that RX and TX wires aren't swapped.
Also, check that you have the correct SerialRX configuration. You might want to revisit the FC Preparation page for the Flight Controller setup.
Also, make sure that the UART where you connected the receiver doesn't have inversion and it's in full duplex mode. You can also try a different UART.
"},{"location":"quick-start/troubleshooting/#my-rx-and-tx-are-bound-and-im-getting-more-than-10-telemetry-sensors-on-my-radio-but-im-not-getting-stick-inputs","title":"My RX and TX are bound, and I'm getting more than 10 Telemetry sensors on my Radio, but I'm not getting stick inputs","text":"My RX and TX are bound, and I'm getting more than 10 Telemetry sensors on my Radio, but I'm not getting stick inputs
This is due to a model mismatch between the receiver and the TX module. The LED on the receiver will have 3 short blinks and then a 1s pause indicating the mismatch.
To \"fix\" this, you might want to turn On Model Matching. Please see Model Matching for more notes.
Another thing to check is whether you have enabled RCVR_INVERT_TX option for your receiver firmware. This option is intended for FCs that don't have any other UARTs available (e.g. AIOs) other than an SBUS pad. See this section for more details: Output Inverting.
For the R9mm/mini receivers, make sure you didn't enable USE_R9MM_R9MINI_SBUS in your firmware option. See Output Inverting for what this option do.
"},{"location":"quick-start/troubleshooting/#my-rx-and-tx-are-bound-and-im-getting-stick-inputs-but-i-can-only-get-10-telemetry-sensors","title":"My RX and TX are bound, and I'm getting stick inputs, but I can only get 10 Telemetry sensors","text":"My RX and TX are bound, and I'm getting stick inputs, but I can only get 10 Telemetry sensors
Check if you have Telemetry Feature enabled in your FC Configuration.
Also, verify the RX pad from the receiver is connected properly to a TX pad in the FC in the same UART as the TX wire from the receiver.
Also, make sure you have deleted and rediscovered the sensors. It's good to increase the TLM Ratio so the acquisition of the sensors will be faster.
This could also mean you'll have to update your FC Firmware to a more recent version that supports at least the CRSFv2 protocol.
"},{"location":"quick-start/troubleshooting/#i-think-my-receiver-and-transmitter-are-bound-as-the-led-on-the-receiver-is-solid-but-i-do-not-have-stick-inputs-or-rssi-on-the-radio","title":"I think my Receiver and Transmitter are bound, as the LED on the Receiver is solid. But I do not have stick inputs or RSSI on the radio.","text":"I think my Receiver and Transmitter are bound, as the LED on the Receiver is solid. But I do not have stick inputs or RSSI on the radio.
You are not bound. Your Receiver is probably in bootloader mode.
Make sure you have unbridged the boot pads if you flashed it via passthrough.
Turn off your Radio and if the LED is still solid, but boot pads aren't bridged, the UART where the receiver is on is putting it into bootloader mode unintentionally. This is primarily caused by pull-down resistor on the RX pad to aid with SBUS line inversion. To verify it is the case with the UART, disconnect the RX and TX wires from the FC UART, and it should start blinking slowly then after the set interval (20s - 30s by default), it will blink fast indicating it's on WiFi Mode. To \"fix\" the issue, you have two options:
Move the receiver into another free UART.
If there's no other UART, wire up a resistor with a value between 300 Ohm to 1k Ohm between a 3.3v pad and the FC's RX pad (where the TX from the receiver connects to).
If, however, despite unsoldering the TX and RX wires, the LED is still solid, you probably have a soft-bricked receiver due to a failed WiFi flash as a result of not letting the receiver reboot normally. Follow the unbricking procedure to recover the receiver.
"},{"location":"quick-start/troubleshooting/#my-osd-is-showing-lq-00-and-rssi-dbm-at-130-dbm-but-i-have-stick-inputs-and-more-than-10-telemetry-sensors","title":"My OSD is showing LQ 0:0 and RSSI dBm at -130 dBm, but I have stick inputs and more than 10 Telemetry sensors","text":"My OSD is showing LQ 0:0 and RSSI dBm at -130 dBm, but I have stick inputs and more than 10 Telemetry sensors
Check whether you have RSSI Channel set to either Aux11 or Aux12. If you do, set it to disabled.
If it's still not fixed with that, check if you have RSSI ADC enabled. If so, set it to disabled.
"},{"location":"quick-start/troubleshooting/#my-osd-is-showing-lq-31-sometimes-lq-39","title":"My OSD is showing LQ 3:1 sometimes LQ 3:9","text":"My OSD is showing LQ 3:1 sometimes LQ 3:9
Move your LQ OSD element around as it could be being obstructed by another element or it's too far to the right of the preview.
"},{"location":"quick-start/troubleshooting/#i-am-getting-telemetry-lostrecovered-and-is-getting-annoying","title":"I am getting Telemetry Lost/Recovered and is getting annoying","text":"I am getting Telemetry Lost/Recovered and is getting annoying
There's a handful of reasons why this is occurring, and if you have newer handset/radio, it shouldn't happen at all unless you're flying very far away using a receiver without an amplifier for its Telemetry signal (e.g. the EP receivers).
You're on an X9D(+) or a QX7 with subpar inverter chips. Check this page on how to remedy it.
You're on an early version of the Happymodel Slim Pro. Check this FB post for the fix from manufacturer.
You're using a 2018 ACCST R9M, while also using a Radio with 400k or higher Baud rate. You will either have to lower the Baud rate on your radio to 115200 (QX7) or do the Resistor mod on the module as described here.
Your module is getting loose inside its enclosure, most common on the first batches of the Happymodel ES24TX (white 3D-Printed enclosure; although the black one is only marginally better having 4 screw points instead of 2). You either have to print your enclosure (search Thingiverse for \"expresslrs\") or find a way to tighten or snug the enclosure with the module board.
Check the S.Port pin and connection in your module and module bay, and make sure they have a solid physical connection. On the DIY modules, particularly the full size module, the round hole/via for the Molex connector's flat pin might not be getting a good connection due to cold solder joint, or insufficient solder.
"},{"location":"quick-start/troubleshooting/#i-need-to-plug-my-fc-a-secondthird-time-before-i-get-a-bind-the-led-on-the-receiver-is-dim-when-i-power-it-up","title":"I need to plug my FC a second/third time before I get a bind. The LED on the receiver is dim when I power it up","text":"I need to plug my FC a second/third time before I get a bind. The LED on the receiver is dim when I power it up
Update to the latest firmware as soon as you can. A batch of HM receivers have reached the market with Voltage regulators (marked SDG) that were insufficient and weren't able to handle the higher current draw during boot up. To learn more about this issue and the fix, please check out this PR.
"},{"location":"quick-start/troubleshooting/#my-blackbox-log-has-stepping-on-the-rc-trace","title":"My Blackbox Log has stepping on the RC trace","text":"My Blackbox Log has stepping on the RC trace
Make sure you have disabled ADC Filter in your Radio Hardware settings.
"},{"location":"quick-start/troubleshooting/#troubleshooting-the-lua-script","title":"Troubleshooting the Lua Script","text":""},{"location":"quick-start/troubleshooting/#expresslrs-lua-script-is-stuck-at-loading","title":"ExpressLRS Lua Script is stuck at Loading...","text":"ExpressLRS Lua Script is stuck at Loading...
Go back to the Radio Setup Guide and make sure your radio is prepped up for ExpressLRS.
Also, make sure your module has been flashed with v3.0 firmware. V3 Lua for V3.0-flashed modules, V2 Lua for v2.x-flashed modules (including some modules fresh from the factory).
For newly-acquired ExpressLRS modules, flashing via USB is the recommended update method.
"},{"location":"quick-start/troubleshooting/#betaflight-lua-is-stuck-at-initializing","title":"Betaflight Lua is stuck at Initializing","text":"Betaflight Lua is stuck at Initializing
Increase the TLM Ratio via the ExpressLRS Lua script to values like 1:4 or even 1:2 and retry the Betaflight Lua script.
Also, you have to make sure you're getting more than ten (10) Telemetry sensors prior to launching the script.
See MSP Section for more info.
"},{"location":"quick-start/troubleshooting/#i-cannot-change-the-switch-mode","title":"I cannot change the Switch Mode!","text":"I cannot change the Switch Mode!
Changing switch modes requires that the TX module and Receiver aren't connected to each other (no C in the top right corner of the Lua Script). Power off the receiver first, change the Switch Mode from the Lua script, then power up the receiver. The Switch Mode should then apply.
"},{"location":"quick-start/troubleshooting/#i-cannot-change-my-packet-rate-to-f1000","title":"I cannot change my Packet Rate to F1000!","text":"I cannot change my Packet Rate to F1000!
F1000 requires higher than 400K baud rates. First update your baud rate setting either in the Model Setup menu or in the System Menu -> Hardware, reboot your radio to ensure that the baud rate setting got applied and then change the Packet Rate.
Do note that not every handset is capable of higher than 400K baud rates. See the Radio Setup Guide for the details.
"},{"location":"quick-start/troubleshooting/#i-cannot-change-to-full-resolution-rates","title":"I cannot change to Full Resolution Rates!","text":"I cannot change to Full Resolution Rates!
As Full Resolution Rates call for an entirely different Switch Modes, you need to first disconnect the Receiver and the TX module from each other, like how you would change Switch Modes. Power down the receiver, change the Packet Rate to the Full Resolution modes, select your Switch Mode scheme and then power up the receiver or the aircraft.
"},{"location":"quick-start/troubleshooting/#vtx-admin-is-not-working-but-i-can-change-vtx-channels-via-osd-menu","title":"VTX Admin is not working but I can change VTX channels via OSD Menu.","text":"VTX Admin is not working but I can change VTX channels via OSD Menu.
As VTX Admin depends on MSP which then depends on Telemetry, ensure that you have Telemetry enabled on your FC Configuration and that you are getting more than 10 Telemetry Sensors on your Radio (Model Setup -> Telemetry page; Delete and Discover New sensors to refresh the sensor list.) Also, make sure Telem Ratio is not Off.
"},{"location":"quick-start/troubleshooting/#there-is-no-c-on-the-top-right-corner-and-im-not-getting-telemetry-in-my-radio","title":"There is no C on the top right corner, and I'm not getting Telemetry in my radio!","text":"There is no C on the top right corner, and I'm not getting Telemetry in my radio!
Make sure Telem Ratio is not set to Off. Set it to Std, or to any other value other than Off.
"},{"location":"quick-start/troubleshooting/#on-v1x-i-can-choose-2w-on-the-lua-but-i-cannot-do-that-anymore-what-gives","title":"On v1.x, I can choose 2W on the Lua, but I cannot do that anymore. What gives?","text":"On v1.x, I can choose 2W on the Lua, but I cannot do that anymore. What gives?
This means your module cannot go that high or that low. The power levels you can select on the new Lua script are based on the power levels your module supports. This also applies to other options like Enable Backpack WiFi or BLE Joystick. If your module doesn't support any of these features, it won't show up on the Lua Script.
Individual hardware Flashing and Updating guide can be found by using the menu on the left sidebar. You can also use the Search Bar on the top of the page to get to your device's Flashing Guide faster.
"},{"location":"quick-start/troubleshooting/#invalid-serial-rx-configuration-detected","title":"Invalid serial RX configuration detected","text":"Invalid serial RX configuration detected
This is often caused by incorrect Serial RX protocol (should be CRSF), or serialrx_inverted = on (should be off) or serialrx_halfduplex=on (should be off). The Passthrough Init section of the log will show you which setting should be corrected. See the FC Preparation Guide for the correct settings.
"},{"location":"quick-start/troubleshooting/#rx-serial-not-found","title":"RX Serial not found !!","text":"RX Serial not found !!
Make sure your Serial RX on the Ports Tab of your FC Firmware configurator is set to the correct UART. See the FC Preparation Guide for the correct settings.
"},{"location":"quick-start/troubleshooting/#no-cli-available","title":"No CLI Available","text":"No CLI Available
This message can be seen on the ExpressLRS Configurator Log while using the Passthrough method and can be caused by a busy Com Port. Make sure any other Configurator Apps were closed and unplug-replug your FC to USB. You might also want to use a different USB port or cable.
This could also mean that the FC cannot be detected by the script. This could also due to the FC being in DFU mode, which for passthrough flashing, is not needed.
Some apps are running in the background that could cause this. One of which is Cura Slicer. If there are such apps, close them first before attempting another Build and Flash.
Unplug-replug the FC's USB before another attempt.
"},{"location":"quick-start/troubleshooting/#10-retries-but-no-success","title":"10 Retries but no Success","text":"10 Retries but no Success
This can be due to several things:
Incorrect bootloader is flashed or it's not flashed properly. This mainly happens on the R9 receivers. Go checkout Bootloader Flashing Guide.
Incorrect wiring. Make sure that RX in the Receiver is connected to a TX pad in the FC and the TX in the Receiver is connected to an RX pad in the FC. Also, make sure the receiver is getting enough voltage (min 4v5) from the FC or voltage supply. Wiring guide is here
Receiver is OFF. Check whether the LED on the receiver is lit, indicating it's powered and in a working state.
The UART has hardware inversion. Make sure that the UART you've connected the receiver to is not an SBUS UART that usually has hardware inversion (most common among F4 Flight Controllers). There are Flight controllers that require you to bridge a pair of pads to enable or disable the Hardware inversion of an RX pad. You can simply try a different UART.
The LED on the receiver is SOLID, while the radio is off, which could only mean that the RX pad in the FC is being pulled LOW, putting the ESP-based receiver (EPs, ES900RX, etc.) into Bootloader mode unintentionally, which will hinder normal passthrough operations. Feel free to try a different UART.
"},{"location":"quick-start/troubleshooting/#failed-to-connect-to-esp8266-timed-out-waiting-for-packet-header","title":"Failed to connect to ESP8266: Timed out waiting for packet header.","text":"Failed to connect to ESP8266: Timed out waiting for packet header.
This can be due to several things:
Receiver is wired incorrectly. Please check if the RX and TX wires aren't swapped and connected RX to RX and TX to TX on the FC. Revisit the Receiver Wiring Guide here.
The receiver's \"boot\" pads aren't bridged (or the button wasn't pressed and held during power up) for passthrough flashing. This is required for Passthrough flashing if the receiver is fresh from the packet and has a firmware version before 1.0.0-RC6.
The receiver UART is putting it in Bootloader mode and is interfering with passthrough flashing. Move it into another UART.
You can also attempt the update via UART using an FTDI Adapter (or a USB to UART Bridge).
Please see the Flashing guide for your particular receiver using the Sidebar on the Left.
"},{"location":"quick-start/troubleshooting/#i-updated-via-wifi-but-now-the-receiver-wont-work-and-has-solid-led","title":"I updated via WiFi but now the receiver won't work and has SOLID LED","text":"I updated via WiFi but now the receiver won't work and has SOLID LED
This is a sign that the WiFi flashing didn't go through properly due to a premature power cycle. To fix this, you will have to bridge the boot pads (see here) and reflash using the Passthrough method (Telemetry option on Betaflight/iNav set to OFF. This is important!) or using an FTDI adapter.
This video shows the steps albeit using a VSCode development environment but the ExpressLRS Configurator will work just fine.
To ensure that the WiFi flashing is finished properly, wait until the LED on the receiver blinks slowly (indicating it's looking for a TX bind) before pulling off power.
If you have other questions or concerns, or maybe you need further help that is not covered by this Guide, head over to our Discord Channel or Facebook Group!
ExpressLRS Discord ExpressLRS Facebook
"},{"location":"quick-start/unbricking/","title":"Unbricking","text":""},{"location":"quick-start/unbricking/#help-i-bricked-my-rx","title":"HELP I BRICKED MY RX!","text":"
Take a breath, calm down, relax.
ALL the ESP-based Receivers have a factory-installed bootloader onboard which CANNOT be damaged or tampered with. You can completely screw up the upgrade and always get it back using this default bootloader.
So technically, your receiver is not bricked unless you have damaged the hardware itself.
But for argument's sake, let's use the word \"bricked\" or \"soft-bricked\" for a receiver that is not in working order and is not behaving as expected.
Follow the steps below very closely to recover your \"bricked\" Receiver.
Make sure your Receiver only powers up with a LiPo Connected.
If your receiver powers up with just USB connected, move the 5v wire of the receiver into a 5v pad that only powers up with LiPo connected.
Take a multi-meter in DC Voltmeter mode.
Plug in USB into your Flight Controller. Disconnect LiPo.
Probe/check each of the 5v pads in the Flight Controller.
The 5v pads that read 0v on the multi-meter are pads that will only power up when a LiPo is connected.
Solder your Receiver 5v into this pad.
If in the above steps, you're not able to find a 5v pad suitable for this procedure, follow the following:
Disconnect the 5v wire of the Receiver from the 5v pad on the Flight Controller.
Solder a different length of wire into any of the 5v pads on the Flight Controller.
Expose a suitable length of conductor of this wire that you can connect with the Receiver's 5v wire LATER.
If you've connected a LiPo from the previous step, disconnect it. Also, unplug the Flight Controller from your computer.
Prepare the receiver for bootloader mode.
If your Receiver have boot pads, bridge them together with solder.
If your Receiver has a button, use an alligator clip to keep the button pressed.
If your Receiver only has one Boot pad, connect it to a Ground pad.
Example Receiver with Boot Pad
Example Receiver with Boot Button
Notice
Even if your Receiver LED is only lighting up solid, DO NOT skip this step to ensure the receiver is indeed in its Bootloader State.
Connect to Betaflight or INAV Configurator and make sure you've properly configured your FC for ExpressLRS use. Set Telemetry to disabled for now.
Save & Reboot. Close Betaflight Configurator. Also, close any other App that's potentially using COM Ports.
Cura Slicer
We found Cura Slicer and possibly others like it would keep a COM port open or busy preventing successful flashing/recovery via Passthrough.
Unplug and replug the USB cable. This will ensure the Flight Controller has a fresh connection to the computer and that the COM port is not busy or in use.
On the ExpressLRS Configurator, select the Firmware Version you're trying to recover. Select your Device Category and Device Target as well, along with your usual Firmware Options.
Set the Flashing Method to Betaflight Passthrough.
Click the Flash button. Wait for the Line PASSTHROUGH DONE to appear in the Build Log and power up the receiver.
Not Seeing PASSTHROUGH DONE? (click/tap to expand)
You've probably skipped some of the steps above or you've misconfigured your flight controller. Go back and make sure to follow EVERY step.
Plug in LiPo or twist the 5v Wires together to power up the receiver (see Step 1). The receiver LED should be Solid.
Wait for the process to finish, hopefully with the Success Message. Otherwise, repeat the procedure above or try a different approach (like reflashing via FTDI/UART Adapter).
You can now power down the flight controller, and disconnect LiPo and/or USB.
Remove the boot pads bridging or connection to Ground, or, if your Receiver has a button, remove the alligator clip used to press the button.
Re-power up the receiver to verify it is back in its normal working state.
"},{"location":"quick-start/unbricking/#wall-of-text-heres-a-video","title":"Wall of Text? Here's a video!","text":""},{"location":"quick-start/unbricking/#what-about-the-tx","title":"What about the TX?","text":"
Most ESP-based ExpressLRS TX Modules either have the via UART Flashing Procedure or the via ETX Passthrough Flashing method available to them. Use any of these other methods to recover your ESP-based TX Module.
For STM-based ExpressLRS TX Modules, there's via STLink Flashing method.
ExpressLRS TX Modules are much harder to screw up during updates, more so if you're following the official Flashing Guides on this website.
"},{"location":"quick-start/webui/","title":"The Web UI","text":""},{"location":"quick-start/webui/#the-expresslrs-web-ui","title":"The ExpressLRS Web UI","text":"
The ExpressLRS Web UI is an essential part of the ExpressLRS ecosystem. In earlier versions of the project, its main use is for updating the ExpressLRS firmware and logging or debugging (on select hardware).
ExpressLRS 3.0 has further expanded the capabilities of the ExpressLRS Web UI. It is now capable of changing Firmware Parameters, including the Binding Phrase, Regulatory Domain (for the 900MHz devices), UART Inversion and more.
"},{"location":"quick-start/webui/#the-banner","title":"The Banner","text":"The ExpressLRS Web UI Banner"},{"location":"quick-start/webui/#the-options-tab","title":"The Options Tab","text":"
This tab allows users to change firmware options without reflashing their devices. It also allows the import and export of the Configuration from one device to another, useful for setting up backup equipment.
Options common to both Receivers and TX Modules:
Binding Phrase: Type in your Binding Phrase here if you want to update it from either the factory setting or from an earlier flashed setting.
It's Blank!
This field doesn't store the plain text Binding Phrase. If you see it blank like shown, do not worry. The next field, UID, has the information.
UID: As you type in your Binding Phrase in the field above, this read-only field will update with the UID translation. This is what actually gets saved in your device.
Regulatory Domain: This only applies to the 900MHz system. This field allows users to change the Regulatory Domain for their device.
What about 2.4GHz?
The EU_CE Regulatory Domain setting is a Compile-time option and the LBT code needs to be baked in for it to work properly.
WiFi \"Auto On\" Interval (in seconds): This field allows you to change how soon WiFi automatically activates when the device is powered up and it's not getting a valid CRSF signal (for TX Modules) or sync packets (for Receivers).
Receiver OptionsTX Module Options
ExpressLRS Receiver Options Tab
UART Baud: The baud rate to which the receiver will send and receive signals to or from a Flight Controller or other serially connected device. Under normal circumstances, this setting should be left at the default 420000 baud.
Exception: If you are running KISS/Kiss Ultra firmware set the receiver's UART baud rate to 400000, as KISS uses this baud rate for CRSF.
Invert TX Pin: This setting should also be left disabled or unchecked under normal circumstances. It inverts the CRSF signal coming out of the TX pin of the receiver.
Receivers that will be connected to an SBUS pad on Flight Controllers without extra uninverted RX pads should enable this setting. Additionally the command set serialrx_inverted = on will be needed in the Flight Controller configuration.
Lock on First Connection: This setting speeds up the reconnection of a Receiver and TX Module if you don't ever change your RF Mode/Packet Rate.
ExpressLRS TX Module Options Tab
TLM Report Interval: This setting controls how often Telemetry packets are sent back to the radio. 240LU is the default setting and is already fast for EdgeTX or OpenTX.
UART Inverted: Keep this enabled or checked if you're using your TX module on an OpenTX or EdgeTX Radio. The S.Port pins in External Module bays are inverted bidirectional pins.
Fan Runtime (in seconds): This setting controls how long the fan on the TX Module will keep spinning even after the current Transmit Power of the module is already Lower than the Fan Threshold Lua Script setting.
"},{"location":"quick-start/webui/#the-wifi-tab","title":"The WiFi Tab","text":"ExpressLRS WebUI WiFi Tab"},{"location":"quick-start/webui/#the-model-tab","title":"The Model Tab","text":"ExpressLRS Receiver Model Tab ExpressLRS PWM Receiver Output Settings"},{"location":"quick-start/webui/#the-buttons-tab","title":"The Buttons Tab","text":"
This section is currently only available for the RadioMaster Ranger module.
"},{"location":"quick-start/webui/#how-to-get-to-the-web-ui","title":"How to get to the Web UI","text":"ReceiversTX Modules
Put your Receiver into WiFi Mode.
Auto WiFi Onvia Lua Script
Make sure your Radio with your TX Module is Off.
Power-cycle your receiver (turn it Off then turn it back On). The Receiver LED should be blinking slowly as shown below.
Receiver LED not Blinking! (click/tap to expand)
If it has a Solid LED light, it may be in bootloader mode if you've only just wired it up. Rewire your receiver into a different uart. If you have attempted to update it before, then it could be soft-bricked. Follow the Unbricking procedure to get it back into normal working condition.
Wait for about 60 seconds or until the Receiver LED blinks rapidly indicating it is now in WiFi Mode.
Make sure the Receiver and TX Module are in sync and bound. RSSI indicators on your Radio Home screen should be visible and the Receiver LED should be Solid as shown.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, go back to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
there should be a C in the top right corner of the Lua Script indicating TX Module and Receiver are Connected.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The WiFi Running screen will briefly show up. Your Receiver is now in WiFi mode as indicated by the rapidly blinking LED.
Note
It is normal for the receiver will disconnect from the TX Module once it is in WiFi Mode. You will hear your radio announce \"Telemetry Lost\" if you have the sound pack on your Radio SD Card.
Scan for the ExpressLRS RX Access Point.
If your Receiver is previously flashed with your Home WiFi SSID and Password, and it can connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Load the Web UI on your browser using these addresses:
http://10.0.0.1/ - If you have connected to the ExpressLRS RX Access Point
Note
This IP address is also often used by some routers. Computers with an ethernet connection to their routers will find that this page doesn't load the ExpressLRS Web UI and instead loads their router or ISP modem configuration dashboards.
We recommend disconnecting from the network first or trying a different device instead, e.g. smartphone or tablet.
Note
On some devices a network login prompt might pop up. Clicking this will often show an incomplete version of the webui that won't behave as expected. Please navigate to http://10.0.0.1/ manually in your browser instead.
http://elrs_rx.local - If you have previously set your Home WiFi SSID and Password into your Receiver when you flashed it.
Note
If your browser cannot resolve this address, chances are MDNS is not set up and working on your computer or network.
Use the IP Address instead! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a which will list all the devices in the Network.
Try each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in to your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Put your module into wifi mode.
via ExpressLRS Lua ScriptExternal Module detached from Radio
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, go back to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
If the Script stopped and is showing a Syntax Error, do not worry. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware or both. It could also be due to the fact your TX module is on an earlier firmware version and you're using a more recent Lua Script.
With your TX module disconnected from your Radio module bay, power it up either via an external power source (2S) or by plugging in a USB cable into its USB Port.
Let it be for 60s and the RGB LED will turn into a Green Breathing LED pattern indicating it is now in WiFi Mode.
TX Modules with an OLED Screen will also show a message regarding WiFi mode.
Scan for the ExpressLRS TX Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it can connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Load the Web UI on your browser using these addresses:
http://10.0.0.1/ - If you have connected to the ExpressLRS TX Access Point
Note
This IP address is also often used by some routers. Computers with an ethernet connection to their routers will find that this page doesn't load the ExpressLRS Web UI and instead loads their router or ISP modem configuration dashboards.
We recommend disconnecting from the network first or trying a different device instead, e.g. smartphone or tablet.
Note
On some devices a network login prompt might pop up. Clicking this will often show an incomplete version of the webui that won't behave as expected. Please navigate to http://10.0.0.1/ manually in your browser instead.
http://elrs_tx.local - If you have previously set your Home WiFi SSID and Password into your TX Module when you flashed it.
Note
If your browser cannot resolve this address, chances are MDNS is not set up and working on your computer or network.
Use the IP Address instead! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a which will list all the devices in the Network.
Try each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in to your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/axisflying-thor/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
Axis Thor
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/axisflying-thor/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/axisflying-thor/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Axisflying 2.4 GHz
Device:
AXIS Thor 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
Locate the Boot button on your receiver, press and hold it.
Plug in your UART Adapter into a USB Port on your Computer. Release/de-press the Boot button.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Axisflying 2.4 GHz
Device:
AXIS Thor 2.4GHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Axisflying 2.4 GHz
Device:
AXIS Thor 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Axisflying 2.4 GHz
Device:
AXIS Thor 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Axisflying 2.4 GHz
Device:
AXIS Thor 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
"},{"location":"quick-start/receivers/betafpv-superd/","title":"BetaFPV SuperD 2.4GHz","text":""},{"location":"quick-start/receivers/betafpv-superd/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. As this receiver uses an RGB LED as indicator, it will appear as if the receiver is OFF when in Bootloader mode. The firmware that drives the RGB LED is inactive when the ESP Chip is in Bootloader mode, thus the RGB LED will not function when in this state.
BetaFPV SuperD Diversity Receiver, ESP-based
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/betafpv-superd/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have connected the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/betafpv-superd/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV SuperD 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
Locate the Boot button on your receiver, press and hold it.
Plug in your UART Adapter into a USB Port on your Computer. Release/de-press the Boot button.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV SuperD 2.4GHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV SuperD 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV SuperD 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV SuperD 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
"},{"location":"quick-start/receivers/betafpv-superd900/","title":"BetaFPV SuperD 900MHz","text":""},{"location":"quick-start/receivers/betafpv-superd900/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. As this receiver uses an RGB LED as indicator, it will appear as if the receiver is OFF when in Bootloader mode. The firmware that drives the RGB LED is inactive when the ESP Chip is in Bootloader mode, thus the RGB LED will not function when in this state.
BetaFPV SuperD Diversity Receiver, ESP-based
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/betafpv-superd900/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have connected the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/betafpv-superd900/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV SuperD 900MHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
Locate the Boot button on your receiver, press and hold it.
Plug in your UART Adapter into a USB Port on your Computer. Release/de-press the Boot button.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV SuperD 900MHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV SuperD 900MHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV SuperD 900MHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV SuperD 900MHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/betafpv2400/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
BetaFPV Nano BetaFPV Lite (Flat & Tower)
The images above show the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/betafpv2400/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/betafpv2400/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz Nano RX (Nano)
BETAFPV 2.4GHz Lite RX (Tower & Flat)
BETAFPV 2.4GHz AIO RX (AIOs with UART-based Receivers)
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
If your Receiver has Boot Pads instead of a Boot Button, solder the Boot Pads together or connect it to Ground. If your Receiver has a Boot Button, locate it then press & hold it.
Plug in your UART Adapter into a USB Port on your Computer.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Once the LED on the Receiver is lit up Solid, release/de-press the button on the receiver if it has one.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz Nano RX (Nano)
BETAFPV 2.4GHz Lite RX (Tower & Flat)
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
If your receiver has a boot pad instead of a boot button, make sure to disconnect it from ground or remove the solder bridge you made on step 2.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz Nano RX (Nano)
BETAFPV 2.4GHz Lite RX (Tower & Flat)
BETAFPV 2.4GHz AIO RX (AIOs with UART-based Receivers)
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz Nano RX (Nano)
BETAFPV 2.4GHz Lite RX (Tower & Flat)
BETAFPV 2.4GHz AIO RX (AIOs with UART-based Receivers)
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz Nano RX (Nano)
BETAFPV 2.4GHz Lite RX (Tower & Flat)
BETAFPV 2.4GHz AIO RX (AIOs with UART-based Receivers)
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/betafpv900/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
BetaFPV Nano
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/betafpv900/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/betafpv900/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV 900MHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
Locate the Boot button on your receiver, press and hold it.
Plug in your UART Adapter into a USB Port on your Computer. Release/de-press the Boot button.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV 900MHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV 900MHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV 900MHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV 900MHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Once you've wired up your Receiver to your Flight Controller, you need to setup the UART for Serial RX. This is usually done on the Ports Tab of your Flight Controller Configurator.
In the example below, the Receiver is wired to UART1 (TX1 and RX1 pads), and so the Serial RX column should be enabled on UART1 in the Ports Tab.
NOTE
This is ONLY an example. Set your Ports according to how your peripherals, including the Receiver, are wired up.
Example Betaflight Serial RX Configuration Example INAV Serial RX Configuration"},{"location":"quick-start/receivers/configuring-fc/#serial-receiver-protocol","title":"Serial Receiver Protocol","text":"
UART-based ExpressLRS Receivers use the CRSF Serial Protocol to communicate with a Flight Controller.
Follow the steps below to set up your Serial Receiver Protocol:
Navigate to Receiver Tab on your Flight Controller Configurator.
Set Receiver Mode or Receiver Type to Serial.
Set Serial Receiver Provider to CRSF.
Set Telemetry to Enabled.
On INAV, Telemetry can be found under the Configuration Tab.
Make sure you set RSSI Channel to Disabled if you are using an Analog FPV System, or any FPV System with MSP DisplayPort or \"Canvas Mode\" support.
Also make sure RSSI ADC is Disabled.
Note
The Location or Labels of these settings can change from version to version of your Flight Controller Configurator. Please consult your Flight Controller Configurator User Guides.
"},{"location":"quick-start/receivers/configuring-fc/#software-inversion-and-duplex-modes","title":"Software Inversion and Duplex Modes","text":"
The CRSF Protocol requires a full UART pair, uninverted and in full-duplex mode. To check for these settings, use the CLI Tab of your Flight Controller Configurator and execute get serialrx.
serialrx_inverted should be OFF; configure it with set serialrx_inverted = off.
serialrx_halfduplex should be OFF; configure it with set serialrx_halfduplex = off.
Don't forget to use save once you're done setting these up.
"},{"location":"quick-start/receivers/configuring-fc/#rc-link-preset-betaflight-only","title":"RC Link Preset (BETAFLIGHT ONLY)","text":"
For flight controllers based on Betaflight, there are 'RC Link Presets' available that configure feedforward smoothing and associated link settings based on your packet rate and usage case.
Warning
Using no link preset, or using the incorrect one for your packet rate, can result in unwanted noise and jitter in feedforward, which can affect setpoint tracking and thus flight characteristics.
To install the correct 'RC Link Preset', follow these steps in Betaflight Configurator:
Select the Preset tab
In the preset tab, select Save Backup and save a backup to a safe location before applying any preset.
Search for 'ExpressLRS' and select the Link Preset that matches your Packet Rate. If no direct match is available, choose the closest preset below your packet rate.
Read through the options by selecting the dropdown list. NOTE: These are all optional, if none of them apply to your circumstances, it is OK to leave everything unticked.
Select 'Pick' to stage the preset:
Select Save and Reboot to apply the preset:
Important
Close your Flight Controller Configurator once you've set it up for ExpressLRS. Keeping it open could prevent the next steps from completing properly, particularly flashing via Passthrough. You must also unplug the FC from USB before proceeding to the next steps to refresh the connection.
With your Flight Controller configured, you can now proceed to the next step: Checking RX Firmware Version.
"},{"location":"quick-start/receivers/diy2400/","title":"DIY 2400RX","text":""},{"location":"quick-start/receivers/diy2400/#flashing-via-passthrough","title":"Flashing via Passthrough","text":"
"},{"location":"quick-start/receivers/diy2400/#flashing-via-wifi","title":"Flashing via WiFi","text":"
Target: DIY_2400_RX_ESP8285_SX1280_via_WIFI
"},{"location":"quick-start/receivers/diy2400/#flashing-via-ftdi","title":"Flashing via FTDI","text":"
Target: DIY_2400_RX_ESP8285_SX1280_via_UART
Please consult the Hardware Repository for your particular receiver.
"},{"location":"quick-start/receivers/diy900/","title":"DIY 900RX","text":""},{"location":"quick-start/receivers/diy900/#flashing-via-passthrough","title":"Flashing via Passthrough","text":"
"},{"location":"quick-start/receivers/diy900/#flashing-via-ftdi","title":"Flashing via FTDI","text":"
Target: DIY_900_RX_ESP8285_SX127x_via_UART
Please consult the Hardware Repository for your particular receiver.
"},{"location":"quick-start/receivers/firmware-version/","title":"Checking FW Version","text":""},{"location":"quick-start/receivers/firmware-version/#why-do-you-have-to-know-the-firmware-version","title":"Why do you have to know the Firmware Version?","text":"
Knowing the ExpressLRS Firmware Version that's currently in your devices will determine whether there is a need to update to a newer version or whether you can simply get your devices bound together without updating. For newcomers in the hobby, or for those just starting with ExpressLRS, it can be a bit daunting to flash a new device.
It is still recommended that you update your gear to the latest firmware version to ensure you have all the bugfixes and latest features.
"},{"location":"quick-start/receivers/firmware-version/#receiver-firmware-version","title":"Receiver Firmware Version","text":"via Web UIvia Lua Script
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the previous step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in sync with a TX Module, power Off the Radio & TX Module first then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, go back to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
Scan for the ExpressLRS RX Access Point.
If your Receiver is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also, try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Load the Web UI on your browser using these addresses:
http://10.0.0.1/ -If you have connected to the ExpressLRS RX Access Point
Note
This IP address is also often used by some routers. Computers with an ethernet connection to their routers will find that this page doesn't load the ExpressLRS Web UI and instead loads their router or ISP modem configuration dashboards.
We recommend disconnecting from the network first or trying a different device instead, e.g. smartphone or tablet.
http://elrs_rx.local - If you have previously set your Home WiFi SSID and Password into your Receiver when you flashed it.
Note
If your browser cannot resolve this address, chances are MDNS is not set up and working on your computer or network.
Use the IP Address instead! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a which will list all the devices in the Network.
Try each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in to your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
The Banner of the Web UI should tell you the firmware version flashed into your Receiver.
The ExpressLRS Web UI Banner
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter Key to activate the Script.
If the script is stuck on a \"Loading...\" screen, go back to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll to the bottom of the page and select Other Devices.
Press the Enter Key to open the Folder.
Select the Receiver Device and Press Enter to query its parameters.
The image below shows the Receiver Firmware Version info.
Shows the Happymodel EP Receiver has 3.2.1 Firmware Version with the Git Hash 8dbbdb.
Receiver Version Line on Colored Screen Radio
Once you have determined the firmware version that's currently flashed into your Receiver, you can now decide to whether keep using it as is or update to the latest version.
Versioning Scheme
The ExpressLRS Firmware Versioning scheme is based on the semantic versioning scheme.
A Version is defined or formatted as \"Major.Minor.Patch\"
- major = major new feature and/or incompatible changes\n- minor = minor features or enhancements and/or new targets\n- patch = bug-fixes\n
That first number in the Version string should match between a TX Module and a Receiver. Examples:
a Receiver with version string of 3.1.2 will sync and work with a TX Module with firmware version 3.0.1
a Receiver with version string of 3.2.0 will NOT sync or bind with a TX Module with firmware version 2.4.0
For the latest ExpressLRS firmware version, check the Releases page in Git Hub
"},{"location":"quick-start/receivers/firmware-version/#i-know-the-version-what-now","title":"I Know the Version. What Now?","text":"I have an old versionI have a recent one
See the next page for the typical updating procedure or expand the Updating Receivers section of the Menu on the left shown below.
You can also use the Search Bar on top of this page to search for the specific Updating/Flashing Guide for your Receiver.
See the Binding Procedure to sync your Receiver with your TX Module.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/flash2400/#check-your-target","title":"Check your Target","text":"
There are more ESP8285 based RXes in the market due to massive shortage of STM32 Chips. These support WiFi updating, and can be easily distinguished with a few tricks. The simplest way to tell is if on the rear of the RX (the side without the U.fl/SMD antenna) there is a large white component with the label RainSun (pictured below). If this is not there, you have an STM32 based target, if it is you have an _ESP_ target, and can update using Wifi!
RainSun Antenna
Note
New versions of the receiver also have the PCB Wifi Antenna, and doesn't have the RainSun SMD Antenna mentioned above. These will use the same ESP-based Target, not the STM-based target.
"},{"location":"quick-start/receivers/flash2400/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX Module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
The images above show the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/flash2400/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/flash2400/#updating-your-receiver-firmware-esp-based","title":"Updating your Receiver Firmware (ESP-based)","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash ESP 2.4GHz RX
NamimnoRC Flash 100mW Diversity 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
If your Receiver has Boot Pads instead of a Boot Button, solder the Boot Pads together or connect it to Ground. If your Receiver has a Boot Button, locate it then press & hold it.
Plug in your UART Adapter into a USB Port on your Computer.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Once the LED on the Receiver is lit up Solid, release/de-press the button on the receiver if it has one.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash ESP 2.4GHz RX
NamimnoRC Flash 100mW Diversity 2.4GHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
If your receiver has a boot pad instead of a boot button, make sure to disconnect it from ground or remove the solder bridge you made on step 2.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash ESP 2.4GHz RX
NamimnoRC Flash 100mW Diversity 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash ESP 2.4GHz RX
NamimnoRC Flash 100mW Diversity 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash ESP 2.4GHz RX
NamimnoRC Flash 100mW Diversity 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
"},{"location":"quick-start/receivers/flash2400/#updating-your-receiver-firmware-stm-based","title":"Updating your Receiver Firmware (STM-based)","text":"
Attention
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
via Passthroughvia STLink
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
If your receiver powers up with just USB connected to your flight controller, unplug it. Press and Hold the boot button on the receiver (not the FC) and then plug in the USB. Release the button right after the LED turn solid.
If your receiver only powers up with a LiPo connected to your flight controller, unplug it. Then unplug-replug the USB cable to your flight controller. Do not replug LiPo yet.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash STM 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the Retry... lines to appear in the Build Log. Connect the LiPo to power up the Receiver if it only powers up with a LiPo connected.
Retry... lines will not show up if your receiver is already in bootloader mode and gets powered up by USB.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Disconnect the Receiver from your Flight Controller.
Wire up the Receiver into an STLink V2 dongle. Find the CLK, DIO, 3v3 and Gnd pads and wire them to the corresponding pins of the dongle.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash STM 2.4GHz RX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Rewire your receiver to your Flight Controller.
"},{"location":"quick-start/receivers/foxeer2400/","title":"Foxeer LNA & Lite 2.4GHz","text":"
Advisory
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/foxeer2400/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
Foxeer LNA and Lite ELRS 2.4GHz
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/foxeer2400/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/foxeer2400/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Foxeer 2.4 GHz
Device:
Foxeer Lite 2.4GHz RX
Foxeer 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
If your Receiver has Boot Pads instead of a Boot Button, solder the Boot Pads together or connect it to Ground. If your Receiver has a Boot Button, locate it then press & hold it.
Plug in your UART Adapter into a USB Port on your Computer.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Once the LED on the Receiver is lit up Solid, release/de-press the button on the receiver if it has one.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Foxeer 2.4 GHz
Device:
Foxeer Lite 2.4GHz RX
Foxeer 2.4GHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
If your receiver has a boot pad instead of a boot button, make sure to disconnect it from ground or remove the solder bridge you made on step 2.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Foxeer 2.4 GHz
Device:
Foxeer Lite 2.4GHz RX
Foxeer 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Foxeer 2.4 GHz
Device:
Foxeer Lite 2.4GHz RX
Foxeer 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Foxeer 2.4 GHz
Device:
Foxeer Lite 2.4GHz RX
Foxeer 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/geprc2400/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
GEPRC Nano GEPRC Nano SE
The images above show the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/geprc2400/#identify-your-receiver-and-flash-the-correct-target","title":"Identify your receiver and flash the correct target","text":"
Important Step!
You MUST flash the correct firmware target to your receiver in order for it to work properly. Look closely at your receiver and make sure you are select the correct firmware target. Flashing the wrong target will result in extremely poor range or failure to connect.
How to identify the correct GEPRC 2.4GHz receiver target
"},{"location":"quick-start/receivers/geprc2400/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/geprc2400/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
GEPRC 2.4 GHz
Device:
GEPRC Nano(SE) 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
If your Receiver has Boot Pads instead of a Boot Button, solder the Boot Pads together or connect it to Ground. If your Receiver has a Boot Button, locate it then press & hold it.
Plug in your UART Adapter into a USB Port on your Computer.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Once the LED on the Receiver is lit up Solid, release/de-press the button on the receiver if it has one.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
GEPRC 2.4 GHz
Device:
GEPRC Nano(SE) 2.4GHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
If your receiver has a boot pad instead of a boot button, make sure to disconnect it from ground or remove the solder bridge you made on step 2.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
GEPRC 2.4 GHz
Device:
GEPRC Nano(SE) 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
GEPRC 2.4 GHz
Device:
GEPRC Nano(SE) 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
GEPRC 2.4 GHz
Device:
GEPRC Nano(SE) 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/geprc900/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/geprc900/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/geprc900/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
GEPRC 900 MHz
Device:
GEPRC Nano 900MHz RX
GEPRC Nano 900MHz PA500 RX
GEPRC True Diversity 900MHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
Locate the Boot button on your receiver, press and hold it.
Plug in your UART Adapter into a USB Port on your Computer. Release/de-press the Boot button.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
GEPRC 900 MHz
Device:
GEPRC Nano 900MHz RX
GEPRC Nano 900MHz PA500 RX
GEPRC True Diversity 900MHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
GEPRC 900 MHz
Device:
GEPRC Nano 900MHz RX
GEPRC Nano 900MHz PA500 RX
GEPRC True Diversity 900MHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
GEPRC 900 MHz
Device:
GEPRC Nano 900MHz RX
GEPRC Nano 900MHz PA500 RX
GEPRC True Diversity 900MHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
GEPRC 900 MHz
Device:
GEPRC Nano 900MHz RX
GEPRC Nano 900MHz PA500 RX
GEPRC True Diversity 900MHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
"},{"location":"quick-start/receivers/ghost2400/#flashingupdating-your-receiver-firmware","title":"Flashing/Updating your Receiver Firmware","text":"via STLinkvia Passthrough
Note
The only way to flash the Ghost Atto/Zepto to ExpressLRS for the first time is by using STLink. This is a one-way process. There is no returning to the factory firmware after flashing.
Disconnect the Receiver from your Flight Controller.
Wire up the Receiver into an STLink V2 dongle. Find the CLK, DIO, 3v3 and Gnd pads and wire them to the corresponding pins of the dongle.
IMRC Ghost
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
ImmersionRC 2.4 GHz
Device:
Ghost Atto 2.4GHz RX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Rewire your receiver to your Flight Controller.
Note
This method can only be used to UPDATE the ExpressLRS firmware on a Ghost Atto/Zepto.
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured. Also make sure [bootloaders] are already flashed to your R9 receiver when applicable.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
If your receiver powers up with just USB connected to your flight controller, unplug it. Press and Hold the boot button on the receiver (not the FC) and then plug in the USB. Release the button right after the LED turn solid.
If your receiver only powers up with a LiPo connected to your flight controller, unplug it. Then unplug-replug the USB cable to your flight controller. Do not replug LiPo yet.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
ImmersionRC 2.4 GHz
Device:
Ghost Atto 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the Retry... lines to appear in the Build Log. Connect the LiPo to power up the Receiver if it only powers up with a LiPo connected.
Retry... lines will not show up if your receiver is already in bootloader mode and gets powered up by USB.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/hglrc-hermes2400/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
HGLRC Hermes 2.4GHz
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/hglrc-hermes2400/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/hglrc-hermes2400/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 2.4 GHz
Device:
HGLRC Hermes 2.4GHz RX
HGLRC Gemini 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
If your Receiver has Boot Pads instead of a Boot Button, solder the Boot Pads together or connect it to Ground. If your Receiver has a Boot Button, locate it then press & hold it.
Plug in your UART Adapter into a USB Port on your Computer.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Once the LED on the Receiver is lit up Solid, release/de-press the button on the receiver if it has one.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 2.4 GHz
Device:
HGLRC Hermes 2.4GHz RX
HGLRC Gemini 2.4GHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
If your receiver has a boot pad instead of a boot button, make sure to disconnect it from ground or remove the solder bridge you made on step 2.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 2.4 GHz
Device:
HGLRC Hermes 2.4GHz RX
HGLRC Gemini 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 2.4 GHz
Device:
HGLRC Hermes 2.4GHz RX
HGLRC Gemini 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 2.4 GHz
Device:
HGLRC Hermes 2.4GHz RX
HGLRC Gemini 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/hglrc-hermes900/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
HGLRC Hermes 900MHz
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/hglrc-hermes900/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/hglrc-hermes900/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 900 MHz
Device:
HGLRC Hermes 900MHz RX
HGLRC Gemini 900M RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
Locate the Boot button on your receiver, press and hold it.
Plug in your UART Adapter into a USB Port on your Computer. Release/de-press the Boot button.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 900 MHz
Device:
HGLRC Hermes 900MHz RX
HGLRC Gemini 900M RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 900 MHz
Device:
HGLRC Hermes 900MHz RX
HGLRC Gemini 900M RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 900 MHz
Device:
HGLRC Hermes 900MHz RX
HGLRC Gemini 900M RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 900 MHz
Device:
HGLRC Hermes 900MHz RX
HGLRC Gemini 900M RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/hmep2400/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/hmep2400/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/hmep2400/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 2.4 GHz
Device:
HappyModel EP1/EP2 2.4GHz RX (EP1 & EP2)
HappyModel EP Dual 2.4GHz RX (EP Dual)
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
If your Receiver has Boot Pads instead of a Boot Button, solder the Boot Pads together or connect it to Ground. If your Receiver has a Boot Button, locate it then press & hold it.
Plug in your UART Adapter into a USB Port on your Computer.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Once the LED on the Receiver is lit up Solid, release/de-press the button on the receiver if it has one.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 2.4 GHz
Device:
HappyModel EP1/EP2 2.4GHz RX (EP1 & EP2)
HappyModel EP Dual 2.4GHz RX (EP Dual)
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
If your receiver has a boot pad instead of a boot button, make sure to disconnect it from ground or remove the solder bridge you made on step 2.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 2.4 GHz
Device:
HappyModel EP1/EP2 2.4GHz RX (EP1 & EP2)
HappyModel EP Dual 2.4GHz RX (EP Dual)
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up.
The file for the EP1 or EP2 receivers will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
The file for the EP Dual will be in bin format (firmware.bin).
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 2.4 GHz
Device:
HappyModel EP1/EP2 2.4GHz RX (EP1 & EP2)
HappyModel EP Dual 2.4GHz RX (EP Dual)
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up.
The file for the EP1 or EP2 receivers will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
The file for the EP Dual will be in bin format (firmware.bin).
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 2.4 GHz
Device:
HappyModel EP1/EP2 2.4GHz RX (EP1 & EP2)
HappyModel EP Dual 2.4GHz RX (EP Dual)
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/hmes900/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX Module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
Happymodel ES900RX
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/hmes900/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/hmes900/#updating-your-receiver-firmware-es900rx","title":"Updating your Receiver Firmware (ES900RX)","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel ES900 RX
HappyModel ES900 Dual RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
If your Receiver has Boot Pads instead of a Boot Button, solder the Boot Pads together or connect it to Ground. If your Receiver has a Boot Button, locate it then press & hold it.
Plug in your UART Adapter into a USB Port on your Computer.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Once the LED on the Receiver is lit up Solid, release/de-press the button on the receiver if it has one.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel ES900 RX
HappyModel ES900 Dual RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
If your receiver has a boot pad instead of a boot button, make sure to disconnect it from ground or remove the solder bridge you made on step 2.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel ES900 RX
HappyModel ES900 Dual RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up.
The file for the ES900 receivers will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
The file for the ES900 Dual will be in bin format (firmware.bin).
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel ES900 RX
HappyModel ES900 Dual RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up.
The file for the ES900 receivers will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
The file for the ES900 Dual will be in bin format (firmware.bin).
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel ES900 RX
HappyModel ES900 Dual RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
"},{"location":"quick-start/receivers/hmes900/#updating-your-receiver-firmware-es915rxes868rx","title":"Updating your Receiver Firmware (ES915RX/ES868RX)","text":"
Attention
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
via Passthroughvia STLink
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
If your receiver powers up with just USB connected to your flight controller, unplug it. Press and Hold the boot button on the receiver (not the FC) and then plug in the USB. Release the button right after the LED turn solid.
If your receiver only powers up with a LiPo connected to your flight controller, unplug it. Then unplug-replug the USB cable to your flight controller. Do not replug LiPo yet.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel ES915 RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the Retry... lines to appear in the Build Log. Connect the LiPo to power up the Receiver if it only powers up with a LiPo connected.
Retry... lines will not show up if your receiver is already in bootloader mode and gets powered up by USB.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Disconnect the Receiver from your Flight Controller.
Wire up the Receiver into an STLink V2 dongle. Find the CLK, DIO, 3v3 and Gnd pads and wire them to the corresponding pins of the dongle.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel ES915 RX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
"},{"location":"quick-start/receivers/hmpp2400/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"Happymodel PP
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
Note
The PP doesn't have a Boot pad so there's no need to bridge any pads.
"},{"location":"quick-start/receivers/hmpp2400/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed smoothly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy (of high importance with the Passthrough Flashing Method).
"},{"location":"quick-start/receivers/hmpp2400/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia STLink
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
If your receiver powers up with just USB connected to your flight controller, unplug it. Press and Hold the boot button on the receiver (not the FC) and then plug in the USB. Release the button right after the LED turn solid.
If your receiver only powers up with a LiPo connected to your flight controller, unplug it. Then unplug-replug the USB cable to your flight controller. Do not replug LiPo yet.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 2.4 GHz
Device:
HappyModel PP 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the Retry... lines to appear in the Build Log. Connect the LiPo to power up the Receiver if it only powers up with a LiPo connected.
Retry... lines will not show up if your receiver is already in bootloader mode and gets powered up by USB.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Disconnect the Receiver from your Flight Controller.
Wire up the Receiver into an STLink V2 dongle. Find the CLK, DIO, 3v3 and Gnd pads and wire them to the corresponding pins of the dongle.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 2.4 GHz
Device:
HappyModel PP 2.4GHz RX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Rewire your receiver to your Flight Controller following the Receiver Wiring guide.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/iflight2400/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
IFlight 2.4GHz IFlight 2.4GHz
The images above show the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/iflight2400/#identify-your-receiver-and-flash-the-correct-target","title":"Identify your receiver and flash the correct target","text":"
Important Step!
You MUST flash the correct firmware target to your receiver in order for it to work properly. Look closely at your receiver and make sure you are select the correct firmware target. Flashing the wrong target will result in extremely poor range or failure to connect.
How to identify the correct iFlight 2.4GHz receiver target
"},{"location":"quick-start/receivers/iflight2400/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/iflight2400/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
iFlight 2.4 GHz
Device:
iFlight 2.4GHz RX
iFlight 2.4GHz Nano RX (smaller)
iFlight 2.4GHz 500mW RX
iFlight 2.4GHz 250mW Diversity RX (two antennas)
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
Locate the Boot button on your receiver, press and hold it.
Plug in your UART Adapter into a USB Port on your Computer. Release/de-press the Boot button.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
iFlight 2.4 GHz
Device:
iFlight 2.4GHz RX
iFlight 2.4GHz Nano RX (smaller)
iFlight 2.4GHz 500mW RX
iFlight 2.4GHz 250mW Diversity RX (two antennas)
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
iFlight 2.4 GHz
Device:
iFlight 2.4GHz RX
iFlight 2.4GHz Nano RX (Smaller)
iFlight 2.4GHz 500mW RX
iFlight 2.4GHz 250mW Diversity RX (two antennas)
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
iFlight 2.4 GHz
Device:
iFlight 2.4GHz RX
iFlight 2.4GHz Nano RX (Smaller)
iFlight 2.4GHz 500mW RX
iFlight 2.4GHz 250mW Diversity RX (two antennas)
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
iFlight 2.4 GHz
Device:
iFlight 2.4GHz RX
iFlight 2.4GHz Nano RX (Smaller)
iFlight 2.4GHz 500mW RX
iFlight 2.4GHz 250mW Diversity RX (two antennas)
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/iflight900/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
IFlight 900MHz
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/iflight900/#identify-your-receiver-and-flash-the-correct-target","title":"Identify your receiver and flash the correct target","text":"
Important Step!
You MUST flash the correct firmware target to your receiver in order for it to work properly. Look closely at your receiver and make sure you are select the correct firmware target. Flashing the wrong target will result in extremely poor range or failure to connect.
How to identify the correct iFlight 900MHz receiver target
"},{"location":"quick-start/receivers/iflight900/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/iflight900/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
iFlight 900 MHz
Device:
iFlight 900MHz RX
iFlight 900MHz Nano RX (smaller)
iFlight 900MHz 500mW RX
iFlight 900MHz 500mW Diversity RX (two antennas)
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
Locate the Boot button on your receiver, press and hold it.
Plug in your UART Adapter into a USB Port on your Computer. Release/de-press the Boot button.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
iFlight 900 MHz
Device:
iFlight 900MHz RX
iFlight 900MHz Nano RX (smaller)
iFlight 900MHz 500mW RX
iFlight 900MHz 500mW Diversity RX (two antennas)
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
iFlight 900 MHz
Device:
iFlight 900MHz RX
iFlight 900MHz Nano RX (smaller)
iFlight 900MHz 500mW RX
iFlight 900MHz 500mW Diversity RX (two antennas)
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
iFlight 900 MHz
Device:
iFlight 900MHz RX
iFlight 900MHz Nano RX (smaller)
iFlight 900MHz 500mW RX
iFlight 900MHz 500mW Diversity RX (two antennas)
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
iFlight 900 MHz
Device:
iFlight 900MHz RX
iFlight 900MHz Nano RX (smaller)
iFlight 900MHz 500mW RX
iFlight 900MHz 500mW Diversity RX (two antennas)
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/jumper-aion/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
Jumper Aion Mini/Nano
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
Take Note
The Jumper Aion Mini has its antenna near the center, beside the boot button. The Jumper Aion Nano has its antenna near the edge, with another chip beside it.
"},{"location":"quick-start/receivers/jumper-aion/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/jumper-aion/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION Mini 2.4GHz RX
Jumper AION Nano 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
Locate the Boot button on your receiver, press and hold it.
Plug in your UART Adapter into a USB Port on your Computer. Release/de-press the Boot button.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION Mini 2.4GHz RX
Jumper AION Nano 2.4GHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION Mini 2.4GHz RX
Jumper AION Nano 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION Mini 2.4GHz RX
Jumper AION Nano 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION Mini 2.4GHz RX
Jumper AION Nano 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
"},{"location":"quick-start/receivers/jumper900/#flashingupdating-your-receiver-firmware","title":"Flashing/Updating your Receiver Firmware","text":"via STLinkvia Passthrough
Note
The only way to flash the Jumper R9 Mini to ExpressLRS for the first time is by using STLink. This is a one-way process. There is no returning to the factory firmware after flashing.
Disconnect the Receiver from your Flight Controller.
Wire up the Receiver into an STLink V2 dongle. Connect + to 3v3, - to GND, C to CLK and D to DIO.
Jumper R9 Mini
Because those pins are so small one option is to only solder wires on the CLK and DIO then power the receiver with the 5v pin with an external power source. Connect - (Gnd) to both power source and the STLink dongle.
Disable 'Readout Protection'. To do this download the ST-LINK Utility and follow this quick how to video. Or alternatively under linux you can use OpenOCD.
How to video:
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 900 MHz
Device:
Jumper 900 Mini RX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Rewire your receiver to your Flight Controller. Connect RX2 and TX2 (you will need to solder on the STM32 pins; see step 2 above) to a flight controller. Configure your flight controller per the FC Configuration Guide.
Note
This method can only be used to UPDATE the ExpressLRS firmware on a Jumper R9 mini.
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured. Also make sure [bootloaders] are already flashed to your R9 receiver when applicable.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
If you have to plug in LiPo to power up your Receiver, make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 900 MHz
Device:
Jumper 900 Mini RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the Retry... lines to appear in the Build Log. Connect the LiPo to power up the Receiver if it only powers up with a LiPo connected.
Retry... lines will not show up if your receiver is already in bootloader mode and gets powered up by USB.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/matek2400/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
R24-D Diversity R24-S SMD
The images above show the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/matek2400/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/matek2400/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Matek Systems 2.4 GHz
Device:
MATEK R24-S 2.4GHz RX
MATEK R24-D 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
If your Receiver has Boot Pads instead of a Boot Button, solder the Boot Pads together or connect it to Ground. If your Receiver has a Boot Button, locate it then press & hold it.
Plug in your UART Adapter into a USB Port on your Computer.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Once the LED on the Receiver is lit up Solid, release/de-press the button on the receiver if it has one.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Matek Systems 2.4 GHz
Device:
MATEK R24-S 2.4GHz RX
MATEK R24-D 2.4GHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
If your receiver has a boot pad instead of a boot button, make sure to disconnect it from ground or remove the solder bridge you made on step 2.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Matek Systems 2.4 GHz
Device:
MATEK R24-S 2.4GHz RX
MATEK R24-D 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Matek Systems 2.4 GHz
Device:
MATEK R24-S 2.4GHz RX
MATEK R24-D 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Matek Systems 2.4 GHz
Device:
MATEK R24-S 2.4GHz RX
MATEK R24-D 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
The R9Mini/R9MM, R9MX and R9Slim+ require ExpressLRS Bootloaders to be flashed before the ExpressLRS firmware. The R9Slim doesn't have a bootloader and first time flash requires STLink.
Download the bootloader .frk file for your respective receiver. The files are as follows:
R9mm/mini: r9mm_elrs_bl.frk (14kB) or r9mm_no_btn_elrs_bl.frk (14kB) (no_btn bootloader is only used if your bind/boot button on the receiver is faulty or has gone bad.)
Copy the relevant file to your handset's SD card (You can put it inside /FIRMWARE folder for easy access).
Wire the receiver to your radio's Smart Port, as shown:
Next, flash the .frk via the S.port flashing option in OpenTX or EdgeTX (It helps if the External RF module is set to PPM mode.)
Open the System Menu on the Radio
For radio handsets with dedicated System Key, press the SYS Key.
For radio handsets with a single Menu Key, long-press the Menu Key.
Press the Page Key until you reach the SD-HC Card page.
Select the FIRMWARE folder and press Enter.
Select the .frk bootloader file then long-press the Enter Key.
Select Flash external module and press Enter
Press Enter once the Writing is complete.
Once done, unplug the receiver and your bootloader is flashed.
FYI
You only need to flash the Bootloader ONCE. After it's flashed into the receiver, you don't have to reflash it in every update.
R9Slim doesn't have a bootloader. As such, you need to flash it first via STLink.
"},{"location":"quick-start/receivers/r9/#troubleshooting-no-sync","title":"Troubleshooting No Sync","text":"
Setting the External RF module to PPM mode helps.
Check if the receiver has its LED lit up or if it's powered.
Check whether you've set your Max Bauds to 115200, especially if you're using a QX7 or an X9D (on OneBit Firmware or EdgeTX). If so, put it back to 400000 and try again.
"},{"location":"quick-start/receivers/r9/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"Wiring up receiver
Note
This will be the same wiring you'll use for flying and the subsequent firmware updates (via Passthrough). Forget the factory wiring guide!
R9Slim need to be flashed via STLink first before you wire it up to your Flight Controller.
"},{"location":"quick-start/receivers/r9/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply on INAV, Betaflight and other flight controller software.
Ports Tab should be setup so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
"},{"location":"quick-start/receivers/r9/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia STLink
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured. Also make sure bootloaders are already flashed to your R9 receiver when applicable.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
If your receiver powers up with just USB connected to your flight controller, unplug it. Press and Hold the boot button on the receiver (not the FC) and then plug in the USB. Release the button once the green and red LEDs blink alternately.
If your receiver only powers up with a LiPo connected to your flight controller, unplug it. Then unplug-replug the USB cable to your flight controller. Do not replug LiPo yet.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
FrSky 900 MHz
Device:
FrSky R9MM/Mini 900MHz RX
FrSky R9MX 900MHz RX
FrSky R9 Slim 900MHz RX (If already flashed via STLink)
FrSky R9 Slim Plus 900MHz RX
FrSky R9 Slim Plus OTA 900MHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the Retry... lines to appear in the Build Log. Connect the LiPo to power up the Receiver if it only powers up with a LiPo connected.
Retry... lines will not show up if your receiver is already in bootloader mode and gets powered up by USB.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Disconnect the Receiver from your Flight Controller.
Wire up the Receiver into an STLink V2 dongle. Find the CLK, DIO, 3v3 and Gnd pads and wire them to the corresponding pins of the dongle.
R9Mini/R9MM
R9MX
R9Slim/R9Slim+
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
FrSky 900 MHz
Device:
FrSky R9MM/Mini 900MHz RX
FrSky R9MX 900MHz RX
FrSky R9 Slim 900MHz RX (If already flashed via STLink)
FrSky R9 Slim Plus 900MHz RX
FrSky R9 Slim Plus OTA 900MHz RX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/radiomaster-rp-2400/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
The images above show the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/radiomaster-rp-2400/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/radiomaster-rp-2400/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
RadioMaster 2.4 GHz
Device:
RadioMaster RP1 2.4GHz RX
RadioMaster RP2 2.4GHz RX
RadioMaster RP3 Diversity 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
If your Receiver has Boot Pads instead of a Boot Button, solder the Boot Pads together or connect it to Ground. If your Receiver has a Boot Button, locate it then press & hold it.
Plug in your UART Adapter into a USB Port on your Computer.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Once the LED on the Receiver is lit up Solid, release/de-press the button on the receiver if it has one.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
RadioMaster 2.4 GHz
Device:
RadioMaster RP1 2.4GHz RX
RadioMaster RP2 2.4GHz RX
RadioMaster RP3 Diversity 2.4GHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
If your receiver has a boot pad instead of a boot button, make sure to disconnect it from ground or remove the solder bridge you made on step 2.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
RadioMaster 2.4 GHz
Device:
RadioMaster RP1 2.4GHz RX
RadioMaster RP2 2.4GHz RX
RadioMaster RP3 Diversity 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
RadioMaster 2.4 GHz
Device:
RadioMaster RP1 2.4GHz RX
RadioMaster RP2 2.4GHz RX
RadioMaster RP3 Diversity 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
RadioMaster 2.4 GHz
Device:
RadioMaster RP1 2.4GHz RX
RadioMaster RP2 2.4GHz RX
RadioMaster RP3 Diversity 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
Note
This is only guaranteed to work on the v3.0 of the receiver.
"},{"location":"quick-start/receivers/siyiFRmini/#flashingupdating-your-receiver-firmware","title":"Flashing/Updating your Receiver Firmware","text":"via STLinkvia Passthrough
Note
The only way to flash the FR Mini to ExpressLRS for the first time is using STLink. This is a one-way process, there is no returning to the stock firmware after flashing.
Disconnect the Receiver from your Flight Controller.
Wire up the Receiver into an STLink V2 dongle. Find the CLK, DIO,RST, 3v3(VDD) and Gnd pads and wire them to the corresponding pins of the dongle.
NOTICE
VDD is 3.3v ONLY! Do not connect 5v here!
Siyi FR Mini
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
SIYI 2.4 GHz
Device:
SIYI FM30 Mini 2.4GHz RX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
This method can only be used to UPDATE the ExpressLRS firmware on an FRmini.
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured. Also make sure [bootloaders] are already flashed to your R9 receiver when applicable.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
If your receiver powers up with just USB connected to your flight controller, unplug it. Press and Hold the boot button on the receiver (not the FC) and then plug in the USB. Release the button right after the LED turn solid.
If your receiver only powers up with a LiPo connected to your flight controller, unplug it. Then unplug-replug the USB cable to your flight controller. Do not replug LiPo yet.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
SIYI 2.4 GHz
Device:
SIYI FM30 Mini 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the Retry... lines to appear in the Build Log. Connect the LiPo to power up the Receiver if it only powers up with a LiPo connected.
Retry... lines will not show up if your receiver is already in bootloader mode and gets powered up by USB.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
If your Receiver has Boot Pads instead of a Boot Button, solder the Boot Pads together or connect it to Ground. If your Receiver has a Boot Button, locate it, then press & hold it.
Plug in your UART Adapter into a USB Port on your Computer.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Once the LED on the Receiver is lit up Solid, release/de-press the button on the receiver if it has one.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
If your receiver has a boot pad instead of a boot button, make sure to disconnect it from ground or remove the solder bridge you made on step 2.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/vantac2400/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
Vantac ELRS 2.4GHz
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/vantac2400/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/vantac2400/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Vantac 2.4 GHz
Device:
Vantac 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
Locate the Boot button on your receiver, press and hold it.
Plug in your UART Adapter into a USB Port on your Computer. Release/de-press the Boot button.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Vantac 2.4 GHz
Device:
Vantac 2.4GHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Vantac 2.4 GHz
Device:
Vantac 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Vantac 2.4 GHz
Device:
Vantac 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Vantac 2.4 GHz
Device:
Vantac 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
"},{"location":"quick-start/receivers/voyager900/","title":"NamimnoRC Voyager","text":""},{"location":"quick-start/receivers/voyager900/#check-your-target","title":"Check your Target","text":"
There are more ESP8285 based RXes in the market due to massive shortage of STM32 Chips. These support WiFi updating, and can be easily distinguished with a few tricks. The simplest way to tell is if on the rear of the RX (the side without the U.fl/SMD antenna) there is a large white component with the label RainSun (pictured below). If this is not there, you have an STM32 based target, if it is you have an _ESP_ target, and can update using Wifi!
RainSun Antenna
Note
New versions of the receiver also have the PCB Wifi Antenna, and doesn't have the RainSun SMD Antenna mentioned above. These will use the same ESP-based Target, not the STM-based target.
"},{"location":"quick-start/receivers/voyager900/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX Module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/voyager900/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/voyager900/#updating-your-receiver-firmware-esp-based","title":"Updating your Receiver Firmware (ESP-based)","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
If you have to plug in LiPo to power up your Receiver, make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 900 MHz
Device:
NamimnoRC Voyager ESP 900MHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
If your Receiver has Boot Pads instead of a Boot Button, solder the Boot Pads together or connect it to Ground. If your Receiver has a Boot Button, locate it then press & hold it.
Plug in your UART Adapter into a USB Port on your Computer.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Once the LED on the Receiver is lit up Solid, release/de-press the button on the receiver if it has one.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 900 MHz
Device:
NamimnoRC Voyager ESP 900MHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
If your receiver has a boot pad instead of a boot button, make sure to disconnect it from ground or remove the solder bridge you made on step 2.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 900 MHz
Device:
NamimnoRC Voyager ESP 900MHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 900 MHz
Device:
NamimnoRC Voyager ESP 900MHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 900 MHz
Device:
NamimnoRC Voyager ESP 900MHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED after a few seconds.
"},{"location":"quick-start/receivers/voyager900/#updating-your-receiver-firmware-stm-based","title":"Updating your Receiver Firmware (STM-based)","text":"
Attention
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
via Passthroughvia STLink
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
If your receiver powers up with just USB connected to your flight controller, unplug it. Press and Hold the boot button on the receiver (not the FC) and then plug in the USB. Release the button right after the LED turn solid.
If your receiver only powers up with a LiPo connected to your flight controller, unplug it. Then unplug-replug the USB cable to your flight controller. Do not replug LiPo yet.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 900 MHz
Device:
NamimnoRC Voyager STM 900MHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the Retry... lines to appear in the Build Log. Connect the LiPo to power up the Receiver if it only powers up with a LiPo connected.
Retry... lines will not show up if your receiver is already in bootloader mode and gets powered up by USB.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Disconnect the Receiver from your Flight Controller.
Wire up the Receiver into an STLink V2 dongle. Find the CLK, DIO, 3v3 and Gnd pads and wire them to the corresponding pins of the dongle.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 900 MHz
Device:
NamimnoRC Voyager STM 900MHz RX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manufacturer-suggested Receiver UARTs, or UARTs alloted for Receivers usually have a pull-down resistor to aid with SBUS (RX pad inversion) which will result into SOLID LEDs on the ESP-based ExpressLRS Receivers. It is best to avoid those UARTs unless you know your UARTs.
Hint!
KISS FCs may label its UARTs differently. You might have to wire up the RX pin into an RX pad, and the TX pin into a TX pad. Always check your FC wiring guide/manual.
UART-based ExpressLRS Receivers use the CRSF Serial Protocol to communicate with a Flight Controller. This protocol uses two pins: one for the Control Signals and the other for the Telemetry Signals. Think of it as a two-lane, no-counterflow highway.
Here's a typical ExpressLRS Receiver pinout indicating to which Flight Controller pads each pin should be connected:
The TX pin of an ExpressLRS Receiver sends or transmits the Control Signals it received from the Radio to the Flight Controller. Meanwhile, the RX pin of an ExpressLRS Receiver accepts or receives the Telemetry Data (like Battery Voltage, Current Draw, GPS Coordinates and/or Craft Attitude) from the Flight Controller for sending back to the Radio Handset.
What's a UART? (click/tap to expand)
A UART is a pair of RX and TX pads on the Flight Controller. It's commonplace to refer to it as your Flight Controller's USB ports where you can connect different peripherals like a GPS or a Receiver. Only one device can occupy a UART and it can only do one function.
R3 and T3 belongs to UART3; RX2 and TX2 belongs to UART2. Flight Controller Manufacturers label their UARTs differently. Some use just \"R\" and \"T\" followed by the UART number. Others use \"RX\" and \"TX\" followed by the UART number.
UART is an acronym for Universal Asynchronous Receiver/Transmitter
"},{"location":"quick-start/receivers/wiring-up/#connecting-a-receiver","title":"Connecting a Receiver","text":"
Now that you have some basic info, connect your receiver to any free UART on your Flight controller. Check your Flight Controller Wiring Manual which UARTs you can use.
The GND or G pad should be connected to any Ground pad on the Flight Controller(FC)
The VCC or 5 pad should be connected to any 5v (or 4v5) pad on the Flight Controller(FC)
The TX or T pad should be connected to an RX pad of the same UART number where the RX or R wire is on the Flight Controller(FC)
The RX or R pad should be connected to a TX pad of the same UART number where the TX or T wire is on the Flight Controller(FC)
Check for shorts between pads and clean up flux or any soldering residue if you have soldered the receiver yourself.
Not so fast!
DO NOT shrink wrap or tuck away the receiver yet. We have to do some preliminary testing first!
Ensure there are no shorts on your wiring and power up the receiver.
Best to power up the flight controller with a LiPo to ensure the receiver will work normally on flight-ready conditions.
It is important to ensure there are no shorts on your wiring BEFORE you power up the system.
Observe the Receiver LED. It should have one of these behaviors:
LED Indication Status Slow blink 500ms on/off Waiting for connection from transmitter Double blink then pause Binding mode is active Fast blinking 25ms on/off WiFi mode has started. Starts after 60s. Solid on Bootloader mode is active
If the Receiver uses an RGB LED(e.g. Foxeer LNA, BetaFPV SuperD, Happymodel EP Dual), the following can be observed:
LED Indication Status Rainbow fade effect Starting Up Slow blink 500ms on/off Waiting for connection from transmitter Orange Double blink then pause Binding mode enabled Green heartbeat WiFi mode has started. Starts after 60s
If the Receiver LED doesn't light up at all, quickly disconnect the power and check your wiring.
If your receiver has the RGB LED (e.g. Foxeer LNA, BetaFPV SuperD, Happymodel EP Dual), and the receiver LED is not lighting up despite making sure it's wired up correctly, this could mean that the Receiver is in Bootloader Mode.
If your Receiver LED lights up but it's just a Solid light, it is in Bootloader mode as the chart above indicates.
My Receiver is in Bootloader Mode! (click/tap to expand)
Here are the things you can do if the Receiver is in Bootloader Mode:
Check if the Boot button on the Receiver is being pressed or if it's damaged.
If the button is being pressed or pinched, remove the cause of the pressing or pinching. Heatshrink can sometimes press a button on the receiver.
If the button is damaged, remove the button or replace the receiver with a better one. Consider asking the seller for a replacement.
If the receiver doesn't have a Boot button and instead has a Boot pad, check if the Boot pad is not connected to a Ground pad.
If the Boot pad is connected to a Ground pad, disconnect or remove the connection.
Disconnect the RX and TX wires of the Receiver from the Flight Controller. Reconnect power to the drone or aircraft. Observe the LED on the Receiver once again.
If it starts Blinking Slowly (500ms Blink Pattern), you will need to move the receiver wiring to a different UART.
If the other UART is occupied by another peripheral, disconnect it and swap places with the Receiver.
If there is no other Full UART, you can try wiring a Pull-up Resistor: Connect a Resistor (300 Ohm to 1k Ohm value; a lower value is more effective) between this UART's RX pad and either a 5v or 3.3v pad as shown below:
If you are using any of the Digital FPV systems like the DJI FPV Air Unit, Caddx Vista or DJI O3 Air Unit, and you wired or connected all six wires to your Flight Controller, you will need to remove the SBUS/DJI HDL wire.
If your receiver is behaving normally (i.e. not in Bootloader Mode), then you can power down your aircraft and proceed to the next step: Configuring your Flight Controller
Not all Jumper T Pros come with an internal ELRS transmitter. Some come with a \"JP4in1 multi-protocol module\" or \"CC2500 multi-protocol module\". This tutorial does not apply to those Jumper T Pros. Check the page you bought it from to determine which unit you purchased.
Advisory
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
"},{"location":"quick-start/transmitters/aion-internal/#updating-and-recovery-procedures","title":"Updating and Recovery Procedures","text":"via WiFi Updatingvia ETX Passthrough Recoveryvia UART Recovery Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device Target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION T-Pro 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device Target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION T-Pro 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device Target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION T-Pro 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Info
ETX Passthrough is the result of the collaborative effort between RadioMaster, EdgeTX and ExpressLRS.
It is only available on Radios with Internal ExpressLRS Modules.
Before you start, ensure you have the latest EdgeTX firmware version on your Radio. Consult the EdgeTX documentation regarding the updating process.
For the Jumper T-Pro, update it to at least EdgeTX 2.7.1 (a55aff0) for full EdgeTX support.
Hot Tip
To ensure updating success with this method, update the EdgeTX firmware on the radio to at least EdgeTX 2.7.1 (a55aff0). The EdgeTX Firmware that comes with this radio is a pre-release version.
Simplest EdgeTX Updating Procedure (click/tap to expand)
Visit http://buddy.edgetx.org/.
Select the EdgeTX version and the Radio Model you want to update from the Left-hand side column.
Click the Download .bin button at the bottom of the page.
Save the firmware file into your Radio's SD Card, inside the Firmware Folder.
Reboot the Radio into DFU/Bootloader mode.
Turn off your radio.
Press and hold the two horizontal Trim switches then press the Power button. The Screen should Light up. Let go of the buttons.
Some Radios have a different procedure, like the BetaFPV Lite Radio 3 Pro. Consult the Manual for the steps to get it into this DFU/Bootloader mode.
Select Write Firmware.
Navigate to the EdgeTX firmware file you just downloaded.
Follow the screen prompts.
Once Writing is complete, reboot the radio.
Check the Radio's Version Page to verify you have the version you need.
Also, make sure you have an internal ELRS module on your Radio. The following steps only apply to handsets with ExpressLRS-specific internal modules.
The current Model on the radio should be using the Internal ExpressLRS Module. Test this by loading the ExpressLRS Lua Script from the Tools Menu.
There's one more setting you want to make sure is set properly before proceeding.
Press the SYS Key on the Radio.
Radios without a dedicated SYS Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to get to the System Menu.
Press the PAGE Key until you reach the Hardware Page.
Scroll down until you see the Serial Ports settings.
Select or highlight USB-VCP. Press Enter and use the Scroll Wheel to set it to CLI mode if it is set to a different setting. Press Enter once more to confirm the changes.
Exit the Hardware menu by long-pressing RTN Key.
Before proceeding, you will need to disassemble the radio. You will need a small Philips screwdriver for this. Ten(10) small Philips screws keep both halves of the radio together.
Handle with Care
There are wires connecting the module to the main board of the radio, along with battery leads. Do not yank out the back cover of the radio from its front half. You don't need to disconnect the wires from the mainboard.
Once you have both halves of the radio apart, you will need to solder a piece of wire on the Boot pad into one of the momentary switches on the radio. Refer to the image below where to solder the ends of the wire.
Once the wire is soldered adequately, reassemble the radio. Tighten up the ten(10) screws to secure both halves of the radio.
Note
If you plan to use the switch as an Aux channel, remove the wire afterward. Leaving this wire connected means the Aux channel will output a constant \"High\" signal.
Now follow the next steps to get your Internal ExpressLRS Module Updated or Recovered:
Connect your powered-up Radio to your Computer via a USB Data Cable.
On your Radio, scroll down and select USB Serial(VCP) then press the Enter Key. Set your Radio aside in the meantime.
On your Computer, check whether your Radio is being recognized correctly as a STMicroelectronics Virtual COM Port device.
Important
This is a vital step and a common failure point. Pay attention.
Windows Users can use Device Manager to check whether the Radio is being recognized correctly.
Yellow Caution Triangles in the Device Manager, or any mention of <Radio Name> Serial Port means drivers aren't installed.
Download the Driver package first. Unzip/extract the contents of the package and run/execute (double-click) the installer file (VCP_V1.5.0_Setup_W7_x64_64bits.exe for Windows 10 Users).
Once Drivers are installed, check again if the Radio is now being recognized correctly. You may have to first unplug-replug the USB Cable or even reboot your computer.
You only have to do this once usually.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device Target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION T-Pro 2.4GHz TX
Set the Flashing Method to EdgeTXPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the Passthrough Init or Passthrough Done section of the log and Press the switch in the radio where you wired up the boot button and hold it until the script has connected. See the image below for the correct timing.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
If you didn't get it right and it fails, don't worry. Just retry and it should go through.
Unplug your Radio from USB.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated or you have it recovered.
Disassemble the radio. You will need a small Philips screwdriver for this. Ten(10) small Philips screws keep both halves of the radio together.
Handle with Care
There are wires connecting the module to the main board of the radio, along with battery leads. Do not yank out the back cover of the radio from its front half. You don't need to disconnect the wires from the mainboard.
Disconnect the internal module from the mainboard of the radio. The pin-out is as follows:
White wire is the RX.
Yellow wire is the TX.
Red wire is the 5v pin.
The Black wire is the Gnd pin.
Connect these four wires into your FTDI dongle or a USB to Serial Adapter: RX pin into the TX pin; TX pin into the RX pin; 5v to 5v, and Gnd to Gnd.
Before you connect the FTDI dongle/Serial Adapter to the USB port of your Computer, hold down the Boot button. Keep the button pressed until you have connected the Serial Adapter to your USB port.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device Target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION T-Pro 2.4GHz TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Attention
Incorrect or loose connections can cause this method to fail. If it does, disconnect the Serial Adapter from the USB, ensure you have the proper connection, and repeat the process. Press and hold the boot button before connecting the Serial Adapter to the USB.
Disconnect the FTDI/UART Adapter and reconnect the module back to the radio mainboard, as shown below.
Reassemble the radio (but do not put in the screws yet) and verify you have a working module once by running the ExpressLRS Lua script.
Once you've verified that your Internal ExpressLRS module is working, replace the screws and tighten things up. Chug one down and celebrate!
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
"},{"location":"quick-start/transmitters/axisflying-thor/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia UART Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Axisflying 2.4 GHz
Device:
AXIS Thor 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Axisflying 2.4 GHz
Device:
AXIS Thor 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Axisflying 2.4 GHz
Device:
AXIS Thor 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here: CP210x Drivers
Windows Users should download the CP210x Windows Drivers package for easier installation. Unzip/Extract the contents of the package and run the setup wizard.
Make sure the switch on the backside of the module is set to the leftmost position.
Note
To flash the TX itself, the switch on the back side of the module must be set to the leftmost position. To flash the TX backpack, the switch must be set to the rightmost position. For normal operation, the switch must be centered.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Axisflying 2.4 GHz
Device:
AXIS Thor 2.4GHz TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB. Return the switch in the back to \"Normal Operation\" position, center.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
"},{"location":"quick-start/transmitters/axisflying-thor/#using-the-module-on-a-dx9","title":"Using the module on a DX9","text":"
Install the latest DX9 firmware with CRSF v2 support via Serial port.
Wire up Power (VBAT & GND) as per Crossfire install instructions.
Use Signal from DX9 to S.Port pin of the Thor TX module.
Optional: Connect an external power source via XT30.
Flash the TX module with UART_INVERTED unchecked.
Adjust your Packet Rate to 250Hz using the Screen & Joystick.
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
"},{"location":"quick-start/transmitters/betafpv2400/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia UART Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz Nano TX
BETAFPV 2.4GHz Micro TX
BETAFPV 2.4GHz 1W Micro TX
BETAFPV SuperG 2.4GHz Gemini TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz Nano TX
BETAFPV 2.4GHz Micro TX
BETAFPV 2.4GHz 1W Micro TX
BETAFPV SuperG 2.4GHz Gemini TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz Nano TX
BETAFPV 2.4GHz Micro TX
BETAFPV 2.4GHz 1W Micro TX
BETAFPV SuperG 2.4GHz Gemini TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here: CP210x Drivers
Windows Users should download the CP210x Windows Drivers package for easier installation. Unzip/Extract the contents of the package and run the setup wizard.
Some TX Modules have switches to change how the USB port interacts with the different components in the module. Make sure to set it in the position for \"Flashing the TX Module via UART\".
The BetaFPV Micro modules have dipswitches at the back. Set switches 1 & 2 to On, set the rest of the switches to Off.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz Nano TX
BETAFPV 2.4GHz Micro TX
BETAFPV 2.4GHz 1W Micro TX
BETAFPV SuperG 2.4GHz Gemini TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB. Return the dipswitches at the back into the \"Normal Operation\" position.
Switches 1,2,5,6,7 should be Off; 3 & 4 should be On. Applicable to the Micro-size module only.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
If you've followed any of the steps above and still cannot get your devices flashed and updated, see this video for the explanation of why and the fix to get your devices flashed and updated (applies to the Nano modules only).
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
"},{"location":"quick-start/transmitters/betafpv900/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia UART Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV 900MHz Nano TX
BETAFPV 900MHz Micro TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV 900MHz Nano TX
BETAFPV 900MHz Micro TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV 900MHz Nano TX
BETAFPV 900MHz Micro TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here: CP210x Drivers
Windows Users should download the CP210x Windows Drivers package for easier installation. Unzip/Extract the contents of the package and run the setup wizard.
Some TX Modules have switches to change how the USB port interacts with the different components in the module. Make sure to set it in the position for \"Flashing the TX Module via UART\".
The BetaFPV Micro modules have dipswitches at the back. Set switches 1 & 2 to On, set the rest of the switches to Off.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV 900MHz Nano TX
BETAFPV 900MHz Micro TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB. Return the dipswitches at the back into the \"Normal Operation\" position.
Switches 1,2,5,6,7 should be Off; 3 & 4 should be On. Applicable to the Micro-size module only.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
If you've followed any of the steps above and still cannot get your devices flashed and updated, see this video for the explanation of why and the fix to get your devices flashed and updated (applies to the Nano modules only).
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
"},{"location":"quick-start/transmitters/betafpvlr3pro/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia ETX Passthrough Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz LiteRadio 3 Pro
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz LiteRadio 3 Pro
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz LiteRadio 3 Pro
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Info
ETX Passthrough is the result of the collaborative effort between RadioMaster, EdgeTX and ExpressLRS.
It is only available on Radios with Internal ExpressLRS Modules.
Before you start, ensure you have the latest EdgeTX firmware version on your Radio. Consult the EdgeTX documentation regarding the updating process.
For the BetaFPV Lite Radio 3 Pro, update it to at least EdgeTX 2.8.0 (f6d140e) for full EdgeTX support.
Hot Tip
To ensure updating success with this method, update the EdgeTX firmware on the radio to at least EdgeTX 2.8.0 (f6d140e, released Nov. 27, 2022). The EdgeTX Firmware that comes with this radio is a pre-release version.
Simplest EdgeTX Updating Procedure (click/tap to expand)
Visit http://buddy.edgetx.org/.
Select the EdgeTX version and the Radio Model you want to update from the Left-hand side column.
Click the Download .bin button at the bottom of the page.
Save the firmware file into your Radio's SD Card, inside the Firmware Folder.
Reboot the Radio into DFU/Bootloader mode.
Turn off your radio.
Press and hold the two horizontal Trim switches then press the Power button. The Screen should Light up. Let go of the buttons.
Some Radios have a different procedure, like the BetaFPV Lite Radio 3 Pro. Consult the Manual for the steps to get it into this DFU/Bootloader mode.
Select Write Firmware.
Navigate to the EdgeTX firmware file you just downloaded.
Follow the screen prompts.
Once Writing is complete, reboot the radio.
Check the Radio's Version Page to verify you have the version you need.
Also, make sure you have an internal ELRS module on your Radio. The following steps only apply to handsets with ExpressLRS-specific internal modules. You can find a sticker at the bottom of the box that the radio came in with containing the barcode and the radio stick mode and type.
The current Model on the radio should be using the Internal ExpressLRS Module. Test this by loading the ExpressLRS Lua Script from the Tools Menu.
There's one more setting you want to make sure is set properly before proceeding.
Press the SYS Key on the Radio.
Radios without a dedicated SYS Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to get to the System Menu.
Press the PAGE Key until you reach the Hardware Page.
Scroll down until you see the Serial Ports settings.
Select or highlight USB-VCP. Press Enter and use the Scroll Wheel to set it to CLI mode if it is set to a different setting. Press Enter once more to confirm the changes.
Exit the Hardware menu by long-pressing RTN Key.
Now follow the next steps to get your Internal ExpressLRS Module Updated:
Connect your powered-up Radio to your Computer via a USB Data Cable.
On your Radio, scroll down and select USB Serial(VCP) then press the Enter Key. Set your Radio aside in the meantime.
On your Computer, check whether your Radio is being recognized correctly as a STMicroelectronics Virtual COM Port device.
Important
This is a vital step and a common failure point. Pay attention.
Windows Users can use Device Manager to check whether the Radio is being recognized correctly.
Yellow Caution Triangles in the Device Manager, or any mention of <Radio Name> Serial Port means drivers aren't installed.
Download the Driver package first. Unzip/extract the contents of the package and run/execute (double-click) the installer file (VCP_V1.5.0_Setup_W7_x64_64bits.exe for Windows 10 Users).
Once Drivers are installed, check again if the Radio is now being recognized correctly. You may have to first unplug-replug the USB Cable or even reboot your computer.
You only have to do this once usually.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz LiteRadio 3 Pro
Set the Flashing Method to EdgeTXPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your Radio from USB.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
"},{"location":"quick-start/transmitters/diy2400/","title":"DIY 2400TX","text":""},{"location":"quick-start/transmitters/diy2400/#flashing-via-usbuart-esp32","title":"Flashing via USB/UART (ESP32)","text":"
Targets:
DIY_2400_TX_ESP32_SX1280_E28_via_UART
DIY_2400_TX_ESP32_SX1280_LORA1280F27_via_UART
DIY_2400_TX_ESP32_SX1280_Mini_via_UART
Plug the ESP32 of the DIY TX into the USB of your computer. Then select the correct target given the RF chip you chose and press Build & Flash. Further updates can be performed by building and flashing the .bin file to the external module using OpenTX.
"},{"location":"quick-start/transmitters/diy900/","title":"DIY 900TX","text":""},{"location":"quick-start/transmitters/diy900/#flashing-via-usbuart-esp32","title":"Flashing via USB/UART (ESP32)","text":"
Targets:
DIY_900_TX_ESP32_SX127x_E19_via_UART
DIY_900_TX_ESP32_SX127x_RFM95_via_UART
Plug the ESP32 of the DIY TX into the USB of your computer. Then select the correct target given the RF chip you chose and press Build & Flash. Further updates can be performed by building and flashing the .bin file to the external module using OpenTX.
"},{"location":"quick-start/transmitters/diy900/#flashing-via-usbuart-ttgo","title":"Flashing via USB/UART (TTGo)","text":"
Targets:
DIY_900_TX_TTGO_V1_SX127x_via_UART
DIY_900_TX_TTGO_V2_SX127x_via_UART
Plug the TTGo into the USB of your computer. Then select the correct target given the version you have and press Build & Flash. Further updates can be performed by building and flashing the .bin file to the external module using OpenTX.
These devices come pre-installed with a 3.x-ready firmware. You don't need to reflash these devices. You can use the Web UI of these devices to update the Binding Phrase or any of the firmware options.
"},{"location":"quick-start/transmitters/emax2400/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia UART Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
EMAX 2.4 GHz
Device:
EMAX Nano 2.4GHz TX
EMAX OLED 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
EMAX 2.4 GHz
Device:
EMAX Nano 2.4GHz TX
EMAX OLED 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
EMAX 2.4 GHz
Device:
EMAX Nano 2.4GHz TX
EMAX OLED 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here: CP210x Drivers
Windows Users should download the CP210x Windows Drivers package for easier installation. Unzip/Extract the contents of the package and run the setup wizard.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
EMAX 2.4 GHz
Device:
EMAX Nano 2.4GHz TX
EMAX OLED 2.4GHz TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
These devices come pre-installed with a 3.x-ready firmware. You don't need to reflash these devices. You can use the Web UI of these devices to update the Binding Phrase or any of the firmware options.
"},{"location":"quick-start/transmitters/emax900/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia UART Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
EMAX 900 MHz
Device:
EMAX Nano 900MHz TX
EMAX OLED 900MHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
EMAX 900 MHz
Device:
EMAX Nano 900MHz TX
EMAX OLED 900MHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
EMAX 900 MHz
Device:
EMAX Nano 900MHz TX
EMAX OLED 900MHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here: CP210x Drivers
Windows Users should download the CP210x Windows Drivers package for easier installation. Unzip/Extract the contents of the package and run the setup wizard.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
EMAX 900 MHz
Device:
EMAX Nano 900MHz TX
EMAX OLED 900MHz TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
This guide applies to all of the following HappyModel TX modules: ES24TX, ES24TX Lite, ES24TX Iron Man, ES24TX Slim Pro and ES24TX Pro Micro. Any module with \"Pro\" in the name uses the _Pro_Series target.
Advisory
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
"},{"location":"quick-start/transmitters/es24tx/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia UART Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
HappyModel ES24 Pro 2.4GHz TX for ES24TX Pro Micro
HappyModel ES24 Slim Pro 2.4GHz TX for ES24TX Slim Pro
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
HappyModel ES24 Pro 2.4GHz TX for ES24TX Pro Micro
HappyModel ES24 Slim Pro 2.4GHz TX for ES24TX Slim Pro
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
HappyModel ES24 Pro 2.4GHz TX for ES24TX Pro Micro
HappyModel ES24 Slim Pro 2.4GHz TX for ES24TX Slim Pro
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
For these TX Modules, you will have to take off the front cover to get access to the USB Port and/or dipswitches/jumper blocks.
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here: CP210x Drivers
Windows Users should download the CP210x Windows Drivers package for easier installation. Unzip/Extract the contents of the package and run the setup wizard.
These TX Modules have switches to change how the USB port interacts with the different components in the module. Make sure to set it in the position for \"TX Module Flashing via UART\".
ES24TX Full Size, Non Pro
ES24TX Lite, for Jumper T-Lite
ES24TX Slim, Iron Man
ES24TX Slim Pro
ES24TX Pro 1W
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
HappyModel ES24 Pro 2.4GHz TX for ES24TX Pro Micro
HappyModel ES24 Slim Pro 2.4GHz TX for ES24TX Slim Pro
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB. Return any dipswitches or jumper blocks to their \"Normal Operation\" position.
Reattach the TX module cover, making sure no wires are being pinched and the antenna pigtail is connected properly.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
"},{"location":"quick-start/transmitters/es900tx/","title":"Happymodel ES900TX","text":""},{"location":"quick-start/transmitters/es900tx/#flashingupdating-the-es900tx-firmware","title":"Flashing/Updating the ES900TX Firmware","text":"
Advisory
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
via WiFivia UART
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel TX ES900TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel ES900 TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel ES900 TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
You will need to disassemble your TX Module to get access to the USB Port and the dipswitches.
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here: CP210x Drivers
Windows Users should download the CP210x Windows Drivers package for easier installation. Unzip/Extract the contents of the package and run the setup wizard.
This TX Module has switches to change how the USB port interacts with the different components in the module. Make sure to set it in the position for \"Flashing the TX Module via UART\".
Set switches 5 & 6 to On, and set the others to Off.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel ES900 TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB. Return the dipswitches to the \"Normal Operation\" position (1 & 2 is On, 3,4,5,6 are Off).
Reassemble the TX Module, making sure no wires are being pinched and the antenna pigtail is connected properly.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
"},{"location":"quick-start/transmitters/es900tx/#flashingupdating-the-es915txes868tx-firmware","title":"Flashing/Updating the ES915TX/ES868TX Firmware","text":"
Attention
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
via Stock_BLvia STLink
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel ES915 TX
Set the Flashing Method to Stock_BL
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Build button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
A Temp folder will open up with the firmware.elrs file. Copy-paste the firmware.elrs file into your Radio's SD Card (preferably to the /FIRMWARE folder for easy access).
On your radio, open the System Menu.
On newer radios, you can press the SYS key to open the System Menu
On older radios, or radios that only have a menu key, long-press the Menu key to open the System Menu
Using the Page key/s, navigate to the SD-HC Card page, scroll-down and open the FIRMWARE folder where you can find the firmware.elrs file.
Highlight the file and press-hold the Enter button and select \"Flash External ELRS\". Wait for the firmware to be written.
No Sync (click/tap to expand)
Make sure you have updated the OpenTX/EdgeTX firmware of your radio to a newer version
Make sure the current model selected on the radio is set up for ExpressLRS Use. See the [Radio Preparation] guide.
With the ExpressLRS Lua Script in the Tools page, verify if the firmware version has been updated.
Disassemble your TX Module to get access to the mainboard.
Connect your STLink V2 dongle to the pads shown in the image below.
Connect your STLink V2 dongle to your Computer's USB Port. Make sure it is being detected properly.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel ES915 TX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Disconnect the STLink V2 dongle from the TX Module PCB and reassemble the TX Module.
Reattach your TX Module to your Radio and, using the ExpressLRS Lua Script, verify if the firmware version has been updated.
"},{"location":"quick-start/transmitters/firmware-version/","title":"Checking FW Version","text":""},{"location":"quick-start/transmitters/firmware-version/#why-do-you-have-to-know-the-firmware-version","title":"Why do you have to know the Firmware Version?","text":"
Knowing the ExpressLRS Firmware Version that's currently in your devices will determine whether there is a need to update to a newer version or whether you can simply get your devices bound together without updating. For newcomers in the hobby, or for those just starting with ExpressLRS, it can be a bit daunting to flash a new device.
It is still recommended that you update your gear to the latest firmware version to ensure you have all the bug fixes and latest features.
There are three methods to determine what firmware version you currently have on your Transmitter module
via Lua Scriptvia OLED Screenvia Web UI
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter Key to activate the Script.
If the script is stuck on a \"Loading...\" screen, go back to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll to the bottom of the page and you should see the Current Version flashed into your TX module.
Shows both have 3.2.1 Firmware Version with the Git Hash 8dbbdb.
Colored Screens ExpressLRS Lua Script Version Line
Mono Screens ExpressLRS Lua Script Version Line
If your External TX module is equipped with a Screen, the Home Screen should show the different parameters currently configured on the module. It will also show the current firmware version flashed into the module.
OLED Screen Version Line
Put your module into WiFi mode.
using the ExpressLRS Lua Scriptusing Auto WiFi mode
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, go back to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
If the Script stopped and is showing a Syntax Error, do not worry. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware or both. It could also be due to the fact your TX module is on an earlier firmware version and you're using a more recent Lua Script.
With your TX module disconnected from your Radio module bay, power it up either via an external power source (2S) or by plugging in a USB cable into its USB Port.
Let it be for at least 60s and the RGB LED will turn into a Green Breathing LED pattern indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
TX Modules with an OLED Screen will also show a message to indicate it is in WiFi Mode.
Scan for the ExpressLRS TX Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also, try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Load the Web UI on your browser using these addresses:
http://10.0.0.1/ -If you have connected to the ExpressLRS TX Access Point
Note
This IP address is also often used by some routers. Computers with an ethernet connection to their routers will find that this page doesn't load the ExpressLRS Web UI and instead loads their router or ISP modem configuration dashboards.
We recommend disconnecting from the network first or trying a different device instead, e.g. smartphone or tablet.
http://elrs_tx.local - If you have previously set your Home WiFi SSID and Password into your TX Module when you flashed it.
Note
If your browser cannot resolve this address, chances are MDNS is not set up and working on your computer or network.
Use the IP Address instead! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a which will list all the devices in the Network.
Try each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in to your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
The Banner of the Web UI should tell you the firmware version flashed into your TX module.
The ExpressLRS Web UI Banner
Once you have determined the firmware version that's currently flashed into your Transmitter module, you can now decide to whether keep using it as is or update to the latest version.
Versioning Scheme
The ExpressLRS Firmware Versioning scheme is based on the semantic versioning scheme.
A Version is defined or formatted as \"Major.Minor.Patch\"
- major = major new feature and/or incompatible changes\n- minor = minor features or enhancements and/or new targets\n- patch = bug-fixes\n
That first number in the Version string should match between a TX Module and a Receiver. Examples:
a TX Module with version string of 3.1.2 will sync and work with a Receiver with firmware version 3.0.1
a TX Module with version string of 3.2.0 will NOT sync or bind with a Receiver with firmware version 2.4.0
For the latest ExpressLRS firmware version, check the Releases page in Git Hub
"},{"location":"quick-start/transmitters/firmware-version/#i-know-the-version-what-now","title":"I Know the Version. What Now?","text":"I have an old versionI have a recent one
See the next page for the typical updating procedure or expand the Updating Transmitters section of the Menu on the left as shown below.
You can also use the Search Bar on top of this page to search for the specific Updating/Flashing Guide for your TX Module.
See the Binding Procedure to sync your TX Module with your Receiver.
"},{"location":"quick-start/transmitters/flash2400/","title":"NamimnoRC Flash","text":""},{"location":"quick-start/transmitters/flash2400/#flashingupdating-the-flash-oled-firmware","title":"Flashing/Updating the Flash OLED Firmware","text":"
Advisory
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
via WiFivia UART
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash OLED 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash OLED 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash OLED 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
Determine whether your TX Module is being detected properly as a USB-SERIAL CH340 device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here:
Windows Users will need the CH340 Drivers (Right-click, Save-as) installed (Unzip the contents of the file; Run the executable installer) for this to work properly.
For other Operating Systems, head to this site to download your needed drivers.
This TX Module has switches to change how the USB port interacts with the different components in the module. Make sure it is set as shown. This is the default position and unless you have moved it before, there's no need to open up the module.
Attention
The left position of the switch is for flashing the backpack. The right position of the switch is for flashing the TX itself. The right position is the default, so there is no need to open your module unless you need to unbrick your TX backpack!
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash OLED 2.4GHz TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
"},{"location":"quick-start/transmitters/flash2400/#flashingupdating-the-flash-non-oled-firmware","title":"Flashing/Updating the Flash Non-OLED Firmware","text":"
Attention
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
via Stock_BLvia STLink
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash 2.4GHz TX
Set the Flashing Method to Stock_BL
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Build button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
A Temp folder will open up with the firmware.elrs file. Copy-paste the firmware.elrs file into your Radio's SD Card (preferably to the /FIRMWARE folder for easy access).
On your radio, open the System Menu.
On newer radios, you can press the SYS key to open the System Menu
On older radios, or radios that only have a menu key, long-press the Menu key to open the System Menu
Using the Page key/s, navigate to the SD-HC Card page, scroll-down and open the FIRMWARE folder where you can find the firmware.elrs file.
Highlight the file and press-hold the Enter button and select \"Flash External ELRS\". Wait for the firmware to be written.
No Sync (click/tap to expand)
Make sure you have updated the OpenTX/EdgeTX firmware of your radio to a newer version
Make sure the current model selected on the radio is set up for ExpressLRS Use. See the [Radio Preparation] guide.
With the ExpressLRS Lua Script in the Tools page, verify if the firmware version has been updated.
Attention
Only use this method if the firmware has been corrupted.
Disassemble your TX Module to get access to the mainboard.
Connect your STLink V2 dongle to the pads shown in the image below.
Connect your STLink V2 dongle to your Computer's USB Port. Make sure it is being detected properly.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash 2.4GHz TX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Disconnect the STLink V2 dongle from the TX Module PCB and reassemble the module.
Reattach your TX Module into your Radio and, using the ExpressLRS Lua Script, verify if the firmware version has been updated.
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
Warning
The R9M Lite Pro can not be flashed via OpenTX or EdgeTX (Stock_BL method), and therefore requires an STLink v2 to flash. See the guide below
This method requires OpenTX 2.3.12 or newer; or EdgeTX 2.4.0 or newer.
Download and save r9m_elrs_bl.frk(14kb) onto the SD card of your radio, in the /FIRMWARE folder.
Flash r9m_elrs_bl.frk to your TX module:
Access the System Menu on your radio.
On newer radios, you can press the SYS key to open the System Menu
On older radios, or radios that only have a menu key, long-press the Menu key to open the System Menu
Using the Page key/s, navigate to the SD-HC Card page.
Scroll-down and open the FIRMWARE folder where you can find the r9m_elrs_bl.frk file.
Flash the frk file by holding Enter key and selecting \"Flash external module\"
FYI
You only need to flash the Bootloader ONCE. After it's flashed into the module, you don't have to reflash it in every update.
Video Guide:
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
FrSky 900 MHz
Device:
FrSky R9M 900MHz TX
FrSky R9M Lite 900MHz TX
Set the Flashing Method to Stock_BL
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Build button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
A Temp folder will open up with the firmware.elrs file. Copy-paste the firmware.elrs file into your Radio's SD Card (preferably to the /FIRMWARE folder for easy access).
On your radio, open the System Menu.
On newer radios, you can press the SYS key to open the System Menu
On older radios, or radios that only have a menu key, long-press the Menu key to open the System Menu
Using the Page key/s, navigate to the SD-HC Card page, scroll-down and open the FIRMWARE folder where you can find the firmware.elrs file.
Highlight the file and press-hold the Enter button and select \"Flash External ELRS\". Wait for the firmware to be written.
No Sync (click/tap to expand)
Make sure you have updated the OpenTX/EdgeTX firmware of your radio to a newer version
Make sure the current model selected on the radio is set up for ExpressLRS Use. See the Radio Preparation guide.
With the ExpressLRS Lua Script in the System Menu's Tools page, verify if the firmware version has been updated.
Warning
This method is an irreversible one. You will not be able to go back to FrSky firmware with this method. You have been warned!
Carefully disassemble your TX Module to get access to the mainboard.
Connect your STLink V2 dongle to the pads shown in the images below:
R9M STLink Connection
R9M Lite STLink Connection
R9M Lite Pro STLink Connection
Connect your STLink V2 dongle to your Computer's USB Port. Make sure it is being detected correctly.
Before flashing, disable 'Readout Protection'. To do this, download the ST-LINK Utility and follow this quick how to video. After such, you can now disconnect (Target -> Disconnect) and close the ST-Link Utility.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
FrSky 900 MHz
Device:
FrSky R9M 900MHz TX
FrSky R9M Lite 900MHz TX
FrSky R9M Lite Pro 900MHz TX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Disconnect the STLink V2 dongle from the TX Module PCB and reassemble the module.
Reattach your TX Module into your Radio and, using the ExpressLRS Lua Script, verify if the firmware version has been updated.
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
This method is an irreversible one. You will not be able to go back to ImmersionRC Ghost firmware with this method. You have been warned!
Video Guide(10 min):
Carefully disassemble your TX Module to get access to the mainboard.
Connect your STLink V2 dongle to the pads shown in the images below:
Wire 3.3v, GND, CLK, and DIO to their respective pins on your part from the StLink. (You can power with the StLink but in the second image, the radio is used to power the module).
Connect your STLink V2 dongle to your Computer's USB Port. Make sure it is being detected correctly.
Before flashing, disable 'Readout Protection'. To do this, download the ST-LINK Utility and follow this quick how to video. After such, you can now disconnect (Target -> Disconnect) and close the ST-Link Utility.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
ImmersionRC 2.4 GHz
Device:
Ghost 2.4GHz TX
Ghost Lite 2.4GHz TX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Disconnect the STLink V2 dongle from the TX Module PCB and reassemble the module.
Reattach your TX Module into your Radio and, using the ExpressLRS Lua Script, verify if the firmware version has been updated.
Info
This method requires OpenTX 2.3.12 or newer; or EdgeTX 2.4.0 or newer.
This method can only be used to UPDATE the firmware on an already-converted Ghost Module
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
ImmersionRC 2.4 GHz
Device:
Ghost 2.4GHz TX
Ghost Lite 2.4GHz TX
Set the Flashing Method to Stock_BL
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Build button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
A Temp folder will open up with the firmware.elrs file. Copy-paste the firmware.elrs file into your Radio's SD Card (preferably to the /FIRMWARE folder for easy access).
On your radio, open the System Menu.
On newer radios, you can press the SYS key to open the System Menu
On older radios, or radios that only have a menu key, long-press the Menu key to open the System Menu
Using the Page key/s, navigate to the SD-HC Card page, scroll-down and open the FIRMWARE folder where you can find the firmware.elrs file.
Highlight the file and press-hold the Enter button and select \"Flash External ELRS\". Wait for the firmware to be written.
No Sync (click/tap to expand)
Make sure you have updated the OpenTX/EdgeTX firmware of your radio to a newer version
Make sure the current model selected on the radio is set up for ExpressLRS Use. See the Radio Preparation guide.
With the ExpressLRS Lua Script in the Tools page, verify if the firmware version has been updated.
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
"},{"location":"quick-start/transmitters/hglrc-hermes/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia UART Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 2.4 GHz
Device:
HGLRC Hermes 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 2.4 GHz
Device:
HGLRC Hermes 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 2.4 GHz
Device:
HGLRC Hermes 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Attach your USB cable to the module while pressing and holding the recessed button at the back of the module. The location of the button is shown in the image below.
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here: CP210x Drivers
Windows Users should download the CP210x Windows Drivers package for easier installation. Unzip/Extract the contents of the package and run the setup wizard.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 2.4 GHz
Device:
HGLRC Hermes 2.4GHz TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
Make sure you are selecting the right Device Category (2.4GHz or 900MHz) that's appropriate for the hardware you have. You cannot flash a 2.4GHz module with the firmware for the 900MHz module and expect it to work properly. Likewise, you cannot flash a 900MHz module with the firmware for the 2.4GHz module. They have different sets of hardware.
You can damage your hardware if you do so. You have been warned!
Advisory
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
"},{"location":"quick-start/transmitters/iflight-commando/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia UART Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Categories:
iFlight 2.4 GHz
iFlight 900 MHz
Devices:
iFlight 2.4GHz TX & iFlight 2.4GHz TX V2
iFlight 900MHz TX & iFlight 900MHz TX V2
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Categories:
iFlight 2.4 GHz
iFlight 900 MHz
Devices:
iFlight 2.4GHz TX & iFlight 2.4GHz TX V2
iFlight 900MHz TX & iFlight 900MHz TX V2
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Categories:
iFlight 2.4 GHz
iFlight 900 MHz
Devices:
iFlight 2.4GHz TX & iFlight 2.4GHz TX V2
iFlight 900MHz TX & iFlight 900MHz TX V2
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Unscrew the two screws holding the Transmitter Module to the back of the radio handset. Carefully lift the Transmitter Module to get access to the USB-c port. Do not tug too much as there are wires connecting the Transmitter Module to the mainboard of the radio handset, along with the antenna cable of the module itself.
TX Module and USB-C connection
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here: CP210x Drivers
Windows Users should download the CP210x Windows Drivers package for easier installation. Unzip/Extract the contents of the package and run the setup wizard.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Categories:
iFlight 2.4 GHz
iFlight 900 MHz
Devices:
iFlight 2.4GHz TX & iFlight 2.4GHz TX V2
iFlight 900MHz TX & iFlight 900MHz TX V2
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB.
Reassemble the TX module into the Radio properly.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
"},{"location":"quick-start/transmitters/jumper-aion/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia UART Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION Nano 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION Nano 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION Nano 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here: CP210x Drivers or CH9102
Windows Users should download the CP210x Windows Drivers package for easier installation. Unzip/Extract the contents of the package and run the setup wizard.
Note
Jumper seems to have switched to a different UART adapter chip on some of these devices. They should be detected as USB-Enhanced Serial CH9102.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION Nano 2.4GHz TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
"},{"location":"quick-start/transmitters/jumper-internal/","title":"Internal Jumper TLite V2","text":""},{"location":"quick-start/transmitters/jumper-internal/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia ETX Passthrough Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION T-Lite 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Long-press the SYS Key on your Radio to display the Tools page, where you can find the Lua Scripts.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION T-Lite 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION T-Lite 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Info
ETX Passthrough is the result of the collaborative effort between RadioMaster, EdgeTX and ExpressLRS.
It is only available on Radios with Internal ExpressLRS Modules.
Before you start, ensure you have the latest EdgeTX firmware version on your Radio. Consult the EdgeTX documentation regarding the updating process.
For the Jumper T-Lite V2, update it to at least EdgeTX 2.8.0 (f6d140e) for full EdgeTX support.
Hot Tip
To ensure updating success with this method, update the EdgeTX firmware on the radio to at least EdgeTX 2.8.0 (f6d140e, released Nov. 27, 2022). The EdgeTX Firmware that comes with this radio is a pre-release version.
Simplest EdgeTX Updating Procedure (click/tap to expand)
Visit http://buddy.edgetx.org/.
Select the EdgeTX version and the Radio Model you want to update from the Left-hand side column.
Click the Download .bin button at the bottom of the page.
Save the firmware file into your Radio's SD Card, inside the Firmware Folder.
Reboot the Radio into DFU/Bootloader mode.
Turn off your radio.
Press and hold the two horizontal Trim switches then press the Power button. The Screen should Light up. Let go of the buttons.
Some Radios have a different procedure, like the BetaFPV Lite Radio 3 Pro. Consult the Manual for the steps to get it into this DFU/Bootloader mode.
Select Write Firmware.
Navigate to the EdgeTX firmware file you just downloaded.
Follow the screen prompts.
Once Writing is complete, reboot the radio.
Check the Radio's Version Page to verify you have the version you need.
Also, make sure you have an internal ELRS module on your Radio. The following steps only apply to handsets with ExpressLRS-specific internal modules.
The current Model on the radio should be using the Internal ExpressLRS Module. Test this by loading the ExpressLRS Lua Script from the Tools Menu.
There's one more setting you want to make sure is set properly before proceeding.
Long-press the SYS Key on the Radio.
Consult your Radio User's Manual on how to get to the System Menu.
Press the PAGE Keys until you reach the Hardware Page.
On this radio, a short-press on the SYS Key is equivalent to < PAGE while a short-press on the MDL Key is equivalent to PAGE > .
Scroll down until you see the Serial Ports settings.
Press the Down button.
Select or highlight USB-VCP by pressing the Down or Up Keys. Press Enter to edit the setting and use the Down or Up Keys to set it to CLI mode. Press Enter once more to confirm the changes.
Exit the Hardware menu by long-pressing RTN Key.
Now follow the next steps to get your Internal ExpressLRS Module Updated:
Connect your powered-up Radio to your Computer via a USB Data Cable.
On your Radio, scroll down and select USB Serial(VCP) then press the Enter Key. Set your Radio aside in the meantime.
On your Computer, check whether your Radio is being recognized correctly as a STMicroelectronics Virtual COM Port device.
Important
This is a vital step and a common failure point. Pay attention.
Windows Users can use Device Manager to check whether the Radio is being recognized correctly.
Yellow Caution Triangles in the Device Manager, or any mention of <Radio Name> Serial Port means drivers aren't installed.
Download the Driver package first. Unzip/extract the contents of the package and run/execute (double-click) the installer file (VCP_V1.5.0_Setup_W7_x64_64bits.exe for Windows 10 Users).
Once Drivers are installed, check again if the Radio is now being recognized correctly. You may have to unplug-replug the USB Cable first or even reboot your computer.
You only have to do this once usually.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION T-Lite 2.4GHz TX
Set the Flashing Method to EdgeTXPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your Radio from USB.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
Make sure you are selecting the right Device Category (2.4GHz or 900MHz) that's appropriate for the hardware you have. You cannot flash a 2.4GHz module with the firmware for the 900MHz module and expect it to work properly. Likewise, you cannot flash a 900MHz module with the firmware for the 2.4GHz module. They have different sets of hardware.
You can damage your hardware if you do so. You have been warned!
"},{"location":"quick-start/transmitters/jumper-t14-t15-internal/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia ETX Passthrough Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Jumper 900 MHz
Device:
Jumper AION T-14 2.4GHz TX
Jumper AION T-15 2.4GHz TX
Jumper AION T-14 900M TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Long-press the SYS Key on your Radio to display the Tools page, where you can find the Lua Scripts.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Jumper 900 MHz
Device:
Jumper AION T-14 2.4GHz TX
Jumper AION T-15 2.4GHz TX
Jumper AION T-14 900M TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Jumper 900 MHz
Device:
Jumper AION T-14 2.4GHz TX
Jumper AION T-15 2.4GHz TX
Jumper AION T-14 900M TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Info
ETX Passthrough is the result of the collaborative effort between RadioMaster, EdgeTX and ExpressLRS.
It is only available on Radios with Internal ExpressLRS Modules.
Before you start, ensure you have the latest EdgeTX firmware version on your Radio. Consult the EdgeTX documentation regarding the updating process.
For any of the variants of the Jumper T14 or Jumper T15, the EdgeTX firmware that came with them (EdgeTX ~2.10.0) should work fine and there's no need to update EdgeTX.
Simplest EdgeTX Updating Procedure (click/tap to expand)
Visit http://buddy.edgetx.org/.
Select the EdgeTX version and the Radio Model you want to update from the Left-hand side column.
Click the Download .bin button at the bottom of the page.
Save the firmware file into your Radio's SD Card, inside the Firmware Folder.
Reboot the Radio into DFU/Bootloader mode.
Turn off your radio.
Press and hold the two horizontal Trim switches then press the Power button. The Screen should Light up. Let go of the buttons.
Some Radios have a different procedure, like the BetaFPV Lite Radio 3 Pro. Consult the Manual for the steps to get it into this DFU/Bootloader mode.
Select Write Firmware.
Navigate to the EdgeTX firmware file you just downloaded.
Follow the screen prompts.
Once Writing is complete, reboot the radio.
Check the Radio's Version Page to verify you have the version you need.
Also make sure the current active Model on the radio is using the Internal ExpressLRS Module. Test this by loading the ExpressLRS Lua Script from the Tools Menu.
There's one more setting you want to make sure is set properly before proceeding.
Long-press the Menu \"Menu\" Key on the Radio.
Consult your Radio User's Manual on how to get to the System Menu.
Press the PAGE Keys until you reach the Hardware Page.
Scroll down until you see the Serial Ports settings.
Press the Down button.
Select or highlight USB-VCP by pressing the Down or Up Keys. Press Enter to edit the setting and use the Down or Up Keys to set it to CLI mode. Press Enter once more to confirm the changes.
Exit the Hardware menu by long-pressing RTN Key.
Now follow the next steps to get your Internal ExpressLRS Module Updated:
Connect your powered-up Radio to your Computer via a USB Data Cable.
On your Radio, scroll down and select USB Serial(VCP) then press the Enter Key. Set your Radio aside in the meantime.
On your Computer, check whether your Radio is being recognized correctly as a STMicroelectronics Virtual COM Port device.
Important
This is a vital step and a common failure point. Pay attention.
Windows Users can use Device Manager to check whether the Radio is being recognized correctly.
Yellow Caution Triangles in the Device Manager, or any mention of <Radio Name> Serial Port means drivers aren't installed.
Download the Driver package first. Unzip/extract the contents of the package and run/execute (double-click) the installer file (VCP_V1.5.0_Setup_W7_x64_64bits.exe for Windows 10 Users).
Once Drivers are installed, check again if the Radio is now being recognized correctly. You may have to unplug-replug the USB Cable first or even reboot your computer.
You only have to do this once usually.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Jumper 900 MHz
Device:
Jumper AION T-14 2.4GHz TX
Jumper AION T-15 2.4GHz TX
Jumper AION T-14 900M TX
Set the Flashing Method to EdgeTXPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your Radio from USB.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
Make sure you are selecting the right Device Category (2.4GHz or 900MHz) that's appropriate for the hardware you have. You cannot flash a 2.4GHz module with the firmware for the 900MHz module and expect it to work properly. Likewise, you cannot flash a 900MHz module with the firmware for the 2.4GHz module. They have different sets of hardware.
The T20 Gemini firmware will ONLY work on the T20 Gemini. Do not Flash this target on the other T20 variants.
You can damage your hardware if you do so. You have been warned!
"},{"location":"quick-start/transmitters/jumper-t20-internal/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia ETX Passthrough Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Jumper 900 MHz
Device:
Jumper Gemini T-20 2.4GHz TX
Jumper AION T-20 2.4GHz TX
Jumper AION T-20 900M TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Long-press the SYS Key on your Radio to display the Tools page, where you can find the Lua Scripts.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Jumper 900 MHz
Device:
Jumper Gemini T-20 2.4GHz TX
Jumper AION T-20 2.4GHz TX
Jumper AION T-20 900M TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Jumper 900 MHz
Device:
Jumper Gemini T-20 2.4GHz TX
Jumper AION T-20 2.4GHz TX
Jumper AION T-20 900M TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Info
ETX Passthrough is the result of the collaborative effort between RadioMaster, EdgeTX and ExpressLRS.
It is only available on Radios with Internal ExpressLRS Modules.
Before you start, ensure you have the latest EdgeTX firmware version on your Radio. Consult the EdgeTX documentation regarding the updating process.
For any of the variants of the Jumper T20, the EdgeTX firmware that came with it (pre EdgeTX 2.9.0) should work fine and there's no need to update it.
Simplest EdgeTX Updating Procedure (click/tap to expand)
Visit http://buddy.edgetx.org/.
Select the EdgeTX version and the Radio Model you want to update from the Left-hand side column.
Click the Download .bin button at the bottom of the page.
Save the firmware file into your Radio's SD Card, inside the Firmware Folder.
Reboot the Radio into DFU/Bootloader mode.
Turn off your radio.
Press and hold the two horizontal Trim switches then press the Power button. The Screen should Light up. Let go of the buttons.
Some Radios have a different procedure, like the BetaFPV Lite Radio 3 Pro. Consult the Manual for the steps to get it into this DFU/Bootloader mode.
Select Write Firmware.
Navigate to the EdgeTX firmware file you just downloaded.
Follow the screen prompts.
Once Writing is complete, reboot the radio.
Check the Radio's Version Page to verify you have the version you need.
The current active Model on the radio should be using the Internal ExpressLRS Module. Test this by loading the ExpressLRS Lua Script from the Tools Menu.
There's one more setting you want to make sure is set properly before proceeding.
Long-press the Menu \"Menu\" Key on the Radio.
Consult your Radio User's Manual on how to get to the System Menu.
Press the PAGE Keys until you reach the Hardware Page.
Scroll down until you see the Serial Ports settings.
Press the Down button.
Select or highlight USB-VCP by pressing the Down or Up Keys. Press Enter to edit the setting and use the Down or Up Keys to set it to CLI mode. Press Enter once more to confirm the changes.
Exit the Hardware menu by long-pressing RTN Key.
Now follow the next steps to get your Internal ExpressLRS Module Updated:
Connect your powered-up Radio to your Computer via a USB Data Cable.
On your Radio, scroll down and select USB Serial(VCP) then press the Enter Key. Set your Radio aside in the meantime.
On your Computer, check whether your Radio is being recognized correctly as a STMicroelectronics Virtual COM Port device.
Important
This is a vital step and a common failure point. Pay attention.
Windows Users can use Device Manager to check whether the Radio is being recognized correctly.
Yellow Caution Triangles in the Device Manager, or any mention of <Radio Name> Serial Port means drivers aren't installed.
Download the Driver package first. Unzip/extract the contents of the package and run/execute (double-click) the installer file (VCP_V1.5.0_Setup_W7_x64_64bits.exe for Windows 10 Users).
Once Drivers are installed, check again if the Radio is now being recognized correctly. You may have to unplug-replug the USB Cable first or even reboot your computer.
You only have to do this once usually.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Jumper 900 MHz
Device:
Jumper Gemini T-20 2.4GHz TX
Jumper AION T-20 2.4GHz TX
Jumper AION T-20 900M TX
Set the Flashing Method to EdgeTXPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your Radio from USB.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
"},{"location":"quick-start/transmitters/lua-howto/","title":"The ExpressLRS Lua Script","text":""},{"location":"quick-start/transmitters/lua-howto/#installing-the-lua-script","title":"Installing the Lua Script","text":"
Download the ELRS v3 Lua Script (you can simply right-click, save-as) into your radio's SD Card under the Scripts/Tools folder.
Access the script by navigating to your radio's System Menu.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
Here's how it looks in the Tools menu (B&W and Color Screens):
Press Enter to Load it.
Stuck at Loading... (click/tap to expand)
Go back to the Radio Preparation Guide and make sure the current model is configured for ExpressLRS use.
Also set your Internal or External RF Baudrate to a higher value if the Script still doesn't load after proper configuration of your Model.
As of 3.3.0:
500Hz or faster packet rates require >400K Baudrate.
333Hz is the fastest packet rate you can use with 400K Baudrate.
"},{"location":"quick-start/transmitters/lua-howto/#understanding-and-using-the-lua-script","title":"Understanding and Using the Lua Script","text":""},{"location":"quick-start/transmitters/lua-howto/#the-header","title":"The Header","text":"
The first line, \"Header\", will show you some information about your ExpressLRS link.
Module Identifier
Shows the name of the current active Transmitter Module or Device.
Packet Counter
Shows the number of Bad and Good Packets the TX Module receives from the Radio. The second set of number should match your selected Packet Rate. e.g. If you've set your Packet Rate to 500Hz, the Packet Counter should show 0/500, which means you're not getting any Bad Packets ( 0 Bad Packets ) and only getting Good Packets ( 500 Good Packets ). Any small fluctuation is normal and often goes back to 100% Good Packets, especially when you change a setting and it's committed into memory.
Should the indicator starts showing Bad Packets, and Good Packets goes down, it isn't a good situation. Make sure your module is not overheating and it's still getting a good connection with the radio. This is most dangerous when you're armed and flying several kilometers/miles out, as this could mean a sudden Failsafe.
Connection Indicator
Shows the current RC Link status. When not connected to any receiver, it will show a dash (-); while a C shows up when bound and connected.
The Model Mismatch message will also show up to indicate you are connected to a receiver, but the model selected on your radio is incorrect. See the Model Match page for more info about Model Matching.
The Armed message will show up if you have the Arming Switch active (High, ~2000us). This is meant to warn users that changing parameters could result in a desync or disconnection with a receiver, resulting into a FAILSAFE.
If you do not meant to have your system Armed and ready for flying, make sure to toggle this switch to the Disarmed position (Low, ~1000us). Update your CH5 settings on the radio so that the output of this switch is correct (Low = disarmed; High = armed). See Switch Configs.
WARNING
Do not change parameters while ARMED. When a parameter is changed, the module goes into Parameter Commit mode, interrupting the normal loop. This could result in a desync on some hardware combination which would result in a FAILSAFE.
The Version Line, found near the bottom of the Lua Script, indicates the firmware version flashed into the Device. This is present on both TX Modules and Receivers.
From these examples:
3.3.0 - The numerical Version Number, in the form of Major.Minor.Patch.
See semantic versioning scheme for the origins of these numbers.
ISM2G4 - The Regulatory Domain set into the Device. TX and RX Regulatory Domains should match.
ae9df3 - The Git commit hash for the version or branch.
Items with > before the name is a folder that when selected shows another level of customization. TX Power, VTX Administrator, Wifi Connectivity are examples of these items.
These items will now show what is currently set for the items within. An example would be on TX Power, which will show the current Power set, and if Dynamic Power is enabled, it will show the current set Max Power, followed by the indicator Dyn.
"},{"location":"quick-start/transmitters/lua-howto/#packet-rate-and-telemetry-ratio","title":"Packet Rate and Telemetry Ratio","text":"
These are shown as Packet Rate and Telem Ratio in the Lua script, which allows you to change your performance parameters.
Packet Rate sets how fast data packets are sent, higher rates send packets more frequently and have lower latency.
The following options are available for 2.4GHz:
50Hz, 150Hz, 250Hz & 500Hz: Lora-based options. Higher means lower latency at the expense of sensitivity. Since v1.0.
F500 & F1000: Pure FLRC for lowest latency, reduced range compared to LoRa, 500Hz and 1000Hz. Details
D250 & D500: Redundant transmit FLRC modes. D stands for D\u00e9j\u00e0 Vu, 250Hz and 500Hz. Higher latency, reduced packet jitter and higher LQ. Same range as other FLRC modes. Details
100Hz Full & 333Hz Full: Lora-based 10-bit Full Resolution with 8ch/12ch/16 Switch Mode options. Details
K1000 : K modes for 2.4GHz are FSK+FEC (Forward Error Correction a.k.a self healing packets) and only available on LR1121 hardware. K modes are very similar to FLRC in their over the air properties and designed for high noise environments such as racing events. FSK Details FEC Details
DK250 & DK500 : These modes offer the same redundancy as D modes but with K modes (FSK+FEC).
The following options are available for 900MHz:
25Hz, 50Hz, 100Hz & 200Hz: LoRa-based options. Higher means lower latency at the expense of sensitivity. Since v1.0.
100Hz Full: Lora-based 10-bit Full Resolution with 8ch/12ch/16 Switch Mode options. Details
D50Hz: Lora-based Redundant transmit mode via DVDA. Details
250Hz: Only Available for GemX Devices. Details
200Hz Full : Only Available for GemX Devices. Details
K1000 Full : K modes for SubGHz are FSK and only available on LR1121 hardware. This mode is design for the highest data throughput when using protocols such as MAVLink. Details
The following options are available for GemX:
X150Hz : Crossband mode, combining 900MHz and 2.4GHz in Gemini Mode.
X100Hz Full : Crossband mode, combining 900MHz and 2.4GHz in Gemini Mode, Full Resolution with 8ch/12ch/16 Switch Mode options
GemX is a 3.4.0 feature
Gemini Crossband (GemX) is available on select hardware, requiring the LR1121 RF Chip. GemX is an ExpressLRS 3.4.0 feature. Details here.
The number following the rate in parentheses (e.g. -105dBm for 500Hz) is the Sensitivity Limit for the rate, the lowest RSSI dBm value where packets will still be received. See Signal Health for more information about the sensitivity limit.
WARNING
Never change the packet rate while flying as this FORCES A DISCONNECT between the TX and RX.
Telem Ratio sets the telemetry ratio or how much of the packet rate is used to send telemetry. The options, in order of increasing telemetry rate, are: Off, 1:128, 1:64, 1:32, 1:16, 1:8, 1:4, 1:2. A Telem Ratio of 1:64 means one out of every 64 packets are used for telemetry data.
v3.0 comes with Std and Race options. Std changes ratio depending on the Packet Rate, and Race is the same as Std, but will disable telemetry and sync while Armed.
For information on telemetry setup, see First Flight: Telemetry and Telemetry Bandwidth.
The Switch Mode setting controls how channels AUX1-AUX8 are sent to the receiver (the 4 main channels are always 10-bit). The options are Hybrid & Wide. Hybrid mode is 6x 2, 3 or 6-position + 1x 16-position, and Wide is 7x 64 or 128-position. For detail about the differences, see the Switch Configs documentation.
In full resolution modes, the Switch Mode parameter selects the number of channels to be used. Full Resolution Switch Modes
Hot Tip
The Switch Mode can only be changed when not connected to a receiver. The top right corner of the Lua script will show a - if you're not connected.
This option is only available to Gemini-capable TX Modules. See the Gemini Page for more details.
Available Options:
Gemini
Transmit on two TX antennas simultaneously at different frequencies 40MHz apart (for 2.4GHz) or ~10MHz apart (for 900MHz).
Ant 1/Ant 2
Transmit only on one antenna.
Switch
Alternate between the two Antennas.
WARNING
When using a Gemini TX with a non-Gemini receiver, you should set the TX in either Switch or Single Antenna (Ant1/Ant2) Mode.
The reason is that as the receiver only get the signal from the TX it has synchronized with, the other TX will act as a noise generator and increase both the noise floor and power consumption.
Introduced in 3.5.0, Link Mode changes the main protocol and function of the TX module.
Normal - This is the default configuration. The TX module simply sends the commands from the radio handset, and receive telemetry from the receiver and send it to the handset.
MAVLink - This option enables native MAVLink Telemetry downlink and Radio Control uplink making the TX module and radio handset to be an intermediary between a GCS and a MAVLink-capable craft. See the MAVLink page for more details.
ExpressLRS supports multiple configuration profiles, and the configuration profile is selected by setting the \"Receiver ID\" property in the Radio Handset's Model Setup -> Internal/External RF -> Receiver (number).
Model Match is used to prevent accidentally selecting the wrong model in the handset and flying with an unexpected handset or ELRS configuration. Setting this to On while a receiver is connected will make that receiver only connect with the current Receiver ID. Setting it to Off will allow a connection with any bound receiver (including those using a Bind Phrase). Both sides of the connection must agree on their Model Match setting. For a detailed explanation of how this restricts connections see Model Match.
The Receiver ID of the active model is shown after the option value.
The TX Power folder is where you can change your TX Module's Transmission Power settings. Press Enter once to access the settings and Press the RTN key to go back to the previous page.
Max Power sets the maximum power level your TX will transmit at. Selecting a power level higher or lower than your TX supports will revert to the closest supported level. The options are 10, 25, 50, 100, 250, 500, 1000 & 2000 mW. If Dynamic Power is set to Off this is the power level your TX always uses.
Dynamic enables the Dynamic Power feature. Off means that the TX will transmit at Max Power at all times. Dyn means the TX will dynamically lower power to save energy when maximum power is not needed. The options AUX9, AUX10, AUX11, AUX12 indicate that the TX can be changed from max power to dynamic power by changing the position of a switch. where switch HIGH (>1500us) = dynamic power, switch LOW (<1500us) = max power. For more information, Dynamic Transmit Power provides a deeper dive into the algorithm and usage.
Fan Thresh sets the power level the Fan should activate, e.g. if set to 100mW, then the fan should spin up if you set Max Power to 100mW with Dynamic set to OFF after a short delay. The fan will continue running for some time even after the power level goes below the threshold. Not all modules have a Fan header that benefits from the setting. . Default fan threshold is 250mW.
VTX Administrator allows you to change your VTX settings directly from your radio, and have those VTX settings be applied to any receiver you connect to. The VTX settings are sent every time a new connection is acquired, or when [Send VTX] is pressed.
Hot Tip
VTX Administrator will send the current VTX settings to the flight controller whenever the TX module detects a connection to the RX. This means that it will resend them after telemetry lost/recovered. So if you have used any other method to change the VTX power level (i.e. OSD), then that will be overridden if you lose/regain telemetry in flight.
Band sets the VTX band, the options are Off, A, B, E, F, R & L, the standard analog FPV bands. Off means that VTX Administrator will not adjust any VTX settings.
Channel sets the VTX channel, the options are 1, 2, 3, 4, 5, 6, 7 & 8 which are the standard channels in the above bands.
Pwr Lvl sets the VTX power by index, the options are -, 1, 2, 3, 4, 5, 6, 7, & 8 which are the power levels that your VTX can do. Refer to your VTX table settings on the flight controller for the exact power levels. For example a VTX may have 1 = 25mW, 2 = 100mW, 3 = 200mW, 4 = 500mW.
Pitmode the options are On & Off which allow you to quickly switch into or out of pit mode
Finally pressing the [Send VTX] button sends the configured settings to the receiver and on to the VTX. These settings are also sent every time a connection is established.
This section contains all the WiFi-related functions.
Enable WiFi will activate the TX module WiFi mode for updating via WiFi (if the TX Module has WiFi Capabilities). Visit this page for instructions on how the updating process works.
Enable RX WiFi will put the bound and connected receiver into WiFi mode to facilitate updating via WiFi (if the receiver has WiFi capabilities).
Enable Backpack WiFi will put the TX Backpack into WiFi mode (available only to TX modules with backpacks connected and updated to the new Backpack firmware).
Enable VRX WiFi will put the VRX Backpack that is bound and connected to the onboard TX Backpack into WiFi mode to facilitate updating via WiFi.
The parameters in this folder enables you to change the Backpack-related parameters.
Backpack - Turn the Backpack function On or Off.
DVR Rec - Set which Aux Channel and what channel position will trigger DVR Recording on the goggles. Only possible on FPV Goggles with VRX Backpack integration.
DVR Srt Delay - How soon should the DVR start Recording upon activation of the Aux switch?
DVR Stp Delay - How soon should the DVR stop Recording upon deactivation of the Aux switch?
HT Enable - Turn Headtracking On or Off. Only available on some FPV Goggles with VRX Backpack integration.
HT Start Channel - Starting Channel to send Head Tracking positions to.
Telemetry - Allow the Backpack to Send the Telemetry frames via ESPNOW. See Backpack Telemetry
Version - The Backpack Firmware version flashed into the TX Backpack.
This command will only work on receivers that are already in Bind Mode (indicated by two blinks LED pattern). Receivers (with version 3.3.2 and earlier) flashed or set with a binding phrase will NOT go into this Bind Mode, and thus this command will not do anything.
Devices with the same binding phrase and compatible firmware versions should automatically sync/bind upon power up.
Pressing the [Bind] button activates the binding mode for traditional binding. This does nothing for users who have configured a bind phrase and is not needed. For more information check out this page on binding.
Pressing the [BLE Joystick] selection activates BluetoothLE Joystick mode which allows connection to simulators through the bluetooth of your computer. Reboot or change models to exit this mode.
The Other Devices folder, if present, allows changing the configuration of other connected devices, such as the current receiver. It is also used to go back to the TX Module options.
The Protocol setting controls the output of the connected receiver. The following options are available:
CRSF - The regular CRSF Protocol Output. Recommended for most application.
Inverted CRSF - The CRSF Protocol inverted for use in Flight Controllers that doesn't have any other UARTs available and the only option is to connect the receiver TX pin into an SBUS pad (Inverted RX). This is the old Invert TX Pin option.
SBUS - Lets the receiver output SBUS signal for use with devices that don't support CRSF protocol, like Stabilizers, Heli Controllers etc.
Inverted SBUS - Like the above, but inverted.
SUMD - Lets the receiver output Graupner HoTT SUMD signal for use with devices that don't support CRSF protocol, like Stabilizers, Heli Controllers etc.
DJI RS2 Pro - Mainly used for the RS2 Pro Gimbals
HoTT Telemetry - Allows to use Graupner HoTT enabled telemetry sensors (Graupner and 3rd party)
MAVLINK - Introduced on ExpressLRS 3.5.0, it allows the receiver to output native MAVLink into a flight controller. See the MAVLink page for more details.
For more information, see Receiver Serial Protocols
The Protocol 2 setting is only available for ESP32-based receivers. This include the True Diversity ones like the RP4TD, Super D, Super P and EP Dual. These receivers have a second UART that can be used for the same purpose as the main UART. Note that not all of the ESP32-based receivers have the extra UART pads or pins exposed for easy use.
It has the same options as the setting above with these additional ones:
Tramp - If you want to control a VTX using Tramp protocol directly through the ExpressLRS Lua Script's VTX Admin.
SmartAudio - If you want to control a VTX using SmartAudio protocol directly through the ExpressLRS Lua Script's VTX Admin.
Off - Set when the auxiliary UART is not in use.
This setting is available on ExpressLRS 3.5.0 and onwards. See PR 2605 for more details.
The Receiver Mode setting is only available for True Diversity receivers. These options are available:
Gemini - Receive on two RX antennas simultaneously at different frequency 40MHz apart (for 2.4GHz) or ~10MHz apart (for 900MHz). Best used when you have a Gemini-capable TX Module.
Diversity - Both Antennas will be active. Receiver will switch to the antenna with better RSSI.
The Telemetry Power setting is used to adjust the telemetry transmit power of the receiver. This option is only available on receivers with a Power Amplifier.
The MatchTX setting will automatically change the telemetry output power to match what the transmitter reports it is using. In MatchTX mode, the receiver will boot at default power output (usually maximum power) until a power update is received from the transmitter, which is only available in Wide Switch Mode or any FullRes mode.
Removed in ExpressLRS 3.4, see Init Rate. The Initialization Rate setting controls the packet rate that the receiver will start checking for the Sync Packet. On boot, the receiver will listen for the Sync Packet starting with the fastest RF Mode or Packet Rate, down to the slowest, then cycles, until it finally Syncs and Binds. Setting this parameter closer or equal to the Packet Rate you've set for the TX module will allow the receiver to Bind or Connect much faster.
Team Racing allows selection between multiple connected models, failsafing all unselected models. See Team Racing
Channel (default CH11 / AUX7) TeamRace Channel - The channel that is checked on the receiver to determine the currently selected model. Has no effect if the TeamRace Position is set to Disabled.
Position (default Disabled) TeamRace Position - Which position of the TeamRace Channel activates this model. 6-position switches are supported (1-6) as well as Low/Mid/High for using a 2 or 3-position switch.
These commands allow the user to Loan/Return the model. For more information, see the Loan Model guide.
This is deprecated and removed in ExpressLRS 3.4.0 in favor of the new Binding Procedures. See the binding page for details or the Bind Storage section below.
Persistent - Binding info is kept across power-cycles.
Volatile - Binding info is forgotten after a power-cycle.
This option is available on ExpressLRS 3.4.0 and newer. See the details here.
Returnable - Introduced in ExpressLRS 3.5.0. It is used to allow models to be safely loaned from a fleet if unbound OTA. A Binding Phrase must be set for this to work properly. see PR 2744 for details.
This line shows the currently set Model ID for the receiver when Model Matching is enabled. This number should match the Receiver ID set with the current active Model on the Radio handset, otherwise, there will be Model Mismatch! See Model Match for more details.
For racing where maximum performance is a must, the 500Hz modes or faster, with the Race Telemetry mode, is ideal. Hybrid Switch Mode is also good here.
For freestyle and general everyday flying, you may use the 250Hz modes or faster, with the Std Telemetry mode. Switch Mode doesn't matter as much here. Select what's appropriate for your Flight Mode settings.
For fixed wings, we recommend using 100Hz Full Res, together with either Std or your choice of Telemetry Ratio. Switch Mode will depend greatly on how many full resolution channels you intend to use.
For Long Range applications, see the Long Range Records page and try the settings the pilots used to achieve the range. It is not guaranteed you'll achieve the same range as they are due to several factors like RF Noise in your area, your location and position and the antenna orientation on your aircraft and transmitter modules. Observe local laws and regulations.
"},{"location":"quick-start/transmitters/lua-howto/#troubleshooting-the-lua-script","title":"Troubleshooting the Lua Script","text":""},{"location":"quick-start/transmitters/lua-howto/#expresslrs-lua-script-is-stuck-at-loading","title":"ExpressLRS Lua Script is stuck at Loading...","text":"ExpressLRS Lua Script is stuck at Loading...
Go back to the Radio Setup Guide and make sure your radio is prepped up for ExpressLRS. Check that the ExpressLRS TX module is enabled - otherwise the script cannot be loaded.
Also, make sure your module has been flashed with v3.0 firmware. V3 Lua for V3.0-flashed modules, V2 Lua for v2.x-flashed modules (including some modules fresh from the factory).
For newly-acquired ExpressLRS modules, flashing via USB is the recommended update method.
"},{"location":"quick-start/transmitters/lua-howto/#i-cannot-change-the-switch-mode","title":"I cannot change the Switch Mode!","text":"I cannot change the Switch Mode!
Changing switch modes requires that the TX module and Receiver aren't connected to each other (no C in the top right corner of the Lua Script). Power off the receiver first, change the Switch Mode from the Lua script, then power up the receiver. The Switch Mode should then apply.
"},{"location":"quick-start/transmitters/lua-howto/#i-cannot-change-my-packet-rate-to-f1000","title":"I cannot change my Packet Rate to F1000!","text":"I cannot change my Packet Rate to F1000!
F1000 requires higher than 400K baud rates. First update your baud rate setting either in the Model Setup menu or in the System Menu -> Hardware, reboot your radio to ensure that the baud rate setting got applied and then change the Packet Rate.
Do note that not every handset is capable of higher than 400K baud rates. See the Radio Setup Guide for the details.
"},{"location":"quick-start/transmitters/lua-howto/#i-cannot-change-to-full-resolution-rates","title":"I cannot change to Full Resolution Rates!","text":"I cannot change to Full Resolution Rates!
As Full Resolution Rates call for an entirely different Switch Modes, you need to first disconnect the Receiver and the TX module from each other, like how you would change Switch Modes. Power down the receiver, change the Packet Rate to the Full Resolution modes, select your Switch Mode scheme and then power up the receiver or the aircraft.
"},{"location":"quick-start/transmitters/lua-howto/#vtx-admin-is-not-working-but-i-can-change-vtx-channels-via-osd-menu","title":"VTX Admin is not working but I can change VTX channels via OSD Menu.","text":"VTX Admin is not working but I can change VTX channels via OSD Menu.
As VTX Admin depends on MSP which then depends on Telemetry, ensure that you have Telemetry enabled on your FC Configuration and that you are getting more than 10 Telemetry Sensors on your Radio (Model Setup -> Telemetry page; Delete and Discover New sensors to refresh the sensor list.) Also, make sure Telem Ratio is not Off.
"},{"location":"quick-start/transmitters/lua-howto/#there-is-no-c-on-the-top-right-corner-and-im-not-getting-telemetry-in-my-radio","title":"There is no C on the top right corner, and I'm not getting Telemetry in my radio!","text":"There is no C on the top right corner, and I'm not getting Telemetry in my radio!
Make sure Telem Ratio is not set to Off. Set it to Std, or any other value other than Off.
"},{"location":"quick-start/transmitters/lua-howto/#on-v1x-i-can-choose-2w-on-the-lua-but-i-cannot-do-that-anymore-what-gives","title":"On v1.x, I can choose 2W on the Lua, but I cannot do that anymore. What gives?","text":"On v1.x, I can choose 2W on the Lua, but I cannot do that anymore. What gives?
This means your module cannot go that high or that low. The power levels you can select on the new Lua script are based on the power levels your module supports. This also applies to other options like Enable Backpack WiFi or BLE Joystick. If your module doesn't support any of these features, it won't show up on the Lua Script.
These devices come pre-installed with a 3.x-ready firmware. You don't need to reflash these devices. You can use the Web UI of these devices to update the Binding Phrase or any of the firmware options.
"},{"location":"quick-start/transmitters/rm-bandit/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia UART Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Radiomaster 900MHz
Device:
RadioMaster Bandit 900MHz TX
RadioMaster Bandit Micro 900MHz TX
RadioMaster Bandit nano 900MHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Radiomaster 2.4 GHz
Device:
RadioMaster Bandit 900MHz TX
RadioMaster Bandit Micro 900MHz TX
RadioMaster Bandit nano 900MHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Radiomaster 2.4 GHz
Device:
RadioMaster Bandit 900MHz TX
RadioMaster Bandit Micro 900MHz TX
RadioMaster Bandit nano 900MHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here: CP210x Drivers
Windows Users should download the CP210x Windows Drivers package for easier installation. Unzip/Extract the contents of the package and run the setup wizard.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Radiomaster 2.4 GHz
Device:
RadioMaster Bandit 900MHz TX
RadioMaster Bandit Micro 900MHz TX
RadioMaster Bandit nano 900MHz TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
"},{"location":"quick-start/transmitters/rm-internal/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia ETX Passthrough Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
RadioMaster 2.4 GHz
Device:
RadioMaster Zorro 2.4GHz TX
RadioMaster TX16S Internal 2.4GHz TX
RadioMaster TX12 Internal 2.4GHz TX
RadioMaster Boxer Internal 2.4GHz TX
RadioMaster Pocket Internal 2.4GHz TX
RadioMaster MT12 Internal 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
RadioMaster 2.4 GHz
Device:
RadioMaster Zorro 2.4GHz TX
RadioMaster TX16S Internal 2.4GHz TX
RadioMaster TX12 Internal 2.4GHz TX
RadioMaster Boxer Internal 2.4GHz TX
RadioMaster Pocket Internal 2.4GHz TX
RadioMaster MT12 Internal 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
RadioMaster 2.4 GHz
Device:
RadioMaster Zorro 2.4GHz TX
RadioMaster TX16S Internal 2.4GHz TX
RadioMaster TX12 Internal 2.4GHz TX
RadioMaster Boxer Internal 2.4GHz TX
RadioMaster Pocket Internal 2.4GHz TX
RadioMaster MT12 Internal 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Info
ETX Passthrough is the result of the collaborative effort between RadioMaster, EdgeTX and ExpressLRS.
It is only available on Radios with Internal ExpressLRS Modules.
Before you start, ensure you have the latest EdgeTX firmware version on your Radio. Consult the EdgeTX documentation regarding the updating process.
TX16S MK2: Update it to at least EdgeTX 2.7.0 (f79978b) or EdgeTX 2.7.1 (a55aff0).
Zorro: Update it to at least EdgeTX 2.7.0 (f79978b) or EdgeTX 2.7.1 (a55aff0). It often comes with an earlier EdgeTX 2.7.0 version (2bdd4974) which results in unsuccessful flashing.
TX12 MK2: Update it to at least EdgeTX 2.8.0 (f6d140e) for full EdgeTX support.
Boxer: The factory EdgeTX firmware should be based off an early EdgeTX 2.8.0 and wouldn't need an update.
Pocket: The factory EdgeTX firmware shouldn't need an update.
MT12: The factory EdgeTX firmware shouldn't need an update.
Hot Tip
To ensure updating success with this method, update the EdgeTX firmware on the radio as mentioned above.
Simplest EdgeTX Updating Procedure (click/tap to expand)
Visit http://buddy.edgetx.org/.
Select the EdgeTX version and the Radio Model you want to update from the Left-hand side column.
Click the Download .bin button at the bottom of the page.
Save the firmware file into your Radio's SD Card, inside the Firmware Folder.
Reboot the Radio into DFU/Bootloader mode.
Turn off your radio.
Press and hold the two horizontal Trim switches then press the Power button. The Screen should Light up. Let go of the buttons.
Some Radios have a different procedure, like the BetaFPV Lite Radio 3 Pro. Consult the Manual for the steps to get it into this DFU/Bootloader mode.
Select Write Firmware.
Navigate to the EdgeTX firmware file you just downloaded.
Follow the screen prompts.
Once Writing is complete, reboot the radio.
Check the Radio's Version Page to verify you have the version you need.
Also make sure you have an internal ELRS module on your Radio. The following steps only apply to handsets with ExpressLRS-specific internal modules. There are stickers marked with \"ELRS\" attached to your radio packaging or boxes, as well as on the JR module bays indicating the type of internal rf module the radio have.
Example Sticker On RadioMaster Handset/Radios
The current Model on the radio should be using the Internal ExpressLRS Module. Test this by loading the ExpressLRS Lua Script from the Tools Menu.
There's one more setting you want to make sure is set properly before you proceed.
Press the SYS Key on the Radio.
Press the PAGE Key until you reach the Hardware Page.
Scroll down until you get to the Serial Ports settings.
Scroll down and select USB-VCP. Press Enter and use the Scroll Wheel to set it to CLI mode if it is set to a different setting. Press Enter once more to confirm the changes.
Exit the Hardware menu by long-pressing RTN Key.
Now follow the next steps to get your Internal ExpressLRS Module Updated:
Connect your powered-up Radio to your Computer via a USB Data Cable.
On your Radio, scroll down and select USB Serial(VCP) then press the Enter Key. Set your Radio aside in the meantime.
On your Computer, check whether your Radio is being recognized correctly as a STMicroelectronics Virtual COM Port device.
Important
This is a vital step and a common failure point. Pay attention.
Windows Users can use Device Manager to check whether the Radio is being recognized correctly.
Yellow Caution Triangles in the Device Manager, or any mention of <Radio Name> Serial Port means drivers aren't installed.
Download the Driver package first. Unzip/extract the contents of the package and run/execute (double-click) the installer file (VCP_V1.5.0_Setup_W7_x64_64bits.exe for Windows 10 Users).
Once Drivers are installed, check again if the Radio is now being recognized correctly. You may have to unplug-replug the USB Cable first or even reboot your computer.
You only have to do this once usually.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
RadioMaster 2.4 GHz
Device:
RadioMaster Zorro 2.4GHz TX
RadioMaster TX16S Internal 2.4GHz TX
RadioMaster TX12 Internal 2.4GHz TX
RadioMaster Boxer Internal 2.4GHz TX
RadioMaster Pocket Internal 2.4GHz TX
RadioMaster MT12 Internal 2.4GHz TX
Set the Flashing Method to EdgeTXPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your Radio from USB.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
These devices come pre-installed with a 3.x-ready firmware. You don't need to reflash these devices. You can use the Web UI of these devices to update the Binding Phrase or any of the firmware options.
"},{"location":"quick-start/transmitters/rm-ranger/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia UART Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Radiomaster 2.4 GHz
Device:
RadioMaster Ranger 2.4GHz TX
RadioMaster Ranger Micro 2.4GHz TX
RadioMaster Ranger nano 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Radiomaster 2.4 GHz
Device:
RadioMaster Ranger 2.4GHz TX
RadioMaster Ranger Micro 2.4GHz TX
RadioMaster Ranger nano 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Radiomaster 2.4 GHz
Device:
RadioMaster Ranger 2.4GHz TX
RadioMaster Ranger Micro 2.4GHz TX
RadioMaster Ranger nano 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here: CP210x Drivers
Windows Users should download the CP210x Windows Drivers package for easier installation. Unzip/Extract the contents of the package and run the setup wizard.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Radiomaster 2.4 GHz
Device:
RadioMaster Ranger 2.4GHz TX
RadioMaster Ranger Micro 2.4GHz TX
RadioMaster Ranger nano 2.4GHz TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
"},{"location":"quick-start/transmitters/siyifm30/#fm30","title":"FM30","text":""},{"location":"quick-start/transmitters/siyifm30/#flashing-via-stlink","title":"Flashing via STLink","text":"
Target: FM30_TX_via_STLINK
Note
The only way to flash the FM30 series is using STLINK. Luckily, their pads are pretty generous on the TX and easy to connect. This is a one-way process, there is no returning to the stock firmware after flashing.
The TX module is opened by removing the four screws on the corners of the case using a small phillips screwdriver, then two further screws to remove the circuit board once inside.
Connect wires to SWDIO, SWCLK, NRST, and GND to the header points shown in red above on the TX. Attach 5V to the VCC pad, not the 3.3V pad!
Connect the other side to a STLINK programmer
Flash using the FM30_TX_via_STLINK target
After the flashing procedure, it is safe to leave the STLINK device connected to test that the firmware is operational, but unplug the USB connection before inserting the module into your handset for testing.
Be sure your handset has the External Module type set to CRSF. See the general Troubleshooting section for other ways to determine your module is flashed and ready for flying.
"},{"location":"quick-start/transmitters/siyifm30/#updating-via-dfu","title":"Updating via DFU","text":"
Target: FM30_TX_via_DFU
Updating the TX is a lot easier and can be done via DFU without needing a STLINK.
Remove the module from your handset. \u26a0\ufe0f DO NOT plug in the USB while the module is still in the handset. There is no protection to prevent connecting the USB's power directly to your handset.
Hold the button labeled \"Bind\" on the FM30 TX. Plug in the USB. There should be an \"ExpressLRS DFU bootloader\" device in Windows Device Manager. If not, the STM32 DFU drivers may need to be installed.
Flash using the FM30_TX_via_DFU target
Note that the process always reports failure but this occurs after flashing, so check for the message \"File downloaded successfully\", not what follows it:
Download [======================== ] 97% 46080 bytes\nDownload [=========================] 100% 47340 bytes\nDownload done.\nFile downloaded successfully\nInvalid DFU suffix signature\nA valid DFU suffix will be required in a future dfu-util release!!!\nError during download get_status\n*** [upload] Error 74\n
"},{"location":"quick-start/transmitters/siyifm30/#fr-mini-rx-as-tx","title":"FR Mini RX as TX","text":"
The RX has the same RF components as the TX does, making it a possible candidate for a small ~200mW TX module. Wiring to the JR Module Bay requires only 3 pins (JR pins are starting from the top down)
JR Module Pin | FR Mini Pin | Description |--|--|--| | CPPM | None | | | Heartbeat | None | | | VMain | VIN | Use the VIN pin on the pin header (middle pin), 3.3-3.4V. Do not connect directly to handset battery voltage-- this will burn out the 3.3V regulator even at 10mW output. Use either a 3.3V boost converter (to raise voltage from 1S provided by the handset) or 3.3V buck converter (to lower 2S or 3S handset voltage). The LDO has a very small dropout voltage, so there's not much benefit to bypassing this soldering directly to the VDD pad on the programming header. Expect over 250mA current draw in practice at 100mW. | | GND | GND | Use either the GND pin on the pin header (outermost pin) or the GND pad on the programming header. | SPORT | TX2 | Use the TX2 pad on the receiver and remove the 4.7K pull-up resistor. Without removing the resistor, the module will work okay-ish as a transmitter, but firmware updates through OpenTX will fail with NoSync
"},{"location":"quick-start/transmitters/siyifm30/#flashing-via-stlink_1","title":"Flashing via STLink","text":"
Target: FM30_RX_MINI_AS_TX_via_STLINK
Note
The only way to flash the FR Mini is using STLINK. This is a one-way process, there is no returning to the stock firmware after flashing.
The flashing procedure is similar to the FM30 TX module flashing listed above but using these pads on the receiver. Use the FM30_RX_MINI_AS_TX_via_STLINK target for initial flashing.
"},{"location":"quick-start/transmitters/siyifm30/#updating-via-uart","title":"Updating via UART","text":"
Target: FM30_RX_MINI_AS_TX_via_UART
Updates are done through OpenTX's built-in firmware flashing tool.
Build the firmware using Configurator and selecting the FM30_RX_MINI_AS_TX_via_UART target. The build process will generate a firmware.elrs file.
Copy this file to the handset FIRMWARE/ directory on the SD card.
Flash the firmware to the module using OpenTX
Hold the MENU/SYS button on the handset to open the system menu
Press PAGE to navigate to the SD card browser
Scroll down to the FIRMWARE directory, and press ENTER
Find firmware.elrs and long press the ENTER key to open the context menu
Select Flash Ext. ELRS from the menu
"},{"location":"quick-start/transmitters/siyifm30/#troubleshooting-flashing","title":"Troubleshooting Flashing","text":""},{"location":"quick-start/transmitters/siyifm30/#unable-to-connect-to-the-target-device","title":"Unable to connect to the target device","text":"Unable to connect to the target device (click/tap to expand)
If the flash fails with \"Unable to connect to target device\" (not \"No STLINK found!\") it is likely your STLINK clone does not have the RST line connected, but you can trigger the needed reset manually with a little more effort. The reason this is needed is that SIYI has disabled \"Software Reset\" to protect you from stealing their firmware binary.
Verify your wiring
Make sure the TX board is powering up (the LEDs light up)
Use the STM32CubeProgrammer or STLINK GUI to connect see next step.
Before you press CONNECT. Short the RST line from the TX to GND. Press CONNECT and quickly remove the wire from the GND pad.
If it works, the GUI will tell you that the board is readout protected and must be disabled. Do this.
"},{"location":"quick-start/transmitters/siyifm30/#flash-loader-run-error","title":"Flash loader run error","text":"Flash loader run error (click/tap to expand)
Before both the TX and RX can be flashed using the st-flash utility used by PlatformIO on Linux, the STM32 chip must have its \"Readout Protection\" (RDP) disabled, which was set by SIYI at the factory to make our lives more difficult. The windows flashing utility usually automatically disables this, but the Linux utility does not. If you do not disable readout protection you'll get this cryptic error when flashing:
The only way I know of to disable the RDP is to use the STM32CubeProgrammer for Linux, or use a Windows VM / machine to use the ST-LINK.exe GUI / CLI to clear the RDP.
Click the \"Connect\" button to connect to the ST-LINK device. You'll probably get a popup error Error: Data read failed. That's normal. If it says it can't connect or no device is present, you'll have to figure that out first.
Click the \"OB\" button on the left.
Expand the \"Read Out Protection\" section.
Select RDP = \"AA\"
Click the \"Apply\" button at the bottom.
You should get a message indicating the \"Option bytes successfully programmed\". If so you're good to go. Click \"Disconnect\" at the top and flash from PlatformIO now. You can also flash directly from this GUI if you have the binaries and know their target addresses.
Insert or attach your External ExpressLRS Transmitter Module into your Radio module bay, making sure no pins are bent or missing. External ExpressLRS Modules require three (3) pins to work: VCC/VBAT, GND and S.Port/Data/Signal.
Micro External Bay Pinout Nano External Bay Pinout"},{"location":"quick-start/transmitters/tx-prep/#internal-expresslrs-modules","title":"Internal ExpressLRS Modules","text":"
Make sure you do have an Internal ExpressLRS Module on your shiny new radio. The following handsets come in both ELRS (ExpressLRS) or 4-in-1 variants; with some coming in with a third (CC2500). Only the ELRS variant works with ExpressLRS. The others will not work as they have a different Hardware incompatible with ExpressLRS.
RadioMaster TX16S Mark II (ELRS, 4-in-1 CC2500) - ExpressLRS variant will have an ELRS sticker on the box.
RadioMaster TX12 Mark II (ELRS, 4-in-1, CC2500) - ExpressLRS variant will have an ELRS sticker on the box and an ELRS sticker in the JR module bay.
RadioMaster Zorro (ELRS, 4-in-1, CC2500) - ExpressLRS variant will have an ELRS sticker on the box.
RadioMaster Boxer (ELRS, 4-in-1, CC2500) - ExpressLRS variant will have an ELRS sticker on the box and an ELRS sticker in the JR module bay.
Jumper T-Lite V2 (ELRS, 4-in-1, CC2500)
Jumper T-Pro V1/V2 (ELRS, 4-in-1)
BetaFPV Lite Radio 3 Pro (ELRS, CC2500) - A sticker with the barcode at the bottom of the box should tell you it's an ELRS variant or the CC2500 variant.
Example Sticker On RadioMaster Handset/Radios"},{"location":"quick-start/transmitters/tx-prep/#radio-operating-system","title":"Radio Operating System","text":"
ExpressLRS requires CRSFShot or Mixer Sync to ensure full support for high packet rates. You should have OpenTX 2.3.12 or newer, or EdgeTX 2.4.0 or newer; These versions have full CRSFShot/Mixer Sync support.
To determine your Radio Operating System Version, load the Version page from the System Menu of your Radio:
Press the SYS Key.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Press PAGE Key until you reach the Version Page.
System Key; Short-Press to access the System Menu Menu Key; Long-Press to access the System Menu
If you have an older version, please first update your Radio OS to at least the mentioned versions. Please consult your Radio Operating System Updating Procedure if you don't know how.
ExpressLRS highly recommends EdgeTX for the best experience and compatibility. EdgeTX has introduced options that old and new Radio handsets will benefit from, like One Bit Sample Mode (mainly for old FrSky Radios like the X9D and the QX7) and Mega Bauds (baud rates higher than 400K).
Simplest EdgeTX Updating Procedure (click/tap to expand)
Visit http://buddy.edgetx.org/.
Select the EdgeTX version and the Radio Model you want to update from the Left-hand side column.
Click the Download .bin button at the bottom of the page.
Save the firmware file into your Radio's SD Card, inside the Firmware Folder.
Reboot the Radio into DFU/Bootloader mode.
Start by turning off your radio.
Press and hold the two horizontal Trim switches then press the Power button. The Screen should Light up. Release the buttons.
Some Radios have a different procedure, like the BetaFPV Lite Radio 3 Pro. Consult the Manual for the steps to get it into this DFU/Bootloader mode.
Select Write Firmware.
Navigate to the EdgeTX firmware file you just downloaded.
Follow the screen prompts.
Once Writing is complete, reboot the radio.
Check the Radio's Version Page to verify you have the version you need.
Check this page for the EdgeTX installation instructions if you're coming in from OpenTX.
The Baud Rate is the speed to which (in this instance) the Transmitter module and the Radio Handset communicate. It is measured in bits per second. Common baud rates include 115200bps (sometimes shown as 115K) and 400000bps (sometimes shown as 400K).
A faster or higher baud rate means that the module and radio can talk much faster, further lowering the end-to-end latency of the system. However, not all radio handsets or transmitter modules are capable of higher baud rates as this is highly dependent on the hardware.
Depending on the firmware that is running on your radio handset, you can change the baud rate setting to better suit your setup.
The minimal required Baudrate depends on the highest Packet Rate you intend to run. The Baudrate should be set to:
400K (400000bps): for Packet Rates of 250Hz and lower. This setting should work on most Radios and TX Modules.
921k (921000bps): for Packet Rates of 500Hz and lower.
1.87M (1870000bps): for Packet Rates F1000 and lower.
However, there are some exceptions:
The FrSky Taranis QX7 ACCST, Horus X12S and Horus X10S cannot reliably run 400K baud rate without the Crossfire Mod.
The FrSky Taranis X9D has proven to be finicky even with the default 400K baud rate and will benefit from the One Bit Sample Mode setting and a Hardware Mod. See Troubleshooting the X9D for more details.
On other Radios, you can set the Baudrate higher than 400K but will highly depend on what TX Module you will use with it.
"},{"location":"quick-start/transmitters/tx-prep/#max-usable-baud-rates","title":"Max Usable Baud Rates","text":"Internal TX Module Max Baud Rate Notes RadioMaster TX16S 5.25M RadioMaster Zorro 5.25M RadioMaster Boxer 5.25M RadioMaster Pocket 5.25M RadioMaster MT12 5.25M RadioMaster TX12 5.25M Jumper T-Lite V2 1.87M Limited by Handset Jumper T-Pro 1.87M Limited by Handset Jumper T20 1.87M Limited by Handset Jumper T14 5.25M Jumper T15 5.25M Jumper T12 Max 5.25M BetaFPV Lite Radio 3 Pro 1.87M Limited by Handset HelloRadio V16 5.25M External TX Module Max Baud Rate Notes Happymodel ES24TX (inc. slim, nano, etc) 5.25M Happymodel ES24TX Pro/Slim Pro 5.25M Happymodel ES900TX 5.25M Happymodel ES915/868TX 1.87M STM-based BetaFPV Micro & Nano (V1 & V2) 5.25M BetaFPV SuperG 5.25M RadioMaster Ranger (Micro & Nano included) 5.25M RadioMaster Bandit (Micro & Nano included) 5.25M Axisflying Thor 5.25M EMAX Aeris OLED & Nano 5.25M NamimnoRC Flash/Voyager (no OLED) 3.75M STM-based NamimnoRC Flash/Voyager OLED 5.25M Vantac Lite 1.87M Jumper Aion Nano 1.87M iFlight Command 8 3.75M wired as external module HGLRC Hermes 5.25M HGLRC T ONE OLED 5.25M FrSky R9M/R9M Lite/R9M Lite Pro 1.87M FrSky R9M 2018 (non-ACCESS) 115K Resistor Mod for 400K QuadKopters JR & Slim 5.25M SIYI FM30 1.87M STM-based ImmersionRC GHOST 1.87M STM-based
Note
The Max Baud Rate for external modules will still depend on the capabilities of the Radio Handset.
As stated above, older radios like the QX7 and X9D(+) will require hardware mods and software tweaks, like the One Bit sampling mode, to work reliably at higher baud rates. We recommend not going higher than 400K on these radios. Set them higher at your own risk.
Newer EdgeTX radios can easily use higher baud rates without modification and we recommend using the maximum baud rate whenever you can.
My TX Module is not in this list! (click/tap to expand)
Don't be salty. That just means the maintainers are late with the updates. Newer TX modules being released are all ESP-based now. If your TX module has WiFi or Bluetooth Connectivity, then they are ESP-based, and thus, should be capable of 5.25M Baud Rate (depending on the handset).
The ADC filter is enabled by default in OpenTX and is known to cause issues with RC Command data. This can result in \"jagged\" RC command responses in black box logs, caused by sequential RC packets that have the same command value (which were \"smoothed\" by the ADC filter). We recommend turning the ADC filter OFF in OpenTX/EdgeTX.
To check and change this setting, follow these steps:
Press SYS Key.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to get to the System Menu.
Press the PAGE Key until you reach the Hardware Page.
Scroll down until you reach the ADC Filter setting.
Press Enter Key to toggle it On or Off.
EdgeTX 2.7.0 (and newer) Per-model Settings (click/tap to expand)
With EdgeTX 2.7 or newer, you can set this per model (Global, On, Off) as this is helpful on Fixed Wing models equipped with PWM receivers connected to slower servos.
Press MDL Key.
Older Radios or those with only one Menu Key will need to short-press the Menu Key to access the Model Menu.
Consult your Radio User's Manual on how to get to the Model Menu.
Press the PAGE Key until you reach the Model Setup Page. On Colored Screen Radios, this should not be needed.
Scroll down until you reach the ADC Filter setting.
Press Enter Key once.
Use the Scroll wheel to select between Global(uses the setting from the Hardware page in the System Menu), On or Off.
If you're using an External ExpressLRS Module, make sure the Internal RF Module is OFF.
If your Radio has an Internal ExpressLRS Module, and you want to use it instead of an external module, then set the External RF Module to OFF, and then set the Internal RF Module to CRSF Protocol.
ExpressLRS uses the CRSF serial protocol to communicate between the transmitter and the TX module. Follow the following procedure to set it up on the currently selected Model:
Older Radios or those with only one Menu Key will need to short-press the Menu Key to access the Model Menu.
Consult your Radio User's Manual on how to get to the Model Menu.
Press the PAGE Key until you reach the Model Setup Page. On Colored Screen Radios, this should not be needed.
Scroll down until you reach the Internal RF settings. Set this to Off.
Scroll down until you reach the External RF settings.
Set the Mode to CRSF.
You can also change the baud rate setting at this point.
(Optional) Set the Receiver ID to a Unique Number.
Press the RTN Key or Exit the Model Menu
Press the MDL Key.
Older Radios or those with only one Menu Key will need to short-press the Menu Key to access the Model Menu.
Consult your Radio User's Manual on how to get to the Model Menu.
Press the PAGE Key until you reach the Model Setup Page. On Colored Screen Radios, this should not be needed.
Scroll down until you reach the Internal RF settings.
Set the Mode to CRSF.
(Optional) Set the Receiver ID to a Unique Number.
Scroll down until you reach the External RF settings. Set this to Off.
Press the RTN Key or Exit the Model Menu
No CRSF Mode Option? (click/tap to expand)
If for some reason, you cannot find the CRSF Protocol under the Internal RF Modes, set the Internal Module Type to CRSF via your Radio's System Menu -> Hardware page.
Press the SYS Key.
Radios without a dedicated SYS Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to get to the System Menu.
Press the PAGE Key until you get to the Hardware page.
Scroll down until you reach the Internal RF settings.
Set the Type to CRSF.
You can also set the Baudrate at this point.
Press the RTN Key or Exit the Hardware Menu, and go back into setting your Internal RF module.
Note
The iFlight Commando 8 is NOT using an internal RF module for its ExpressLRS units, unlike the RadioMaster Zorro, RadioMaster TX16S MK2, RadioMaster TX12 MK2, Jumper T-lite V2, Jumper T-pro or the BetaFPV Lite Radio 3 Pro.
Set the Internal RF module to Off, and set the External RF module to CRSF protocol, as any External RF module requires.
"},{"location":"quick-start/transmitters/tx-prep/#switches-and-aux-channels","title":"Switches and Aux Channels","text":"
By default, a fresh model does not have any Aux Channels configured (Aux channels start from Ch5, with the first 4 Channels assigned to your joysticks). If moving any of the switches in your radio doesn't affect your Modes in Betaflight or INAV, this is one of the main reasons. So let's get this sorted out!
Press the MDL Key.
Older Radios or those with only one Menu Key will need to short-press the Menu Key to access the Model Menu.
Consult your Radio User's Manual on how to get to the Model Menu.
Press the PAGE Key until you reach the Mixes Page.
Scroll down and select the Channel you want to configure.
Long press Enter and select Edit and press Enter once more.
(Optional) You can name this channel however you want to remind you of its purpose.
Select Source. Press the Enter Key.
Activate or flick the Switch you'd want to use for this channel.
An example would be for CH5, which will be your Arming switch, you'd want to choose a 2-position switch.
Press the Enter Key once more to set the switch.
Press RTN Key once to exit the Channel Mix editor.
Repeat steps 3-9 until you have configured all the switches you think you will need.
Mono-Screen RadioColored-Screen Radio
"},{"location":"quick-start/transmitters/updating/","title":"Typical Updating Steps","text":""},{"location":"quick-start/transmitters/updating/#esp-based-tx-module-updating-methods","title":"ESP-based TX Module Updating Methods","text":"via WiFivia UARTvia ETX Passthrough Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
Some TX Modules would require disassembly before you can reach the USB port.
Determine whether your TX Module is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
Commonly used USB-to-UART chip for ExpressLRS Modules include: CP210x, CH340 and the CH9102 (driver download pages linked).
Some TX Modules have switches to change how the USB port interacts with the different components in the module. Make sure to set it in the position for \"Flashing the TX Module via UART\".
The ES24TX line of modules from Happymodel have jumper blocks or dipswitches inside the module.
The BetaFPV Micro modules have dipswitches at the back.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB. Return any dipswitches or jumper blocks to their \"Normal Operation\" position.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
Info
ETX Passthrough is the result of the collaborative effort between RadioMaster, EdgeTX and ExpressLRS.
It is only available on Radios with Internal ExpressLRS Modules.
Before you start, ensure you have the latest EdgeTX firmware version on your Radio. Consult the EdgeTX documentation regarding the updating process.
TX16S MK2: Update it to at least EdgeTX 2.7.0 (f79978b) or EdgeTX 2.7.1 (a55aff0).
Zorro: Update it to at least EdgeTX 2.7.0 (f79978b) or EdgeTX 2.7.1 (a55aff0). It often comes with an earlier EdgeTX 2.7.0 version (2bdd4974) which results in unsuccessful flashing.
TX12 MK2: Update it to at least EdgeTX 2.8.0 (f6d140e) for full EdgeTX support.
Boxer: The factory EdgeTX firmware should be based off an early EdgeTX 2.8.0 and wouldn't need an update.
BetaFPV Lite Radio 3 Pro: Update it to at least EdgeTX 2.8.0 (f6d140e) for full EdgeTX support.
Jumper T-Pro: Update it to at least EdgeTX 2.7.1 (a55aff0) for full EdgeTX support.
Jumper T-Lite V2: Update it to at least EdgeTX 2.8.0 (f6d140e) for full EdgeTX support.
Simplest EdgeTX Updating Procedure (click/tap to expand)
Visit http://buddy.edgetx.org/.
Select the EdgeTX version and the Radio Model you want to update from the Left-hand side column.
Click the Download .bin button at the bottom of the page.
Save the firmware file into your Radio's SD Card, inside the Firmware Folder.
Reboot the Radio into DFU/Bootloader mode.
Turn off your radio.
Press and hold the two horizontal Trim switches then press the Power button. The Screen should Light up. Let go of the buttons.
Some Radios have a different procedure, like the BetaFPV Lite Radio 3 Pro. Consult the Manual for the steps to get it into this DFU/Bootloader mode.
Select Write Firmware.
Navigate to the EdgeTX firmware file you just downloaded.
Follow the screen prompts.
Once Writing is complete, reboot the radio.
Check the Radio's Version Page to verify you have the version you need.
Also, make sure you have an internal ELRS module on your Radio. The following steps only apply to handsets with ExpressLRS-specific internal modules. There are stickers marked with \"ELRS\" attached to your radio packaging or boxes, as well as on the JR module bays indicating the type of internal rf module the radio has.
The current Model on the radio should be using the Internal ExpressLRS Module. Test this by loading the ExpressLRS Lua Script from the Tools Menu.
There's one more setting you want to make sure is set properly before proceeding.
Press the SYS Key on the Radio.
Radios without a dedicated SYS Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to get to the System Menu.
Press the PAGE Key until you reach the Hardware Page.
Scroll down until you see the Serial Ports settings.
Select or highlight USB-VCP. Press Enter and use the Scroll Wheel to set it to CLI mode if it is set to a different setting. Press Enter once more to confirm the changes.
Exit the Hardware menu by long-pressing RTN Key.
Now follow the next steps to get your Internal ExpressLRS Module Updated:
Connect your powered-up Radio to your Computer via a USB Data Cable.
On your Radio, scroll down and select USB Serial(VCP) then press the Enter Key. Set your Radio aside in the meantime.
On your Computer, check whether your Radio is being recognized correctly as a STMicroelectronics Virtual COM Port device.
Important
This is a vital step and a common failure point. Pay attention.
Windows Users can use Device Manager to check whether the Radio is being recognized correctly.
Yellow Caution Triangles in the Device Manager, or any mention of <Radio Name> Serial Port means drivers aren't installed.
Download the Driver package first. Unzip/extract the contents of the package and run/execute (double-click) the installer file (VCP_V1.5.0_Setup_W7_x64_64bits.exe for Windows 10 Users).
Once Drivers are installed, check again if the Radio is now being recognized correctly. You may have to first unplug-replug the USB Cable or even reboot your computer.
You only have to do this once usually.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Set the Flashing Method to EdgeTXPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your Radio from USB.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
"},{"location":"quick-start/transmitters/vantac-lite/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia UART Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Vantac 2.4 GHz
Device:
Vantac Lite 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Vantac 2.4 GHz
Device:
Vantac Lite 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Vantac 2.4 GHz
Device:
Vantac Lite 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from the links below:
Windows users: CH340 Windows Drivers
For other Operating Systems, head to this site to download your needed drivers.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Vantac 2.4 GHz
Device:
Vantac Lite 2.4GHz TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
"},{"location":"quick-start/transmitters/voyager900/#flashingupdating-the-tx-module-firmware","title":"Flashing/Updating the TX Module Firmware","text":"via Stock_BLvia STLink
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 900 MHz
Device:
NamimnoRC Voyager 900MHz TX
Set the Flashing Method to Stock_BL
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Build button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
A Temp folder will open up with the firmware.elrs file. Copy-paste the firmware.elrs file into your Radio's SD Card (preferably to the /FIRMWARE folder for easy access).
On your radio, open the System Menu.
On newer radios, you can press the SYS key to open the System Menu
On older radios, or radios that only have a menu key, long-press the Menu key to open the System Menu
Using the Page key/s, navigate to the SD-HC Card page, scroll-down and open the FIRMWARE folder where you can find the firmware.elrs file.
Highlight the file and press-hold the Enter button and select \"Flash External ELRS\". Wait for the firmware to be written.
No Sync (click/tap to expand)
Make sure you have updated the OpenTX/EdgeTX firmware of your radio to a newer version
Make sure the current model selected on the radio is set up for ExpressLRS Use. See the [Radio Preparation] guide.
With the ExpressLRS Lua Script in the Tools page, verify if the firmware version has been updated.
Attention
Only use this method if the firmware has been corrupted.
Disassemble your TX Module to get access to the mainboard.
Connect your STLink V2 dongle to the pads shown in the image below.
Connect your STLink V2 dongle to your Computer's USB Port. Make sure it is being detected correctly.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 900 MHz
Device:
NamimnoRC Voyager 900MHz TX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Disconnect the STLink V2 dongle from the TX Module PCB and reassemble the module.
Reattach your TX Module into your Radio and, using the ExpressLRS Lua Script, verify if the firmware version has been updated.
With the addition of MAVLink support in ELRS 3.5, it is no longer recommended to use Airport for MAVLink telemetry. Please see the MAVLink page for more info.
AirPort provides a firmware option that allows you to turn a regular ExpressLRS transmitter and receiver pair into a bi-directional transparent serial data link, over the air. A TX module can connect via USB to a laptop, and RX modules (or those flashed using RX-as-TX) can connect to a free UART on your device, as per usual. This allows for a wireless serial data link between TX and RX, as if they were connected directly via serial. Note that due to the packet size and sensitive LoRa modulation parameters used by ELRS, the data rate is relatively slow. Also, as the protocol has no knowledge of the data being transported, there is no ACK or retransmission which may result in dropped packets.
Warning
The AirPort option completely replaces the RC link, and repurposes it as a data link. If you intend to retain RC control via ELRS, you will need to run 2x TXs and 2x RXs on the ground and air, respectively. One TX+RX pair sends your normal RC link data, just as it does now, and the other TX+RX pair sends the serial data.
ExpressLRS TX module: A dedicated external TX module is required for the data link. The TX should ideally have an external USB port to make it easy to attach to a computer (assuming a computer is the desired endpoint for the data link). It is also favorable to use a module with a screen and a 5-way button, which makes packet rate and power selection easier. The TX should use an ESP-based microcontroller (for access to the WebUI).
ExpressLRS RX: Any ExpressLRS ESP-based receiver is compatible with AirPort (technically STM-based receivers can work too, but it will be harder to set up and is therefore not covered in this guide). Receivers with higher telemetry power output (i.e. 100mW telemetry power) will provide better results.
Frequency band
If you plan to use two side-by-side ELRS links on the craft (one for RC and one for telemetry), it is HIGHLY recommended to use different frequencies for each link. For example, you will see good results with RC on 2.4GHz and AirPort on 900MHz. The range will be severely reduced if both RC and AirPort are on the same frequency band.
"},{"location":"software/airport/#data-rate-vs-baud-rate","title":"Data rate vs Baud rate","text":"
AirPort uses a 64-byte buffer to queue bytes that it receives from the FC or GCS, before sending them over the air. If the buffer overflows, the entire 64 bytes are discarded. For this reason, it is VERY important to select a serial baud rate that limits the flow of serial bytes to match the maximum over-the-air (OTA) data rate.
The OTA data rate is determined by the selected packet rate. A faster packet rate will result in a higher data rate at the expense of range. The table below shows the baud rate you should use when configuring the AirPort feature.
Packet Rate Maximum OTA Data Rate (bytes/s) Baud Rate to Select 25Hz 62 600 50Hz 125 1200 100Hz 250 2400 100Hz Full Res 500 4800 200Hz 500 4800 250Hz 625 4800 333Hz Full Res 1665 14400 or 9600 500Hz 1250 9600 1000Hz 2500 19200
Once AirPort is enabled, there will be no way to access the RX settings from the LUA script. Before enabling the AirPort option, it is recommended that you bind the TX and RX normally, and (using the LUA) set the RX telemetry power output to maximum. If you already have AirPort enabled, and need to change the RX power, you will need to disable the AirPort checkbox by doing the reverse of the steps below, change the power using LUA, then re-enable AirPort.
Binding Phrases
Use a binding phrase that is different from whatever you are using for your RC link if you intend to run RC + AirPort side by side in ANY way.
TX ModulesRXes
Flash the TX Module with the latest ELRS release version (AirPort is available in v3.3.0 onwards).
Enable WiFi on the TX module. This can be enabled by inserting the TX into a handset, and in the LUA script select WiFi Connectivity -> Enable WiFi. WiFi can also be enabled via the screen + 5-way if your TX has one (while powered via USB).
Using a computer or mobile device, connect to the TX WiFi using your preferred method (hotspot or home WiFi).
Open the WebUI (10.0.0.1 for hotspot, or http://elrs_tx.local for home WiFi) in a browser.
In the ELRS WebUI, check the Use as AirPort Serial device checkbox.
In the AirPort UART baud field, enter your desired baud rate. IMPORTANT: Pay close attention to the \"Data rate vs Baud rate\" section above when choosing your baud. A good default is 9600 baud for 2.4GHz and `4800`` baud for 868/900MHz.
Click SAVE & REBOOT.
Flash the RX with the latest ELRS release version (AirPort is available in v3.3.0 onwards).
Enable WiFi on the RX. This can be enabled by powering on the RX with no TX powered and waiting for the WiFi timeout.
Using a computer or mobile device, connect to the RX WiFi using your preferred method (hotspot or home WiFi).
Open the WebUI (10.0.0.1 for hotspot, or http://elrs_rx.local for home WiFi) in a browser.
In the ELRS WebUI, check the Use as AirPort Serial device checkbox.
In the UART baud field, enter your desired baud rate. IMPORTANT: Pay close attention to the \"Data rate vs Baud rate\" section above when choosing your baud. A good default is 9600 baud for 2.4GHz and `4800`` baud for 868/900MHz.
Once you have enabled the AirPort setting on both TX and RX, they should be ready to send bi-directional serial data. If you have an FTDI (USB to serial adapter) handy, you can confirm that the link is working as expected before installing it in a craft.
Using a suitable USB cable, connect your TX module to a computer.
Open a serial terminal client, such as PuTTY, and connect to the COM port for your TX module using the baud rate you chose in the section above.
Connect your FTDI to your computer, and connect the RX to the FTDI
Open a second instance of PuTTY, and connect to the COM port for your FTDI using the baud rate you chose in the section above.
Type chars into each PuTTY window, and confirm you can see them on the opposite terminal session (i.e. typing into the TX PuTTY should result in the same chars appearing in the RX PuTTY window). If you see comms, everything is working.
Connect the RX to a spare UART on your flight controller, as per normal:
Example AirPort Receiver Wiring
Using the appropriate Configurator tool for your FC firmware, configure your selected UART with your desired telemetry protocol. For example, if using AirPort for MAVLink in ArduPilot, you would set:
SERIALN_BAUD to the baud you entered in the section above,
SERIALN_OPTIONS to 0,
SERIALN_PROTOCOL to 1 or 2 (for MAVLink v1 or MAVLink v2).
Connect the TX to a computer via USB, open the program that you intend to view the telemetry in, then connect to the COM port for your TX module at the baud you entered above. For example, if using AirPort for MAVLink in ArduPilot, you would open Mission Planner / QGC etc. and select the TX COM port, enter the baud, then click Connect.
Version 3.4+ of ELRS introduces a new option in the Backpack section of the ELRS LUA script called \"Telemetry.\" This feature allows a Backpack equipped ELRS Transmitter to forward CRSF telemetry frames to any peer that is capable of receiving ESPNOW messages. These frames can be consumed by any Backpack receivers that are bound with your bind phrase.
Sentinel Integration
This capability is particularly useful for devices like the Sentinel Antenna Tracker, which can subscribe to ESPNOW telemetry packets and read GPS data from the telemetry feed. See the Sentinel product page
ELRS transmitter and receiver with the latest firmware.
Backpack-capable receiver (e.g., in the Sentinel Antenna Tracker).
Configured ELRS LUA script on your transmitter.
"},{"location":"software/backpack-telemetry/#setting-up-the-backpack-telemetry-feature","title":"Setting Up the Backpack Telemetry Feature","text":""},{"location":"software/backpack-telemetry/#step-1-update-firmware","title":"Step 1: Update Firmware","text":"
Ensure both your transmitter and receiver are running the latest firmware. Follow the firmware update guide for detailed instructions. This feature is available in v3.4.0 onwards.
"},{"location":"software/backpack-telemetry/#step-2-enable-backpack-telemetry-in-elrs-lua-script","title":"Step 2: Enable Backpack Telemetry in ELRS LUA Script","text":"
Access the LUA Script:
Power on your transmitter and navigate to the System menu.
Execute the ELRS LUA script.
Navigate to the Backpack Section:
Scroll to find the \"Backpack\" section within the LUA script.
Select the \"Telemetry\" option.
Enable Backpack Telemetry:
Set the \"Telemetry\" option to ESPNOW.
Exit the script.
NOTE: Backpack telemetry is transmitted on the 2.4G WiFi band, via ESPNOW (this should have a very limited impact on any LoRa signals, as it is modulated via OFDM like a normal WiFi hotspot). Every telemetry message that your transmitter receives from the craft will be re-transmitted via ESPNOW. You may want to disable Backpack Telemetry to reduce your footprint on the RF noise floor when you aren't using it, especially if you are at something like a race day, where there is often contention on the RF spectrum. To disable Backpack Telemetry:
Execute the ELRS LUA script.
Scroll to find the \"Backpack\" section within the LUA script.
Ensure your Backpack receivers (e.g., the one in the Sentinel Antenna Tracker) are bound using your bind phrase. This allows them to receive telemetry data sent via ESPNOW. See the Sentinel ELRS setup guide
"},{"location":"software/backpack-telemetry/#using-the-telemetry-feature-with-sentinel-antenna-tracker","title":"Using the Telemetry Feature with Sentinel Antenna Tracker","text":""},{"location":"software/backpack-telemetry/#sentinel-configuration","title":"Sentinel Configuration","text":"
The Sentinel Antenna Tracker includes an ESP12 Backpack-capable receiver that can consume ESPNOW telemetry frames. Ensure the tracker is properly configured to subscribe to ESPNOW telemetry packets. See the Sentinel ELRS setup guide
Once configured, power up your GPS-equipped craft and establish the link between your ELRS Transmitter and Receiver. Ensure that GPS telemetry is being received on your Handset (go to the Model menu in EdgeTX, and inspect the Telemetry page to make sure you are getting GPS coordinates). The Sentinel Antenna Tracker will be able to read GPS data and other telemetry information from the telemetry feed provided by the ELRS transmitter.
"},{"location":"software/backpack-telemetry/#advanced-use-cases","title":"Advanced Use Cases","text":"
This new telemetry feature can be expanded for various applications, e.g.:
Real-time flight data monitoring.
Integration with other ESP Backpack-compatible devices.
Any Espressif ESP-based microcontroller, like the ESP32 or ESP8266 (and many variants) is capable of receiving ESPNOW frames. Custom firmware could be written to decode the CRSF telemetry and consume it in your own custom solution. See this ESPNOW guide for an example of developing using ESPNOW.
No Telemetry Data: Ensure the \"Telemetry\" option is set to ESPNOW in the Backpack section of the LUA script and that the firmware is up to date. Also check that your Telemetry Ratio is set to a value that is able to provide frequent telemetry packets. As a rule of thumb, a ratio somewhere between 1:2 to about 1:16 (depending on your packet rate) will suffice. See Packet Rate and Telemetry Ratio and Telemetry
Binding Issues: Verify that the bind phrase is correctly set and matches between the Backpack on your transmitter and the Sentinel receiver.
Interference: The Backpack Telemetry feature uses a point to point WiFi-based link to forward telemetry. The Sentinel tracker (or other Backpack receiver type) should be within 10m of the ELRS transmitter (ideally 5m or less) for good WiFi signal. Some ELRS transmitters have better Backpack WiFi antennas than others, so your mileage may vary depending on your hardware. If you are experiencing drops in the link between ELRS and the Sentinel tracker (or other Backpack receiver type), try moving the two closer, or move to an area with less WiFi noise.
Dynamic Power allows the TX module to lower its output power from the configured power level using signal information from the RX. The TX will lower power if the signal level is above a threshold (see below) and will raise power if it is not, has a low LQ, or has a sudden drop in LQ. Because Dynamic Power relies on telemetry, telemetry must be enabled. That is, \"Telem Ratio\" must be set to anything except \"Off\" or \"Race\".
Warning
Dynamic Power relies on telemetry. If no telemetry is received while armed, then the power level will be kicked up to the maximum configured power level.
"},{"location":"software/dynamic-transmit-power/#how-to-configure-dynamic-power","title":"How to configure Dynamic Power","text":"
In the ELRS Lua script, select > TX Power. There are three configurable elements.
Max Power: The output power will never exceed this power output level in any situation.
Dynamic: Three options are available.
Off: Fixed power, always set power to the configured Max Power output.
Dyn: Dynamic power is enabled.
AUX9-AUX12: Dynamic power is enabled only when this AUX channel is high, and power is fixed to the Max Power when low. Demo Video
Fan Thresh: Fan threshold. If the module has a fan, it will be enabled starting at this power level after a short delay.
Another important setting is to make sure your craft is armed on AUX1=high (~2000us). See Switch Modes for more information about AUX channels.
For non-FLRC modes, Dynamic Power uses the average signal to noise ratio (SNR) reported by the receiver. If the SNR is above a threshold, the power will be lowered by one level. SNR is used because it takes into account interference (the \"noise\" in signal-to-noise) and is not affected by receivers with LNAs, which boost RSSI dBm. The thresholds for lowering the power are specific to each packet rate. For example, 250Hz (LoRa) will lower the power if SNR is >= 9.5 but 150Hz (LoRa) will lower power if the SNR is >= 8.5.
For FLRC modes (packet rates beginning with F or D) Dynamic Power averages the last few RSSI dBm readings from the RX. If the RSSI is >= -83dBm, the transmit power is lowered by one level.
For both algorithms, the power will only be lowered if the link quality (LQ) is 95% or higher.
The opposite of the \"lowering power\" algorithm is also in place, to raise power as needed slowly such as when flying away on a long range flight. The algorithms are the same as for lowering power, except with different thresholds. Examples:
250Hz (LoRa) raise power if SNR <= 3.0
150Hz (LoRa) raise power if SNR <= 0.0
F500 (FLRC) raise power if RSSI <= -89 dBm. Note that all FLRC modes use this same limit.
To be proactive when telemetry is not received, Dynamic Power will also increase power one level for each missed telemetry packet, starting when two are missed back to back.
TX misses first telemetry packet: no action, maintain power level
TX misses second telemetry packet: increase power 1 level
TX misses third telemetry packet: increase power 1 level
...
TX receives telemetry packet: normal raise / lower conditions apply
In addition to the slow power ramp up, three LQ-based conditions will raise the power immediately to the maximum configured value.
If the LQ ever drops below the hard limit (50% LQ), the power will jump to the max.
If the LQ drops suddenly in a single telemetry update compared to the moving average. This is intended to react to flying behind a structure where the LQ suddenly takes a hit and is expected to drop further. Example: LQ is running 100% (as ExpressLRS does under most conditions) and the TX receives a telemetry packet with 80% LQ, the power will jump to the max.
If telemetry is lost entirely with the arm switch high. Any time the TX is \"disconnected\" while armed, the power will jump to the max.
Finally, if reported LQ is below 85% and no other condition has been met this period, increase the power one level.
Because dynamic power relies on information coming back from the RX to know how to adjust the power, dynamic power is only available if the \"Telemetry Ratio\" is not set to Off / Race. Any ratio will allow it to operate, but the algorithm is optimized around having at least 2x Link Statistics telemetry packets per second, which is provided with the \"Std\" telemetry option. If using a manual telemetry ratio, it is recommended to use at least the ratio suggested below.
Packet Air Rate Telemetry Ratio 1000Hz 1:128 500Hz 1:128 250Hz 1:64 200Hz 1:64 150Hz 1:32 100Hz 1:32 50Hz 1:16
On startup, the output power will be set to the lowest possible value. If telemetry is lost while disarmed, the output power will stay at the current value until telemetry is received again. This is intended to prevent everyone's TX from blasting to max power when swapping batteries.
"},{"location":"software/dynamic-transmit-power/#osd-power-display","title":"OSD Power Display","text":"
To see the current output power on your FPV OSD, enable the TX Uplink Power OSD element and set Switch Mode to Wide in the ELRS lua. TX Uplink Power is not available if Switch Mode is set to Hybrid, or on older Betaflight (<4.3.0) and iNav (<2.6.0) versions.
"},{"location":"software/dynamic-transmit-power/#edgetx-opentx-power-readout","title":"EdgeTX / OpenTX Power Readout","text":"
Alternatively, a handset special function can be used to generate an audio notification when the TX power level changes.
Set a logical switch to |\u0394|>x / TPWR / 1mW as shown in L04 below. The logical switch triggers when the power changes by at least 1mW.
For a readout when the power changes, set a special function triggered from the logical switch, and assign Play Value / TPWR / 1x (SF10 in the picture). If instead you'd prefer the power to be read out periodically, choose a switch to enable the special function, and assign Play Value / TPWR / (SF11 in the picture, with 10s interval).
Note
OpenTX has no value for 50mW in the CRSF Telemetry protocol and instead will be read as 0mW. EdgeTX versions 2.5.0 and newer have the proper 50mW readout.
"},{"location":"software/gemini/","title":"Gemini","text":""},{"location":"software/gemini/#what-is-gemini","title":"What is Gemini?","text":"
Gemini is a dual channel 2.4GHz and/or 900MHz (and potentially other low-band frequencies) transmission mode that leverages true diversity hardware to maximize LQ. This page covers single-band Gemini mode, which uses diversity hardware to transmit in multiple channels within the same band (e.g. 2.4GHz or 900MHz). There is also a dual-band mode, Gemini Xrossband or GemX, which is capable of transmitting on both 2.4GHz and 900MHz bands simultaneously. Please see the PR here for more info while the documentation is updated.
In Gemini Mode, a TX module simultaneously transmits a packet in two frequencies 40MHz apart for 2.4GHz and ~10MHz apart for 900MHz users. The packet separation used is half of the frequency domain selected and will vary a little. A true diversity Receiver is used to receive both packets simultaneously. Transmitting on 2 separate frequencies provides better interference avoidance and/or mitigation, in a similar way DVDA does by sending repeat packets sequentially on different frequencies. This means, the Receiver has an increased chance of receiving the packet. This results in a much higher and stable LQ.
Via Lua set your TX AND RX Antenna Modes to Gemini.
Use Model Config Matching to set the correct antenna mode based on the active Model on the radio. e.g. use Model 5 for single antenna receivers, Model 6 for Gemini-capable receivers.
"},{"location":"software/gemini/#introductory-video-and-testing","title":"Introductory Video and Testing","text":""},{"location":"software/gemini/#what-about-using-gemini-with-dvda","title":"What about using Gemini with DVDA?","text":"
Gemini doubles the redundancy of DVDA modes. For example, D500 sends 2 repeat packets on 2 different frequencies. When using D500 with a Gemini TX you will now have 4 packets sent across 4 different frequencies.
When using D250 which sends 4 repeat packets across 3 frequencies. With Gemini you will now have 8 repeat packets across 6 different frequencies.
"},{"location":"software/gemini/#what-are-the-benefits","title":"What are the Benefits?","text":""},{"location":"software/gemini/#freestylers","title":"Freestylers","text":"
Flying in urban environments with lots of RF noise? Gemini will help to dodge the interference and maintain a strong link.
Flying at events with 6 to 8 up racers, plus who knows how many handsets left powered up in the pits, can cause your precious link to take a hit. Gemini is an obvious choice for these environments when every packet counts.
"},{"location":"software/gemini/#lovers-of-telemetry","title":"Lovers of Telemetry","text":"
A Gemini TX has the advantage of not only sending simultaneous packets, but also receiving simultaneous packets. Or when used in single antenna mode (or switch mode) both antennas will listen for the same TLM packet, in the same way a diversity RX listens for RC packets. So your TLM link becomes stronger with fewer missed packets, even when not used in Gemini mode and with single antenna receivers.
"},{"location":"software/gemini/#airport-and-mavlink-users","title":"AirPort and MAVLink users","text":"
For data links a single missed packet can mean more than 1 missed packet. If a single packet is missed, this means the rest of the data that was received for that MAVLink packet is now wasted. As the MAVLink packet may have been split across multiple OTA packets and will not be complete. The single missed packet can turn into 10 packets missed. Gemini will help with making sure you get the highest MAVLink packet rate possible!
"},{"location":"software/gemini/#will-gemini-increase-my-range","title":"Will Gemini increase my range?","text":"
No. The packet sensitivity remains the same for the RF Mode (or Packet Rate) used. Gemini will help maintain a higher LQ to the point of failsafe. However failsafe will still happen at approximately the same distance e.g. the moon.
"},{"location":"software/gemini/#comparison-with-other-antenna-modes","title":"Comparison with other Antenna Modes","text":""},{"location":"software/gemini/#is-there-antenna-switching-with-gemini-can-antenna-1-of-receiver-talk-with-antenna-2-of-tx-if-they-are-in-the-same-polarization-during-a-flight","title":"Is there antenna switching with Gemini? Can Antenna 1 of Receiver talk with Antenna 2 of TX if they are in the same polarization during a flight?","text":"
Yes, there is antenna switching.
"},{"location":"software/gemini/#what-happens-if-i-use-a-gemini-tx-in-gemini-mode-with-a-single-antenna-receiver","title":"What happens if I use a Gemini TX, in Gemini Mode, with a single Antenna Receiver?","text":"
The Gemini TX will function as designed, in Gemini Mode. The Receiver will only get the signal from the TX it has synchronized with. The other TX, will act as a noise generator. Therefore, you should set the TX in either Switch or Single Antenna (Ant1/Ant2) Mode.
"},{"location":"software/gemini/#what-happens-if-i-use-a-gemini-tx-in-gemini-mode-with-gemini-incapable-diversity-receivers","title":"What happens if I use a Gemini TX, in Gemini Mode, with Gemini-incapable Diversity Receivers?","text":"
As above, with the Receiver antennas only getting sync from one TX. We recommend setting the TX to non-Gemini Modes.
"},{"location":"software/gemini/#how-does-a-gemini-rx-behave-when-paired-with-a-non-gemini-tx","title":"How does a Gemini RX behave when paired with a non-Gemini TX?","text":"
The Receiver will still listen on both Antennas, but only get sync on one. Both RX will send out Telemetry, but only one of them will be used.
You are flying with your buddies and your friend has crashed all his models. You'd like to be able to lend him one of yours but you can't because it's using a binding phrase, so he's relegated to being the crashed model fetcher for the rest of the day!
No longer is he destined to be running to the bando and back again fetching downed quads. You can use the \"Loan Model\" feature and lend him one of your models!
This is deprecated and removed in ExpressLRS 3.4.0 in favor of the new Binding Procedures. See the binding page for details.
"},{"location":"software/loan-model/#how-to-loan-model","title":"How to \"Loan Model\"","text":""},{"location":"software/loan-model/#on-the-lenders-handset","title":"On the lenders handset","text":"
Connect to the model you wish to loan out with your handset
Enter the LUA screen and select \"Other Devices\" at the bottom of the list
Choose the RX from the list
Select the \"Loan Model\" entry
The receiver LED should go into the bind flashing state
"},{"location":"software/loan-model/#on-the-borrowers-handset","title":"On the borrowers handset","text":"
From the main ExpressLRS LUA screen select [Bind]
The receiver LED should turn solid on, and the handset should connect to the receiver
"},{"location":"software/loan-model/#returning-a-loaned-model","title":"Returning a \"Loaned\" Model","text":"
There are a couple of ways to return a model to the owner.
The first method is for the borrower to return it from the LUA script as follows:
On the borrowers handset, connect to the \"loaned\" model
Enter the LUA screen and select \"Other Devices\" at the bottom of the list
Choose the RX from the list
Select the \"Return Model\" entry
The second method used if the borrower forgets to return the model, is as follows:
Power cycle the model 3 times in rapid succession, turning it off each time after the LED flashes on and off again.
If done correctly, the model will return to the state where it is bound to your transmitter.
Note
If the LED returns to normal flashing between reboots, the counter is reset to 0 and you must restart the process.
"},{"location":"software/loan-model/#bump-to-loan","title":"Bump to Loan","text":"
On transmitter modules with an accelerometer (such as the Axis Thor), you can loan and return a model by bumping it to another transmitter.
The process is easy - simply hold both the lender and the borrower's transmitters vertically while a model is connected and not armed and bump them together.
Note
If the borrower does not have an accelerometer, the borrower must go into binding mode manually.
Although MAVLink has been in development for some time, and has been tested by a community of early adopters using ArduPilot crafts, MAVLink support is still a recent addition. There may be unexpected bugs; Exercise due caution.
NOTE
Enabling MAVLink forces the use of Hybrid or 16ch/2 switch mode. Wide switch mode is not supported. Enabling MAVLink forces a telemetry ratio of 1:2
ExpressLRS now has full bi-directional MAVLink support, enabling native MAVLink telemetry downlink and RC control uplink. Users can now enjoy seamless integration of telemetry and RC control.
Unlike airport, you do NOT need a second RX/TX pair for RC control, since ELRS' implementation allows you to do BOTH telemetry and RC control over one link.
To start using MAVLink, you just need one ESP ELRS transmitter, and one ESP ELRS receiver. The majority of recent ELRS hardware is ESP based, and will be compatible with MAVLink. An easy way to check is, if the RX/TX have WiFi, then it is ESP based.
NOTE
If you are using an internal TX module (e.g. a TX16S with internal ELRS), you will be required to use the TX Backpack to connect to you GCS via WiFi (USB cable between the TX and the PC is not an option for internal modules). See WiFi Connectivity below.
NOTE
If you are planning to use 915/868MHz, note that the data rate will be significantly slower than on 2.4GHz. This will result in especially slow parameter downloading, and with 200Hz packet rate at 915MHz, it takes 2+ minutes to pull parameters.
"},{"location":"software/mavlink/#flashing-and-configuring-mavlink-rc","title":"Flashing and Configuring MAVLink-RC","text":"
Ensure both your transmitter module, the embedded TX-Backpack (if using WiFi forwarding), and your receiver are up to date with the latest release versions:
For the main ELRS firmware, follow the Firmware Update Guide for detailed instructions.
For the TX-Backpack, follow the Transmitter Backpack Firmware Guide for detailed instructions.
The minimum versions to use this feature are: - Transmitter / receiver firmware: 3.5.0 - TX Backpack firmware: 1.5.0
Using the guides above, flash both the RX and TX
Turn on both the RX and TX, and ensure they connect properly
In ELRS LUA script, select Other Devices, select your receiver, and set the serial protocol to MAVLink. This configures the RX to output MAVLink protocol on the UART.
Back out to the LUA scripts main menu, and select the new Link Mode option. Change it from Normal to MAVLink. This configures the TX module to send / receive MAVLink.
Configure your usual power, packet rate, etc. The telemetry ratio will be preset to 1:2 (and cannot be changed while in MAVLink mode).
(Optional) Configure Source and Target SysIDs
Power-cycle the receiver
Go to Other Devices and select your receiver
Set Target SysID to the vehicle SysID
Set Source SysID to preferred GCS SysID
Wire the RX to a free UART on your flight controller that is suitable for TLM + RC. A DMA-capable UART is recommended.
ArduPilotPX4INAVBetaflight
For the below steps, when a UART connection is mentioned, it will be written as SERIALx. Replace x with the UART number you are using.
Configure SERIALx_PROTOCOL=2, SERIALx_BAUD=460, and RSSI_TYPE=5
Connect the TX module to the computer running the Ground Control Station via a USB cable (or alternatively via WiFi - See WiFi Connectivity below)
Select the COM port on the GCS, and connect using 460800 baud
For the below steps, when a UART connection is mentioned, it will be written as SER_TELx. Replace x with the UART number you are using.
Configure SER_TELx_BAUD to 460800 8N1
Configure MAVLink with MAV_0_CONFIG to TELEM2
Configure MAVLink sending rate with MAV_0_RATE to 9600 B/s
UNSUPPORTED, CURRENTLY IN DEVELOPMENT - Released versions (up to version 7) of iNav cannot use MAVLink due the limitations highlighted in the Betaflight tab. As of version 8.0, which is currently not released yet, these limitations have been partially resolved and there is limited MAVLink support.
For testing of development version: For the below steps, when a UART connection is mentioned, it will be written as UARTx. Replace x with the UART number you are using.
In the Ports tab, set the UARTx Telemetry Protocol to MAVLink, and the baud rate to 460800. Make sure RX Serial is disabled.
In the Receiver tab, set the Receiver type to SERIAL and the Serial Receiver Provider to MAVLink. Leave inverted & half-duplex disabled.
Betaflight contains an incomplete implementation of the MAVLink protocol standard (lacking RADIO_STATUS flow control). This causes an Betaflight aircraft to saturate the bandwidth of a telemetry link using soft flow control, and renders it unusable, ergo breaking support with ExpressLRS MAVLink.
For TX modules that have an onboard Backpack, the MAVLink data can be sent / received via WiFi to a PC or tablet etc. that is running the GCS software. This provides for a cable-free solution on your handset, as it removes the need for a USB cable between the TX and the GCS device.
To setup WiFi forwarding for MAVLink:
Ensure the TX Backpack is running version 1.5.0 or later
In the ELRS LUA script, select Backpack, scroll to the Telemetry option, and change the value to WiFi
If you are NOT using Home WiFi on the Backpack, a new WiFi access point will be available to connect to. Use your PC or tablet etc. to search for and connect to a WiFi network with SSID of ExpressLRS TX Backpack xxx (where xxx will be part of your UID). The WiFi password is expresslrs. Alternatively, if you ARE using Home WiFi on the Backpack, the Backpack will automatically start WiFi and connect to your router.
Power on the craft, so that the TX and RX have an active link.
On your PC or other GCS device, open your GCS software (e.g. Mission Planner) and set the connection type to UDP. Click connect, and use the default UDP port of 14550. The GCS should successfully connect to the craft and start downloading params.
Attention!
DO NOT manually put the TX Backpack into WiFi mode via WiFi Connectivity -> Enable Backpack WiFi. It's not in the steps above for a reason. When you set Telemetry into WiFi mode, the backpack automatically starts its WiFi mode, and so, there's no need to manually kick it into WiFi mode.
When set to MAVLink mode, ELRS changes the allocation of uplink and downlink frame as follows:
Uplink frames from TX to RX continue to include stick/switch data in the standard ELRS format
Uplink frames are opportunistically replaced with MAVLink data from your GCS to your aircraft, which is limited to a maximum of 50% of the link's upstream bandwidth. In general, MAVLink from GCS to the aircraft consumes very little bandwidth, due to it being mainly GCS heartbeats.
Downlink telemetry frames from RX to TX are completely replaced by MAVLink data
Your TX converts the MAVLink telemetry into standard CRSF format which is understood by EdgeTX
ELRS uses its stubborn telemetry sender system for MAVLink messages - this system retries packets which weren't delivered, keeping MAVLink link quality high over longer distances and/or with interference.
ExpressLRS provides an integration with the MFD Crossbow and mini Crossbow antenna trackers, which wirelessly forwards the telemetry from an ELRS TX module to the Crossbow in order to track the craft.
"},{"location":"software/mfd-crossbow/#how-does-it-work","title":"How does it work?","text":"
In order to forward the telemetry data (that the TX is receiving from the craft) over to the MFD Crossbow, we have leveraged the \"Backpack\" functionality that is built-in to many ELRS transmitter modules. The Backpack allows an ELRS TX module to communicate with nearby devices using ESP-NOW, which is a peer to peer WiFi-based protocol.
By flashing the MFD Crossbow Antenna Tracker Backpack firmware to a receiver, it will now listen for ESP-NOW telemetry packets, and forward them as MAVLink (via UART) to the Crossbow.
When the main ELRS firmware receives the telemetry from the craft, it sends it to the onboard TX-Backpack device, which then broadcasts it via ESP-NOW to any Backpack receivers that are flashed with your bind phrase. The receiver on the Crossbow receives these packets, and is able to track the craft.
"},{"location":"software/mfd-crossbow/#what-do-i-need","title":"What do I need?","text":"
An ELRS transmitter module with internal TX-Backpack.
A Backpack-capable receiver - this can be an ESP-based ExpressLRS receiver, or for better WiFi performance, you can also use an ESP32 dev board, etc.
An MFD Crossbow (mini or full size) tracker
ELRS LUA script installed on your handset
A GPS-equipped craft with an ELRS receiver
"},{"location":"software/mfd-crossbow/#what-will-i-need-to-do-to-set-this-up","title":"What will I need to do to set this up?","text":"
To work through this guide, you will need to:
Update the firmware on your TX and TX-Backpack (depending on your current version)
Flash an ELRS receiver, or an ESP-based dev board as a Backpack receiver
Wire the receiver to the Crossbow
Setup the Crossbow for MAVLink protocol
Setup ELRS via LUA for telemetry forwarding on the Backpack
Ensure both your transmitter module, and the embedded Backpack are up to date with the latest release versions:
For the main ELRS firmware, follow the Firmware Update Guide for detailed instructions.
For the TX-Backpack, follow the Transmitter Backpack Firmware Guide for detailed instructions.
The minimum versions to use this feature are:
Main TX firmware: 3.5.0
TX Backpack firmware: 1.5.0
"},{"location":"software/mfd-crossbow/#select-a-backpack-receiver","title":"Select a Backpack Receiver","text":"
Select a Backpack receiver to use on the Crossbow. Most ExpressLRS receivers will work for this (STM32 receiver cannot be used as they don't have WiFi).
When selecting a receiver for this integration, the quality of the WiFi antenna (not to be confused with the ELRS antenna) on the receiver is important if you want decent range (more than 5 meters). Some ELRS receivers have a chip antenna for the onboard WiFi, which helps.
The best receiver for WiFi range is an ESP32 dev board:
ESP32 Dev Board
These can be found on Amazon for cheap, and have much better WiFi range than a standard ELRS receiver.
Once you have chosen a receiver to use, you need to determine the MCU type that it uses:
ESP8285 / ESP8266
ESP32
ESP32C3
ESP32S3
If you are using an ELRS receiver, you can look this up (for supported hardware) in the targets.json file. Click the targets.json link, and then search for your receiver (e.g. RadioMaster RP1) and note the platform that it uses:
Platform for the RadioMaster RP1
If you are using an ESP32 dev board, check the listing to see if it's an ESP32, an ESP32C3 or an ESP32S3.
"},{"location":"software/mfd-crossbow/#flash-the-backpack-receiver","title":"Flash the Backpack Receiver","text":"
Open the ExpressLRS Configurator and select Backpack in the left hand menu bar.
Select the 1.5.0 or newer Backpack Release version from the Releases dropdown.
Select MFD Crossbow Antenna Tracker Backpack under Device category
Select Generic ESPxxxx Receiver (where \"ESPxxxx\" is the platform for your receiver type) in the Device dropdown
Enter your Binding Phrase and your Home WiFi SSID and Password (Optional).
Choose your Flashing Method based on your hardware (choose from the options below):
"},{"location":"software/mfd-crossbow/#flashing-via-usbuart","title":"Flashing via USB/UART","text":"
Use this method if you have an FTDI (USB to serial converter), or if you are using an ESP32 dev board connected to the PC via a USB cable.
Ensure you have the drivers installed for your FTDI, and the device shows up as a COM port in Device Manager when plugged in.
Connect the receiver to the FTDI:
FTDI to receiver wiring
Hold down the BOOT button on the receiver / dev board, or temporarily bridge the BOOT pads if the receive uses pads instead (e.g. with tweezers) as you plug the USB / FTDI into the PC.
In the Configurator, select the UART option under Flashing Method.
Ensure you have completed the steps in the \"Flash the Backpack Receiver\" section above, then click Flash on the ExpressLRS Configurator.
Wait for the process to complete and you should see the green Success notification.
"},{"location":"software/mfd-crossbow/#flashing-via-wifi","title":"Flashing via WiFi","text":"
If you are flashing an ExpressLRS receiver, you may chose to use WiFi to flash the Backpack firmware.
Power on the receiver (with no transmitter active), and wait for it to enter WiFi mode (fast flashing LED).
If you are NOT using Home WiFi, connect to the ExpressLRS RX WiFi access point (password is expresslrs) and navigate your browser to http://10.0.0.1/?force=true NOTE THE EXTRA ?force=true ON THE url
If you ARE using Home WiFi, navigate your browser to http://elrs_rx.local/?force=true NOTE THE EXTRA ?force=true ON THE url
In the Configurator, select the WIFI option under Flashing Method.
Ensure you have completed the steps in the \"Flash the Backpack Receiver\" section above, then click Build on the ExpressLRS Configurator.
Grab the built firmware.bin.gz (do NOT extract it) and drag-and-drop it into the File Upload section of the webpage. If you are using an ESP32 based device, the filename may be firmware.bin. Drag-and-drop it into the File Upload section of the webpage.
Click Update. Wait a bit (~10s) for the \"Update Success! Rebooting...\". The AP should automatically disappear and disconnect.
WiFi ESP"},{"location":"software/mfd-crossbow/#step-2-wire-the-receiver-to-the-crossbow","title":"Step 2: Wire the receiver to the Crossbow","text":"
The receiver communicates via UART with the Crossbow, using the MAVLink protocol at 115200 baud. We need to wire the tx pad on the receiver to one of the rx pins on the Crossbow:
Crossbow Wiring Diagram
The Crossbow mini can communicate via MAVLink on RX3 or RX1, depending on which port you want to use:
Crossbow Ports
If you use the L-Port on the mini, you also get a +5V and GND source for the receiver:
Example Crossbow RX Wiring"},{"location":"software/mfd-crossbow/#step-3-configure-the-crossbow-for-mavlink","title":"Step 3: Configure the Crossbow for MAVLink","text":"
Refer to the respective user manual for your model of Crossbow in order to change the UART to MAVLink protocol, at a baud rate of 115200.
For example, on the Crossbow mini, assuming you are using the L-Port:
Long press the left button to enter the menu
Short press the left button until you get to L-Baudrate and short press the right button to enter
Short press the left button until 115200 is highlighted, and short press the right button to confirm
Short press the left button until Exit is highlighted, and short press the right button to exit
Short press the left button until you get to Protocol and short press the right button to enter
Short press the left button until L:<protocol> is highlighted, and short press the right button until it reads L:MAVLink
Short press the left button until Exit is highlighted, and short press the right button to exit. Do the same again to exit the main menu.
"},{"location":"software/mfd-crossbow/#step-4-enable-backpack-telemetry-in-elrs-lua-script","title":"Step 4: Enable Backpack Telemetry in ELRS LUA Script","text":"
Access the LUA Script:
Power on your transmitter and navigate to the System menu.
Execute the ELRS LUA script.
Navigate to the Backpack Section:
Scroll to find the \"Backpack\" section within the LUA script.
Select the \"Telemetry\" option.
Enable Backpack Telemetry:
Set the \"Telemetry\" option to ESPNOW.
Exit the script.
Your TX module is now configured to broadcast telemetry to the Backpack receiver.
NOTE: Backpack telemetry is transmitted on the 2.4G WiFi band, via ESPNOW (this should have a very limited impact on any LoRa signals, as it is modulated via OFDM like a normal WiFi hotspot). Every telemetry message that your transmitter receives from the craft will be re-transmitted via ESPNOW. You may want to disable Backpack Telemetry to reduce your footprint on the RF noise floor when you aren't using it, especially if you are at something like a race day, where there is often contention on the RF spectrum. Disabling Backpack Telemetry will cause the Crossbow integration to stop working.
To disable Backpack Telemetry (only do this if you are NOT using the Crossbow integration):
Execute the ELRS LUA script.
Scroll to find the Backpack section within the LUA script.
Select the \"Telemetry\" option.
Set the \"Telemetry\" option to Off.
Exit the script.
"},{"location":"software/mfd-crossbow/#step-5-set-the-telemetry-ratio","title":"Step 5: Set the Telemetry Ratio","text":"
The Crossbow requires frequent GPS coordinate updates in order to track the craft, and to maintain the link.
The recommendation is to use a telemetry ratio of:
1:2 or 1:4 if you are using a low packet rate such as 50Hz or 100Hz
1:2 to 1:8 if you are using a higher packet rate such as 250Hz or above
Once configured, power up your GPS-equipped craft and establish the link between your ELRS Transmitter and Receiver. Ensure that GPS telemetry is being received on your handset (go to the Model menu in EdgeTX, and inspect the Telemetry page to make sure you are getting GPS coordinates).
The Crossbow status screen should now be showing DLink:100% and GPS: should reflect the number of sats acquired. Once GPS: is greater than 6, press the right button to set home, as per the user manual.
No Telemetry Data / DLink:0%: Ensure the \"Telemetry\" option is set to ESPNOW in the Backpack section of the LUA script and that the firmware is up to date. Also check that your Telemetry Ratio is set to a value that is able to provide frequent telemetry packets. As a rule of thumb, a ratio somewhere between 1:2 to about 1:16 (depending on your packet rate) will suffice. As a troubleshooting step, try 1:2 to guarantee that the tracker is getting regular updates. For more info, see Packet Rate and Telemetry Ratio and Telemetry
Binding Issues: Verify that the bind phrase is correctly set and matches between the Backpack on your transmitter and the Backpack receiver. This should also match the bind phrase that you use for regular ELRS receivers.
Interference / Poor Range: The Backpack Telemetry feature uses a point to point WiFi-based link to forward telemetry. The Backpack receiver should be within 10m of the ELRS transmitter (ideally 5m or less if using an ELRS receiver) for good WiFi signal. Some ELRS transmitters and receivers have better Backpack WiFi antennas than others, so your mileage may vary depending on your hardware. If you are experiencing drops in the link between ELRS and the tracker, try moving the two closer, or consider using an ESP32 dev board as the receiver.
ExpressLRS stores separate configurations for each CRSF Receiver number configured in OpenTX/EdgeTX. This can be used with or without model matching - for example, a single drone being used for long-range and freestyle can have its RF params switched quickly by changing the model on the radio. The value is shown highlighted below on a TX16s.
The parameters stored per-Receiver number are:
Setting Description Packet Rate The RC update frequency (500Hz, 250Hz, etc) Telem Ratio Telemetry ratio (Off, 1:128, 1:64, etc) Switch Mode Method for sending switches to the receiver Model Match Enable the model match feature (see below) Max Power Transmitter output power level Dynamic Power Enable Dynamic Power switching
All other configuration parameters are global across all Receiver numbers. Note: not \"per receiver\" but \"per Receiver number\". For details about the configurable parameters, see Lua Configuration.
ExpressLRS uses a binding phrase, which means the transmitter will connect to any receiver built with that binding phrase. Model Match is a feature which prevents a full connection if the Model Match number does not match. In this mode, the receiver will connect to the handset, but no data will be sent from the receiver to the flight controller. This allows a user to force that the model selected in OpenTX only connects to a specific receiver, for example preventing using a quad OpenTX model definition with a fixed wing model.
The terms Receiver number (set in OpenTX/EdgeTX) and Model Match number (set in the receiver) are used interchangeably here-- they are the same.
If the Model Match option is Off, then only receivers with no Model Match number (255) can be connected. If the Model Match option is On, then the Receiver number configured in the external module configuration (as shown in the image above) must match the Model Match number stored on the receiver module for the receiver and transmitter to fully connect.
The implementation follows this set of rules for handling half connections / full connections
TX ModelMatch TX Receiver ID RX Model ID Result Off Any Off Connects / Communicates as usual Off Any A Connects but does not communicate to FC On Any Off Connects but does not communicate to FC On A A Connects / Communicates as usual On B A Connects but does not communicate to FC"},{"location":"software/model-config-match/#setting-model-match-number","title":"Setting Model Match number","text":"
Set the Receiver number to be used in the OpenTX Model Setup -> External Module -> Receiver
Be sure the receiver to be assigned is connected and has a high LQ
Use the ExpressLRS Lua to set the Model Match option to \"On\"
The receiver now has its Model Match number set to match the Receiver number and will only fully connect when using this Receiver number.
Alternatively
For WiFi-enabled RX modules, use the WebUI to set the Model Match directly. \"Model Match\" must still be set to \"On\" in the Lua config.
"},{"location":"software/model-config-match/#clearing-model-match-number","title":"Clearing Model Match number","text":"
Be sure the receiver to be assigned is connected and has a high LQ
Use the ExpressLRS Lua to set the Model Match option to \"Off\"
The receiver now has its Model Match number cleared and will connect with any configuration profile which has Model Match set to \"Off\"
Alternatively
For WiFi-enabled RX modules, use the WebUI to set the Model Match to 255 to disable matching. \"Model Match\" must still be set to \"Off\" in the Lua config.
This page contains old user_defines.txt that have been removed or superseded by new defines.
New items should be added to the top of the list so the last entry here is the oldest. The order of each entry should be [code]definename[/code] followed by the original text of the documentation, ending with a separate paragraph \"REMOVED [version] [replacement or reason for removal]\".
Enable antenna-switching diversity for RX that supports it. Safe to leave it on for hardware that doesn't have diversity except for DIY builds which did not populate the RF switch.
REMOVED 3.0. Diversity is now a receiver option, changed via Lua for devices that support it in hardware.
DYNPOWER_THRESH_UP=15\nDYNPOWER_THRESH_DN=21\n
Change the RSSI thresholds used by the Dynamic Power algorithm. If the RSSI moving average is below DYNPOWER_THRESH_UP dBm from the sensitivity limit, the algorithm will increase the power output by one step. Similarly, if the RSSI is above DYNPOWER_THRESH_DN from the sensitivity limit, the power will be decreased by one step.
REMOVED 3.0. The dynamic power algorithm uses SNR which is defined per-rate so the thresholds are more complicated than 2 defines.
NO_SYNC_ON_ARM\n
no sync on arm doesn't transmit sync packets while armed. This is useful for racing as there is less time & packets wasted \ud83d\uddd1\ufe0f on sending sync packets (one packet every 5 seconds if connected). HOWEVER if you are doing serious long range \u26f0\ufe0f, keep this disabled because, in the case of a sustained failsafe, the link can not be regained while armed.
AUX1 is the channel ExpressLRS uses to detect \"ARMED\", and this feature assumes that a low value of the arm switch is disarmed, and a high value is armed. OpenTX can invert your switch if you prefer it to be mechanically inverted. It is best not to enable no sync on the arm when you are first setting up ExpressLRS as it can be a source of confusion.
REMOVED 3.0. Replaced with \"Race\" telemetry mode, which also disables sending SYNC on arm.
These features enable lower latency \ud83c\udfc3\u200d\u2642\ufe0f and offset from the OpenTX radio to the TX. The first is lower latency which should be kept enabled. The second is more experimental and can lower the offset from the radio by tuning it as close as possible to 0, but is experimental (even in 1.0) and is best left disabled.
Both require OpenTX 2.3.12 or above. To install it, you will have to use OpenTX companion application.
Deviation radio users such as those with the T8SG v2/v3 should disable this feature.
You can also use EdgeTX.
REMOVED After 2.2.0. Sync packets were always sent regardless of if this was enabled, but the sync offset would just be wrong if it wasn't defined.
USE_ESP8266_BACKPACK\n
This enables communication with the ESP Backpack for over-the-air updates (env:FrSky_TX_R9M_via_WiFi) \ud83d\udda5\ufe0f and debugging via WebSocket \ud83d\udd0d. Uncommented by default, does not need to be changed.
REMOVED 2.0 development. Replaced with USE_TX_BACKPACK.
#-DHYBRID_SWITCHES_8\n
Changes how the AUX channels are sent over the air. The default option is Normal Mode with 8x 2-position low-latency switches. Enabling HYBRID_SWITCHES_8 changes this to 1x 2-pos + 6x 7-pos + 1x 16-pos, with only the 2-position being low-latency. In Normal Mode, all switches are sent with every packet, in Hybrid Mode, only AUX1 is sent with every packet and the rest are rotated through. Note: The switch mode MUST match between the RX and TX. A detailed explanation of the differences between the two options can be found in Switch Modes, but 1. If only two position switches are needed, and they must be updated as fast as possible: Normal Mode 2. Almost everyone: Hybrid Mode (Put ARM on AUX1)
REMOVED 2.0 development, all switch modes are available via Lua configuration. HYBRID_SWITCHES_8 is always enabled / available.
#-DENABLE_TELEMETRY\n
Enable advanced telemetry support. This option must be enabled on both TX and RX. The following telemetry messages are supported:
GPS
BATTERY_SENSOR
ATTITUDE
DEVICE_INFO
FLIGHT_MODE
MSP_RESP
Note
Increase the telemetry rate with the ExpressLRS Lua script. Increase the rate until the sensor lost warnings go away. It is normal to set it up to 1:16 with 200 Hz refresh rate.
Note
It must be enabled together with HYBRID_SWITCHES_8.
REMOVED 2.0 development, ENABLE_TELEMETRY is always enabled. Advanced Telemetry will only be sent if telemetry messages are received from the FC.
-DUSE_500HZ\n
This enables 500Hz mode for 2.4 GHz RXes and TXes. The drawback is that you have to give up 25Hz mode to add 500Hz mode. It requires OpenTX 2.3.12 or Newer, EdgeTX or a Radio firmware that has CRSFShot or Mixer Sync.
REMOVED 1.0.0-RC9, this option is now always enabled and in turn, 25Hz has been dropped/removed.
-DUSE_UART2\n
This enables integration with Jye's FENIX rx5805 pro-diversity module
REMOVED Somewhere in the 1.0.0-RC cycle. Feature removed.
-DFAST_SYNC\n
An option that adds faster initial syncing, by changing how long the receiver waits for a connection in each mode while not connected. This option is now the default, but disabling it can help to sync at lower packet rates (50Hz and below).
REMOVED 1.0.0-RC2 initial sync replaced with a full FHSS period wait
#-DR9M_UNLOCK_HIGHER_POWER \n
REMOVED 1.0.0-RC1 replaced with generic -DUNLOCK_HIGHER_POWER
#-DARM_CHANNEL=AUX1\n
If you are using a different channel than the default you need to edit \ud83d\udd25 (or you may not be able to gain sync safely - the default is listed in #DARM_CHANNEL as AUX1 which is Channel 5).
NB This feature assumes that a low value of the arm switch is disarmed, and a high value is armed. If you have the arm switch reversed it will not work correctly and the link won't be established. For this reason, it may be best not to enable no sync on the arm when you are first setting up ExpressLRS as it can be a source of confusion.
REMOVED 1.0.0-RC1 AUX1 is always the arm switch now, no longer configurable
#-DLOCK_ON_50HZ\n
LOCK_ON_50HZ locks the RX at 50Hz mode from the power-up. (Only recommended for long range, and partly redundant with the previous feature.) Merged in Pull 143
REMOVED 1.0.0-RC1 not sure why this was removed
-DAUTO_WIFI_ON_BOOT\n
REMOVED 1.0.0-RC1 replaced with -DAUTO_WIFI_ON_INTERVAL=X"},{"location":"software/open-ocd/","title":"OpenOCD for STLink","text":""},{"location":"software/open-ocd/#overview","title":"Overview","text":"
If you are using Linux then you can't use the ST-LINK utility from st.com. But fortunately, you can achieve the same effect with openocd on the Linux command line. This tutorial assumes you have an STLink v2.
Install openocd from your distro's repository. For Debian/Ubuntu use: sudo apt-get install openocd
Issue the full command:
a. For R9mm/Mini openocd -f interface/stlink-v2.cfg -f target/stm32f1x.cfg -c 'init; reset halt; stm32f1x unlock 0; reset run; shutdown'
b. For Ghost Atto/Zepto openocd -f interface/stlink-v2.cfg -f target/stm32f3x.cfg -c 'init; reset halt; stm32f3x unlock 0; flash protect 0 0 last off; reset halt; exit'
Restart your device so the disabled readout protection can take effect.
Now you can proceed with flashing your receiver. This may work on other devices or it might not.
"},{"location":"software/serial-protocols/","title":"Receiver Serial Protocols","text":""},{"location":"software/serial-protocols/#description","title":"Description","text":"
ExpressLRS receivers can communicate using a variety of serial protocols:
CRSF (Crossfire) + Inverted
SBUS + Inverted
SUMD
DJI RS2 Pro (Modified SBUS with pre-configured limits)
For R9MM and R9-Mini receivers SBUS, DJI RS2 Pro and CRSF Inverted protocols will be output on the SBUS (A2) pad. This is a hardware limitation of these receivers, as they do not have software controllable inverters.
On a serial based receiver or a PWM receiver with output pins configured for serial communication (as shown below), the protocol used for serial communication can be selected from the receiver WebUI in the Serial Protocol section.
Alternately, in the Lua script, enter > Other Devices and change the value of the Protocol field.
"},{"location":"software/serial-protocols/#pwm-receiver-serial-pin-selection","title":"PWM Receiver Serial Pin Selection","text":"
A PWM receiver may also be configured to communicate via serial on two of its pins. The exact pins will vary depending on the receiver. This can be configured in either the receiver WebUI or in the receiver Lua script.
Note
Not all pins support serial communication. Only the pins that support serial will have the option in the Mode dropdown in the WebUI or the Output Mode field in the Lua script.
Start the WebUI on the receiver and go to the Model tab. From there you will be able to select Serial TX or Serial RX on an output pin that supports serial communication.
Once you've configured the output pins to allow Serial communications you will be presented with a new section, Serial Protocol, underneath the PWM Output section. In this section you can choose the serial protocol you wish to use.
When connected to the receiver with the transmitter, enter the ExpressLRS Lua script and select > Other Devices then select > Output Mapping. In that screen select the output channel/pin that supports serial (either Serial TX or RX) and set that as the output mode. Setting one automatically enables the other matching pin for serial communications.
"},{"location":"software/serial-protocols/#second-serial-interface-on-esp32-non-pwm-and-pwm-receivers","title":"Second Serial Interface on ESP32 non-PWM and PWM receivers","text":"
Starting with firmware version 3.5 an additional serial interface (Serial2) can be assigned on any featured PWM Output or exposed pins of some non-PWM receivers to run any of the available serial protocols. Both serial interfaces can be be used simultaneously. This enables setups like running a CRSF wing stabilization unit and HoTT telemetry, Tramp or SmartAudio at the same time. Serial2 can also be used to simplify the wiring of e.g. an SBUS connection on receivers which have the first serial interface on separate connectors (e.g. RM receivers with JST connectors).
"},{"location":"software/serial-protocols/#assigning-serial2-tx-vs-serial2-rx-and-serial2-tx","title":"Assigning Serial2 TX vs Serial2 RX and Serial2 TX","text":"
Most of the supported serial protocols are uni-directional (only sending data) or are bi-directional (sending and receiving data) on one single wire (half duplex). For those protocols it is only necessary to assign a TX pin. True (full duplex) serial protocols require the assignment of RX and TX. The following list shows the configuration requirements for the supported protocols:
CRSF and MAVLINK: require Serial2 TX and additionally Serial2 RX if the device returns data (e.g. telemetry)
all others: require Serial2 TX only
"},{"location":"software/serial-protocols/#configuring-serial2-on-esp32-pwm-receivers","title":"Configuring Serial2 on ESP32 PWM receivers","text":"
Serial2 is best configured using the WebUI but can also be configured using the LUA script.
Open the WebUI as described in section \"How to get to the Web UI\" and scroll down to the PWM Output table. Any PWM Output with the blue Serial2 feature tag can be used to assign Serial2 TX or Serial2 RX.
Assign Serial2 TX. If necessary for the serial protocol you intend to run assign Serial2 RX also. In this example we want to run a protocol that only requires Serial2 TX (see above section). Choose Serial2 TX using the Mode drop down list on the desired PWM Output.
Scroll down a little further. A new line named Serial2 protocol is now available to choose the desired protocol.
Save the configuration using the SAVE button at the bottom of the page.
Restart the receiver and connect your serial device to the configured PWM Output.
"},{"location":"software/serial-protocols/#configuring-serial2-on-esp32-non-pwm-receivers","title":"Configuring Serial2 on ESP32 non-PWM receivers","text":"
Some non-PWM receivers like the RadioMaster RP4TD have spare pins exposed. The pins are configured for Serial2 by default.
Serial2 protocol selection is best configured using the WebUI but can also be configured using the LUA script.
Open the WebUI as described in section \"How to get to the Web UI\". Scroll down to line Serial2 protocol and choose the desired.
Save the configuration using the SAVE button at the bottom of the page.
Restart the receiver and connect your serial device to the configured PWM Output.
SUMD is the Graupner HoTT bus protocol used to transmit multiple channel data over a single serial line. It transports up to 16 full res channels at a rate of 100Hz and is mainly used to provide digital channel data to Flybarless Control Systems for helicopters and older Flight Controllers.
As already stated many times in this manual, ExpressLRS expects AUX1 (channel 5) to control the arm state. This may lead to a conflict using serial protocols like SUMD in conjunction with devices having fixed channel assignments. To circumvent the problem, SUMD implements a channel remapping by swapping channels 5 and 8 in its serial output:
This opens the possibility to assign a linear output channel order for channels 1 to 7 using an appropriate OpenTX/EdgeTX mixer setup.
Example: Microbeast flybarless controller without RPM governor. (Follow the Microbeast manual to setup the single line receiver mode.)
Microbeast expected channel order for SRXL/SUMD:
Required OpenTX/EdgeTX mixer setup to satisfy the Microbeast expected channel order:
"},{"location":"software/serial-protocols/#dji-rs2-pro-notes","title":"DJI RS2 Pro Notes","text":"
Here's a few things to be aware of when using this Receiver Mode:
The ELRS TX should be set to 100Hz Full, and Switch Mode to 8ch.
Channels 1, 2, 4 are Pan, Tilt, Roll
Aux1/CH5 is unused but should be set as an arm switch and left in the unarmed position (Low).
Aux2/CH6 should be a 3 way switch. From the switch center position to high/low, Rec start/stop or photos can be captured.
Aux3/CH7 should be a 3 way switch. Each of the 3 positions corresponds to Modes 1, 2 or 3.
Aux4/CH8 should be a 3 way switch. From the switch center position to high/low, Selfie or Recenter can be activated.
Rec, photos, recenter, and selfies are done by toggling the switch from the center position to high/low, and back to center in a quick 0.4s movement. With some ETX and mixer magic these functions can be improved and mapped to buttons etc.
ETX Outputs for the channels should be -100 to 100.
The HoTT Telemetry Serial Protocol allows to connect multiple Graupner HoTT Telemetry devices and intends to support the growing community of ELRS enthusiasts flying fixed wing or helicopter models by providing access to commercially available external telemetry devices without the use of flight controllers or DIY data hubs.
A typical use case for an electric fixed wing model could make use of a the electric Swiss knife SM Unisens-E to downlink flight battery data like voltage, current, consumed capacity and flight data like altitude, vertical velocity while an electric glider pilot could choose a YGE or Graupner Telemetry ESC to downlink flight battery data and a GPS/Vario to downlink flight data like GPS position, GPS speed, GPS (MSL) altitude together with barometric vertical velocity and barometric altitude.
HoTT Telemetry example setup - GPS/Vario and Voltage Module connected to a RadioMaster ER6 receiver:
Tested receivers:
ESP8285 platform
BetaFPV Nano RX 2.4 GHz
Happymodel EPW6
ESP32 platform
BetaFPV SuperD 900MHz
BetaFPV SuperP 14ch
RM ER6 (G and V variants too)
RM ER8 (G and V variants too)
Tested HoTT Telemetry devices (OEM and 3rd party):
Graupner 33600 GPS/Vario
Graupner 336001 Vario
Graupner 33631 Voltage Module
Graupner S3046 ESC +T50 (all other +T ESCs will work too)
SM GPSLogger 3
SM Unisens-E
SM Microvario (with TEK support)
YGE 35LVT. ESC (all other YGE Telemetry ESCs will work too)
VSpeak Vario Pro
X-Vario 2
HoTT Telemetry protocol is running on a multi-device capable single wire half duplex bus and requires a bus master to orchestrate the communication between the bus master and the connected devices. The ELRS receiver acts as the bus master communicating with the devices. The bus master receives selected HoTT Telemetry data to be forward to the ELRS CRSF protocol based over-the-air telemetry down link. The list of additional telemetry sensors provided shows the telemetry sensors available for EdgeTX depending on the HoTT Telemetry devices connected to the HoTT Telemetry bus:
Baro altitude (AGL)
Baro vertical speed (Vario)
GPS latitude
GPS longitude
GPS groundspeed
GPS heading
GPS altitude (MSL)
GPS number of satellites
GPS distance - possible if added as EdgeTX calculated sensor
GPS traveled distance - possible with LUA script
Batt voltage
Batt current
Batt capacity
Batt remaining
Requirements for using HoTT Telemetry:
The Serial port must be enabled. The Serial port is enabled by default on some receivers, e.g. RadioMaster ER6x/ER8x receivers. On other receivers the Serial port must be enabled using the WebUI or LUA script, see above section WebUI and Lua Script.
The Serial Protocol must be set to HoTT Telemetry, see above section WebUI and Lua Script.
On some receivers adapter cables are required.
Adapter cables
If an adapter cable is required depends on the platform the receiver is based on (ESP8285 or ESP32) and the way the serial port is designed on the specific receiver. RadioMaster uses a dedicated JST connector, on other receivers including the BetaFPV SuperP one or two of the PWM servo connectors are used.
ESP32 based receivers with Serial on dedicated PWM servo connectors like the BetaFPV SuperP 14ch:
No adapter cable is required. HoTT sensors can be directly connected to the PWM servo connector of any of the PWM pins configured for Serial2 TX (see above section).
ESP32 based receivers with Serial on the JST connector.
RadioMaster ER6x/ER8x need a JST to JR adapter. The JST pigtail RadioMaster included in the package can be used.
Caveat: the SuperP 14ch also has a JST connector but it can't be used as a Serial port, see the first ESP32 category.
Alternatively use any of the PWM pins configured for Serial2 (see above section 2).
ESP8285 based receivers:
Require a Schottky diode between Serial RX and Serial TX:
Example realization of an adapter cable with diode for ESP8285 non-PWM receivers like the BetaFPV Nano RX:
Example adapter cable setup for ESP8285 PWM receivers like the Happymodel EPW6:
SmartAudio/Tramp are loosely-defined protocols with edge cases, misinterpretations, and shoddy cloned implementations. ExpressLRS does not intend to support the vast majority of VTXes. SmartAudio was tested on a TBS Unify Pro32 HV, and Tramp was tested on an ImmersionRC Tramp HV, and both were tested with OpenVTX. It may work on other hardware, but it's not guaranteed and changes won't be made to accommodate broken implementations.
NOTE
ESP32 is the only supported platform for SmartAudio/Tramp at this time; ESP8266 RXes lack the necessary UART functionality to do this the right way, and are not supported.
ExpressLRS now has support for controlling an external video transmitter through SmartAudio/Tramp protocols. This is a powerful feature for PWM+FPV users who don't have a flight controller to manage their VTX settings.
Using serial VTX control requires at least a secondary UART TX pin assigned on your ESP32-based receiver, such as the RadioMaster RP4TD or the BetaFPV SuperP. You may need to assign a pin as Serial TX using the Lua script \"Other devices\" section, or using the RX Web UI if one is not already set up.
Ensure both your transmitter module and your receiver are up to date with the latest release versions; follow the Firmware Update Guide for detailed instructions.
The minimum version to use this feature is: - Receiver firmware: 3.5.0
"},{"location":"software/serialvtx/#setting-up-serial-vtx-control-via-lua","title":"Setting up serial VTX control (via Lua)","text":"
Open the ExpressLRS LUA script, scroll to the bottom and select Other Devices, then select your receiver.
Select Output Map, and assign an available Output Ch as Serial2 TX.
Select \"BACK\" to return to the main RX menu
Select Protocol2 and set it to SmartAudio or Tramp. This configures the RX to output SmartAudio or Tramp on the previously-selected pin.
Wire the selected Output Ch to your video transmitter's SmartAudio or Tramp pin
Select \"BACK\" to return to the main Lua menu
You can now use the ExpressLRS VTX Administrator function to control your VTX
ExpressLRS does not intend to support full VTX control, and especially not \"VTX Table\" functionality. To that end, here are some of the implementation decisions we've made in supporting SmartAudio/Tramp
Only bands A/B/E/F/R/L and channels 1-8 are supported. Custom frequencies, and non-5.8GHz VTXes don't work, and we're not interested in making them work.
These protocols support methods to confirm the settings on the VTX and update them on the controlling device (flight controller, RX). Our implementation is one-way only.
"},{"location":"software/serialvtx/#smartaudio-power-levels","title":"SmartAudio power levels","text":"
SmartAudio has 3 different ways to specify a power level: a raw DAC output value, a power output in dBm, or a \"power level\" starting from 0. We've chosen to implement the third option.
Here's the result on a Unify Pro32 HV
VTX Administrator \"Pwr Lvl\" Output power in dBm Output power in mW 1 14 25 2 23 200 3 27 500 4 29 800"},{"location":"software/serialvtx/#smartaudio-pit-mode","title":"SmartAudio pit mode","text":"
SmartAudio once again has 3 different ways to do something: pit mode is able to be specified as \"in-range\", \"out-range\", both at the same time, and a running or not flag (which is documented backwards of how it actually works). It's difficult to determine the \"right\" way of entering/exiting pitmode, and it never behaved how I expected it to in testing. YMMV.
"},{"location":"software/serialvtx/#tramp-power-levels","title":"Tramp power levels","text":"
ImmersionRC Tramp takes a completely different approach to power levels; just send the output power you want in mW. Unfortunately this doesn't match our \"Pwr Lvl\" approach from VTX Administrator, so we had to arbitrarily determine some output power levels. ImmersionRC hardware will only support the first 5; the last 3 are \"YMMV\" options for \"other\" video transmitters that support Tramp protocol.
VTX Administrator \"Pwr Lvl\" Output power in mW 1 10 2 25 3 200 4 400 5 600 6 1000 (not supported by ImmersionRC Tramp) 7 1600 (not supported by ImmersionRC Tramp) 8 3000 (not supported by ImmersionRC Tramp)"},{"location":"software/stlink-fix/","title":"PIO STLink Fix","text":""},{"location":"software/stlink-fix/#overview","title":"Overview","text":"
PlatformIO has an older version of STLink. It is unable to communicate with the STM32L MCUs on some RXs.
Paste files from \"st-link utility\" folder into \"stlink\" folder in your user PIO location C:\\Users\\username\\ .platformio\\packages\\tool-stm32duino
Put your arm switch on AUX1, and set it as ~1000 is disarmed, ~2000 is armed.
"},{"location":"software/switch-config/#summary-of-switch-configuration-modes","title":"Summary of Switch Configuration Modes","text":"
This table summarizes the switch configuration modes, available channel switch positions and resolutions, channel update rate, and packet rate as it applies to each channel or flight controller auxiliary channel (Aux). Below the table are descriptions for each option.
Channel Flight Controller Hybrid Wide Full Res 8ch Full Res 16ch Rate/2 Full Res 12ch Mixed 1 Sticks NormalRange NormalRange CRSF ExtLimits CRSF ExtLimitsH CRSF ExtLimits 2 Sticks NormalRange NormalRange CRSF ExtLimits CRSF ExtLimitsH CRSF ExtLimits 3 Sticks NormalRange NormalRange CRSF ExtLimits CRSF ExtLimitsH CRSF ExtLimits 4 Sticks NormalRange NormalRange CRSF ExtLimits CRSF ExtLimitsH CRSF ExtLimits 5 Aux 1 2-posArm 2-posArm 2-posArm CRSF ExtLimitsHArm 2-posArm 6 Aux 2 6-posRR 64/128-posRR CRSF ExtLimits CRSF ExtLimitsH CRSF ExtLimitsH 7 Aux 3 6-posRR 64/128-posRR CRSF ExtLimits CRSF ExtLimitsH CRSF ExtLimitsH 8 Aux 4 6-posRR 64/128-posRR CRSF ExtLimits CRSF ExtLimitsH CRSF ExtLimitsH 9 Aux 5 6-posRR 64/128-posRR CRSF ExtLimits CRSF ExtLimitsH CRSF ExtLimitsH 10 Aux 6 6-posRR 64/128-posRR - CRSF ExtLimitsH CRSF ExtLimitsH 11 Aux 7 6-posRR 64/128-posRR - CRSF ExtLimitsH CRSF ExtLimitsH 12 Aux 8 16-posRR 64/128-posRR - CRSF ExtLimitsH CRSF ExtLimitsH 13 Aux 9 - - - CRSF ExtLimitsH CRSF ExtLimitsH 14 Aux 10 - - - CRSF ExtLimitsH - 15 Aux 11 - - - CRSF ExtLimitsH - 16 Aux 12 - - - CRSF ExtLimitsH - PacketRates 50 thruF1000 50 thruF1000 100&333Only 100&333Only 100&333Only"},{"location":"software/switch-config/#switch-position-channel-resolution","title":"Switch Position / Channel Resolution","text":"Label Description Normal Range 10-bit or 1024 positions mapped to PWM 988us to 2012us (1 bit = 1us) CRSF Ext Limits 10-bit or 1024 positions mapped to PWM 885us to 2115us (1 bit = 1.23046875us) 64 / 128-pos The bit depth is dependent on the selected telemetry ratio. For a telemetry ratio of 1:2 and 1:4 these channels are 6-bit/64 pos. For all other ratios, these channels are 7-bit/128 pos. The 7-bit/128 positions is 12.5% the resolution of 10-bit, and 6-bit/64 positions is 6.25% the resolution of 10-bit. This may not be enough resolution for a head tracker but definitely enough for flight modes, flaps, gear, etc. 16-pos 4-bit which is good for flight modes, flaps, gear, etc. 6-pos 3-bit which is good for flight modes, flaps, gear, etc. 2-pos 1-bit for Arm, ~1000us is the disarmed state and ~2000us is the armed state (see the explanations below of why the armed state is very important for safety and performance)
WARNING
Put your arm switch on AUX1, and set it as ~1000 is disarmed, ~2000 is armed.
Note
If using a receiver with PWM outputs and you would like to use the PWM output 5 on the receiver for a servo, gear, etc. Go into the WiFi interface of the receiver and map any of the other channels to PWM Output 5. Please always still use AUX1 for the 2-pos Arm switch.
"},{"location":"software/switch-config/#channel-update-rate-versus-packet-rate","title":"Channel Update Rate versus Packet Rate","text":"Label Description Bolded This channel will be included in every packet at the selected packet rate (So a 150Hz Packet Rate = 150Hz Channel Update Rate) H Half Rate Half of the channels are included in each packet - Rate/2 (So a 100Hz Packet Rate cut in half = 50Hz Channel Update Rate) RR Round Robin These channels wait their turn to be sent in a packet (So a 150Hz Packet Rate sends a channel every 7th packet = 22Hz Channel Update Rate) 50 thruF1000 The Hybrid and Wide switch modes are only available on packet rates of 50Hz, 150Hz, 250Hz, 500Hz, D250Hz, D500Hz, F500Hz, and F1000Hz 100&333Only The Full Resolution switch modes (8ch, 16ch Rate/2, 12ch Mixed) are only available on packet rates of 100Hz Full and 333Hz Full"},{"location":"software/switch-config/#detailed-description-of-switch-configuration-modes","title":"Detailed Description of Switch Configuration Modes","text":"
Note
The switch configuration mode can only be changed when a receiver is not connected to the transmitter and when the transmitter is not armed. The mode is changed using the LUA Configuration in EdgeTX / OpenTX or using buttons, joystick, screen, etc. on the actual transmitter itself.
ExpressLRS has a few options for how switches are transmitted; Hybrid, Wide, Full Res 8ch, Full Res 16ch Rate/2, Full Res 12ch Mixed.
"},{"location":"software/switch-config/#hybrid-and-wide-switch-configuration-modes","title":"Hybrid and Wide Switch Configuration Modes","text":"
These two switch modes are only available when packet rates of 50Hz, 150Hz, 250Hz, 500Hz, D250Hz, D500Hz, F500Hz, and F1000Hz and selected.
The stick inputs (Chan 1-4) are sent with every packet at the normal range resolution of 10-bit or 1024 positions mapped to a PWM of 988us to 2012us (1 bit = 1us) which corresponds to -100% and 100% in EdgeTX / OpenTX.
The first switch (Chan 5 / AUX 1) is sent with every packet. PUT YOUR ARM ON THIS CHANNEL / AUX 1. It is used to enable safeguards and performance settings in the software and hardware. See the FAQ below. This switch is 1-bit / 2-position and is mapped to a PWM of ~1000us for disarmed and ~2000us for armed.
For the remaining 7 switches (Chan 6 thru 12 / AUX 2 thru AUX 8), only one switch is sent with each packet and is rotated on each packet (Round Robin).
In Hybrid mode, AUX2-AUX7 / Chan6-11 are 3-bit and can be used as either 2-position, 3-position, or 6-position switches or selector buttons. These are mapped to a PWM of 1000us to 2000us.
2-posSwitch 3-posSwitch 6-posSwitch Approx. ChannelInput PWM (us) ChannelOutput (us) ArduPilot Mode 1 1 1 988 1000 Mode1 (up position for 2-pos / 3-pos) 2 1192 1275 Mode2 3 1398 1425 Mode3 2 - 1500 1500 Mode4 (center position in 3-pos) 4 1602 1575 Mode4 5 1807 1725 Mode5 2 3 6 2012 2000 Mode6 (down position for 2-pos / 3-pos)
In Hybrid mode, AUX8 / Chan12 is 4-bit / 16-position and is mapped to the PWM table below. It takes 7 packets to send the complete set of switches before cycling back to AUX2. You can stack all your modes in here, Bardwell style, or get some low-res camera pan action (180 degrees / 16 = 11ish deg per position which isn't terrible). Clever math-heads might note that there's no \"center position\" (1500us) in a 16-position switch, so using AUX8 with a 3-position switch means it will come out as 1533 at the flight controller.
In Wide mode, AUX2-AUX8 / Chan6-12 are 6-bit / 64-position for telemetry ratios of 1:2 and 1:4. For all other telemetry ratios, these 7 switches are 7-bit / 128-position. It takes 8 packets to send the complete set of switches before cycling back to AUX2 (one more than Hybrid). Wide uses the 8th slot to transmit extra data to the receiver, including the current transmitter power. This is the only switch mode which can show the transmitter power TPwr on the flight controller's OSD. These behave more like traditional channels although with lower precision. You can tell you're operating in Wide mode when a switch in the middle position shows up as 1503 instead of 1500.
If using ArduPilot in Wide mode you will see that the channel outputs don't line up very well with the standard -100% (988us) to +100% (2012us) output range in EdgeTX / OpenTX when using a 6-position selector as input. Both the first two and the last two positions get binned into Mode 1 and Mode 6 respectively. To get the full 6 ArduPilot modes, go to the Outputs page on the OpenTX model setup and set the min / max for the channels to -75% / +75%.
These switch modes come in three flavors based on the number of output channels you would like and are only available on packet rates of 100Hz Full and 333Hz Full.
8ch - Channels 1 to 4 and Channels 6 to 9 are sent 10-bit, at the selected Packet Rate, along with Channel 5 (AUX1) in 1-bit (2-position) for Arming.
16ch Rate/2 - All the Channels are sent 10-bit but at half rate.
12ch Mixed - Channels 1 to 4 are sent 10-bit with Channel 5 (AUX1) in 1-bit (2-position) for Arming at the selected Packet Rate. Channels 6 to 13 are then sent at 10-bit but at half rate.
All of these 10-bit or 1024 positions are mapped to PWM 885us to 2115us (1 bit = 1.23046875us) in what is called \"CRSF Extended Limits\"
"},{"location":"software/switch-config/#faq","title":"FAQ","text":""},{"location":"software/switch-config/#why-do-you-keep-saying-put-arm-on-aux1","title":"Why do you keep saying \"put arm on AUX1\"?","text":"Why do you keep saying \"put arm on AUX1\"?
For safety and performance reasons.
SAFETY
AUX1 is sent with every packet going out, this is the most reliable way to be able to tell your model to disarm. If your arm switch is on another aux channel, it may be several packets before that switch is transmitted, and there's no guarantee that the RX will actually receive that packet. There's a non-trivial chance your model may not ever disarm if the link quality is low and it just so happens that the packet containing the arm switch is getting missed every time. Forcing the arm switch into every packet on AUX1 means that if any packet is received by ExpressLRS, it will disarm your model, not just a less than 1-in-7 chance.
It also protects against unintentional disarms caused by a corrupt packet changing the value of the arm switch to disarmed. Betaflight requires that 4x \"disarm\" commands are received before disarming to guard against this possibility. With arm on AUX1, a single corrupt packet can not disarm your model. With arm on AUX2-8, the one corrupt switch value will be sent 6 times before the value is refreshed, but the flight controller would have already disarmed by that point.
Your transmitter and receiver also act differently when \u201carmed\u201d and when \u201cdisarmed\u201d. When disarmed, the transmitter and receiver are free to adjust their communication in order to make the LUA and other configuration operations more responsive. When \"disarmed\", everything will appear to be working appropriately but none of the safeguards will be in place and performance will not be what you expect.
When IsArmed is enabled, these safeguards are applied:
All \"Button\" inputs are disabled
All \"Joystick\" (5-way buttons) are disabled
Bump to Share is disabled
VTX Admin is disabled
Integrated VTX channel change is disabled
PERFORMANCE
When IsArmed is enabled, these performance features are activated:
Dynamic Power is fully enabled
Race telemetry mode turns telemetry off
Some thermal-based fan controls are enabled
Arming is an extremely important part of the performance of the control link. Please use Aux 1 / Chan 5 as indicated. Also keep in mind that for ExpressLRS, ~1000us is the disarmed state and ~2000us is the armed state.
"},{"location":"software/switch-config/#i-use-a-3-pos-switch-for-arm-this-software-is-unusable","title":"I use a 3-pos switch for arm, this software is unusable?","text":"I use a 3-pos switch for arm, this software is unusable?
Good news, you can still use a 3-position switch to arm! However, you will need to adjust the model input / mixer settings for AUX1 in EdgeTX / OpenTX to remap the switch to be 2-position / on-off switch. If your 3-position arm switch had a second function as well, such as enabling Blackbox, just use one of the other channels to send the same switch on a second channel using the model input / mixer settings EdgeTX / OpenTX.
"},{"location":"software/switch-config/#what-about-normal-one-bit-switch-mode","title":"What about \"Normal\" one bit switch mode?","text":"What about \"Normal\" one bit switch mode?
In version 1.0 of ExpressLRS, there was also a switch mode called \"Normal\" where there were eight 1-position switches sent in every packet. This mode was removed in version 2.0 due to its unpopularity and the flash space was used for other features. Please use Hybrid or Wide modes and all of the high performance packet rates.
"},{"location":"software/switch-config/#every-time-i-change-switch-mode-in-lua-it-changes-back-is-my-transmitter-broken","title":"Every time I change switch mode in Lua, it changes back! Is my transmitter broken?","text":"Every time I change switch mode in Lua, it changes back! Is my transmitter broken?
If the Lua loads then you know its communicating with your transmitter. However, the switch mode can only be changed when a receiver is not connected and makes it appear as if the changes are not saving. This is done to ensure consistency between the RX and TX interpretation of the switch data being actively transmitted. This is a safeguard. Power down your receiver, wait for the \"Telemetry Lost\" callout, and the switch mode change will stick / save. The receiver will talk to the transmitted when it is powered up to handshake on the new settings.
"},{"location":"software/teamracing/","title":"Team Racing","text":""},{"location":"software/teamracing/#what-is-team-racing","title":"What is Team Racing?","text":"
Team Racing is a receiver feature that allows multiple models to be connected to one transmitter at the same time. Each model is assigned to a different switch position and will select that model to control. Any non-selected model is failsafed and will have its telemetry disabled.
The purpose of the receiver selection is to allow a downed model (which is physically unreachable mid-race) to be deactivated and allow the pilot to take control of another model using the same controller. In a default setup, if the pilot plugged in a new model and armed, both models will respond and arm which is incredibly undesirable. This would be used in a Team Race event such as MultiGP Mayhem.
0 or 1 active transmitters with a distinct binding phrase. \"One pilot operating their transmitter\"
Multiple receivers bound to that transmitter's binding phrase, all powered at the same time.
Pilot has the ability to direct which receiver is currently \"active\" including:
Sending channels data and LinkStats information to flight controller
Transmitting telemetry to the TX
Updating servo positions
"},{"location":"software/teamracing/#team-racing-does-not","title":"Team Racing does NOT","text":"
Allow multiple pilots (more than 1 active transmitter) to control a model. There is only one binding phrase and ExpressLRS rule is one active transmitter per binding phrase.
Support different packet rates / switch modes per model. All models use the same packet parameters.
Encourage pilots to have multiple active models flying at once, e.g. launching a model and putting it into autopilot, then switching to a second model to chase it by effectively failsafing the first via TeamRace switch.
Two configuration parameters are present in the Receiver Lua (ExpressLRS Lua -> Other Devices -> (select receiver item) -> Team Race). See ExpressLRS Lua script
Channel - The channel that is checked to determine the currently selected model.
Position - Which position of the TeamRace Channel activates this model.
No flight controller setup is needed. The receiver selection is completely transparent to the flight controller-- the channels will stop updating and it should failsafe as normal. NOTE Servos will wait 1s before switching to failsafe positions, which may be longer than normal (LQ dropping to 0 is usually faster than the 1s hard timeout).
Team Racing works in Hybrid and Wide switch mode as well as FullRes packet modes. When the receiver is in a TeamRace Mismatch mode, the LED will display the \"Model Mismatch\" blink pattern / color. The Lua will not display Model Mismatch, as telemetry will be disabled.
No VTX Admin / Control is performed when deselecting a model at this time due to the variety of ways a user might configure their VTX to go into Pit Mode: ExpressLRS VTX Admin Pit Switch, Betaflight PitMode mode switch, or USER1/USER2/pinio_box power cut. The user must still configure their method to disable the deselected VTX using the Team Race channel. For CRSF mode serial output, ExpressLRS guarantees at least one packet with the proper deselected channel position will be sent to the flight controller to handle this.
We recommend using VSCode's built-in Git client, as it requires the least 3rd party software \ud83e\udd16.
\ud83d\udd3d Download a copy of git (this is also needed for PlatformIO)
Install git, click yes to the default options (there are a LOT \ud83d\udcaf)
Important
Make sure you select this option during installation, it adds git to PATH which is necessary for VSCode cloning (the next step).
"},{"location":"software/toolchain-install/#cloning-the-repo","title":"Cloning the Repo","text":"
In VSCode open the command palette (using Cmd+Shift+P on MacOS or Ctrl+Shift+P on Windows)
Enter Git: Clone
Click that! \ud83d\udc48
Then, enter ExpressLRS Repo URL -> https://github.com/ExpressLRS/ExpressLRS.git \ud83d\udcbb
Choose a folder for ExpressLRS. \ud83d\udcc2
"},{"location":"software/toolchain-install/#selecting-the-latest-release","title":"Selecting the Latest Release","text":"
Before we can do any building, you need to select a release build of ELRS. For example, release 0.1.0-RC1. In Visual Studio Code select that tag. The location of the selector is shown below. \ud83d\uddb1\ufe0f
Click the selector, and then type in the name of the tag, in this case 0.1.0-RC1.
Once you had the time of your life setting up your toolchain \ud83e\uddf0 you are ready to Flash \u26a1 ExpressLRS to supported hardware.
"},{"location":"software/toolchain-install/#building-targets-using-platformio","title":"Building Targets using PlatformIO","text":"
\ud83d\udcc2 When you first launch Visual Studio Code, you should see the PlatformIO Home Page in a tab. Click the Open Project button. Navigate to the ExpressLRS repo directory. Navigate into the src folder (i.e. ./ExpressLRS/src/). Finally, press the Open button.
\u270f\ufe0f Edit the file ./src/user_defines.txt to define user specific variables. \ud83d\ude08 Please make sure you edit the file according to your needs!
\ud83d\udcca In the toolbar on the left, click the PlatformIO icon, which will show the list of tasks. Now, select Project Tasks, expand your desired target and select Build/Upload (depending on the method). You should see the result in the terminal.
\ud83d\ude43 If something went wrong - please check the Terminal, too. It will contain at least a hint of what the issue is. Please ask the community for further help\ud83e\uddd1\u200d\ud83d\udd27!
"},{"location":"software/toolchain-install/#updating-your-local-repo","title":"Updating your Local Repo","text":"
You've cloned the repository and are now wondering how to get new updates down the line. Then this document is meant for you! Here's a primer on how to keep your local copy of the repository up-to-date.
"},{"location":"software/toolchain-install/#method-1-the-clean-way-fetch-reset","title":"Method 1: The Clean Way - Fetch & Reset","text":"
Probably the easiest and least troublesome method, however, it'll overwrite any changes you've made to your local copy.
Open the terminal
You can either straight up open bash/cmd and navigate to your project folder or open an integrated terminal in VSCode:
Open the command palette (using Cmd+Shift+P on MacOS or Ctrl+Shift+P on Windows)
Enter: Create New Integrated Terminal
In the terminal, type: git fetch -pu && git reset --hard origin/master
This will get you the latest version and destroy any local changes you've made.
"},{"location":"software/toolchain-install/#method-2-the-lazy-way-commit-pull-merge","title":"Method 2: The lazy way - Commit, Pull & Merge","text":"
The advantage this method has over the first method is that all your changes to the user_defines.txt (or any other file, for that matter) will get merged with any new updates. There's a possibility that, if changes are too big, you could end up with a merge conflict. If that doesn't appeal to you, stick to the first method.
Commit your changes to your local repository
In VSCode open the command palette (using Cmd+Shift+P on MacOS or Ctrl+Shift+P on Windows)
Enter: Git: Commit
VSCode will tell you that there are unstaged changes and ask if you want to add them to the commit. Confirm this! This will just commit your changes to the user_defines.txt to your local repository. No worries, you're not overwriting anything on GitHub! :octocat:
Open the terminal, how-to is detailed in method 1
In the terminal, type: git pull -f
This will pull a new revision of the remote repository to your local repository and automatically merge it with your changes.
With more features being added consistently, ./src/user_defines.txt has gotten complicated \ud83e\udd37\u200d\u2642\ufe0f. So we will break it down! \ud83d\udd28
Info
This is the full list of currently supported User Defines and would help you should you intend to compile the firmware using the Toolchain or manual mode on the ExpressLRS Configurator.
This step is simple but important. Both the TX and RX NEED to have the same binding phrase or ExpressLRS WILL NOT WORK. Anyone using the same binding phrase as you will be able to control your model, so be unique. Set something memorable, and limit to alphanumeric phrases conforming to the Latin alphabet*.
Receivers flashed with firmware builds that do not have binding phrases enabled will support and require the traditional binding method. \ud83d\udcdc For ESP/ESP32 hardware, this value can also be changed through the WebUI.
This feature can, but should not be used as a model match feature (to lock a single specific transmitter to a single specific receiver). For that use, the Model Match option.
* This phrase gets md5 hashed and gets built into the binary you will be flashing.
This is a relatively simple one - enable whatever regulatory domain you are in. EU 868 \ud83c\uddea\ud83c\uddfa is compliant to the frequency but is not LBT compliant \ud83d\udc42 . Every other band is near compliant \ud83d\udc7f but may not be fully compliant for your regulatory domain.
TLM_REPORT_INTERVAL_MS=240LU\n
The TX module sends the LinkStats telemetry to the OpenTX frequently to let the handset know the connection is still active and reduce \"Telemetry Lost\" warnings. Reducing this value may reduce warnings caused by handset errors at higher baud rates. This only affects the connection from the TX module to the handset and does not do anything with the telemetry connection from the receiver. The default value is 240LU. When changing this value, suffix your milliseconds value with LU. For example, to specify a 100ms LinkStats update rate, you have to enter it like this: 100LU."},{"location":"software/user-defines/#output-power-limit","title":"Output Power Limit","text":"
UNLOCK_HIGHER_POWER \n
By default the max power of the hardware is limited to what it can safely output without extra cooling. Some hardware supports increasing the power by enabling the following option. Check the supported hardware page to see if this is available and what cooling modifications can be made. By enabling this, you are risking permanent damage to your hardware, sometimes even when you add extra cooling. For example, R9M modules will burn out without cooling."},{"location":"software/user-defines/#performance-options","title":"Performance Options","text":"
LOCK_ON_FIRST_CONNECTION\n
RF Mode Locking - When the RX is waiting for a connection, it cycles through all available rates waiting for a connection on each one. By default, ExpressLRS will go back to this mode after a disconnect (failsafe). If LOCK_ON_FIRST_CONNECTION is used, ELRS will not cycle after a disconnect, but instead, just stay at whatever rate the last connection was. This makes connection re-establishment quick, because the RX is always listening at the proper rate. This is generally what everyone wants, but there is utility in being able to switch the TX to the lowest rate to get more range to re-establish a link with a downed model, which can't happen if the RX is locked at the previous rate.
When cycling through the rates, the RX starts with the fastest packet rate and works down to the slowest, then repeats. It waits PACKET_INTERVAL * PACKS_PER_HOP * HOP_COUNT * 1.1 at each rate. Example: 4ms * 4 * 80 * 1.1 = 1.408s for 250Hz. The duration is extended 10x if a valid packet is received during that time. Even with LOCK_ON_FIRST_CONNECTION, the rate can be changed by changing the TX rate using ELRS.lua while connected, or by power cycling the RX.
FAN_MIN_RUNTIME=30\n
For TX devices with fans, FAN_MIN_RUNTIME keeps the fan running even after the power level has dropped below the configured Fan Threshold. This prevents the fan from turning on and off every few seconds if the power level is constantly changing. The default is 30 seconds if not defined, the value can be 0-254. There is always a short delay before the fan is activated, which can not be disabled. "},{"location":"software/user-defines/#compatibility-options","title":"Compatibility Options","text":"
UART_INVERTED\n
This only works with ESP32 based TXes (will not work with modules without built-in inversion/uninversion), but enables compatibility with radios that output inverted CRSF, such as the FrSky QX7, TBS Tango 2, RadioMaster TX16S. You want to keep this enabled in most cases. If your radio is T8SG V2 or you use Deviation firmware turn this setting off.
RCVR_INVERT_TX\n
This only works with ESP8266/ESP8285 based RXes. Invert the TX pin in the receiver code to allow an inverted RX pin on the flight controller to be used (usually labeled SBUS input or RXI). Inverted CRSF output. RX pin (telemetry) is unaffected. Update via_BetaflightPassthrough will not work, only via_Wifi. Note that just because this description includes the word SBUS, it doesn't mean the RX will output SBUS. It is still a CRSF protocol, only inverted, so CRSF should still be the receiver protocol selected in the flight controller software.
RCVR_UART_BAUD=420000\n
Use a custom baud rate on the receiver instead of the default 420000 baud. This is useful for a KISS v1 FC (which runs at 400000) or any other oddball baud, like 115200 for interfacing with an Arduino.
USE_R9MM_R9MINI_SBUS\n
This does not turn on SBUS protocol it simply changes the pin used for communication from those two side pins (A9 and A10) to use the pin labeled \"SBUS\" on the RX, which is inverted. This is useful for F4 FCs which only have an inverted receiver input UART RX. \ud83d\udd3c. This is only one way, so you lose the telemetry downlink to your radio as well as passthrough flashing. Enabling this turns on CRSF protocol output on the S.BUS \ud83d\ude8c pin on your R9MM/R9Mini. set serialrx_inverted = ON may also be needed within Betaflight \ud83d\udc1d for compatibility"},{"location":"software/user-defines/#network-options","title":"Network Options","text":"
AUTO_WIFI_ON_INTERVAL=30\n
\u26a0\ufe0f Must be defined if you plan to update your RX over WiFi without using a button on the RX \u26a0\ufe0f This will automatically turn the WiFi \ud83d\udcf6 on for any module that has an ESP8285 on it if no TX connection is established after N seconds from boot (the 30 is the time). This enables pushing firmware updates to the RX by connecting to its WiFi network and visiting http://10.0.0.1.
HOME_WIFI_SSID\nHOME_WIFI_PASSWORD\n
These options set Home Network Access for your WiFi-enabled hardware. With these sets, the devices will try connecting to your existing WiFi Network when you click on \"(WiFi) Update\" on the ExpressLRS Lua script (for some TX Modules) or automatically after your set interval time. Once the devices connect to your Home WiFi, the Update page can be accessed anywhere, from any device on the same network. The TX Module WiFi update page can be reached using the address http://elrs_tx.local, while the receivers' update page can be reached via http://elrs_rx.local.
WiFi mode will first try to connect to the network specified before falling back and creating a new WiFi network. The Home Network can also be modified from the website.
For TXes like the R9M, this sets if the TX only beeps one-time versus playing a startup song. Currently, it is set to play the startup song \ud83c\udfbc , but if you don't prefer it, uncomment this to turn it off. \u2716\ufe0f
For all your customization needs, use DMY_STARTUP_MELODY to define your own startup melody using the BLHeli32 or RTTTL syntax. For BLHeli32, the parameters music string and bpm are required, whereas semitone offset is optional to transpose the entire melody up or down by the defined amount of semitones.
For example, BLHeli32 melodies are available on Rox Wolf's youtube channel, some experimentation may be required though. To write your own melody, this (Sheet Music 101) and this (BLHeli Piano) are useful resources.
The build process also supports RTTTL-formatted ringtone strings. RTTTL melodies are delimited by colons : and start with a description versus the BLHeli style with pipes |. e.g. Mario:d=4,o=5,b=100:32p,16e6,16e6,16p,16e6,16p,16c6,16e6,16p,16g6,8p,16p,16g
DISABLE_STARTUP_BEEP\n
Disables beep sequence at startup of TX, but the TX will still beep when the CRSF connection is acquired
DISABLE_ALL_BEEPS\n
Disables all TX buzzer beeps at any state
USE_TX_BACKPACK\n
Enables code for talking to a connected ESP8266 backpack on the TX module, and associated Lua params. The device target should enable this automatically for devices that come with this built-in, but can be added to any device. The TX backpack allows wireless integration with VRX modules and planned telemetry mirroring over WiFi."},{"location":"software/user-defines/#debug-options","title":"Debug Options","text":"
DEBUG_LOG\n
Turn on debug messages, sent to the TX Backpack UART if available or else right out the main CRSF UART (such as on the receiver).
DEBUG_LOG_VERBOSE\n
Use to see verbose debug logging (spammy stuff)
DEBUG_RX_SCOREBOARD\n
Print a letter for each packet received or missed (receiver debugging)
DEBUG_CRSF_NO_OUTPUT\n
Don't send CRSF messages over the CRSF UART (receiver only). Used to only see logging and not logging mixed with CRSF.
DEBUG_RCVR_LINKSTATS\n
Prints a log line for every channels packet received at the RX ID,Antenna,RSSI,LQ,SNR,PWR,FHSS,TimingOffset. The ID is generated on the TX side and overwrites CH1-CH4 and increments once for every channel packet. Writes directly to Serial, and does not require DEBUG_LOG. Flash both TX & RX with this enabled to use it if the ID is required.
DEBUG_FREQ_CORRECTION\n
Enable reporting of RF FreqCorrection in receiver's SNR LinkStatistics, also decreases packet rate on Team2.4 for the additional time needed to include the packet header / enable FreqCorrection. The current FreqCorrection value will be reported in RSNR in the LinkStats scaled -127 to +127, where 127 is the maximum allowable deviation. 200kHz for Team2.4, 100kHz for Team900. Dynamic power must be OFF, or else it will adjust based on the FreqCorrection reported in SNR. Both the TX and RX must have this definition enabled otherwise they will not bind."},{"location":"software/user-defines/#obsolete-user_defines","title":"Obsolete user_defines","text":"
After performing CRC tests using the CRC-13 it was found that CRC includes parity checking so adding a separate parity check was wasteful. CRC checking has now been updated to 14-bit.
The following tests were performed using the new CRC-14 bit implementation with a polynomial of 0x372B, which gives a hamming distance of 6 in a 57-bit range. What this means is that it can detect up to 5 randomly flipped bits of a message that is 57 bits long.
Three stress tests have been performed on the 50-bit data with CRC-14. The tests create random data in 7 bytes (the first byte only has the lower 2 bits set) and then perform random bit flipping based on three styles.
Bear in mind that the CRC is not in the data and so is not subject to bit flipping.
"},{"location":"software/testing/crc-testing/#random-flipped-bits-within-14-bit-range","title":"Random flipped bits within 14-bit range","text":"
Anything over 14 is fairly useless as it will just flip bits back!
1 : 0 out of 1000000 false positives, 0.000000%\n2 : 0 out of 1000000 false positives, 0.000000%\n3 : 0 out of 1000000 false positives, 0.000000%\n4 : 0 out of 1000000 false positives, 0.000000%\n5 : 0 out of 1000000 false positives, 0.000000%\n6 : 0 out of 1000000 false positives, 0.000000%\n7 : 0 out of 1000000 false positives, 0.000000%\n8 : 0 out of 1000000 false positives, 0.000000%\n9 : 0 out of 1000000 false positives, 0.000000%\n10 : 0 out of 1000000 false positives, 0.000000%\n11 : 0 out of 1000000 false positives, 0.000000%\n12 : 0 out of 1000000 false positives, 0.000000%\n13 : 0 out of 1000000 false positives, 0.000000%\n14 : 0 out of 1000000 false positives, 0.000000%\n15 : 0 out of 1000000 false positives, 0.000000%\n16 : 0 out of 1000000 false positives, 0.000000%\n17 : 0 out of 1000000 false positives, 0.000000%\n18 : 0 out of 1000000 false positives, 0.000000%\n19 : 0 out of 1000000 false positives, 0.000000%\n20 : 0 out of 1000000 false positives, 0.000000%\n21 : 0 out of 1000000 false positives, 0.000000%\n22 : 0 out of 1000000 false positives, 0.000000%\n23 : 0 out of 1000000 false positives, 0.000000%\n24 : 0 out of 1000000 false positives, 0.000000%\n25 : 0 out of 1000000 false positives, 0.000000%\n26 : 0 out of 1000000 false positives, 0.000000%\n27 : 0 out of 1000000 false positives, 0.000000%\n28 : 0 out of 1000000 false positives, 0.000000%\n29 : 0 out of 1000000 false positives, 0.000000%\n30 : 0 out of 1000000 false positives, 0.000000%\n
"},{"location":"software/testing/crc-testing/#flipped-bits-in-a-single-sequence-at-the-random-start-position","title":"Flipped bits in a single sequence at the random start position","text":"
The number 1-30 is the number of consecutive bits that are flipped at a random starting position.
1 : 0 out of 1000000 false positives, 0.000000%\n2 : 0 out of 1000000 false positives, 0.000000%\n3 : 0 out of 1000000 false positives, 0.000000%\n4 : 0 out of 1000000 false positives, 0.000000%\n5 : 0 out of 1000000 false positives, 0.000000%\n6 : 0 out of 1000000 false positives, 0.000000%\n7 : 0 out of 1000000 false positives, 0.000000%\n8 : 0 out of 1000000 false positives, 0.000000%\n9 : 0 out of 1000000 false positives, 0.000000%\n10 : 0 out of 1000000 false positives, 0.000000%\n11 : 0 out of 1000000 false positives, 0.000000%\n12 : 0 out of 1000000 false positives, 0.000000%\n13 : 0 out of 1000000 false positives, 0.000000%\n14 : 0 out of 1000000 false positives, 0.000000%\n15 : 0 out of 1000000 false positives, 0.000000%\n16 : 0 out of 1000000 false positives, 0.000000%\n17 : 0 out of 1000000 false positives, 0.000000%\n18 : 0 out of 1000000 false positives, 0.000000%\n19 : 0 out of 1000000 false positives, 0.000000%\n20 : 0 out of 1000000 false positives, 0.000000%\n21 : 0 out of 1000000 false positives, 0.000000%\n22 : 0 out of 1000000 false positives, 0.000000%\n23 : 0 out of 1000000 false positives, 0.000000%\n24 : 0 out of 1000000 false positives, 0.000000%\n25 : 0 out of 1000000 false positives, 0.000000%\n26 : 0 out of 1000000 false positives, 0.000000%\n27 : 0 out of 1000000 false positives, 0.000000%\n28 : 0 out of 1000000 false positives, 0.000000%\n29 : 0 out of 1000000 false positives, 0.000000%\n30 : 0 out of 1000000 false positives, 0.000000%\n
Interestingly this is where the hamming distance shows any flipped bits less that HD6 is detected. Also this is where the built-in parity shows up as it detects the odd numbered bit flips.
1 : 0 out of 1000000 false positives, 0.000000%\n2 : 0 out of 1000000 false positives, 0.000000%\n3 : 0 out of 1000000 false positives, 0.000000%\n4 : 0 out of 1000000 false positives, 0.000000%\n5 : 0 out of 1000000 false positives, 0.000000%\n6 : 101 out of 1000000 false positives, 0.010100%\n7 : 0 out of 1000000 false positives, 0.000000%\n8 : 134 out of 1000000 false positives, 0.013400%\n9 : 0 out of 1000000 false positives, 0.000000%\n10 : 129 out of 1000000 false positives, 0.012900%\n11 : 0 out of 1000000 false positives, 0.000000%\n12 : 123 out of 1000000 false positives, 0.012300%\n13 : 0 out of 1000000 false positives, 0.000000%\n14 : 116 out of 1000000 false positives, 0.011600%\n15 : 0 out of 1000000 false positives, 0.000000%\n16 : 106 out of 1000000 false positives, 0.010600%\n17 : 0 out of 1000000 false positives, 0.000000%\n18 : 113 out of 1000000 false positives, 0.011300%\n19 : 0 out of 1000000 false positives, 0.000000%\n20 : 118 out of 1000000 false positives, 0.011800%\n21 : 0 out of 1000000 false positives, 0.000000%\n22 : 131 out of 1000000 false positives, 0.013100%\n23 : 0 out of 1000000 false positives, 0.000000%\n24 : 102 out of 1000000 false positives, 0.010200%\n25 : 0 out of 1000000 false positives, 0.000000%\n26 : 111 out of 1000000 false positives, 0.011100%\n27 : 0 out of 1000000 false positives, 0.000000%\n28 : 159 out of 1000000 false positives, 0.015900%\n29 : 0 out of 1000000 false positives, 0.000000%\n30 : 116 out of 1000000 false positives, 0.011600%\n
A 5hr OTA soak test was done at RSSI -108dBm (2.4GHz, 500Hz) and branch counting-flipped-bits@e3ddcc. RC data bytes were hard coded 0xAA and checked for CRC14 pass/fail, and the number of bits flipped counted.
The below table columns are the number of bits flipped, crc passed tally, crc failed tally. Where passed means a bad packet that passes the CRC check and would accepted by the RX. On the 0 row, Passed is good, Failed is where the data is good, but the CRC itself was changed by bit-flips.
The RX Scoreboard is a developer/troubleshooting feature that shows the outcome of every receiver packet cycle with a single character. Enable it with -DPRINT_RX_SCOREBOARD when compiling any RX environment and connect to the debug serial UART, usually the same as the CRSF output UART for most environments.
\u26a0\ufe0f For that reason, it should not be enabled during normal RC control operations since it will get mixed in with real CRSF data sent to the FC.
"},{"location":"software/testing/rx-scoreboard/#character-legend","title":"Character Legend","text":"Character Meaning Description R Receive \u2714\ufe0f A valid RC sticks or MSP packet was received which passes all validation T Telemetry \u2714\ufe0f Telemetry was successfully transmitted s SYNC \u2714\ufe0f A valid SYNC packet was received. Sync packets come about once every 4 seconds, or more frequently around a telemetry ratio or packet rate change _ Missing \u274c No packet was received at all yet one was expected \ud83d\udc7b . CRC \u274c A packet was received but failed CRC check"},{"location":"software/testing/rx-scoreboard/#name-origin","title":"Name Origin","text":"
The term scoreboard originated from an Apache (web server) feature that would display the state of every work as a single character in a text block. Thanks to them for the feature name and the dodecatillion web pages they've enabled serving.
In the windows search bar type env and select Edit the system environment variables
Click the Environment Variables... button and in the System variables section double-click Path and click New then paste C:\\Program Files (x86)\\mingw-w64\\i686-8.1.0-posix-dwarf-rt_v6-rev0\\mingw32\\bin. This path may be different on your system, but it is the path that mingw-w64 was installed previously and where g++.exe is located.
"},{"location":"software/testing/unit-testing/#running-the-tests","title":"Running the tests","text":"
In VSCode with the ExpressLRS project open, click on the New Terminal button in the status bar
Ensure the native platform is installed by entering pio platform install native in the terminal window.
Now you can enter pio test -e native to run the tests.
It is also possible to use the PlatformIO module and select Native/Advanced/Test in the target selection list.
Once you have Flashed ELRS onto your receivers they can be conveniently updated using the passthrough feature of Betaflight (and similar FC FW). This is a relatively simple process.
Open VS Code or the configurator and prepare to compile and upload.
Plug in your FC to your computer, but do NOT connect to the betaflight configurator.
Select env:YOUR_RX_via_Betaflight_Passthrough and hit upload.
Since 1.0.0, ESP receivers can be updated via passthrough without using the boot button as long as the firmware is not corrupted. If you're unable to get it to work, your firmware might be corrupted, in which case you'll need to temporarily turn off the telemetry feature in betaflight. If it still doesn't work, the bootloader might be messed up and the following steps should work.
Open VS Code or the configurator and prepare to compile and upload.
Plug in your FC to your computer, but do NOT connect to the betaflight configurator and do NOT power the RX. If your RX gets powered from USB, desolder the power wire so that you can manually power it up independently of the flight controller.
Hold the boot button of the RX or jump the boot jumper.
Select env:YOUR_RX_via_Betaflight_Passthrough and hit upload.
If it fails to flash (may display a success message but has errors show up above the final success output), check if it is flashing the correct COM. Sometimes an ethernet adapter on your motherboard will populate a COM port, which will confuse the script and it will attempt to flash to that COM.
The solution that could work would be manually editing the UARTUpload.py and BetaflightinitPassthrough.py files in src/python.
Another possible solution could be changing the COM to a higher number for the unnecessary COMs
Sometimes the boot jumper or button must be used while powering up the receiver.
Connect the autopilot to a PC using a USB cable and connect with a Ground Station (i.e. Mission Planner, QGC, etc).
Set SERIAL_PASSTIMO to a length of time (in seconds) that gives you enough time to connect with the sensor\u2019s configuration software. 30 to 60 seconds is a good choice
Set SERIAL_PASS2 to the number of the serial port connected to the sensor. I.e. \u201c2\u201d if the sensor is connected to Telem2/Serial2.
Be sure to set each port\u2019s baud rate appropriately using the SERIALx_BAUD parameter. The rates may be different for each port. ArduPilot will do the buffering.
Press the \u201cDisconnect\u201d button on the ground station but leave the USB cable from the PC to the autopilot connected.
Open the sensor\u2019s configuration software and connect to the autopilot\u2019s COM port. If all goes well the configuration software should work as it does when the PC is directly connected to the sensor
If the configuration fails to connect there are some things to try:
Some configuration software will not allow connecting to the autopilot\u2019s COM port by default but may have an option to display all available COM ports
If no serial messages are received from the PC the timeout will expire and SERIAL_PASS2 will revert to -1
You can also refer to the ArduPilot official docs for serial passthrough.
Build your firmware file, either via the ExpressLRS Configurator or PlatformIO. The ExpressLRS Configurator will open a folder for you where the correct firmware file was created and should be named like <target name>-<version>.bin (e.g. for the Happymodel ES24TX, the file will be HappyModel_ES24TX_2400_TX-2.0.0.bin). Meanwhile, PlatformIO should create the file within the \\src\\.pio\\build\\<target name>\\ folder.
Put your device in WiFi Updating mode. For TX modules, this is accomplished using the ExpressLRS Lua Script. Simply select WiFi Update from the script and it should start the Update Hotspot. For receivers, power the receiver and wait until AUTO_WIFI_ON_INTERVAL time has elapsed and the LED on the receiver is blinking fast.
Connect to the hotspot that the device has created. For TX modules, this hotspot should show up as ExpressLRS TX while for receivers, the hotspot will have a name such as ExpressLRS RX. They have the same password: expresslrs.
Updating on Phones (click/tap to expand)
In case your computer does not have WiFi capabilities, you can use a WiFi capable smartphone as well. Most phones will display a notification after a successful connection. This is because the phone does not recognize an internet connection. It is recommended to acknowledge this notification because the phone might disconnect again.
On iOS, the WiFi Update Page may open immediately. You can close it via the \"Cancel\" button on the top right and choose \"Use without internet\"
On Android, you may see a notification. Click the notification to open the WiFi Update Page and then hit the three dots on the top right and choose \"Use this network as is\".
Now continue with the guide below.
Note
The receivers, due to their respective sizes, don't have robust WiFi antennas and you will have to bring them closer to the device you're connecting from. The window that opens can easily be closed.
Navigate your browser to http://10.0.0.1/ and the WiFi Update Page should show up.
Using the Choose File button, navigate to the folder where the Firmware file is. You can also drag-and-drop the file from the folder window into the Choose File field.
Click the Update button adjacent to the Upload field, and the Update process should commence. A progress bar will be shown to show the status of the Update.
Once the Update process completes, a Popup should show the result of the Update. Normally, it will show the Success Message. Otherwise, some info will be shown for the reason it failed, like a wrong firmware file, old firmware or a wrong firmware file format.
DO NOT unplug/turn off the device yet. For TX Modules, wait for the Lua Script to return to its Main Screen, indicating that the TX Module has rebooted. For receivers, wait until the LED started blinking again, or you can even wait for it to activate WiFi Mode again for good measure.
Additionally, using this same Wifi Update page, you can also configure the receiver to connect to your local Wifi Network, in preparation for the other (better) methods.
"},{"location":"software/updating/wifi-updating/#method-2-home-network","title":"Method 2: Home Network","text":"
This method will only work if the device has been configured to connect to the local Wifi Network, either via the Join Network section in the Hotspot, or it's flashed with a firmware with the Home WiFi Network SSID and Password options set.
Build your firmware file, either via the ExpressLRS Configurator or PlatformIO. The ExpressLRS Configurator will open a folder for you where the correct firmware file was created and should be named like <target name>-<version>.bin (e.g. for the Happymodel ES24TX, the file will be HappyModel_ES24TX_2400_TX-2.0.0.bin). Meanwhile, PlatformIO should create the file within the \\src\\.pio\\build\\<target name>\\.
Put your device in WiFi Updating mode. For TX modules, this is accomplished using the ExpressLRS Lua Script. Simply select WiFi Update from the script and it should connect to your WiFi Network. For receivers, power the receiver and wait until AUTO_WIFI_ON_INTERVAL time has elapsed and the LED on the receiver is blinking fast.
Using your browser, navigate to the Wifi Update page. For TX Modules, this should be http://elrs_tx.local while for receivers, the URL should be http://elrs_rx.local.
Using the Choose File button, navigate to the folder where the Firmware file is. You can also drag-and-drop the file from the folder window into the Choose File field.
Click the Update button adjacent to the Upload field, and the Update process should commence. A progress bar will be shown to show the status of the Update.
Once the Update process completes, a Popup should show the result of the Update. Normally, it will show the Success Message. Otherwise, some info will be shown for the reason it failed, like a wrong firmware file, old firmware or a wrong firmware file format.
DO NOT unplug/turn off the device yet. For TX Modules, wait for the Lua Script to return to its Main Screen, indicating that the TX Module has rebooted. For receivers, wait until the LED started blinking again, or you can even wait for it to activate WiFi Mode again for good measure.
"},{"location":"software/updating/wifi-updating/#method-3-build-and-flash","title":"Method 3: Build and Flash","text":"
This method will only work if the device has been configured to connect to the local Wifi Network, either via the Join Network section in the Hotspot, or it's flashed with a firmware with the Home WiFi Network SSID and Password options set.
Put your device in WiFi Updating mode. For TX modules, this is accomplished using the ExpressLRS Lua Script. Simply select WiFi Update from the script and it should start the Update Hotspot. For receivers, power the receiver and wait until AUTO_WIFI_ON_INTERVAL time has elapsed and the LED on the receiver is blinking fast.
Set your User Defines or Firmware Options. Make sure you've selected the correct Target.
With PlatformIO, select Upload with the Wifi Target. With the ExpressLRS Configurator, click Build and Flash. Wait for the Compile to finish and you should see a section of the log like the image below:
DO NOT unplug/turn off the device yet. For TX Modules, wait for the Lua Script to return to its Main Screen, indicating that the TX Module has rebooted. For receivers, wait until the LED started blinking again, or you can even wait for it to activate WiFi Mode again for good measure.
"}]}
\ No newline at end of file
+{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"],"fields":{"title":{"boost":1000.0},"text":{"boost":1.0},"tags":{"boost":1000000.0}}},"docs":[{"location":"faq/","title":"FAQ","text":""},{"location":"faq/#why-expresslrs","title":"Why ExpressLRS?","text":"Why ExpressLRS?
ExpressLRS is a high-performance, open-source radio control protocol built from the ground up to be an extremely fast (Express), extremely sensitive (Long Range) System. ELRS uses Semtech SX12xx LoRa transceivers and a lightweight, highly optimized over-the-air (OTA) protocol to provide superior performance compared to legacy RC links. While ExpressLRS started with DIY and repurposed hardware, a large number of manufacturers are now producing high-quality, low-cost transmitters and receivers to make it easy for anyone to get started!
"},{"location":"faq/#how-does-expresslrs-compare-to-other-systems","title":"How does ExpressLRS compare to other systems?","text":"How does ExpressLRS compare to other systems?
ExpressLRS is capable of extremely high packet rates (up to 1000 Hz) and extreme sensitivity (ranges well over 100+ km have been achieved with 2.4 GHz hardware), making it extremely competitive with any commercially available system. And since ExpressLRS is open-source, it costs much less than other systems too!
"},{"location":"faq/#which-opentxedgetx-version-do-i-need-and-why-should-i-update","title":"Which OpenTX/EdgeTX version do I need and why should I update?","text":"Which OpenTX/EdgeTX version do I need and why should I update?
ExpressLRS requires OpenTX 2.3.12 or newer, as it depends on CRSFShot (a.k.a mixer sync) to work properly. However, as OpenTX is no longer being maintained, it is strongly recommended that you update to EdgeTX in order to take advantage of the latest performance improvements and bug fixes.
Click here to read more about radio firmware requirements and setup.
"},{"location":"faq/#how-do-i-flashupdate-my-receivermodule","title":"How do I flash/update my receiver/module?","text":"How do I flash/update my receiver/module?
See Getting Started for a Quick Setup guide and detailed instructions on flashing, features, hardware, and troubleshooting.
"},{"location":"faq/#will-x-receiver-work-with-y-tx-module-from-z-manufacturer","title":"Will x Receiver work with y TX Module from z Manufacturer?","text":"Will x Receiver work with y TX Module from z Manufacturer?
Any Receiver and TX Module from the same Band (e.g. 2.4 GHz or 900 MHz) will work together. For example, a 900 MHz receiver from BetaFPV will work with a 900 MHz TX module from HappyModel. Likewise, any 2.4 GHz receiver will work with any 2.4 GHz TX Modules, from any manufacturer (including DIY ones). This of course assumes the hardware is working properly, flashed with the same major ELRS version (e.g. 3.x), and is using the same binding phrase and configuration options (e.g. Regulatory Domain).
"},{"location":"faq/#whats-the-difference-between-the-different-24-ghz-receivers-pp-ep1rp1-ep2rp2-ep1-dual-rp3-rp4td-tcxo","title":"What's the difference between the different 2.4 GHz receivers (PP, EP1/RP1, EP2/RP2, EP1 Dual, RP3, RP4TD, TCXO)?","text":"What's the difference between the different 2.4 GHz receivers (PP, EP1/RP1, EP2/RP2, EP1 Dual, RP3, RP4TD, TCXO)?
Early ELRS receivers like the HappyModel PP used an STM32 MCU, while later designs EP1/EP2/etc use ESP MCUs. All offer firmware updates via UART or Betaflight Passthrough, but the ESP-based hardware also support firmware update and configuration over WiFi. The EP1/RP1 receivers use u.fl (external) antennas, while the EP2/RP2 receivers use on-board ceramic antennas. Receivers like the RP3 and R24D have two antennas for antenna diversity, while receivers like the EP1 Dual, RP4TD, and SuperD add a second parallel RF path to provide full receiver diversity.
See here for more about different antenna configurations.
"},{"location":"faq/#what-is-required-to-achieve-a-1000-hz-update-rate-on-24-ghz","title":"What is required to achieve a 1000 Hz update rate on 2.4 GHz?","text":"What is required to achieve a 1000 Hz packet rate on 2.4 GHz?
In order to achieve the fastest packet rate, your radio must be running a supported firmware, set to a minimum hardware baud rate of 921000, and be connected to a serial ELRS receiver (SPI receivers do not support the FLRC modes required). Also make absolutely sure ADC filter is disabled on your radio, and that you have applied the appropriate RC Link Preset in Betaflight.
You can use the ELRS lua to check your current packet rate and ensure the radio mixer sync is working properly. See Using the Lua Script for more details.
"},{"location":"faq/#how-many-channels-does-elrs-support","title":"How many channels does ELRS support?","text":"How many channels does ELRS support?
ELRS supports up to 16 channels*. Channels 1-4 are always sent at full-resolution (10-bit). The resolution and update rate of the remaining channels can be configured as follows, based on your requirements:
4x full-resolution (10-bit) channels for sticks (CH1-4) with either:
HYBRID Mode 1x 2-position channel, AUX1 (CH5; Must be used for Arming), 6x 2-position/3-position/6-position (AUX2-7) and 1x 16-position (AUX8), OR
WIDE Mode 1x 2-position channel, AUX1 (CH5; Must be used for Arming), 7x 64 or 128-position channels (AUX2-8). Available via the Lua Script since 2.0.
8x full-resolution (10-bit, ext-limits) with 1x 2-position channel, AUX1
16x full-resolution (10-bit, ext-limits, all half rate) with 1x 2-position channel, AUX1
12x full-resolution (10-bit, ext-limits) with 1x 2-position channel, AUX1, channels AUX2-9 run at half rate.
See Switch Modes for more details on switch modes and how they work.
"},{"location":"faq/#is-my-binding-phrase-a-secret","title":"Is my binding phrase a secret?","text":"Is my binding phrase a secret?
No, just like what channel your VTX is on is not a secret. If everyone kept their VTX channel a secret, the chances of you blasting someone out of the sky accidentally is high. The binding phrase is not used for security, it is used to prevent collisions. Specifically, the binding phrase is hashed and used to seed the random number generator that determines the frequency hopping pattern. Thus, each binding phrase results in a unique hopping pattern, minimizing the likelihood of collisions with other users. To provide the best chance of not interfering with other pilots and them not interfering with you, be sure you're not using the same dumb bind phrase as someone else. Express your style with a hilarious or saucy bind phrase.
"},{"location":"faq/#what-does-rqly-tqly-rssi-x2-snr-x2-mean","title":"What does RQLY, TQLY, RSSI x2, SNR x2 mean?","text":"What do RQLY, TQLY, RSSI x2, SNR x2 mean? Datapoint Description Range Info RQly Uplink - link quality (valid packets) 0 - 100 The number of successful packets out of the last 100 from TX. TX \u2192 RX 1RSS Uplink - received signal strength antenna 1 (RSSI) -128 - 0 First antenna RSSI dBm as reported by the RX. Values vary depending on mode, antenna quality, output power and distance. TX \u2192 RX 2RSS Uplink - received signal strength antenna 2 (RSSI) Second antenna RSSI dBm, for diversity receivers. TX \u2192 RX ANT RX active antenna 0 - 1 Active receiver antenna for diversity RX. RSNR Uplink - signal-to-noise ratio SNR reported by the RX. Value varies mostly by radio chip and gets lower with distance (once the agc hits its limit). TX \u2192 RX RFMD Uplink - packet rate 0 - 7 RF Mode Indexes TPWR Uplink - transmitting power 50mW reported as 0, as CRSF/OpenTX do not have this option TQly Downlink - link quality (valid packets) 0 - 100 An LQ indicator of telemetry packets received by TX. RX \u2192 TX TRSS Downlink - received signal strength (RSSI) RSSI dBm of telemetry packets received by TX. RX \u2192 TX TSNR Downlink - signal-to-noise ratio SNR reported by the TX for telemetry packets. RX \u2192 TX
See the Signal Health page for more info on interpreting link stats.
If you have other questions or concerns, or maybe you need further help that is not covered by this Guide, head over to our Discord Channel or Facebook Group!
ExpressLRS Discord ExpressLRS Facebook
"},{"location":"gsod/","title":"Google Season of Docs: Project Page","text":"
Review and Expand ExpressLRS User Documentation - expresslrs.org
"},{"location":"gsod/#about-the-organization","title":"About the organization","text":"
ExpressLRS (ELRS) is an open source project focusing on developing a radio control (RC) link. The link is primarily designed for first-person view (FPV) crafts (e.g Multicopters, Planes). ELRS aims to provide the best completely open source, high refresh radio control link, minimizing latency while maximizing range. A vast range of hardware in both 900 MHz and 2.4 GHz frequencies is available.
FPV is a community built on top of open source projects such as flight controller firmware Betaflight and RC handset firmware EdgeTX. ELRS fills a void for an open source and high performance RC link with an active development team of about 20 volunteers.
github.com/ExpressLRS was created nearly 4 years ago and in the past 12 months has experienced significant growth. Not only in code contributions, but also users and commercial manufacturers releasing ELRS compatible hardware.
"},{"location":"gsod/#about-the-project","title":"About the project","text":""},{"location":"gsod/#the-projects-problem","title":"The project\u2019s problem","text":"
During early ELRS development users were required to Do It Yourself (DIY) and build their own hardware. This tended to attract tech savvy users. However, in the past 12 months a number of commercial manufacturers have released ELRS compatible hardware. A much wider user group now exists of varying knowledge and initial setup of ELRS can be troublesome. More so for users who are also new to FPV.
A review of the existing user documentation by a technical writer, who has not previously been exposed to FPV, will bring a fresh pair of eyes to the project and help identify knowledge gaps.
Introduce the Technical Writer to the FPV community and teach them about flying a FPV multicopter\u2026 Lets try and have some fun first
Introduce the Technical Writer to our troubleshooting procedures.
This experience will help to identify any knowledge gaps in existing user ELRS documentation.
Devs and Advanced Users will provide information on general user queries from project volunteers and assist with documentation on recurring issues.
Review documentation used to assist manufacturers where English may not be their first language.
Hopefully assist in a major release (ELRS V3) and release notes.
We estimate that this work will take 4-6 months to complete.
Work that is out-of-scope of ELRS project: - In-depth PID Tuning of RC vehicles (Multicopter, Fixed - Wing, Boat, Rover). - Auxiliary function of RC vehicles (Mapping, Package Delivery, Pest Control Drone, Weaponry).
The ELRS project runs a Facebook group (8.4k users at time of application) and Discord Server (8.1k users at time of application) to help users troubleshoot setup issues. A milestone of this work will be to see the number of users posting setup issues reduced, and to have documentation for all common issues presented in a user first perspective and mindset.
The project would be a success if we could provide a link to users for 90% of new user questions.
ELRS Developers also volunteer a lot of time communicating with commercial manufacturers. For a majority of the manufacturers English is not their native language and current ELRS documentation may be confusing. A long term goal of the project is to minimize design errors in commercial hardware releases.
The documentation project will take approximately four to six months. It is expected the initial learning about FPV, Multicopters and ELRS may take 4 - 8 weeks. During which time the existing documentation can be used and reviewed. The remaining time will be used updating and expanding existing user, manufacturer, and developer documentation. ELRS has set its next major release goal before November to include release notes coordinated from this project.
Dates Action Items May - June Learning FPV and ELRS from scratch July - August Updating and expanding current User and Manufacturer documentation September - October ELRS V3 release notes and new feature documents November Project Completion"},{"location":"gsod/#proposed-budget","title":"Proposed Budget","text":"Budget Item Amount Running Total Notes Technical Writer 10,000 10,000 26 wk, 6 hrs/wk Technical Writer Hardware 2,000 12,000 FPV Hardware Volunteer stipends 500 14,500 2 ELRS Devs + 3 Adv User Total 14,500"},{"location":"gsod/#additional-information","title":"Additional information","text":"
The ELRS development team includes a range of expertise, from software professionals, academics, researchers, scientists, and university students. And we love nothing more than nerding out on all things FPV in our free time
ExpressLRS (ELRS) is an open source project focusing on developing a radio control (RC) link. The link is primarily designed for first-person view (FPV) crafts (e.g Multicopters, Planes). ELRS aims to provide the best, completely open source, high refresh radio control link, minimizing latency and maximizing range. A vast range of hardware in both 900 MHz and 2.4 GHz frequencies is available.
FPV is a community built on top of open source projects such as flight controller firmware Betaflight and RC handset firmware EdgeTX. ELRS fills a void for an open source and high performance RC link with an active development team of about 20 volunteers.
github.com/ExpressLRS was created nearly 4 years ago and in the past 12 months has experienced significant growth. Not only in code contributions, but also users and commercial manufacturers releasing ELRS compatible hardware.
Problem Statement / Proposal Abstract
During early ELRS development users were required to Do It Yourself (DIY) and build their own hardware. This tended to attract tech savvy users. However, in the past 12 months a number of commercial manufacturers have released ELRS compatible hardware. A much wider user group now exists of varying knowledge and initial setup of ELRS can be troublesome, especially for users who are new to FPV.
A review of the existing user documentation by a technical writer, who has not previously been exposed to FPV, will bring a fresh pair of eyes to the project and help identify knowledge gaps.
Project Description
Creating the proposal
The proposal idea was pretty easy for us, as we like to keep it simple. GSoD is fundamentally about improving documentation and also supporting technical writers, so we collectively decided we needed the support to hire a writer to review & write better documentation. The exploding ELRS users base meant we could not continue to provide 1 on 1 support to new users, unlike in the beginning of the project. The demand for more and better documentation is and will be ongoing during the ELRS growth period. However, the community appears to have reached a critical mass and the user base is great at supporting new users.
Budget
Of the initially deposited $5800:
$3000 was invoiced by our Technical Writer.
$1,849.42 of the proposed $2000 hardware budget has been spent.
$600 of the proposed $1000 volunteer stipend has been claimed.
The project was able to stay within the initial budget. Some ExpressLRS hardware manufacturers were even able to help with additional hardware and we thank (in alphabetical order) BETAFPV, Happymodel, and RadioMaster for their assistance in providing hundreds of dollars of free hardware to our technical writer.
Participants
The project had 5 volunteers that were either developers or long term users who were integral community members with their insight: deadbyte, maybenikhil, StonedDawg, YeOldePirate, and commanderguy3001.
We selected our writer Agha Saad after reviewing many resumes and cover letters. He offered an incredibly detailed set of goals and timeline & had previous season of docs experience with Arduino.
While no one dropped out of the project, there were personal issues that arose during the period that made it difficult for some volunteers to be available. This did significantly impact the project's timeline and delay hardware delivery.
Selecting a writer with a pre-existing interest in RC or similar hobby that aligned with the projects, and not focus solely on writing experience, may also have assisted with keeping to the timeline, due to hardware being more accessible to them.
Timeline
Our initial timeline has been heavily delayed through the delivery of hardware to our Writer and the eventual confiscation of said hardware. More details are provided below.
Results
A number of PRs were merged by the Technical Writer, which include major technical topics/issues such as Crystal Oscillator (XO) Frequency Error. However key beginner documents were difficult without hardware for our writer to have hands on experience with.
Metrics
A key metric for the success of the project was to address common user issues in the documentation. Another key metric is the project's user base & growth: at the time of the proposal the Facebook group had 8.4k and Discord 8.1k users. These groups have now grown to 12.4k and 13k respectively!
Therefore, we can say that we observed significant growth as a project & organization within the months of Google Season of Docs, but have no strong metrics correlating to use of documentation, as compared to the beginning of the project.
Analysis
A number of challenges were met during this project. With the final hurdle being the import of FPV hardware to the Technical Writer. In the end the hardware required for learning FPV, building, and flying were confiscated by the country's Ministry of Defense. This massively limited what could/can be completed during the project.
In good faith, the ExpressLRS devs can not call this project a success, as without hardware to write about the documentation that most affects new users did not see many significant improvements.
Summary
A number of PRs were merged by the Technical Writer, which is to be commended without access to hardware. If ELRS was to participate in GSoD again in the future there are a couple major conditions that require checking before hiring a writer:
Is FPV legal in their country?
Is the import of FPV/RC hardware legal in their country?
Hot tip for other organizations participating in GSoD and dealing with hardware (especially within the RC & FPV communities). Potentially look to hire someone in a country, or in close proximity to one of the participating developers or volunteers. Local expertise to help with delivery and hand up assistance will be invaluable, as well as an existing understanding of complex regulations surrounding the project.
"},{"location":"hardware/crystal-frequency-error/","title":"Crystal Oscillator (XO) Frequency Error","text":""},{"location":"hardware/crystal-frequency-error/#principle","title":"Principle","text":"
ExpressLRS TX and RX modules generate RF signals based on an external clock source, such as a crystal oscillator (XO). For example, an ExpressLRS 2.4GHz module has an SX1280/1281 RF transceiver chip with a 52 MHz XO. Theoretically, XO is desired to be 52 MHz exactly to generate an accurate 2.4GHz RF signal. However, a real-world XO has deviation for various reasons, such as manufacturing error and ambient temperature.
Real-world TX and RX modules deviate from the reference frequency, depending on the quality of XO used and circuit design. Despite that, if the frequency difference is within a certain threshold, they can communicate with each other (working pairs #1 and #2 in the picture). However, the last malfunctioning TX/RX pair will not communicate. In ELRS 2.4GHz@500Hz, the threshold is around 190 kHz.
This issue may affect both 2.4GHz and 900MHz units. To compensate for this, 900MHz modules do online frequency correction, which tunes the RX frequency automatically to the TX unit once connected. Even in this case, if the TX/RX frequency error is too large to make any connection, the frequency correction won't help. 2.4GHz modules are more vulnerable to frequency error because they can't do frequency correction due to some technical issues, which has risks of a connection drop due to frequency drift from the change of unit temperature.
"},{"location":"hardware/crystal-frequency-error/#recommendation-to-elrs-hardware-manufacturers","title":"Recommendation to ELRS hardware manufacturers","text":"
For SX1280/1281, USE 52 MHZ XO RATED 10 PPM TOLERANCE, 10 PF LOAD CAPACITANCE.
Do not add unnecessary extra load capacitors. If you add the extra caps for the frequency fine-tune, please VERIFY THE FREQUENCY ACCURACY WITH YOUR FINAL PRODUCT (for every new batch). The detailed procedure is described in this document.
TCXO (Temperature Compensated Crystal Oscillator) is a special kind of crystal oscillator, which equips a temperature-compensation circuit inside the package. Unfortunately, TCXO could not be a drop-in replacement for a normal XO, as it requires additional circuitry and needs a redesign of the module. Please refer to SX1280 reference design (part 15.2, Application Design with optional TCXO) to apply.
The advantage of TCXO over a normal XO is its frequency accuracy and stability. Usually, the frequency tolerance of a TCXO is <2 ppm, while the error of a good XO is limited to about 10 ppm. While a good XO is totally fine for ELRS operations (it can tolerate up to 50 ppm relative errors), a TCXO could be a silver bullet to eliminate the frequency offset issue entirely.
So far, we have established two ways of measuring the XO frequency error:
Absolute
Relative
"},{"location":"hardware/crystal-frequency-error/#measuring-absolute-xo-error-not-for-everyone","title":"Measuring absolute XO error (not for everyone)","text":"
Note
This procedure requires a special instrument, which is not expected of a regular ELRS user.
The current ELRS master branch (after PR #1785) equips a test-tone mode. After flashing a TX/RX unit with master branch, get into WiFi update mode, and access http://10.0.0.1/cw.html which should look like the figure below:
By clicking the START CONTINUOUS WAVE button, the unit will generate a continuous wave at 2440 MHz. By measuring the output frequency with a spectrum analyzer (e.g., HackRF SDR), you can determine how the XO deviates from the reference frequency (2440 MHz). Within 20 ppm (=~50 kHz) absolute error over the entire working operating temperature (from -20 to 85 degC) is expected for a good unit. Up to 40 ppm error (=~100 kHz) is acceptable.
Caution: don't use Continuous Wave mode for longer periods of time to avoid excessive heat up of the RF unit.
"},{"location":"hardware/crystal-frequency-error/#measuring-relative-xo-error-between-a-tx-rx-pair","title":"Measuring relative XO error between a TX-RX pair","text":"
You'll need to use \"Manual mode\" in the configurator to enable a special debug mode. In addition to this debug mode flag, you should add any other user defines you need to get your TX/RX to connect (check the user defines section).
For example, this might look like (which is safe to just copy-paste in general):
Using the configurator and user defines, include the -DDEBUG_FREQ_CORRECTION define for BOTH TX AND RX builds of any version of ELRS past v3.0.0 (i.e. V3.0.0 RC2)
After loading the new firmware on both TX and RX, go to the telemetry screen in your model settings on the TX side. Note the \"RSNR\" value. This is the relative difference between your TX and RX clocks.
The closer this value is to 0, the better!. Negative means the RX clock is slower than TX, and positive means that it is faster.
\u00b1 20 ticks (~30 kHz offset) is nearly perfect. \u00b160 ticks (~95 kHz) will still likely be completely fine, though not ideal. \u00b170 ticks and further is marginal and might be fine, but you should be careful.
The TX-RX pair can communicate up to about 110 ticks (~170 kHz). However, because you'll want some safety margin, DO NOT USE the gears with \u00b190 ticks of error.
The tick value that appeared in the RSNR field is a scaled value of the frequency offset, and here is the conversion formula:
\\(Freq_{kHz} = Tick \\times 1.575\\)
For example, if you got the tick value of 30, the frequency offset between your TX and RX is \\(30 \\times 1.575 = +47.25_{kHz}\\), and this means your receiver is generating 47.25 kHz higher frequency than your TX.
When one unit in the measured pair uses TCXO with good error tolerance (desirably <1 ppm) as the SX1280 clock source, the measured ticks will represent the absolute error of the counterpart unit.
We measured the frequency deviation of RX modules from various makers and samples, using the absolute method mentioned above. In the graph, 0 is the reference frequency, and the amount of frequency deviation is shown as the bars. Closer to zero is better. More than 200 kHz deviation is considered to be out of tolerance. Please note that they are only a few samples acquired by the devs, which may not represent the entire product batches.
There are a few interesting points in the graph.
1 All three samples from JHEMCU have significantly deviated more than other makers. A TX module at the reference frequency will not bind to JHEMCU #3 (yellow bars). Also, a TX module with a slight positive frequency deviation will not bind to JHEMCU #1 and #2 as well. 2 Ambient temperature changes the operating frequency of a module. In the graph, Jumper Aion RX (blue bars) and JHEMCU #3 (yellow bars) were chilled and heated, and their operating frequencies were changed around +- 50 kHz. 3 A few makers added extra load capacitors to XO, which lowered their operating frequencies. In this graph, Matek (pink and green bars) and Jumper (blue bars) modules were shipped with the extra load caps. Removing them shifted the frequency to the higher side. 4 Overall frequency errors tend to shift toward the negative side. This might be caused by using XO designed for 8pF load, while the internal load capacitance of SX1280 is 10 pF.
To conclude, XO frequency error is unavoidable. However, a careful circuit design and good-quality parts can control the error within the tolerable amount.
Just to note, we've had some mismatching cases as follows:
JHEMCU (which are rebranded and sold as Flywoo, HiYounger as well) SP24S and EP24S units have frequently reported not being able to bind. (Their units tested here are bad as well)
A few cases were reported that Matek R24-D, R24-S, and Jumper Aion RX Mini units were not able to bind with some TXes (e.g., HappyModel ES24TX Pro). Removing the additional caps around 52 MHz XO solved the issue.
Caps to be removed Jumper Aion Caps Flywoo Caps"},{"location":"hardware/crystal-frequency-error/#how-to-video","title":"How-to-video","text":"
You can also follow the below video which helps to fix ELRS RX Frequency Error by removing extra caps.
The Crystal Oscillator error documentation would not have been possible without the work and huge effort from the @SunjunKim
"},{"location":"hardware/fan-mod/","title":"R9M Fan Mod","text":"
Initially, this mod is brought to life by Niklas Voigt and Seba112PL as a beta tester and is still a work in progress.. if you have suggestions don't hesitate to contact.
DISCLAIMER
Users have experienced temperature issues on R9M that degrades the link quality. We recommend you use the lowest power setting required for your flight and turn on dynamic power at all times (ELRS v2.0+)
Hot Tip
It might seem counterintuitive, but using less power might help for longer flight times and more range by reducing the heat. ELRS does not require a lot of energy and looking at the long-range leader board
You need a 20x20mm or 25x25mm fan in 5V version. Both sizes are supported. To secure the fan into the cover you can use 2x M2 screws, a thread is already in the print. You can solder the pins of the fan directly to the 5v port of the R9M or use the Controllable Fan Mod which can control the fan out of software (fan blows only at >250mW).
R9M Fan Mod Cover is built out of four Parts and a Sticker:
"},{"location":"hardware/fan-mod/#controllable-fan-mod","title":"Controllable Fan Mod","text":"
Additionally to the fan, you'll need one NPN Transistor (e.g. 2N4401) or N-Channel MOSFET (e.g. BS170 has built-in Schottky-Diode) and a resistor (200-3k7)
The PB9 pad location on the R9M2019 module is a bit different. Please see the photo.
PB9 pad location"},{"location":"hardware/fan-mod/#2w-mod","title":"2W Mod","text":"
WARNING
Only do this if you are comfortable with modding hardware
In addition to the 3D printed Cover & the Controllable Fan Mod you'll need:
Fan + Heatsink \"2507 25MM 25x25x13MM Hydraulic bearing Graphics card Cooling fan with heat sink 5V 12V m.2 SSD Fan with 2pin\"
Thermal Pad 0.5mm \"1pc 100mmx100mmx0.5mm GPU Northbridge IC LED Chipset Heatsink Cooling Conductive Silicone Thermal Pad,100x100x0.5mm w/ 3.2W/M-K\"
The screw heads are cut off to reduce height.
As you can see in picture 3, the 5v fan is connected to the power source of the module, so the fan is used with some overvoltage and spins with higher rpm... tested for a long time and should not be a problem for the fan. If you don't know how to allow the 2W in the firmware, don't do this mod!\ud83e\udd26\u200d\u2642\ufe0f
"},{"location":"hardware/fan-mod/#here-are-some-makes","title":"Here are some makes","text":""},{"location":"hardware/hardware-selection/","title":"Hardware Selection","text":"
ExpressLRS is #blessed with the benefit of there being many options of transmitters and receivers available from a variety of manufacturers. This begs the question \"what is the best?\" There is no best option for hardware, only one that has the features you want for the price you want to pay in the size you want it. ExpressLRS does not recommend a specific brand or model, but provide the information to help you select the right ELRS hardware for your needs. The following page will list manufacturers and features to look out for on their hardware.
Note
This list will list primarily 2.4GHz hardware with 900MHz only listed in the frequency category, as 2.4GHz has become a significantly larger portion of the ELRS market.
This section exists to list some common features of receivers and will give some examples of receivers with these features.
Each build is different, but these are recommended things to look for when selecting a receiver:
Whoops / Toothpicks / Light aircraft: Size is probably the most important feature, with a light small receiver and an onboard antenna being the best choice.
Racing Quads: Size is again most important. Ceramic antennas could be less easily damaged, and the reduced range of tucking them inside the frame is fine due to the short flight range. An external 2.4GHz antenna dipole is still pretty easy to fit and can be tucked away for a small improvement over the ceramic, but comes with a chance of Choppage.
Freestyle Quads: Minimum size is no longer an issue so Nano-sized receivers are the best bet here. An LNA is going to give you better reception behind obstacles. External antennas are a benefit as well, but you need to trade off how unobstructed the antenna will be versus getting it chopped. Diversity can be of major benefit in medium-range scenarios to prevent antenna nulls from pointing towards transmitters and carbon or concrete blocking one antenna.
Long Range: For sure you need an LNA, an external antenna, and a PA to extend the telemetry range. This isn't to say these are required for long range, 5km is achievable on a ceramic antenna receiver with no LNA/PA at 250Hz/100mW with a clear line of sight. Diversity can be useful for longer-range quads, to prevent carbon from blocking antennas or antenna nulls from pointing toward the transmitter in certain flight orientations. For planes without a flight controller, PWM receivers will work great. For absolute maximum range, 900MHz can do more but 2.4GHz can still do 50+km.
Frequency
ExpressLRS offers both 2.4GHz and 900MHz systems, with each only working with receivers and transmitters of the same frequency. 2.4GHz is the currently most popular frequency given its legality, features and cost. 2.4GHz links offer the fastest packet rates allowing for a more locked-in feel while piloting and still offering massive amounts of range. 900MHz is the original long-range frequency and still can be great for high wifi pollution environments with slightly better penetration.
For new users, unless you plan on flying hundreds of kilometers or in a high-noise environment we recommend 2.4GHz hardware such as:
Happymodel EP Series
Radiomaster RP Series
NamimnoRC Flash Series
If you have an R9 system or similar or plan on flying beyond reasonable ranges, some great 900MHz receivers include:
BetaFPV Nano900
Happymodel ES900RX
GEPRC Nano 900MHz
Antenna Type
Antennas are where the radio waves come and go from the receiver. ExpressLRS offers many different antenna types, with dipoles and ceramic antennas (see SMD Antennas) being the most common types of reciever antennas. In terms of range: Ceramic antenna < Mini Dipole (\"Minimortal-T\" style) < sleeved dipole < Half-wave Dipole. A diagram of the antennas and their sizes for the 2.4GHz band is shown below:
Unless otherwise noted, most receivers will have a U.FL/IPEX connecter which supports external antennas. Some receivers with ceramic antennas are:
Happymodel EP2
Radiomaster RP2
MatekSys R24-S
Diversity
Diversity improves reception compared to standard receivers by using multiple antennas. A standard receiver has a single antenna, while antenna diversity uses two antennas and a switch to route the signal from one or the other. True diversity takes it a step further by using two radio chips, each connected to a different antenna, and choosing the one with the strongest reception at any given time. This provides a level of redundancy which is particularly beneficial for flight where the antenna nulls can point towards the pilot (e.g. freestyle flight)
Some receivers with antenna diversity include:
Radiomaster RP3
Namimno Flash Diversity
Matek R24-D
Some receivers with true diversity include:
Happymodel EP1 Dual
BetaFPV SuperD
PWM
PWM is used for crafts that do not have flight controllers and allow for direct control of ESCs and Servos. See the page on PWM for more in-depth information on using PWM.
Some PWM receivers include:
MatekSys R24-P6
Happymodel EPW6
Radiomaster ER5A/C
PA/LNA
A Low Noise Amplifier (LNA) directly adds to your incoming RSSI. Typical gains are in the ballpark of +12dBm which will be observed in the RSSI as being 12dBm higher than it would have been without the LNA. This is because the LNA amplifies the incoming signal coming from the antenna before going to the RF chip, which increases the sensitivity of the receiver by boosting the incoming signal. An LNA also boosts the noise by the same amount so the sensitivity limit will likely be lower than the value quoted by the Lua.
A Power Amplifier (PA) boosts the outgoing signal strength and extends the telemetry range back to the TX. Without a PA, the power output is limited by the RF chip's max power output itself (around +13dBm 20mW). It works the same way as turning up the power output on the transmitter module, however it is not adjustable. The receiver's output can be ran at adjustable power levels given range needs. Most PAs are 20dBm/100mW, meaning the telemetry transmit power can be adjusted to 10, 25, 50 or 100mW.
Receivers with a PA/LNA will have a listed telemetry output power in dBm or mW
Some receivers with a PA & LNA are the following:
Radiomaster RP3 (100mW)
Skystars Nano SS24D (20dBm)
MatekSys R24-D (23dBm)
BetaFPV SuperD (20dBm)
Size
The FPV world shook when ELRS released receivers that were half the size of \"nano\" sized receivers, included the antenna onboard, and still had kilometers of range at 250Hz/100mW. A small receiver can fit in tight places, but remember that tucking a tiny receiver's ceramic antenna deep inside a stack behind carbon reduces its performance, which was already compromised by the elimination of amplifiers to make it that small. Larger ELRS receivers regain these amplifiers offering better reception and telemetry range at the cost of size and weight. The common size classes are shown below, but there are other receivers with slightly different sizes:
PP Sized Receivers (absolute smallest, lowest range regardless of antennas):
Happymodel EP/PP
Radiomaster RP
BetaFPV Lite
Nano Sized Receivers (medium sized, can have PA/LNA but tends to lack some features):
BetaFPV Nano
iFlight RXes
Namimno Flash Diversity RX
Axisflying Thor RX
Namimno Flash RX
Larger Receivers (most feature rich but also significantly larger)
This section lists out some common features of transmitters and some examples of transmitters with those features
Everyone has different needs for a transmitter but the main needs come down to size, range and integration.
Built-In Transmitters
Certain manufacturers have made handsets with built in ELRS modules, which offer tighter integration with ELRS. These can be updated through the handset as well as generally over WiFi as is standard.
Some handsets with built-in ELRS include:
RadioMaster TX16S ELRS
RadioMaster Zorro ELRS
BetaFPV Lite Radio 3 Pro ELRS
Jumper T-Pro
Jumper T-Lite v2
A notable exception to this list is the iFlight Commando, which, while including a TX built into the handset is simply wired as an external module, and put within the casing. It does support an external module and notably has both 868/915MHz and 2.4GHz options available
Frequency
ExpressLRS offers both 2.4GHz and 900MHz systems, with each only working with receivers and transmitters of the same frequency. 2.4GHz is the currently most popular frequency given it's legality, features and cost. 2.4GHz links offer the fastest packet rates allowing for a more locked-in feel while piloting and still offer massive amounts of range. 900MHz is the original long range frequency and still can be great for high wifi pollution environments with slightly better penetration.
For new users unless you plan on flying hundreds of kilometers or in a high noise environment we recommend 2.4GHz hardware such as:
Axisflying Thor
RadioMaster Ranger
HappyModel ES24TX Pro
Namimno Flash
If you want to push the limits of range, a 900MHz system might fit within your needs. Some off the shelf 900MHz transmitters include:
Namimno Voyager
Happymodel ES900TX
BetaFPV Micro 915/868MHz
Size
Most ExpressLRS Transmitter modules fit into one of two classes - Micro and Nano. There are some exceptions that fit into multiple or have interesting features that may make them work better for your needs.
Micro modules will fit into the JR bay of a standard transmitter such as a TX16s or QX7, with some examples including:
RadioMaster Ranger Micro
Namimno Flash
HappyModel ES24TX
Nano modules will fit into a lite module bay such as that on a Zorro, T-Pro or X-Lite with some examples including:
HappyModel ES24TX Slim Pro
RadioMaster Ranger Nano
Jumper AION Nano
BetaFPV Nano
Some notable exceptions that can fit into multiple or very specific module bays include:
HappyModel ES24TX Lite - Fits onto Jumper T-Lite
Axisflying Thor - Has a wire system to be able to plug into any radio with a CRSF output
Radiomaster Ranger - includes Micro & Nano mounts and wiring for any CRSF compatible radio
Power
Most ELRS Transmitters have a 250mW or 500mW power cap, but if you need to go a bit further, a select few 1W modules exist (see the Inverse-square law for info on why 1W does not double the range over 500mW), packing that punch needed to go even further. These transmitters include large heatsinks, fans and sometimes temperature-sensing to cool the RF components. Some of these 1W transmitters are:
HappyModel ES24TX Pro
RadioMaster Ranger (Full Size, Micro and Nano all are 1W)
Axisflying Thor
BetaFPV Micro TX 1W
RadioMaster Boxer
Jumper T-Pro Internal
NamimnoRC Flash (both OLED & non-OLED models)
Screens
Some transmitters include a small screen that displays useful information and pairs with a small joystick to quickly change settings on the go. This can be useful when paired with handsets running firmware that does not support lua scripts. The two main types of screens are TFT and OLED:
The only transmitter with a TFT screen on the market at the moment is the Axisflying Thor TX.
Some transmitters with an OLED include:
Namimno Flash OLED
RadioMaster Ranger
BetaFPV Micro TX
Jumper AION Nano
Backpack
Most current transmitters will include a backpack, which enables communication with accessories such as a VRX allowing for tighter integration with the transmitter and drone. Transmitters with a built-in backpack include:
HappyModel ES24TX Pro
HappyModel Slim Pro
NamimnoRC Flash
AxisFlying Thor
RadioMaster Zorro
BetaFPV Micro TX 1W
Antennas
Besides handset integrated transmitters, all ELRS TX modules support many antennas so this serves as a guide to antenna types and connectors.
ELRS TX Modules have two connecters, which are visually similar - SMA and RP-SMA
These connecters mount many types of antennas which have different types of radiation patterns. The first figure depicts the types of antennas commonly sold with transmitters:
The most common antennas sold besides simple dipoles are moxons and folded dipoles, which visually look similar which helps distinguish the two:
The radiation patterns of a moxon and folded dipole are depicted below in a isotropic, lateral and top view
Bling Features
Certain transmitters have \"bling features\" which are less important than the other listed features. Some of these include RGB LEDS, Temperature Sensors and G Sensors.
RGB LEDs are included on many modern TXes, and also serve as a useful status indicator.
Temperature sensors are useful for higher power transmitters, to turn on the fan only when needed instead of constantly running while transmitting which reduces noise. Currently the only transmitter with this feature is the Axisflying Thor.
G Sensors/Motion sensors use a 3 axis linear accelerometer to detect the orientation of the transmitter and also can use bump to handoff for loan model. The transmitters that ship with this feature is the Axisflying Thor & RadioMaster Ranger
To benefit from the higher bitrate of 400 kilobits per second using OpenTX/EdgeTX you need to add a pull-up resistor to the inverter of the serial port on the R9M 2018\ud83d\uddfb\ud83c\udd99
Strongly suggested being done for anybody looking for higher than standard packet rates using ExpressLRS \ud83d\udd2e
ExpressLRS now supports direct PWM output from receivers. This documentation refers to only receivers with native PWM output, not receivers attached to external CRSF to PWM converters such as the CRServoF or Matek CRSF-PWM-C.
"},{"location":"hardware/pwm-receivers/#channel-mapping-and-failsafe","title":"Channel Mapping and Failsafe","text":"
The default channel mapping is straight through: CH1 from the TX goes to PWM Output 1, CH2 to Output 2, etc. To change this on ESP-based receivers, allow the receiver to go into WiFi mode then use the WebUI to configure the mapping. Any input channel can be mapped to any output channel, and the same input can be used for as many outputs as desired. AUX1/CH5 is always 1-bit, so you'll likely want to change this mapping to a channel with more resolution.
PWM Output WebUI
Failsafe values are set using this UI as well with values that can range from 988us to 2012us. Failsafe is entered if the receiver is connected and Link Quality (LQ) drops to 0, or 1 second has passed without a valid channels packet being received, whichever comes first. On startup, no pulses are generated until a transmitter connects, allowing ESC throttle calibration with the standard \"raise the throttle before connecting\" method. The default failsafe value is 1500us for all channels except Output 3, which defaults to 988us.
PWM output is still subject to the resolution of the ELRS protocol, which means by default there are still only 4x full resolution channels (10-bit CH1-CH4) and 8x switch channels (CH5-CH12). For the best resolution on the switch channels, use Switch Mode: Wide and a TLM Ratio of 1:8 to 1:256 for 7-bit (128 pos) switch channel resolution. Higher TLM Ratios (1:2 and 1:4) are reduced to 6-bit (64 pos) resolution. Remember that switch channels are sent one per packet in Wide mode, taking 8 packets to send all 7 channels (e.g. 150Hz mode 1:64 = 18.657Hz updates to CH6-CH12). AUX1/CH5 is sent in every packet in all switch modes but is only 1-bit (2-pos). See Switch Configs for more information.
Full-Resolution Switch Modes
ELRS v3 now supports full-res switch modes, which provide 8, 12, or 16 full-resolution (10-bit) channels at 100Hz (900MHz and 2.4GHz) or 333Hz (2.4GHz only). For PWM receivers with more than 4 channels, it is recommended that you use one of the full-res modes for best performance.
Normal pulse width (988-2012us - center 1500us), extended pulse width (885-2115us - center 1500us), and also half pulse width servos (494-1006us - center 750us)
10kHz Duty Cycle 0-100% PWM (e.g. for driving a brushed motor FET)
On top of this, outputs can also be set to:
Binary On/Off (High/Low signal output)
DSHOT300 (for driving brushless motor ESCs; ESP32-based receivers only)
PWM receivers can also output any supported serial protocol, such as CRSF or SBUS. Select the desired output protocol using the ELRS lua, or on the Model tab in the receiver's WebUI. The default pins used for serial output vary by receiver. If your receiver has a dedicated serial port (e.g. RadioMaster ER6, ER8, ER8G(V)), serial output will be over this port. Otherwise, check the Model tab in the receiver's WebUI to see which pins can be mapped to Serial TX and RX (usually Ch2 and Ch3).
JST-GH Serial Port on RadioMaster ER6 PWM Receiver
Advanced Output Mapping
Advanced users can remap serial, I2C, and PWM outputs to any available pin using the hardware.html page in the receiver's WebUI. Please ask on the ELRS Discord if you need help configuring non-standard receiver output mapping.
Have you ever been frustrated that you can't finish a race because your receiver antenna got chopped? Have you ever wished you could build a quad without worrying about how to mount your antenna? If so, the SMD Antenna is for you!
SMD Antenna
This perky little fellow is worse at receiving signals than his snaky brothers, but don't let that deter you! Because of the amazing range of ExpressLRS, he still gets all the range a racer could ever need. The SMD Antenna is available now on Happymodel PP/EP hardware and other 2.4GHz receivers. Take a look at the videos below to see what Mr. SMD can do for you.
The antenna is sort of fragile and can break off or be melted by a stray soldering iron. If this happens, you can save your receiver by soldering a U.FL/IPEX1 connector onto the pads as shown here. Just make sure the center pin has continuity with the filter at the other end of the trace, and no continuity with the ground.
Conversely, the SMD antenna can be soldered to regular U.FL footprints if you're brave.
SPI receivers DO NOT support D(D250, D500), F(F500, F1000) and Full Res(100Hz Full Res, 333Hz Full Res) Modes (Packet Rates) and thus will not bind or sync with a TX module in any of these modes.
You must use one of these packet rates with an SPI receiver: 50Hz, 150Hz, 250Hz, 500Hz.
Update Betaflight 4.5.1 and newer now support FLRC modes (F500,F1000) for SPI receivers. F1000 is not recommended for FCs with F411 MCUs.
A few Flight Controllers and AIOs have been released with ExpressLRS receivers on-board using SPI instead of a regular UART. This means you can build a more compact and lightweight whoop or nano long range rig without the need for an external receiver. More of these flight controllers are coming into stores.
Because the ExpressLRS code is \"baked-in\" to the flight controller firmware instead of using a second microcontroller, these can not be updated the same way external UART-based receivers are updated.
NOTE
You cannot use the ExpressLRS Configurator to update these FCs. You must update the flight controller software, e.g. Betaflight.
SPI receiver compatibility with ExpressLRS v3.x requires your flight controller be flashed with Betaflight 4.4.0 or newer. If you are running Betaflight 4.3.0 or Betaflight 4.3.1, your receiver will only work with ExpressLRS v2.x. Please update to Betaflight 4.4 or newer for ExpressLRS v3.x compatibility.
In preparation for updating, you should save a copy of your diff all dump. Simply go into the CLI Tab of the Betaflight Configurator and execute the command diff all then press enter. A bunch of text will show up on the screen. At the bottom of the page, click the Save to File button and navigate to the folder you want the file to be saved. Finally click Save after taking note of the folder and filename of the text file. You will need to navigate to this file later on, moreover if you already have customized your settings on the flight controller, like rates, PID tune, OSD.
Using the latest Betaflight Configurator, navigate into Firmware Flasher and select the latest Betaflight release. Depending on your AIO board, the target will differ. Betaflight targets for FCs with SPI receivers will usually end in SX1280. Examples:
Happymodel AIO: CRAZYBEEF4SX1280
BetaFPV AIO: BETAFPVF4SX1280
If your Flight Controller model is not in the list above, consult your Flight Controller manufacturer for details.
NOTE
The Happymodel Mobula6 900MHz AIO with the CrazyF4 ELRS FC (Target: CRAZYBEEF4DX) doesn't use an SPI ExpressLRS receiver. Check the page for ES915RX instead.
Likewise, the v2.0 BetaFPV F4 1S 5A comes with an on-board UART-based ExpressLRS Receiver and doesn't use the SPI ExpressLRS implementation. Use the BETAFPV AIO 2400 RX Device target.
If you're using Windows and flashing fails to start, you may need to correct the drivers using a tool like ImpulseRC Driver Fixer. These tools and other drivers are also linked in the Welcome tab of Betaflight Configurator.
Once flashed, you will need to connect and restore settings from the diff all you have saved. Go into the CLI Tab of the Betaflight Configurator and press the Load From File button. Select the diff all file you made previously and press execute. If there were any errors, you will need to manually type in the save command and press enter. Betaflight Configurator should disconnect. After reconnecting, review your Betaflight settings (for example the Receiver Type and Protocol in Receiver tab; it should be set to SPI Receiver, with Provider as ExpressLRS).
As of Betaflight 4.4 (with Betaflight Configurator version 10.9.0 or newer), your ExpressLRS Binding Phrase can be set directly on the receiver tab in Betaflight Configurator.
Proper configuration of the Betaflight Receiver tab for ExpressLRS SPI Receivers. Receiver Mode (1) should be set to SPI RX. SPI Bus Receiver Provider (2) should be set to EXPRESSLRS. Enter your binding phrase in the box (3) and it will be converted to UID bytes (4) and saved to your Betaflight config. You can also take this opportunity to enable Telemetry (5) if desired, and make sure RSSI_ADC (6) and RSSI Channel (7) are disabled as shown.
Put the receiver into bind mode using any of these procedures:
\"Bind\" button in the Betaflight Configurator, Receiver Page (if can't be found, update the Betaflight firmware).
Using the CLI, type in bind_rx and press enter once.
Press the bind button on the flight controller.
Using the CLI, type in set expresslrs_uid = 0, press enter once, then save and reboot
Once the SPI receiver is in Bind Mode (indicated by two immediate blinks followed by a short pause), execute the ExpressLRS Lua script in your handset and press the Bind option. The RX and TX should be now bound (indicated by a SOLID LED on the Flight Controller).
Please mind the order, RX first, TX second.
Video Tutorial (thanks to @JyeSmith):
"},{"location":"hardware/spi-receivers/#binding-phrase-via-cli","title":"Binding Phrase via CLI","text":"
The binding phrase is hashed into 6 bytes represented as numbers. These 6 bytes are referred to as the UID bytes. UID bytes are entered into the Betaflight CLI for binding. Please look below for instructions.
NOTE
When building via ExpressLRS Configurator or via VS Code, note down the UID bytes from the build log. You can also use the generator below to retrieve your UID bytes from your binding phrase.
In order to set or retrieve current Model ID through Betaflight you need to use CLI: - Set new Model ID: set expresslrs_model_id = N - Get current Model ID: get expresslrs_model_id
Go to Betaflight CLI and enter the following commands.
As shown above, Betaflight Configurator 10.9.0 also supports entering the Binding Phrase directly in the Receiver Tab. It will generate the UID bytes for you. Clicking Save and Reboot will save the Binding Phrase into the flight controller configuration.
Supported RF Modes
SPI receivers DO NOT support D(D250, D500), F(F500, F1000) and Full Res(100Hz Full Res, 333Hz Full Res) Modes (Packet Rates) and thus will not bind or sync with a TX module in any of these modes.
The SPI ExpressLRS implementation would not have been possible without the work and huge efforts from the following developers:
Pawe\u0142 Stefanski (@phobos-)
Dominic Clifton (@hydra)
Hans Christian Olaussen (@klutvott123)
Steve Evans (@SteveCEvans)
ctzsnooze (@ctzsnooze)
"},{"location":"hardware/x9d-troubleshooting/","title":"Troubleshooting the X9D(+)","text":"
For quite some time we had the impression that the X9D(+) radio works well with the high baud rates, needed for ExpressLRS. However, some users report it's not working as it should with ExpressLRS. For example:
ExpressLRS Lua script just shows Loading...
ExpressLRS Lua script shows unstable behavior, especially on the higher packet rates, showing values different from 0/[SELECTED PACKET RATE]
It is possible that the X9D(+) radio also suffers from a slow inverter circuit that messes up the 400000 baud UART signals.
As you may know, for the Taranis QX7(S) you can do the Crossfire inverter mod or select a lower baud rate in the Hardware menu (Page 6/7) of OpenTX to fix the issue.
Well, the final verdict is not out yet, but the following may help to resolve the issue:
Do a hardware mod as well on your X9D(+) as you can read all about here in PR# 59 for EdgeTX. This requires changing the 10k resistor R82 to a 1k resistor.
Download a OneBit_Status firmware using this OpenTX version, based on OpenTX(2.3.12 or 2.3.14) and enable ONEBIT Sample Mode (System Menu -> Hardware). One Bit Sample Mode is also available on EdgeTX.
Sample Mode: Normal Sample Mode: OneBit
Select 115200 baud using the above OpenTX version. (ExpressLRS will lock you out of 500Hz packet rate with 2.4GHz, but any packet rate below that should be stable now.)
The nice thing about the OpenTX build above is that it also adds two additional Sync lines to show the current OpenTX/UART behavior. This will show in your Model Setup (Page 2/11) where you select the external module type (where you selected CRSF to enable ELRS):
The first Sync line shows something like L00002R04000u. L and R indicate the microseconds of Lag and Rate.
The L is how much OpenTX is trying to compensate to nail the rate you selected. (The closer to 0 the better)
The R is just the Packet Rate you selected using the ExpressLRS Lua script.
The second Sync line shows something like G11 C00 F00. This stand for G (good packets), C (CRC error), F (Framing error). The goal is to have zero errors here. (Don't forget to power your receiver so a link is established!)
If this has helped you in any way (good or bad) with your X9D(+) radio, let us know on the ExpressLRS discord!
Most of the ESP-based ExpressLRS modules come with the TX Backpack. A \"TX Backpack\" refers to an additional WiFi-capable microcontroller inside the TX module, which can communicate wirelessly with \"Backpack receivers\". This allows the TX to communicate with other devices such as your Goggles (to change VRX channel), race timers, antenna trackers, ground control stations, etc.
Open the ExpressLRS Configurator and select Backpack in the left hand menu bar.
Select the latest Backpack Release version from the Releases dropdown.
Select your device target. If there is a target that matches your hardware, use it. If you can't find a target that matches your TX module, use the Generic backpack for any TX module targets.
Enter your Binding Phrase and your Home WiFi SSID and Password (Optional).
Choose your Flashing Method based on your hardware (choose from the options below):
"},{"location":"hardware/backpack/backpack-tx-setup/#flashing-via-usbuart-for-older-tx-modules-with-dip-switches-jumper-pins","title":"Flashing via USB/UART (for older TX modules with DIP switches / jumper pins)","text":"
Applies to: Older TX modules that have DIP switches or jumper pins, e.g. Happymodel TX modules. Recent transmitter modules do not required any preparation prior to flashing the TX-Backpack firmware. If your TX module does not have any DIP switches or jumper pins, you can skip this step, and proceed to flash via Passthrough or WiFi.
For older TX modules like the Happymodel TX Modules, you will need to move the jumpers or DIP switches into the correct position before flashing the firmware. Please see the USB/UART Flashing section of your particular TX Module for the jumper or DIP switch position.
ES24TX Jumpers
ES900TX Jumpers
You need to activate the Backpack Flashing jumper or DIP switch (middle pair). Opening up the module enclosure will be needed as well to access the Buttons on the modules. Make sure your computer recognizes your TX module as a USB to UART Bridge. Windows drivers are linked in the Flashing Guides.
For the NamimnoRC Flash and Voyager TX Modules without an OLED screen (Gen 1 STM-based), make sure you're able to access the Backpack Web Update page (see Flashing Guide) via WiFi.
For the Happymodel TX modules, connect to your computer via USB. As stated above, the module should be detected as a USB to UART Bridge and the jumper/DIP switches are set in the correct position (middle pins/switches should be On).
Button Dance: A few buttons are needed to be pressed on the module while the firmware is compiling. Press and Hold the GPI0 button then the RST button (GPIO is still pressed) then release the RST button and then the GPIO button.
Module Buttons
In the Configurator, select the UART option under Flashing Method.
Ensure you have completed the steps in the Setup section above, then click Flash on the ExpressLRS Configurator.
Wait for the process to complete and you should see the green Success notification.
Unplug the USB and change the position of the jumpers/DIP switches for the Normal Operation (refer back to the module's Flashing Guide page for the correct position).
Put back the cover of the module and attach it to your module bay.
"},{"location":"hardware/backpack/backpack-tx-setup/#flashing-via-passthrough","title":"Flashing via Passthrough","text":"
Applies to: Newer TX modules that do NOT have DIP switches / jumper pins, e.g. Radiomaster Ranger Series
Plug a USB Data Cable into the TX module.
In the Configurator, select the Passthrough option under Flashing Method.
Ensure you have completed the steps in the Setup section above, then click Flash on the ExpressLRS Configurator.
Wait for the process to complete and you should see the green Success notification.
"},{"location":"hardware/backpack/backpack-tx-setup/#flashing-via-wifi","title":"Flashing via WiFi","text":"
Applies to: All TX modules that have a Backpack (this method assumes that the Backpack firmware has been flashed in the past and is functional).
Using the ExpressLRS Lua script, navigate to WiFi Connectivity and select Enable Backpack WiFi.
The LUA script will briefly show Sending, then return to the WiFi menu.
The Backpack WiFi Access Point (or Home WiFi, if you enabled it) will activate.
Home WiFi
With your Home Network SSID and Password set, when you activate the WiFi mode via the Lua script (WiFi Connectivity -> Enabled Backpack WiFi), the Backpack will try to connect to your Home WiFi Network. Once connected, you can access the Web Update page via http://elrs_txbp.local/ and upload your firmware there.
If you are NOT using Home WiFi, connect to the ExpressLRS TX Backpack WiFi access point (password is expresslrs) and navigate your browser to http://10.0.0.1/.
If you ARE using Home WiFi, navigate your browser to http://elrs_txbp.local/.
In the Configurator, select the WIFI option under Flashing Method.
Ensure you have completed the steps in the Setup section above, then click Flash on the ExpressLRS Configurator.
Wait for the process to complete and you should see the green Success notification.
Alternatively, you can build the firmware file, then drag it to the WebUI. To do this, ensure you have completed the steps in the Setup section above, then click Build on the ExpressLRS Configurator.
Grab the built firmware.bin.gz (do NOT extract it) and drag-and-drop it into the File Upload section of the webpage. If you are using an ESP32 based Backpack, the filename may be firmware.bin. Drag-and-drop it into the File Upload section of the webpage.
Click Update. Wait a bit (~10s) for the \"Update Success! Rebooting...\". The AP should automatically disappear and disconnect.
WiFi ESP"},{"location":"hardware/backpack/backpack-tx-setup/#flashing-via-wifi-older-namimnorc-gen1-tx-modules","title":"Flashing via WiFi (older NamimnoRC Gen1 TX Modules)","text":"
For the First Generation NamimnoRC TX modules (No OLED), you will have to first Build the Backpack firmware. Once built, grab the backpack.bin file from the folder that the ExpressLRS Configurator opened. Open the URL http://elrs_tx.local on your browser and scroll down to where the WiFi Backpack Firmware Update section is (shown in the image below). If the page isn't loading, make sure you have followed the Wifi Flashing guide for these modules (see Flashing Guide).
Wifi Backpack
Wait for a bit (~10s) after the message \"Update Success! Rebooting...\" appears before you power-cycle the module. Your TX Backpack should now be ready.
"},{"location":"hardware/backpack/backpack-tx-setup/#flashing-via-etx-passthrough","title":"Flashing via ETX Passthrough","text":"
Applies to: Internal ExpressLRS TX modules, e.g. RadioMaster Zorro TX Backpack, RadioMaster TX16S Backpack, etc.
FYI
This method is the result of the collaborative effort between EdgeTX, RadioMaster, and ExpressLRS.
With your handset turned on, connect a USB data cable to the USB data port of the Radio.
Select USB Serial(Debug) or USB Serial(VCP) in the options window that pops up.
In the Configurator, select the EdgeTXPassthrough option under Flashing Method.
Ensure you have completed the steps in the Setup section above, then click Flash on the ExpressLRS Configurator.
Wait for the process to complete and you should see the green Success notification.
Unplug the USB from the handset and you're set!
"},{"location":"hardware/backpack/backpack-tx-setup/#how-to-check-you-have-updated-the-tx-backpack-firmware","title":"How to check you have updated the TX Backpack Firmware?","text":"
Make sure you set the jumpers or DIP switches on your modules (if required, e.g. the Happymodel TX Modules) to the Normal Operation position (refer to the top of this page). This allows the main ESP32 chip to talk to the Backpack chip. The Backpack will NOT work properly if the DIP switches or jumper pins are not in the Normal Operation position.
Attention
Change the position of the DIP switches or jumper pins to Normal Operation if required for your module (e.g. Happymodel TX modules).
Navigate to the WiFi Connectivity folder of the ExpressLRS Lua script and select Enable Backpack WiFi. Scan for Access Points, and ExpressLRS TX Backpack should appear. Connect to it and point your browser to http://10.0.0.1/.
If you have set your Home Network SSID and Password, point your browser to http://elrs_txbp.local/.
The main banner will show you what kind of device it is and the firmware version that's flashed into it.
"},{"location":"hardware/backpack/backpack-tx-setup/#setup-your-vrx-backpack","title":"Setup your VRX Backpack","text":"
Proceed to the VRX Backpack Setup section to setup your VRX Backpack, if desired.
The Backpack Usage section provides further details on ExpressLRS Backpack Operation, including Binding, LED Status codes, and more.
"},{"location":"hardware/backpack/backpack-vrx-setup/","title":"VRx Backpack Setup","text":""},{"location":"hardware/backpack/backpack-vrx-setup/#flashing-methods-for-backpack-device","title":"Flashing Methods for Backpack Device:","text":"
Before wiring up your VRX Backpack into your VRX Module, you MUST first flash the VRX Backpack firmware, either via WiFi or UART/FTDI.
Good VRX Backpack candidates are the EP1 or EP2 receivers from Happymodel as these have Boot pads instead of Boot buttons. The Boot pad will be repurposed for the SPI Clock signal from the VRX module.
The VRX firmware you will flash into your Backpack Device will depend on what VRX module you want to connect it to. If you do not flash the correct firmware, it will not work properly.
"},{"location":"hardware/backpack/backpack-vrx-setup/#flashing-via-wifi-esp-based-expresslrs-receivers","title":"Flashing via WiFi (ESP-based ExpressLRS Receivers)","text":"
Power up your selected VRX Backpack device (connect 5v and GND pads to any 5v power source). Let it go into WiFi Update mode (fast blinking LED) and load up the WiFi Update page. In the Address bar of your browser, add ?force=true to ensure it will accept the VRX Backpack firmware. The resulting URL should read http://10.0.0.1/?force=true (if you connected via Access Point) or http://elrs_rx.local/?force=true (if your device has connected to your local WiFi network).
Note
The ?force=true is not needed for ESP-based receivers with factory firmware. It is only required if you have previously flashed the receiver and want to repurpose it as a VRX Backpack.
Go to the Assets section of the Backpack Release on GitHub, Download the binary suited for your VRX module. Upload this binary into the VRX device using the Web Update page. Wait (~30s) until the LED on the VRX device has turned on again.
Alternatively, you can use the ExpressLRS Configurator to create your binaries for you. Build your binary, with the set binding phrase (Optional) as well as Home Network SSID and Password (Optional; available starting 0.2.0). Upload the resulting binary on the WiFi Update page as outlined above.
"},{"location":"hardware/backpack/backpack-vrx-setup/#flashing-via-uartftdi","title":"Flashing via UART/FTDI","text":"
Note
This method is best used for the DIY ESP01F VRX Backpacks, as these devices do not have any firmware from the factory.
Connect your FTDI RX pin into the TX pad of your VRX Device, and the FTDI TX pin into the RX pad of the VRX Device; then the 5V and GND pads. The Boot pad needs to be bridged with the Ground pad. Connect your FTDI, with the connected VRX device, into a free USB port (VRX Device's LED should light up SOLID). Using the ExpressLRS Configurator, select your VRX module, select the via UART method and set your binding phrase (Optional) and the Home Network SSID and Password (Optional; Available starting 0.2.0). Click Build and Flash and the compiling and flashing should commence. If done right, the Success bar should appear and your VRX Backpack should now be ready for wiring into your selected VRX Module.
"},{"location":"hardware/backpack/backpack-vrx-setup/#flashing-tbs-fusion-for-the-first-time","title":"Flashing TBS Fusion for the First Time","text":"
You will need an FTDI dongle (USB to UART Bridge) to flash the VRX Backpack firmware into your TBS Fusion module for the first time. You will also have to follow the TBS Fusion WiFi Module Unbricking Guide but instead of uploading the WiFi Firmware file from TBS, you will upload the VRX Backpack Firmware that the ExpressLRS Configurator compiled from Build.
Any subsequent firmware updates can be done via WiFi.
"},{"location":"hardware/backpack/backpack-vrx-setup/#starting-with-020-you-can-also-update-via-your-home-wifi","title":"Starting with 0.2.0, you can also Update via your Home WiFi","text":"
With your Home Network SSID and Password set, when you activate the WiFi mode via the Lua script (WiFi Connectivity -> Enabled VRX WiFi), the Backpack will try to connect to your Home WiFi Network. Once connected, you can access the Web Update page via http://elrs_vrx.local/ and upload your firmware there.
The ExpressLRS Configurator will also detect the device after it has been connected. It will be listed in the \"Device List\" section, and you can press SELECT, so that the correct target is automatically selected for Build.
Alternatively, you can also Build and Flash via the Configurator through WiFi without having to access the Web Update page (just like any ESP-based ExpressLRS receiver).
"},{"location":"hardware/backpack/backpack-vrx-setup/#vrx-module-setup-before-wiring-it-all-up","title":"VRX Module Setup Before Wiring It All Up","text":"
IMPORTANT: You will need to set your VRX module to the highest band and channel it can go, usually Race 8 (5917MHz) before wiring up any VRX Backpack. This is to ensure the VRX Backpack knows \"where it is\" in the selectable channels.
"},{"location":"hardware/backpack/backpack-vrx-setup/#connecting-the-vrx-backpack-to-your-vrx-module","title":"Connecting the VRX Backpack to Your VRX Module","text":"
Currently supported VRX Modules include:
ImmersionRC Rapidfire
SkyZone SteadyView
Generic RX5808 Module
FENIX Module
Shark Byte RX5.1 HDZero Module
VRX Backpacks communicate with these modules via SPI, and require 3 signal lines: CLK, DATA, CS. Additionally, depending on your VRX Backpack, they will either need 5v (ExpressLRS ESP-based Receiver) or 3.3v (ESP01F module) and of course the GND line.
For the ESP01F Module, you will have to source out a voltage regulator such as an AMS1117 (1A Low Drop-out Voltage Regulator) which will lower the 5V voltage from the VRX module to the needed 3.3v.
The VRX has an easily accessible UART on the main board, which is accessed by removing the 4 screws which secure the back plate. Use the goggle mount to pull the back plate from the housing.
Solder your VRX backpack as shown below:
It is unlikely that you can close the back plate with the backpack module between the plate and the main board. There are two solutions:
Route the wires out of the cooling vents and mount them externally
Mount the backpack in the front patch, routing the wires through the goggle mount as shown below:
Make sure that your RX5808 is running in SPI mode. Then wire it up as shown below:
"},{"location":"hardware/backpack/backpack-vrx-setup/#how-to-check-you-have-updated-the-vrx-backpack-firmware","title":"How to check you have updated the VRX Backpack Firmware?","text":"
Navigate to the WiFi Connectivity folder of the ExpressLRS v3 Lua script and select Enable VRX WiFi. The LED will begin blinking rapidly. Scan for Access Points and ExpressLRS VRX Backpack should appear. Connect to it and point your browser to http://10.0.0.1/.
If you have set your Home Network SSID and Password, point your browser to http://elrs_vrx.local/.
The main banner will show you what kind of device it is and the firmware version that's flashed into it.
"},{"location":"hardware/backpack/backpack-vrx-setup/#setup-your-tx-backpack","title":"Setup your TX Backpack","text":"
Proceed to the TX Backpack Setup section to setup your TX Backpack.
The Backpack Usage section provides further details on ExpressLRS Backpack Operation, including Binding, LED Status codes, and more.
"},{"location":"hardware/backpack/esp-backpack/","title":"Backpack Info","text":""},{"location":"hardware/backpack/esp-backpack/#what-is-a-backpack","title":"What is a Backpack?","text":"
A Backpack is an add-on device that facilitates wireless communication between an ExpressLRS module and another device (e.g. a Video Receiver on your goggles) using the ESPnow protocol.
Communication between an ExpressLRS module and a Video Receiver"},{"location":"hardware/backpack/esp-backpack/#usage-scenario","title":"Usage Scenario","text":"
You are setting up to fly with others, and your favorite video channel is already in use. You're asked to use R2 as that's the vacant one. Using the ExpressLRS Lua script, you change the setting into R2 (this while your aircraft is still unpowered). You power up your goggles equipped with a VRX Backpack. Then plug in your aircraft. Upon the establishment of the connection, the VTX and the VRX are automatically set to R2. You're now ready to fly. No fiddling with channels on the OSD or your goggles.
"},{"location":"hardware/backpack/esp-backpack/#okay-im-sold-what-do-i-need-to-get-this-working","title":"Okay, I'm sold. What do I need to get this working?","text":"
You already have the majority of the hardware needed. Most of the ESP-based ExpressLRS modules come with the TX Backpack. For the VRX Backpack, you can reuse any ESP-based ExpressLRS receiver (recommended are the EP1/EP2 receivers as they have boot pads, instead of boot buttons), or for a complete DIY route, you'll need an ESP-01F module.
An off-the-shelf VRX Backpack has also appeared from Happymodel: the EP82
See the tables below for a partial list of supported devices:
Backpack Requirement
All new ExpressLRS TX releases after October 10th, 2023 require a TX backpack to be integrated into the hardware
"},{"location":"hardware/backpack/esp-backpack/#supported-tx-backpack-targets","title":"Supported TX-Backpack Targets","text":"TX Module Support Happymodel ES24TX Pro \u2714\ufe0f Fully supported Happymodel ES24TX \u2714\ufe0f Fully supported Happymodel Slim Pro \u2714\ufe0f Fully supported Happymodel Slim Ironman \u2714\ufe0f Fully supported Happymodel Slim T-Lite \u2714\ufe0f Fully supported Happymodel ES900TX \u2714\ufe0f Fully supported Happymodel ES915TX (STM32 version) \u274c Not compatible FrSky R9M \u2714\ufe0f Supported with the addition of an ESP8285 FrSky R9 (all others) \u274c Not compatible NamimnoRC Flash (STM32 version) \u2714\ufe0f Fully supported NamimnoRC Flash OLED(ESP version) \u2714\ufe0f Fully supported NamimnoRC Voyager (STM32 version) \u2714\ufe0f Fully supported NamimnoRC Voyager OLED(ESP version) \u2714\ufe0f Fully supported Axis Flying THOR \u2714\ufe0f Fully supported HGLRC Hermes \u274c Not compatible BETAFPV 2.4 Micro TX 1W \u2714\ufe0f Fully supported BETAFPV 2.4 Micro TX 500mW \u274c Not compatible BETAFPV 900 Micro TX \u274c Not compatible RadioMaster Zorro \u2714\ufe0f Fully supported RadioMaster Pocket \u2714\ufe0f Fully supported Jumper Aion T-Pro Internal \u274c Not compatible Jumper Aion Nano \u274c Not compatible Vantac Lite \u274c Not compatible ImmersionRC Ghost TX \u274c Not compatible QuadKopters 2.4 TX \u274c Not compatible SIYI FM30 \u274c Not compatible DIY TX \u2714\ufe0f Fully supported with the addition of an ESP8285"},{"location":"hardware/backpack/esp-backpack/#supported-vrx-backpack-targets","title":"Supported VRX-Backpack Targets","text":"Backpack Target Compatibility Tested? Happymodel EP1/EP2 \u2714\ufe0f Compatible Yes Happymodel ES900RX \u2714\ufe0f Compatible Yes Happymodel EP82 \u2714\ufe0f Compatible Yes BETAFPV Nano 2.4 \u2714\ufe0f Compatible No Flywoo EL24E \u2714\ufe0f Compatible No Flywoo EL24P \u2714\ufe0f Compatible No Ghost ATTO \u274c Not compatible N/A HappyModel PP \u274c Not compatible N/A HGLRC 2400RX \u2714\ufe0f Compatible No JHEMCU / HiYOUNGER EP24S \u2714\ufe0f Compatible No JHEMCU / HiYOUNGER SP24S \u2714\ufe0f Compatible No JHEMCU / HiYOUNGER RX24T \u2753 Unsure No Matek R24-S \u2714\ufe0f Compatible No Matek R24-D \u2714\ufe0f Compatible No Jumper Aion RX \u2714\ufe0f Compatible No Vantac 2.4GHz RX \u2714\ufe0f Compatible No Namimno Flash (ESP) \u2714\ufe0f Compatible No QuadKopters Nano \u2714\ufe0f Compatible No SIYI FR Mini \u274c Not compatible N/A"},{"location":"hardware/backpack/esp-backpack/#video-receivers-currently-supported-include","title":"Video Receivers currently supported include:","text":"VRX Module Support ImmersionRC Rapidfire \u2714\ufe0f Fully supported (Versions 1.2.5 of the rapidFIRE firmware and later) SkyZone SteadyView \u2714\ufe0f Fully supported TBS Fusion \u2714\ufe0f Fully supported (FTDI needed) Generic RX5808 Module (some) \u2714\ufe0f Fully supported FENIX Module \u2714\ufe0f Fully supported HDZero VRX4 \u2714\ufe0f Fully supported HDZero Goggles (built-in, no mods required) \u2714\ufe0f Fully supported"},{"location":"hardware/backpack/esp-backpack/#im-ready-to-proceed-what-do-i-do-next","title":"I'm Ready to Proceed. What do I do next?","text":"
If your TX module is already equipped with a TX backpack (see list above), your next step is to update the firmware of the backpack. Proceed to the TX Backpack Setup page for more details.
If you're using a DIY TX module and want to add a backpack to it, proceed to the Backpack Wiki.
For the VRX Backpack, you will need to first update the firmware on the ESP device. The firmware will highly depend on which VRX module you will use it on. Proceed to VRX Backpack Setup page for more info.
"},{"location":"hardware/backpack/esp-backpack/#backpack-usage","title":"Backpack Usage","text":""},{"location":"hardware/backpack/esp-backpack/#led-status-codes","title":"LED Status codes","text":"
Solid - The backpack is powered up and ready to receive packets.
Fast Continuous Blinking - WiFi Mode is active, and either the Access Point is ready for connection or the Backpack has connected to your Local WiFi Network (0.2.0; Home Network SSID and Password have been set).
Double Blink, Pause - The Backpack is in Binding Mode. Using the ExpressLRS Lua Script, press Bind, and the TX Backpack should bind with the VRX Backpack.
Pressing and Holding down the button during Power Up puts the device into Bootloader mode. From here, you can flash the firmware via UART using an FTDI dongle (USB to UART Bridge). The LED on the Backpack device will be SOLID when in this mode.
A Single Press during Normal or Binding mode will put the device into WiFi Mode.
A Single Press during WiFi Mode will put back the device into Normal Mode.
Just like any ExpressLRS device, you can set a Binding Phrase for both the TX Backpack and VRX Backpack so they automatically bind with each other during power up. This Binding Phrase can be the same as what you used with your other ExpressLRS devices or can be entirely different. The concept is the same.
Should you choose to bind manually, the procedure is as follows:
Make sure you didn't flash the VRX firmware with a Binding Phrase.
Power Cycle the VRX Backpack 3 times every ~30s. This interval gives ample time for your goggles and VRX module to power up and down more gracefully. If your VRX Backpack has a button, it can also be used to power-cycle the device by cycling between WiFi Mode and Normal mode 3x (as WiFi mode reboots the device).
The LED on the Backpack should now blink twice followed by a brief pause, then repeats, indicating it is in Binding Mode.
Using the ExpressLRS Lua script, navigate into the Bind option. Press it once, and the LED on both Backpacks should blink once and stay SOLID thereafter.
Your Backpacks are now bound and connected, and you can now use VTX Administrator on the ExpressLRS Lua script to sync your VTX and VRX modules.
When in Binding Mode (Double Blink & Pause) and no Bind packets have been received within 120s, the VRX Backpack will switch into WiFi Mode. This provides the users a means to enter WiFi Mode when their VRX Backpack doesn't have a Button.
"},{"location":"hardware/backpack/hdzero-goggles/","title":"HDZero Goggle VRx Backpack","text":""},{"location":"hardware/backpack/hdzero-goggles/#flashing-the-hdzero-goggles-backpack","title":"Flashing the HDZero Goggles Backpack:","text":"
After building the VRX firmware, copy the following 4 files into a folder named ELRS on the root of the SD card: - firmware.bin - partitions.bin - bootloader.bin - boot_app0.bin
Insert the SD card into the goggles and boot the goggles as normal.
The first step is to ensure that you have the backpack enabled in the Connections page in the goggles.
Scroll down to the Firmware page and select the Update ESP32 option.
The 4 firmware files will be flashed to the ESP32 backpack, and you should see a progress bar with the name of the current file being flashed at the start.
When the upload has completed, the page will display the version (or branch) of backpack firmware that is installed next to the update button.
To start the WiFi endpoint on the backpack, navigate to the Connections page of the goggles UI and select the Start Backpack WiFi option. If you have configured your backpack with your home WiFi credentials, it will attempt to connect to that and will fallback to creating an access point if it cannot connect, with the name ExpressLRS VRX Backpack and password expresslrs. The web UI will be available as http://elrs_vrx or http://elrs_vrx.local.
"},{"location":"hardware/backpack/hdzero-goggles/#binding-to-your-transmitter","title":"Binding to Your Transmitter","text":"
Attention
Since the goggles have a bind button in the Connections page in the UI, the option to enter binding mode by power-cycling 3x to bind has been disabled.
If you entered the same binding phrase as on your TX module and TX backpack when building the goggle backpack firmware, your device will connect automatically. You can validate this looking at the UID next to the Start Backpack Binding button on the Connections page in the goggle UI.
If you have NOT entered your binding phrase into ExpressLRS Configurator when building your backpack firmware, you can use the Start Backpack Binding option in the Connections page in the UI. Once you have selected this option, the goggles will wait for a bind message from your transmitter. To perform the bind from the transmitter, load the ExpressLRS Lua Script on your radio handset and select the [Bind] option there. When the message is sent and the goggles have received the bind message, they should display Success in place of the button text. If they do not receive a bind message, they will timeout after 2 minutes and display a Timeout message.
You can validate the binding by navigating to the Connections page and verifying that the correct UID is displayed next to the Start Backpack Binding button.
20x20 footprint and uses 0805 size SMD components. SMD components have been positioned on the PCB in a soldering iron friendly way. \ud83d\udeb8
ELRS Nano
The ELRS Nano RX is 18mm x 11mm and uses the same pinout as the Crossfire Nano RX. This allows for direct mounting to compatible flight controllers. \u26a0\ufe0f This PCB uses 0402 SMD components and will require a hot air rework station and probably a microscope. \ud83d\udd2c
Uses the ESP-01F for WiFi and a RFM95 for our business \ud83d\udd74\ufe0f
Requires ordering PCBs from Gerber files, a regulator chip, a few passives, a ESP-01F and a RFM95 (915/868MHz)
Multiple RX PCB designs are available \u2705
20x20 RX
discrete SMD antenna for Wifi and RF directly soldered to PCB
Target DIY_900_RX_ESP8285_SX127x_via_UART
20x20 RX 0805 - easier to build due to bigger SMD parts. PCB antenna for Wifi and u.fl connector for RF
Mini RX - the smallest form factor, lightest weight and lowest cost per PCB
If you need help soldering, please check out this video
"},{"location":"hardware/special-targets/diy-rx/#flashing-custom-rx","title":"Flashing Custom RX","text":""},{"location":"hardware/special-targets/diy-rx/#before-you-start","title":"Before you start","text":"
The steps for building are in each individual README.md for the RX of your choice
If you are using an ESP-12F instead of ESP-01F it is recommended to follow this tutorial but use the appropriate RX target \ud83e\uddd1\u200d\ud83c\udfeb
"},{"location":"hardware/special-targets/diy-rx/#get-it-flashed","title":"Get it flashed","text":"
Connect the serial adapter to GND, TX, RX, and the appropriate 3V3 or 5V.
Additionally, connect IO0 to GND to activate the bootloader and enable flashing
Quite some serial adapters have TX and RX swapped, mislabeled, or both \ud83d\ude38. Please double-check!
Finally, select the appropriate RX target, make sure your user defines are correct, and press Upload in PlatformIO
Possibly one of the biggest benefits of using ExpressLRS is custom hardware!
\ud83d\udcf6 Custom ESP 2.4 GHz TX
\ud83d\udce1 Custom Super Slim ESP 2.4 GHz TX
\u26a1 Custom 900 MHz TX
"},{"location":"hardware/special-targets/diy-tx/#custom-esp-24-ghz-tx-for-jr-module-bay","title":"Custom ESP 2.4 GHz TX (for JR module bay)","text":"
All of the info on this topic can be found here
"},{"location":"hardware/special-targets/diy-tx/#custom-super-slim-esp-24-ghz-tx-for-lite-module-bay","title":"Custom Super Slim ESP 2.4 GHz TX (for lite module bay)","text":"
The super slim is an evolution of the slim. It uses the same base hardware as the JR size one. It's the same size as an R9M Lite, and fits in all handsets with a lite module bay such as the X-Lite, X9 Lite, and Tango 2 (with the proper adapter). The rest of the info can be found here
"},{"location":"hardware/special-targets/diy-tx/#custom-900-mhz-tx-not-built-anymore","title":"Custom 900 MHz TX (not built anymore)","text":"
In the beginning, 900 MHz transmitters were sometimes built DIY. Today they're not. If you have one, the max output power defaults to 100mW, but with UNLOCK_HIGHER_POWER, that can be increased to 250mW.
PlatformIO is a prerequisite for developing custom hardware.
The hardware pinouts for ExpressLRS are kept at ExpressLRS/targets. Clone this repo within src/ of your ExpressLRS/ExpressLRS repo - or, if you run a build, it'll happen automatically.
In the RX and TX directories, you can find the pinouts and configuration for different layouts stored as JSON files.
Within targets.json, there are listed all the possible build targets for ExpressLRS.
To access your target's configuration, you must add a new entry to the targets.json file - mimic the closest existing one and change the values to match your hardware. It's critical the firmware field match your processor.
Select the matching build target from PlatformIO:
After you run a build, you should be met with a hardware configuration selector and your new configuration!
The Nuclear RX is designed to be as small as possible, using the same software target as the DIY Nano RX, and assembled by JLCPCB. It uses the 2400MHz band and the ExpressLRS firmware.
20x20 stack mounting with break-off tabs for compact applications
SMD Antenna
WiFi updating
Up to 500Hz packet rate
When you get your Nuclear RX, it will likely be on the latest release firmware. You'll probably have to update it to work with your TX. To update, follow the steps in the WiFi updating page. Alternatively, you can use betaflight passthrough should work, but the boot jumper must be bridged while applying power to the RX.
When building, use one of the DIY_2400_RX_ESP8285_SX1280_via_X targets. To use via_wifi, put your RX in binding mode, connect your computer to the RX WiFi, and hit upload.
LED Status Blinking Slowly Waiting for Connection Fast Double Blink Binding Mode Super Fast Blink WiFi Updating Mode Solid On Connected
If for some reason the RX needs to be in boot mode, bridge the jumpers as shown here:
The Nuclear TX is designed to be the same size as a FrSky slim module and use the same software target as the DIY Slim TX. It uses the 2400MHz band and the ExpressLRS firmware. There is also a case that fits a full size JR module bay with the same PCB.
If you ordered a Nuclear TX that wasn't fully assembled, these steps should help you finish it.
"},{"location":"hardware/special-targets/nuclear-hardware/#print-a-case","title":"Print a case","text":"
The latest version of the Nuclear TX STL files can be found here. Print the pieces in the orientation in the image and use support. Tree support in Cura works great. Keep in mind that PLA may melt if left in a hot car or in direct sunlight.
Slap it together as seen below. Solder the wires to the pin header in the order in the picture, then slide it in from the outside. The header should press in with a little force. Add some glue on the inside to keep it from sliding out when removing it from your handset. Put the SMA pigtail in the hole in the top and screw it down. Use a wrench to make sure it doesn't come loose when you screw on your antenna. Plug the U.FL into the module and route it under, and loop up around the side.
When you get your Nuclear RX, it will likely be on the latest release firmware. You'll probably have to update it to work with the RX you have. To update, follow the steps in the WiFi updating page. If your transmitter module ever becomes bricked from a bad upload, connect it with a serial adapter as shown here. MAKE SURE THE ADAPTER IS SET TO 3.3V; 5V WILL KILL THE MODULE! Use tweezers or solder to bridge the boot jumper while you power on the module to put it in boot mode. Use the target DIY_2400_TX_ESP32_SX1280_E28_via_UART.
Note
The version of the boards with the 6-pad layout for programming has the TX and RX named backward. The actual order of the pins is TX, RX, 3V3, GND, GND.
In normal state, the top right corner of the LUA will display - or C for RX connection status. in Warning or Critical Warning, the top right corner of the LUA will display a number to debug. As the LUA title will only show the current most critical warning only.
Converting the number on the top right corner to bits, you can decode the on going warnings.
Bit Status Solution 0 RX connection status connect a RX with TLM ratio other than Off 1 Reserved Status 2 Model Mismatch Warning set ModelMatch to Off or Select/Set the correct Model ID 3 Armed Status LUA should be closed to maximize sent Stick Command 4 Reserved Warning 5 Not While Connected Do not change this parameter when connected to a RX 6 Reserved Critical Warning 7 Reserved Critical Warning"},{"location":"info/advance-technical-info/#debug-logging","title":"DEBUG Logging","text":"Defines Description -DDEBUG_LOG Turn on debug messages, if disabled then all debugging options (starting with DEBUG_) are disabled -DDEBUG_LOG_VERBOSE Use DEBUG_LOG_VERBOSE instead (or both) to see verbose debug logging (spammy stuff) -DDEBUG_RX_SCOREBOARD Print a letter for each packet received or missed (RX debugging) -DDEBUG_CRSF_NO_OUTPUT Don't send RC messages over UART -DDEBUG_BF_LINK_STATS These debugging options send extra information to Betaflight in the LinkStatistics packet"},{"location":"info/glossary/","title":"Glossary","text":""},{"location":"info/glossary/#technical-words-with-explanations","title":"Technical words with explanations","text":"
Below you can find a list of terms you might not be sure about, as well as some common abbreviations:
BL: Bootloader, loads the FW
CRSF: TBS Crossfire, more specifically in our case most often referring to the communication protocol between TX and TX module and RX and FC respectively
ESC: Electronic Speed Controller
FC: Flight Controller
FW: Firmware
LQ: Link Quality, percentage of expected packets received. Our preferred method of measuring the quality of the control link
Lua: Means \"Moon\" in Portuguese. As such, Lua is the correct way to write and not all uppercase. The ExpressLRS Lua script can be installed on a OpenTX radio, to easily alter TX parameters like Packet rate, Telemetry ratio and Output power. But also shows if the radio (OpenTX) is communicating correctly with the module. ( e.g. 0:50, 0:150, 0:200 and so on.)
MCU: Micro Controller Unit, generally denotes an embedded system controller as opposed to big iron CPU
OSD: On Screen Display, refer to this page for instructions for setup in BF
OTA: Update your device Over The Air (WiFi)
OTX: OpenTX
RSSI: Received Signal Strength Indicator, \"arbitrary\" scaled version of RSSI dBm or LQ. Signal Health: LQI and RSSI Explained
RSSI dBm: Measure of power level measured in dBm. Basically, how strong the signal being received is
S.Port: SmartPort, sometimes referred to as sport. FrSky \"telemetry\" protocol. The S.Port also gets used for updating FrSky receivers.
To be continued.
"},{"location":"info/init-rate/","title":"Init Rate","text":""},{"location":"info/init-rate/#what-happened-to-the-lua-init-rate-option","title":"What happened to the Lua Init Rate option?","text":"
The Init Rate receiver Lua option was removed in ExpressLRS 3.4 in favor of automatic Init rate storage.
"},{"location":"info/init-rate/#what-is-init-rate","title":"What is Init Rate?","text":"
On boot, the receiver will listen for the Sync Packet starting with the fastest RF Mode or Packet Rate, down to the slowest, then cycles, until it finally Syncs and Binds. The Initialization Rate controls the packet rate that the receiver will start checking for the Sync Packet which can allow for near-instant connection when the receiver is powered up.
However, when the receiver is connected, it can not save its configuration without failsafing, which leads to a problem of how to store the connected rate as the Init Rate for use next power up. Unfortunately, this means you must failsafe the receiver once to configure its Init Rate.
"},{"location":"info/init-rate/#setting-init-rate","title":"Setting Init Rate","text":""},{"location":"info/init-rate/#method-1-switch-to-rate","title":"Method 1: Switch To Rate","text":"
Power on both a receiver and transmitter and wait for them to connect on any packet rate.
On the transmitter, select the packet rate to set the receiver's Init Rate to.
NOTE the packet rate must actually change for the setting to be sent. This means changing away from, then back to the desired packet rate if already connected at the desired rate.
The receiver briefly failsafes when changing packet modes and will save the target rate.
The receiver will now boot at the selected rate on next boot.
"},{"location":"info/init-rate/#method-2-transmitter-power-off","title":"Method 2: Transmitter Power Off","text":"
Power on the transmitter and select the packet rate to set the receiver's Init Rate to.
Power on the receiver and wait for it to connect. The LED on the receiver should be on solid / not blinking.
Power off the transmitter with the receiver still connected, bypassing any EdgeTX warnings along the way.
The receiver should failsafe and the LED will start blinking again.
The receiver will now boot at the selected rate on next boot.
"},{"location":"info/long-range/","title":"Long Range Competition","text":"
One of the most frequently asked questions that are asked by people who are interested in, but haven't yet tried ELRS is \"How far does it go, and at what power level?\"
The following table is a leaderboard of the current record holder for each packet rate, and the longest distance from home. Note that not every flight resulted in a failsafe at max range, so the link could go further in some cases. The leaderboard is separated into two different tables: 2.4GHz, and 900MHz. A leaderboard entry will only stay if it is the \"best\" for any specific packet rate, be it via power, range, or craft type.
To enter, press the pencil in the upper right corner of this page, and enter your record's info into the table, sorted by distance, and then PR it into the docs repository,
Anyone can add an entry to the table, and entries should include the:
Max distance from home
RF freq (900MHz / 2.4GHz)
Packet rate
Power level
If the link failsafed at max range
The pilot name
A link to your DVR on youtube
2.4 GHz Rankings900 MHz Rankings Max Dist. (km) Packet Rate (Hz) TX Power (mW) Type Failsafe at Max Range? Pilot Handle Link to DVR 101.3 50 2000 Wing No Snipes Link 43.7 150 250 Wing No Slickshot Link 40.6 50 25 Wing No Shawn U Link 35.0 250 100 Wing No Snipes Link 20.0 150 100 Wing Yes Pairan Link 18.9 150 50 Wing yes TitanDynamics Link 17.1 50 10 Wing No Denks Link 12.2 500 250 Wing No B\u00f6rner Link 10.2 500 10 Quad Yes mrscythe Link 10.0 50 250 Quad No Disnator Link 7.1 500 100 Wing No Bri'ish Link 7.0 150 50 Quad No Taufik Link 5.0 250 500 Quad No ZoFPV Link 4.6 50 25 Quad No febbyeka Link 3.0 150 25 Quad No Taufik Link Max Dist. (km) Packet Rate (Hz) TX Power (mW) Type Failsafe at Max Range? Pilot Handle Link to DVR 50.1 25 500 Wing No Yarillo Link 40.7 50 10 Wing No Leslie Yagin Link 13.1 50 100 Quad No Taufik Link 10.0 100 100 Wing No Flight Cub Link 6.0 100 50 Wing No Snipes Link 5.0 200 50 Quad No S0L4R Link 2.2 50 10 Quad No Mike Malagoli Link"},{"location":"info/signal-health/","title":"Signal Health","text":"
RSSI has become somewhat a generic term for how good a signal is, and every manufacturer can have their own scale, with most agreeing that \"100\" is the best, less than that is bad, and expect have RXLOSS at ???. This is an explanation of the signal metrics provided by ExpressLRS and how to understand their values.
"},{"location":"info/signal-health/#two-types-of-signal-health","title":"Two Types of Signal Health","text":"
There are two main types of signal information available from ExpressLRS: RSSI and LQI
RSSI - Received Signal Strength Indicator, this value indicates how loud \ud83c\udfba the reception is. RSSI must be above the sensitivity level to be understood. Units are dBm and start from 0 and go down as the volume gets lower (-130dBm hard limit).
LQI - Link Quality Indicator, this value indicates how much of the conversation is being understood and ultimately all that matters. Units are percent, with 100% being every packet is received, and 0% means no packets are being received.
Consider you're having a conversation in a quiet room. Your partner speaks loudly enough for you to hear, so the RSSI of their voice is above the sensitivity of your ears. You're going to understand the conversation because you're hearing every word. That's a 100% LQI-- you're receiving 100% of the words. Now imagine someone blows an air horn right in the middle of a sentence. The RSSI is still the same level, you still hear what you could make out at the same volume, you missed a word so the LQI is lower. The closer the volume of the conversation is to the background noise level in the room, the greater the chance is that you'll miss a word due to it getting mixed in with the background noise and lowering your LQI. Remember, LQI is all that matters. Your partner could shout as loud as they want but if you could hear every word anyway, the volume doesn't matter, you always heard every word.
"},{"location":"info/signal-health/#which-do-i-care-about","title":"Which do I care about?","text":"
Both really. LQI is most important because you can't fly if you're not getting packets. RSSI is important because it tells you how close you are to the radio receiver not being able to receive packets at all. I'd say if you have just one, pick LQI, because that tells you what percentage of packets are getting through and you get to make the decision if it isn't enough. What you can't tell from LQI alone is when that number is going to drop off a cliff, and it could happen extremely fast because you hit the RSSI sensitivity limit.
This is the lowest theoretical RSSI value that can be distinguished by the radio receiver. It is displayed next to the packet rate in the ELRS.lua script, as different packet rates and frequency bands have different sensitivity limits. Lower rates are more sensitive, -123dBm for 25Hz 915MHz up to -105dBm for 500Hz 2400MHz. This gives you the limit you know you can't fly below.
A sensible warning value is 5-10dBm higher than the sensitivity limit shown in the RF Mode Indexes (e.g. 250Hz=-108dBm, so -103dBm to -98dBm for the alarm).
RSSI and LQI are included already in the protocol used to communicate to the flight controller, so the \"RSSI Channel\" on the Receiver tab should be set to Disabled. RSSI_ADC / \"Analog RSSI input\" on the Configuration tab should also be disabled.
RSSI dBm - This is the true RSSI value we've talked about here, and is available on Betaflight after 4.1 (?) and iNav after 2.6 (?)
Link Quality - This is LQI discussed here, and has the same version requirements. Betaflight and iNav (LQ TYPE2 option) display add the RF Mode to this as well, e.g. 7:100 means mode 7 = 250Hz and 100% LQI.
RSSI Value - Or sometimes just RSSI. This is the old undefined units of Signal Strength value that everyone is used to with no idea what value is good or what value is too bad. What value you'll actually see here varies, even on ExpressLRS, and is covered in the RSSI Value OSD field section. It is not recommended to use this field unless you have to (e.g. DJI).
"},{"location":"info/signal-health/#rssi-value-osd-field","title":"RSSI Value OSD field","text":"
What appears in the RSSI Value field is based on what is selected as the RSSI Channel as ExpressLRS also sends LQI and RSSI as channels (AUX11/ch15 and AUX12/ch16 respectively). It is better to use the dBm or LQ OSD fields instead of this one if you can. DJI users are forced to use this due to it being the only field supported by their OSD. Changes to RSSI Channel in Betaflight requires a reboot to take effect.
Disabled is set as the \"RSSI Channel\" field in Betaflight - Displays RSSI dBm scaled as a percentage from -130dBm to 0dBm. Not recommended since what percentage of 130 is the Sensitivity Limit for your selected rate? Math!
AUX11/ch15 is set as the \"RSSI Channel\" - Simply LQI although the value might be slightly off due to rounding.
AUX12/ch16 is set as the \"RSSI Channel\" - Displays the RSSI dBm scaled as a percentage from the current Sensitivity Limit to -50dBm and is a decent indicator of how much range is left before the LQI cliff (0 here = Sensitivity Limit).
In iNav, the RSSI Value on the OSD is called RSSI (Signal Strength), and will always display 0. To show a filtered (by iNav) LQI in that field, set the rssi_source to protocol using the CLI with set rssi_source = PROTOCOL.
OSDs report the packet rate using an index instead of the actual rate, either as a RATE:LQ% or with rate in the hundreds digit such as 799 where 7 is the RATE and 99 is the LQ%. Handsets display the rate using the RFMD telemetry item.
SNR stands for Signal to Noise ratio and compares RSSI dBm to the RF background noise level and is in dB units (not dBm), higher is better. Notice it compares the background noise level and not the Sensitivity Limit. The reported value changes quite a bit from packet to packet and what values are good depend on what packet rate is being used. The RF chip can only approximate the noise level and only registers a value so high above the noise floor leading to this value getting clipped. Add to that, LoRa modulation can actually receive data below the noise floor to some degree.
All FLRC modes (F1000, F500, D500, D250) always report 0 for SNR.
TBS Crossfire I believe reports SNR * 4-- their values can be much higher.
ExpressLRS uses an averaged SNR to control dynamic power, with the following low/high values. The lowest possible SNR a packet can still be received is 5-10dB lower than the \"Raise Power\" limit.
"},{"location":"info/signal-health/#team24","title":"Team2.4","text":"Packet Rate \"Raise Power\" (bad) SNR \"Lower Power\" (good) SNR 500Hz 5.0dB 9.5dB 333Hz Full 5.0dB 9.5dB 250Hz 3.0dB 8.5dB 150Hz 0.0dB 8.5dB 100Hz Full 0.0dB 8.5dB 50Hz -1.0dB 6.5dB"},{"location":"info/signal-health/#team900","title":"Team900","text":"Packet Rate \"Raise Power\" (bad) SNR \"Lower Power\" (good) SNR 200Hz 1.0dB 3.0dB 100Hz Full 1.0dB 3.0dB 100Hz 1.0dB 2.5dB 50Hz 1.0dB 1.5dB D50 1.0dB 3.0dB 25Hz -3.0dB 0.5dB"},{"location":"info/signal-health/#how-far-can-i-go-on-x-mw","title":"How far can I go on X mW?","text":"
Very far? This question is usually used in place of the actual question \"Will I get good signal where I fly?\" which is impossible to answer.
ExpressLRS 2.4GHz can go over 40km at 250Hz 100mW on omnidirectional antennas with excellent LQI, or it can go 400m with less stellar LQI. By far the biggest factor in determining maximum range is direct line of sight. Blocking line of sight reduces RSSI dBm. A few trees or a building isn't going to keep you from flying due to ExpressLRS's excellent sensitivity even when line of sight isn't available, but range is reduced a bit for every physical object between you and the receiver. Piloting from an elevated position can eliminate some ground obstacles and provide a measurable boost in range.
The second largest factor is interference. Interference is the clobbering of our packets by outside sources, such as WiFi on 2.4GHz or other ISM transmissions on 868/915MHz, and is seen as a drop in LQI well before the sensitivity limit. Increasing TX power output is usually not the solution you'd expect, where each doubling in output power only might only add 10% to the usable range due to interference.
"},{"location":"info/signal-health/#team868team915-or-team24","title":"#Team868/#Team915 or #Team2.4","text":"
Unfortunately, there is a misconception about the 2.4GHz range thanks to other radio protocols on the market. ExpressLRS uses LoRa, which has had some amazing results on 2.4GHz. Again, 40km on 100mW 250Hz on 2.4GHz. The advantages of 2.4GHz is that the antennas are 2.5x smaller than 915MHz antennas, and there's more spectrum for ExpressLRS to hop around in, opening up the air for more pilots at once. 868/915MHz does have increased penetration and is the ultimate king of long range flying, but penetration difference may not be as great as you think. The high sensitivity of ExpressLRS receivers allows them to fly places you wouldn't dream of flying FSK-based 2.4 receivers such as FrSky ACCST/ACCESS, FlySky AFHDS2A, Spektrum DMX, or Redpine.
We have all heard the stories of racers powering up his TBS crossfire full module at 2W and causing people to fail-safe during a race. This happens because the 868/915MHz band has limited bandwidth. The solution for this is to use a low power mode during races, so you do not blast anyone out of the sky. 2.4GHz does not have this issue. Flite Test has a world record of having 179 RC airplanes in the sky using 2.4 GHz.
2.4GHz LoRa can also handle WiFi noise very well. Studies have been conducted with the coexistence of WiFi and LoRa bands.
868/915 does not have to worry about WiFi signal but it does have to worry about cell towers and other RF noise. You are fighting against thermostats, fire systems, burglar systems and any other device running on that band.
Telemetry Burst describes the allocation of telemetry packets in ExpressLRS added in #472. There are two types of packets, LINK and DATA. LINK is the standard link statistics and is always available, and DATA is \"Advanced Telemetry\" which is telemetry coming from the flight controller and shares bandwidth with MSP transfers. Burst mode attempts to maintain a minimum rate of LINK packets and use the rest of the available telemetry slots for DATA.
The LINK rate chosen was one every 512ms, roughly 2 per second but slightly higher to allow more rates to have an additional burst packet at lower ratios.
"},{"location":"quick-start/ardupilot-setup/","title":"Ardupilot Setup","text":""},{"location":"quick-start/ardupilot-setup/#ardupilot-serial-setup","title":"ArduPilot Serial Setup","text":"
ArduPilot Firmware must be 4.1 or higher to run CRSF protocol. As with any serial-based receiver, you need to attach the TX/RX pads to a UART on your flight controller, then enable Serial RX in the corresponding UART in ArduPilot. In mission planner, you will need to go to the config tab -> parameter tree
Our packet rate is different from the ArduPilot CRSF packet rate, and ArduPilot will keep on reporting the mismatch, but recently they have an option to suppress the report. Currently ArduPilot provide a way to suppress this notification with the parameter below. (this will not cause any effect to RC link or telemetry Link.)
RC_OPTIONS turn on Bit 9th which is \"Suppress CRSF mode/rate message for ELRS systems\".\n
Another bit you should enable on RC_Options is the use of 420K baud rate. ExpressLRS receivers use 420K Baudrate to talk to flight controllers.
Once you have set the parameter above, power-cycle the flight controller by disconnecting and reconnecting your battery and USB. ArduPilot should automatically run with ELRS, but if it fails, set RC_PROTOCOL parameter 9th bit to 1 (CRSF option) and set the other parameter as below:
ArduPilot default flight modes channel is channel 8, but ELRS 8 position channel is on channel 12 (in hybrid switch mode). you will need to set your handset to use channel 12 as flight modes and set ArduPilot parameter:
FLTMODE_CH=12\n
if you are using Wide Switch mode (only available in ELRS V2 and above), you can use any channel for your 8 flight mode selection (beside channel 15 which is LQ and channel 16 which is RSSI)."},{"location":"quick-start/ardupilot-setup/#ardupilot-rssi-and-link-quality","title":"ArduPilot RSSI and Link Quality","text":"
To get RSSI and LQ shown in OSD (in %) set:
RSSI_TYPE = 3 (ReceiverProtocol)\n
and go to your OSD tab, and place your RSSI and LQ element where you want them to be.
If you feel any delay or lag in the control, check the RX connection to the Flight Controller. On some Flight Controllers you have to use full DMA supported input pin.
You can select a short and simple Binding Phrase for your devices before flashing or updating using the field in the ExpressLRS Configurator.
Binding Phrase Field
Alternatively, you can also change the Binding Phrase via the WebUI if your device has WiFi capabilities and is already updated to ExpressLRS 3.0 or newer. See this page for the WebUI User's Guide.
Binding Phrase Field in the WebUI
We recommend using a unique phrase with at least 8 alpha-numeric characters. The best candidate is your Pilot Handle. This phrase need not be complicated or super-secret as it isn't a password or encryption key.
Is my binding phrase a secret? (click/tap to expand)
No, just like what channel your VTX is on is not a secret. The binding phrase is not for security, it is for anti-collision. If everyone kept their VTX channel a secret, the chances of you blasting someone out of the sky accidentally are pretty high. To provide the best chance of not interfering with other pilots and them not interfering with you, be sure you're not using the same dumb bind phrase as someone else. Express your style and some creativity with a hilarious or saucy bind phrase.
For traditional binding to work, a Binding Phrase must not be set, at least for the Receiver.
Updated on 3.4.0
Any Receiver flashed with 3.4.0 or newer can be put into Bind Mode, even with a set Binding UID.
Notice
A Receiver flashed or set with a Binding Phrase WILL NOT initiate Manual Binding mode, however many times you try the procedure below. You must first reflash the receiver with the Binding Phrase field disabled and/or unset. Why would you not use a bind phrase though if you're already having to flash the RX anyway?
The Receiver LED should also be blinking when powered up.
Receiver LED doesn't Blink (click/tap to expand)
Here are the things you can do if the Receiver is in Bootloader Mode:
Check if the Boot button on the Receiver is being pressed or if it's damaged.
If the button is being pressed or pinched, remove the cause of the pressing or pinching. Heatshrink can sometimes press a button on the receiver.
If the button is damaged, remove the button or replace the receiver with a better one. Consider asking the seller for a replacement.
If the receiver doesn't have a Boot button and instead has a Boot pad, check if the Boot pad is not connected to a Ground pad.
If the Boot pad is connected to a Ground pad, disconnect or remove the connection.
Disconnect the RX and TX wires of the Receiver from the Flight Controller. Reconnect power to the drone or aircraft. Observe the LED on the Receiver once again.
If it starts Blinking Slowly (500ms Blink Pattern), you will need to move the receiver wiring to a different UART.
If the other UART is occupied by another peripheral, disconnect it and swap places with the Receiver.
If there is no other Full UART, you can try wiring a Pull-up Resistor: Connect a Resistor (300 Ohm to 1k Ohm value; a lower value is more effective) between this UART's RX pad and either a 5v or 3.3v pad as shown below:
If you are using any of the Digital FPV systems like the DJI FPV Air Unit, Caddx Vista or DJI O3 Air Unit, and you wired or connected all six wires to your Flight Controller, you will need to remove the SBUS/DJI HDL wire.
The procedure is as follows:
Power off your transmitter/radio.
Power-cycle the receiver 3 times.
Supply power to the receiver.
The receiver LED lights up.
Turn it off within 2 seconds.
Repeat 2 more times.
Caution
This step is best done using a LiPo flight pack, so make sure you've wired your flight controller properly and checked for any shorts. You don't want to let out the blue smoke!
Make sure the LED is doing a quick double-blink, which indicates the receiver is in bind mode.
Power up your transmitter/radio and use the [BIND] button on the ExpressLRS Lua script, which sends out a binding pulse. The Popup will briefly show up and then disappear.
If the receiver LED turned into a solid light, it's bound!
"},{"location":"quick-start/binding/#updated-binding-procedure-since-expresslrs-340","title":"Updated Binding Procedure since ExpressLRS 3.4.0","text":"
With PR#2542 being part of the 3.4.0 update, users now have the following methods to bind an ExpressLRS receiver with a TX module:
Binding Phrase, flashed or set (via the WebUI) into both devices.
3x Power Cycle.
Bind Receiver button in Betaflight Configurator 10.10 (or newer) Receiver Tab (bind_rx CLI command also works). This will ONLY work if your flight controller is flashed with Betaflight 4.5.0 or newer.
1.5s Button Press on the Receiver itself (or Boot pad shorting to Ground).
With the last 3 methods, the Receiver LED will blink twice, pause then repeats, until the Bind is established indicated by a solid LED light. Pressing [Bind] in the ExpressLRS Lua Script should establish the Bind, per the Traditional Binding Procedure above.
After a Receiver is bound using any of the methods above, users can put the Receiver back into Bind Mode anytime following any of the last 3 methods above. The Bind will persist or stay with the receiver until another Binding Procedure is initiated, with any of the methods above.
To cancel Bind Mode, a reboot or power-cycle is needed, or Binding the receiver with a Transmitter. The old Binding Info will be used if the receiver is rebooted without the new Bind.
A Lua Script or WebUI option can be toggled to make the Bind volatile upon power-cycle or reboot. Volatile Bind means that the Bind is only valid while the receiver is powered up. Once the receiver is power-cycled or rebooted, the Bind information is wiped and the receiver will boot up in Bind Mode.
Using the ExpressLRS Lua Script, look for a C in the top-right corner of the screen which indicates TX module and Receiver are Connected and Communicating.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, go back to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
A C in the top-right corner should be visible indicating TX module and Receiver are connected and Communicating.
Model Mismatch (click/tap to expand)
If the ExpressLRS Lua Script is showing a C in the top-right corner alright, but then that line disappears and is replaced with a line saying \"Model Mismatch\", do not worry. ExpressLRS has detected that the set Model ID in the Receiver is different from the Receiver ID set in the current Model in your Radio Model Configuration.
This is also indicated by the Receiver LED as 3 fast blinks then a pause:
If you've deliberately set up Model Matching following this page, make sure your settings are correct.
If the Model Match item in the ExpressLRS Lua is set to On, and you do want to use the Model Matching Feature, briefly set it to Off, then set it back to On to assign the current Receiver and Model ID to the Receiver.
Otherwise, simply set the Model Match item to Off.
If Model Match is set to Off, briefly set it to On and after a second or so, set it back to Off. This should clear the Model Match ID in the receiver.
This must be done while the TX module and Receiver are both powered up and connected/bound.
This page aims to explain only the key options in ExpressLRS Configurator you may need for your initial setup. For a full description of all the options available, see the User Defines page.
Some of these options are present on both the TX and RX Targets. It is important that these options match to both the TX module and receiver in order for them to bind. team2400 and team900 also share a few options and some options are unique to that frequency band. Shown below are common options available on team2400 and team900 TXes respectively.
Entering a binding phrase allows you to skip the binding step with your receivers-- you want this set. Any transmitter using the same binding phrase will connect to any receiver with the same binding phrase, so be unique. Limit to alphanumeric phrases conforming to the Latin alphabet. Receivers flashed with firmware builds that do not have binding phrase enabled will require binding with the traditional binding method.
Set these to have the \"WiFi Update\" mode try to connect to an existing WiFi network using these credentials. Configure them with the WiFi settings for where you'll be flashing your firmware, to save the step of switching WiFi networks on your computer or phone during the flashing process. If the device is unable to connect to this network, it will create its own network."},{"location":"quick-start/firmware-options/#other-options","title":"Other Options","text":"
UNLOCK_HIGHER_POWER \n
Enables higher output power for devices that support it but will possibly melt themselves to give it to you. Do not enable it without first updating your cooling setup or verifying the device isn't overheating when running at your chosen power.
UART_INVERTED\n
This only works with ESP32 based TXes. Almost all handsets require UART_INVERTED on, such as the FrSky QX7, TBS Tango 2, and RadioMaster TX16S. For T8SG V2 or Deviation firmware turn this setting off."},{"location":"quick-start/firmware-options/#receiver-only-options","title":"Receiver Only Options","text":"
Note
Configuration of Receivers should match the configuration of the Transmitter Module for Sync/Binding to happen between devices.
Most of the options listed above for the Transmitter Modules also apply to Receivers. The following are options specific to receivers that you might need.
If using an a flight controller that only has an RXI / SBUS (RX inverted) pad, turn on this option to invert the CRSF output from the receiver to be able to use that pad. This does not convert the output to SBUS, it is inverted CRSF, so CRSF should still be the receiver protocol selected in the flight controller software. ESP-based receivers only.
USE_R9MM_R9MINI_SBUS\n
On the R9MM/R9Mini only, this changes the pin used to output CRSF from the receiver the two side pins (A9 and A10) to the pin labeled \"SBUS\" on the RX, which is inverted. Similar to RCVR_INVERT_TX this does not convert the output to SBUS protocol, so CRSF should still be the receiver protocol selected in the flight controller software."},{"location":"quick-start/firmware-options/#should-i-turn-these-offon","title":"Should I turn these off/on?","text":"
NO_SYNC_ON_ARM\n
Sync packets are one packet out of every 5 seconds when armed. Leave this off unless running telemetry ratio Off because you won't be able to reconnect after a failsafe while armed if this is on.
LOCK_ON_FIRST_CONNECTION\n
Keeps the receiver on the last packet rate it was on if it failsafes, instead of trying every packet rate to reconnect. Should be left on."},{"location":"quick-start/firmware-options/#full-list","title":"Full List","text":"
For a complete list of User Defines, head over to the User Defines page.
Done! It's time to flash the firmware on your transmitter
The ExpressLRS team works closely with manufacturers to review and test hardware. It isn't until after testing that a specific ExpressLRS Configurator Target is added.
Hardware not found in the ExpressLRS Configurator means the hardware did not pass requirements, or the manufacturer has chosen not to collaborate. In this case, the manufacturer should be contacted for tech support.
Generic targets are meant for pre-production or DIY hardware. Off-the-shelf Hardware should be using Hardware-specific targets.
TL;DR: Check the Configurator before purchasing, and support manufacturers that support open source and the ExpressLRS project.
"},{"location":"quick-start/getting-started/#welcome-to-the-quick-start-guide","title":"Welcome to the Quick Start Guide","text":""},{"location":"quick-start/getting-started/#prerequisites","title":"Prerequisites","text":"
You should be comfortable navigating through your Radio Handset firmware (OpenTX/EdgeTX) and setting up models, as the guide on this website mainly covers setting up your radio for you to be able to use ExpressLRS.
Likewise, you should also be comfortable with your Flight Controller firmware (Betaflight, INAV, etc), as the guide only covers setting up your ExpressLRS receiver to work with your flight controller firmware.
"},{"location":"quick-start/getting-started/#what-should-i-do-first","title":"What should I do first?","text":"
So you got your ExpressLRS Hardware, be it a new Radio Handset with an Internal ExpressLRS module, or an External ExpressLRS Module; and a set of ExpressLRS Receivers in a bundle or a Bind-and-Fly drone with the Receiver already wired up. Where do you start?
Here's our recommendation:
Transmitter SideReceiver Side
Setup your Radio
Check the TX Firmware Version
Update the TX Module
Wire your Receiver
Configure your Flight Controller
Check the Receiver Firmware Version
Update the Receiver Firmware
After both of these, you can then proceed with the following:
Bind
Do the Bench Test
Other Radio and Flight Controller Configuration
Fly!
"},{"location":"quick-start/getting-started/#how-to-use-or-navigate-through-the-guide","title":"How to Use or Navigate through the Guide","text":"
This User Guide is organized to cater to both new and seasoned users of the system. The navigation menu on the left is arranged to start with getting the ExpressLRS Configurator installed, an Explanation of the Options available, Steps concerning the Radio and TX module, FC and Receiver setup, a \"Before you Fly\" page and a Troubleshooting page.
You can also use the Footer Navigation shown below to go through these steps:
For a specific hardware flashing guide, the pages are either in the Updating Receivers or Updating Transmitters sections organized semi-alphabetically.
You can also use the Search Bar for any topic or info you are after:
Longer pages have a Table of Contents menu found on the right-hand side of the page.
Each Updating Method available for a device can be accessed by clicking on their respective Tab.
We hope these pages will help you get started with ExpressLRS and experience one of the best and most innovative RC links in the hobby.
If you have other questions or concerns, or maybe you need further help that isn't covered by this Guide, head over to our Discord Channel!
ExpressLRS Discord
"},{"location":"quick-start/getting-started/#where-are-the-video-guides","title":"Where are the Video Guides?","text":"
Due to the current fast pace of development, video guides often end up outdated faster than intended. Specific hardware guides sometimes use pre-release firmware targets or targets intended for different hardware which can confuse when specific firmware targets are added.
We will be adding a separate videos section soon, but for now, until we find high-quality, relevant and applicable guides, you are on your own. Please take note of the publication date for these videos to make sure they are still relevant.
"},{"location":"quick-start/installing-configurator/","title":"Installing the Configurator","text":"
Download the latest ExpressLRS Configurator application for your platform, following the instructions written by jurgelenas.
ExpressLRS Configurator
The targets for each of the supported hardware can be seen on the individual device pages. Use the navigation menu on the left to get to the specific hardware page.
On the next page, you will find the different Firmware Options you can set along with their explanations.
"},{"location":"quick-start/led-status/","title":"LED Status","text":""},{"location":"quick-start/led-status/#receivertransmitter-led-status","title":"Receiver/Transmitter LED Status","text":"
ExpressLRS uses the LED to communicate the status of the transmitter/receiver.
The conditions and status LED are as follows:
Receiver Single Color LEDReceiver RGB LEDTransmitter RGB LED LED Indication Status Solid on Connected to a transmitter, or bootloader mode enabled Double blink then pause Binding mode enabled Slow blink 500ms on/off Waiting for connection from transmitter Triple blink then pause Connected to transmitter but mismatched model-match configuration Medium speed blink 100ms on/off Radio chip not detected Fast blinking 25ms on/off WiFi mode enabled LED Indication Status Rainbow fade effect Starting Up Green heartbeat Web update mode enabled Slow blink 500ms on/off Waiting for connection from transmitter Red flashing 100ms on/off Radio chip not detected Orange Double blink then pause Binding mode enabled Orange Triple blink then pause Connected to transmitter but mismatched model-match configuration Solid single color Connected to a transmitter, color indicates packet rate No Light Off or in Bootloader Mode LED Color 2.4GHz Packet rate (Hz) 915/868MHz Packet rate (Hz) Red F1000 200 Yellow F500 Yellow-Green D500 100 Full Green D250 100 Cyan 333 Full Light Blue 500 50 Blue 250 25 Blue-Purple 150 Purple 100 Full D50 Magenta 50 LED Indication Status Rainbow fade effect Starting Up Green heartbeat Web update mode enabled Blue heartbeat Bluetooth joystick enabled Red flashing 100ms on/off Radio chip not detected One Orange flash every second No handset connection Solid single color Connected to receiver, color indicates packet rate Fading single color No connection to receiver, color indicates packet rate LED Color 2.4GHz Packet rate (Hz) 915/868MHz Packet rate (Hz) Red F1000 200 Yellow F500 Yellow-Green D500 100 Full Green D250 100 Cyan 333 Full Light Blue 500 50 Blue 250 25 Blue-Purple 150 Purple 100 Full D50 Magenta 50"},{"location":"quick-start/pre-1stflight/","title":"Before First Flight","text":"
Prior to your first ExpressLRS flight, you may want to do a few tweaks to your setup to ensure a fun and trouble-free ExpressLRS experience!
By default, ExpressLRS uses limited bits for AUX switches (1-bit for AUX1, and 3-4 bits for other AUX channels), which results in very coarse resolutions up to 8 or 16 positions to Betaflight/INAV on the AUX channels. In most cases, it is enough (especially on a multirotor), but if you need finer resolution, enabling the Wide Switch Mode option expands the resolution of AUX2-AUX8 up to 128 positions. For more information, read the switch modes page.
One important thing to keep in mind is that Aux1 should be used as your Arming switch, with LOW (~1000us) as disarmed and HIGH (~2000us) as armed. AUX1 is the low-latency switch, sent with every packet, and only supports on/off (2-position) operation. ExpressLRS uses AUX1 to determine if your model is armed and this is the most reliable way to be able to tell your model to disarm. If your arm switch is in another aux channel, it may be several packets before that switch is transmitted, and there's no guarantee that the Receiver will receive that packet.
WARNING
Please make sure your ARM mode is on the AUX1 channel, and the armed state is set ~2000.
"},{"location":"quick-start/pre-1stflight/#rssi-and-link-quality","title":"RSSI and Link Quality","text":"
To get RSSI and Link Quality displayed in the OSD, set both RSSI Channel and RSSI_ADC to Disabled. Both settings can be found in the Receiver Tab.
On the OSD Tab, use the Link Quality and RSSI dBm value elements (not \"RSSI Value\"). INAV has put this in the CRSF RX Statistics section.
If you wish to enable the RSSI dBm warning, you'll have to change the alarm level using set osd_rssi_dbm_alarm = -100 in CLI. A sensible value is 5-10 higher than the sensitivity shown in the ELRS.lua for the packet rate (e.g. 250Hz=-108, so -103 to -98 for the alarm).
Likewise, if you want to change the LQ Alarm level, you can use the CLI command set osd_link_quality_alarm = x with x as your LQ Alarm level. 60 is a good value to start with.
If you're using DJI Goggles V1 or V2 (unrooted/unmodded), you're required to use \"RSSI Value\" as the OSD element. Therefore you have to decide between LQ or RSSI, by selecting either AUX11 (LQ) or AUX12 (RSSI) as RSSI Channel on the Receiver tab (see images above).
For digital FPV systems with \"Canvas Mode\" or full native OSD support via MSP DisplayPort (Walksnail Avatar, HDZero, DJI O3), you can treat the config as any analog FPV setup. Therefore, you do NOT have to set RSSI Channel (leave it at disabled).
More information about signal metrics can be found in this great article on signal health.
"},{"location":"quick-start/pre-1stflight/#bench-test","title":"Bench Test","text":"ExpressLRS Bench Test
Shown above is a Bench Test to determine if you're getting a good signal from your radio. This aims to provide you with information on whether you should check your antennas (particularly the R9's Super 8) or if you have good hardware overall.
Set your ExpressLRS module to the lowest power level using the Lua script. The packet rate doesn't matter much here.
Put your radio 1m (3ft) from your receiver and power it up. Make sure the receiver and TX module antennas are oriented in the same way. (You might want to disconnect your VTX/Air Unit temporarily, put VTX in pit mode, or have a fan blowing on it).
Using your OSD or the Telemetry Page of your radio, take note of the RSSI dBm or the 1RSS telemetry data.
On the 900MHz hardware, a value of -20dBm or thereabouts is a good indication your hardware is in working order. On the 2.4GHz hardware, around -40dBm up to -25dBm should be good. If you're getting lower numbers than these (closer to 0 is higher and better), here are a few things you could check:
The ExpressLRS module antenna could be loose. On some 3D printed module cases, the print may be too thick at the part where the pigtail's RP-SMA/SMA end would be attached; if so, tighten the nut on the RP-SMA/SMA to give the antenna some more space to get tightened up.
The antenna pigtail may be damaged or not connected properly to the module's mainboard.
On receivers using SMD antennas, expect lower values than those equipped with wire antennas. If the receiver with the SMD antenna has heat shrink, enclosed in a whoop canopy, surrounded with carbon parts or buried inside a plane/fixed wing, expect some more attenuation of the signal.
The Super 8 antenna from FrSky, which most of the R9Ms came with is notorious for being faulty or would degrade from just a few weeks of use. Replace it or as a temporary fix, solder all around the junction where the coax shielding and the RP-SMA meet. Another failure point is the connection of the coax to the active elements itself. It would seem okay, but due to the twisting of the antenna, the connection could be severed.
Super8 Antenna's common points of failure
Check if there aren't any missing components in your receivers, like the RF filter (can be found near the antenna or UFL). Also check if the SMD antenna is not broken or damaged and it's soldered in properly.
Most DIY modules require moving the 0-ohm resistor on the E28 from the PCB antenna side towards the UFL side. A solder bridge will work just fine as well, but make sure it is on the correct pads.
Swap out antennas on the receiver and/or the TX module; Most ExpressLRS receiver antennas use IPEX 1/UFL connectors and as long as the frequency tuning of the antenna is appropriate for the frequency you're in, it should work. You can also use old 2.4GHz WiFi Router antennas for your 2.4GHz modules, but avoid those that are dual-band. Also, make sure that the connector on the antenna is the appropriate one (RP-SMA on R9 modules; SMA on most off-the-shelf ExpressLRS modules)
Blackbox is handy for evaluating the performance of the RF link for a flight. Set your BB to debug mode RC_SMOOTHING_RATE, which will capture the rate that Betaflight is receiving RC Packets from the RX.
The RX transmits a subset of telemetry it receives from the flight controller. Disabling certain messages only works if the flight controller firmware does support it. For Betaflight this is possible with the telemetry_disabled_* CLI settings:
Since telemetry messages are sent with low priority it may take some time to transmit the data. The telemetry rate in the Lua settings script controls how often a telemetry message should be sent. So a ratio of 1:2 means that every second message is a telemetry message, so the telemetry data is transferred very fast. A ratio of 1:64 means that only one of 64 messages is a telemetry message and so the transfer happens much slower.
The refresh rate also impacts the transfer speed. 50 Hz is slower compared to 200 Hz. So if you need a fast telemetry update rate choose a high refresh rate, and a ratio that favors telemetry messages e.g. 200 Hz and 1:16 usually works well. For detailed information on telemetry bandwidth at different rates and ratios, see this page on telemetry bandwidth.
To finish the telemetry setup open the telemetry page on your transmitter and select \"Discover new sensors\" and wait for the list to fill.
* Indication
Notice, that there is a * sign for each row. This star indicates that this telemetry sensor was just updated.
[ ] Indication
If you see a row that does not change, and the name of the row is in square brackets it means that this sensor was not updated for some time.
The first values (including RSSI and link quality) should always be updated (flashing stars). If this does not happen multiple times per second the transmitter will issue a \"telemetry warning\". To prevent this warning use the setting TLM_REPORT_INTERVAL_MS.
It should look like this (and if it does not there is something wrong with your setup):
The remaining values are updated at a different rate (depending on refresh rate and telemetry ratio). So if you use 50 Hz and 1:64 it will happen slowly, and the update takes multiple seconds for each sensor:
If you use 200Hz and 1:2 Tlm ratio the stars will not even blink because the update happens so fast:
To configure Betaflight from your transmitter it's possible to use the Betaflight lua scripts. This requires the telemetry feature enabled for the RX+TX. If the telemetry page of OpenTX does not show regular updates for all sensors the LUA script will also not work.
To get a responsive UI configure ExpressLRS for fast data transfer so make sure to use something like 200Hz/500Hz with 1:2 Tlm and a serial baud rate of 400000. Currently, MSP is limited to 50Hz on 115200 Baud and does not work with a 500`` Hz refresh rate. The initial VTX tables download does take some time - but is cached after that.
If you get a \"retrying\" message while saving changes it means that the Lua script did not receive a response fast enough. But the change usually still goes through so try reloading the page to check if the change was saved. With the recommended settings this does not happen but with slower settings, it could happen.
"},{"location":"quick-start/troubleshooting/","title":"Troubleshooting","text":""},{"location":"quick-start/troubleshooting/#general-troubleshooting","title":"General Troubleshooting","text":""},{"location":"quick-start/troubleshooting/#my-rx-and-tx-are-bound-but-fc-is-not-responding-to-inputs-and-i-can-only-see-10-telemetry-sensors","title":"My RX and TX are bound, but FC is not responding to inputs, and I can only see 10 Telemetry sensors","text":"My RX and TX are bound, but FC is not responding to inputs, and I can only see 10 Telemetry sensors
Check whether you have wired the receiver correctly and that RX and TX wires aren't swapped.
Also, check that you have the correct SerialRX configuration. You might want to revisit the FC Preparation page for the Flight Controller setup.
Also, make sure that the UART where you connected the receiver doesn't have inversion and it's in full duplex mode. You can also try a different UART.
"},{"location":"quick-start/troubleshooting/#my-rx-and-tx-are-bound-and-im-getting-more-than-10-telemetry-sensors-on-my-radio-but-im-not-getting-stick-inputs","title":"My RX and TX are bound, and I'm getting more than 10 Telemetry sensors on my Radio, but I'm not getting stick inputs","text":"My RX and TX are bound, and I'm getting more than 10 Telemetry sensors on my Radio, but I'm not getting stick inputs
This is due to a model mismatch between the receiver and the TX module. The LED on the receiver will have 3 short blinks and then a 1s pause indicating the mismatch.
To \"fix\" this, you might want to turn On Model Matching. Please see Model Matching for more notes.
Another thing to check is whether you have enabled RCVR_INVERT_TX option for your receiver firmware. This option is intended for FCs that don't have any other UARTs available (e.g. AIOs) other than an SBUS pad. See this section for more details: Output Inverting.
For the R9mm/mini receivers, make sure you didn't enable USE_R9MM_R9MINI_SBUS in your firmware option. See Output Inverting for what this option do.
"},{"location":"quick-start/troubleshooting/#my-rx-and-tx-are-bound-and-im-getting-stick-inputs-but-i-can-only-get-10-telemetry-sensors","title":"My RX and TX are bound, and I'm getting stick inputs, but I can only get 10 Telemetry sensors","text":"My RX and TX are bound, and I'm getting stick inputs, but I can only get 10 Telemetry sensors
Check if you have Telemetry Feature enabled in your FC Configuration.
Also, verify the RX pad from the receiver is connected properly to a TX pad in the FC in the same UART as the TX wire from the receiver.
Also, make sure you have deleted and rediscovered the sensors. It's good to increase the TLM Ratio so the acquisition of the sensors will be faster.
This could also mean you'll have to update your FC Firmware to a more recent version that supports at least the CRSFv2 protocol.
"},{"location":"quick-start/troubleshooting/#i-think-my-receiver-and-transmitter-are-bound-as-the-led-on-the-receiver-is-solid-but-i-do-not-have-stick-inputs-or-rssi-on-the-radio","title":"I think my Receiver and Transmitter are bound, as the LED on the Receiver is solid. But I do not have stick inputs or RSSI on the radio.","text":"I think my Receiver and Transmitter are bound, as the LED on the Receiver is solid. But I do not have stick inputs or RSSI on the radio.
You are not bound. Your Receiver is probably in bootloader mode.
Make sure you have unbridged the boot pads if you flashed it via passthrough.
Turn off your Radio and if the LED is still solid, but boot pads aren't bridged, the UART where the receiver is on is putting it into bootloader mode unintentionally. This is primarily caused by pull-down resistor on the RX pad to aid with SBUS line inversion. To verify it is the case with the UART, disconnect the RX and TX wires from the FC UART, and it should start blinking slowly then after the set interval (20s - 30s by default), it will blink fast indicating it's on WiFi Mode. To \"fix\" the issue, you have two options:
Move the receiver into another free UART.
If there's no other UART, wire up a resistor with a value between 300 Ohm to 1k Ohm between a 3.3v pad and the FC's RX pad (where the TX from the receiver connects to).
If, however, despite unsoldering the TX and RX wires, the LED is still solid, you probably have a soft-bricked receiver due to a failed WiFi flash as a result of not letting the receiver reboot normally. Follow the unbricking procedure to recover the receiver.
"},{"location":"quick-start/troubleshooting/#my-osd-is-showing-lq-00-and-rssi-dbm-at-130-dbm-but-i-have-stick-inputs-and-more-than-10-telemetry-sensors","title":"My OSD is showing LQ 0:0 and RSSI dBm at -130 dBm, but I have stick inputs and more than 10 Telemetry sensors","text":"My OSD is showing LQ 0:0 and RSSI dBm at -130 dBm, but I have stick inputs and more than 10 Telemetry sensors
Check whether you have RSSI Channel set to either Aux11 or Aux12. If you do, set it to disabled.
If it's still not fixed with that, check if you have RSSI ADC enabled. If so, set it to disabled.
"},{"location":"quick-start/troubleshooting/#my-osd-is-showing-lq-31-sometimes-lq-39","title":"My OSD is showing LQ 3:1 sometimes LQ 3:9","text":"My OSD is showing LQ 3:1 sometimes LQ 3:9
Move your LQ OSD element around as it could be being obstructed by another element or it's too far to the right of the preview.
"},{"location":"quick-start/troubleshooting/#i-am-getting-telemetry-lostrecovered-and-is-getting-annoying","title":"I am getting Telemetry Lost/Recovered and is getting annoying","text":"I am getting Telemetry Lost/Recovered and is getting annoying
There's a handful of reasons why this is occurring, and if you have newer handset/radio, it shouldn't happen at all unless you're flying very far away using a receiver without an amplifier for its Telemetry signal (e.g. the EP receivers).
You're on an X9D(+) or a QX7 with subpar inverter chips. Check this page on how to remedy it.
You're on an early version of the Happymodel Slim Pro. Check this FB post for the fix from manufacturer.
You're using a 2018 ACCST R9M, while also using a Radio with 400k or higher Baud rate. You will either have to lower the Baud rate on your radio to 115200 (QX7) or do the Resistor mod on the module as described here.
Your module is getting loose inside its enclosure, most common on the first batches of the Happymodel ES24TX (white 3D-Printed enclosure; although the black one is only marginally better having 4 screw points instead of 2). You either have to print your enclosure (search Thingiverse for \"expresslrs\") or find a way to tighten or snug the enclosure with the module board.
Check the S.Port pin and connection in your module and module bay, and make sure they have a solid physical connection. On the DIY modules, particularly the full size module, the round hole/via for the Molex connector's flat pin might not be getting a good connection due to cold solder joint, or insufficient solder.
"},{"location":"quick-start/troubleshooting/#i-need-to-plug-my-fc-a-secondthird-time-before-i-get-a-bind-the-led-on-the-receiver-is-dim-when-i-power-it-up","title":"I need to plug my FC a second/third time before I get a bind. The LED on the receiver is dim when I power it up","text":"I need to plug my FC a second/third time before I get a bind. The LED on the receiver is dim when I power it up
Update to the latest firmware as soon as you can. A batch of HM receivers have reached the market with Voltage regulators (marked SDG) that were insufficient and weren't able to handle the higher current draw during boot up. To learn more about this issue and the fix, please check out this PR.
"},{"location":"quick-start/troubleshooting/#my-blackbox-log-has-stepping-on-the-rc-trace","title":"My Blackbox Log has stepping on the RC trace","text":"My Blackbox Log has stepping on the RC trace
Make sure you have disabled ADC Filter in your Radio Hardware settings.
"},{"location":"quick-start/troubleshooting/#troubleshooting-the-lua-script","title":"Troubleshooting the Lua Script","text":""},{"location":"quick-start/troubleshooting/#expresslrs-lua-script-is-stuck-at-loading","title":"ExpressLRS Lua Script is stuck at Loading...","text":"ExpressLRS Lua Script is stuck at Loading...
Go back to the Radio Setup Guide and make sure your radio is prepped up for ExpressLRS.
Also, make sure your module has been flashed with v3.0 firmware. V3 Lua for V3.0-flashed modules, V2 Lua for v2.x-flashed modules (including some modules fresh from the factory).
For newly-acquired ExpressLRS modules, flashing via USB is the recommended update method.
"},{"location":"quick-start/troubleshooting/#betaflight-lua-is-stuck-at-initializing","title":"Betaflight Lua is stuck at Initializing","text":"Betaflight Lua is stuck at Initializing
Increase the TLM Ratio via the ExpressLRS Lua script to values like 1:4 or even 1:2 and retry the Betaflight Lua script.
Also, you have to make sure you're getting more than ten (10) Telemetry sensors prior to launching the script.
See MSP Section for more info.
"},{"location":"quick-start/troubleshooting/#i-cannot-change-the-switch-mode","title":"I cannot change the Switch Mode!","text":"I cannot change the Switch Mode!
Changing switch modes requires that the TX module and Receiver aren't connected to each other (no C in the top right corner of the Lua Script). Power off the receiver first, change the Switch Mode from the Lua script, then power up the receiver. The Switch Mode should then apply.
"},{"location":"quick-start/troubleshooting/#i-cannot-change-my-packet-rate-to-f1000","title":"I cannot change my Packet Rate to F1000!","text":"I cannot change my Packet Rate to F1000!
F1000 requires higher than 400K baud rates. First update your baud rate setting either in the Model Setup menu or in the System Menu -> Hardware, reboot your radio to ensure that the baud rate setting got applied and then change the Packet Rate.
Do note that not every handset is capable of higher than 400K baud rates. See the Radio Setup Guide for the details.
"},{"location":"quick-start/troubleshooting/#i-cannot-change-to-full-resolution-rates","title":"I cannot change to Full Resolution Rates!","text":"I cannot change to Full Resolution Rates!
As Full Resolution Rates call for an entirely different Switch Modes, you need to first disconnect the Receiver and the TX module from each other, like how you would change Switch Modes. Power down the receiver, change the Packet Rate to the Full Resolution modes, select your Switch Mode scheme and then power up the receiver or the aircraft.
"},{"location":"quick-start/troubleshooting/#vtx-admin-is-not-working-but-i-can-change-vtx-channels-via-osd-menu","title":"VTX Admin is not working but I can change VTX channels via OSD Menu.","text":"VTX Admin is not working but I can change VTX channels via OSD Menu.
As VTX Admin depends on MSP which then depends on Telemetry, ensure that you have Telemetry enabled on your FC Configuration and that you are getting more than 10 Telemetry Sensors on your Radio (Model Setup -> Telemetry page; Delete and Discover New sensors to refresh the sensor list.) Also, make sure Telem Ratio is not Off.
"},{"location":"quick-start/troubleshooting/#there-is-no-c-on-the-top-right-corner-and-im-not-getting-telemetry-in-my-radio","title":"There is no C on the top right corner, and I'm not getting Telemetry in my radio!","text":"There is no C on the top right corner, and I'm not getting Telemetry in my radio!
Make sure Telem Ratio is not set to Off. Set it to Std, or to any other value other than Off.
"},{"location":"quick-start/troubleshooting/#on-v1x-i-can-choose-2w-on-the-lua-but-i-cannot-do-that-anymore-what-gives","title":"On v1.x, I can choose 2W on the Lua, but I cannot do that anymore. What gives?","text":"On v1.x, I can choose 2W on the Lua, but I cannot do that anymore. What gives?
This means your module cannot go that high or that low. The power levels you can select on the new Lua script are based on the power levels your module supports. This also applies to other options like Enable Backpack WiFi or BLE Joystick. If your module doesn't support any of these features, it won't show up on the Lua Script.
Individual hardware Flashing and Updating guide can be found by using the menu on the left sidebar. You can also use the Search Bar on the top of the page to get to your device's Flashing Guide faster.
"},{"location":"quick-start/troubleshooting/#invalid-serial-rx-configuration-detected","title":"Invalid serial RX configuration detected","text":"Invalid serial RX configuration detected
This is often caused by incorrect Serial RX protocol (should be CRSF), or serialrx_inverted = on (should be off) or serialrx_halfduplex=on (should be off). The Passthrough Init section of the log will show you which setting should be corrected. See the FC Preparation Guide for the correct settings.
"},{"location":"quick-start/troubleshooting/#rx-serial-not-found","title":"RX Serial not found !!","text":"RX Serial not found !!
Make sure your Serial RX on the Ports Tab of your FC Firmware configurator is set to the correct UART. See the FC Preparation Guide for the correct settings.
"},{"location":"quick-start/troubleshooting/#no-cli-available","title":"No CLI Available","text":"No CLI Available
This message can be seen on the ExpressLRS Configurator Log while using the Passthrough method and can be caused by a busy Com Port. Make sure any other Configurator Apps were closed and unplug-replug your FC to USB. You might also want to use a different USB port or cable.
This could also mean that the FC cannot be detected by the script. This could also due to the FC being in DFU mode, which for passthrough flashing, is not needed.
Some apps are running in the background that could cause this. One of which is Cura Slicer. If there are such apps, close them first before attempting another Build and Flash.
Unplug-replug the FC's USB before another attempt.
"},{"location":"quick-start/troubleshooting/#10-retries-but-no-success","title":"10 Retries but no Success","text":"10 Retries but no Success
This can be due to several things:
Incorrect bootloader is flashed or it's not flashed properly. This mainly happens on the R9 receivers. Go checkout Bootloader Flashing Guide.
Incorrect wiring. Make sure that RX in the Receiver is connected to a TX pad in the FC and the TX in the Receiver is connected to an RX pad in the FC. Also, make sure the receiver is getting enough voltage (min 4v5) from the FC or voltage supply. Wiring guide is here
Receiver is OFF. Check whether the LED on the receiver is lit, indicating it's powered and in a working state.
The UART has hardware inversion. Make sure that the UART you've connected the receiver to is not an SBUS UART that usually has hardware inversion (most common among F4 Flight Controllers). There are Flight controllers that require you to bridge a pair of pads to enable or disable the Hardware inversion of an RX pad. You can simply try a different UART.
The LED on the receiver is SOLID, while the radio is off, which could only mean that the RX pad in the FC is being pulled LOW, putting the ESP-based receiver (EPs, ES900RX, etc.) into Bootloader mode unintentionally, which will hinder normal passthrough operations. Feel free to try a different UART.
"},{"location":"quick-start/troubleshooting/#failed-to-connect-to-esp8266-timed-out-waiting-for-packet-header","title":"Failed to connect to ESP8266: Timed out waiting for packet header.","text":"Failed to connect to ESP8266: Timed out waiting for packet header.
This can be due to several things:
Receiver is wired incorrectly. Please check if the RX and TX wires aren't swapped and connected RX to RX and TX to TX on the FC. Revisit the Receiver Wiring Guide here.
The receiver's \"boot\" pads aren't bridged (or the button wasn't pressed and held during power up) for passthrough flashing. This is required for Passthrough flashing if the receiver is fresh from the packet and has a firmware version before 1.0.0-RC6.
The receiver UART is putting it in Bootloader mode and is interfering with passthrough flashing. Move it into another UART.
You can also attempt the update via UART using an FTDI Adapter (or a USB to UART Bridge).
Please see the Flashing guide for your particular receiver using the Sidebar on the Left.
"},{"location":"quick-start/troubleshooting/#i-updated-via-wifi-but-now-the-receiver-wont-work-and-has-solid-led","title":"I updated via WiFi but now the receiver won't work and has SOLID LED","text":"I updated via WiFi but now the receiver won't work and has SOLID LED
This is a sign that the WiFi flashing didn't go through properly due to a premature power cycle. To fix this, you will have to bridge the boot pads (see here) and reflash using the Passthrough method (Telemetry option on Betaflight/iNav set to OFF. This is important!) or using an FTDI adapter.
This video shows the steps albeit using a VSCode development environment but the ExpressLRS Configurator will work just fine.
To ensure that the WiFi flashing is finished properly, wait until the LED on the receiver blinks slowly (indicating it's looking for a TX bind) before pulling off power.
If you have other questions or concerns, or maybe you need further help that is not covered by this Guide, head over to our Discord Channel or Facebook Group!
ExpressLRS Discord ExpressLRS Facebook
"},{"location":"quick-start/unbricking/","title":"Unbricking","text":""},{"location":"quick-start/unbricking/#help-i-bricked-my-rx","title":"HELP I BRICKED MY RX!","text":"
Take a breath, calm down, relax.
ALL the ESP-based Receivers have a factory-installed bootloader onboard which CANNOT be damaged or tampered with. You can completely screw up the upgrade and always get it back using this default bootloader.
So technically, your receiver is not bricked unless you have damaged the hardware itself.
But for argument's sake, let's use the word \"bricked\" or \"soft-bricked\" for a receiver that is not in working order and is not behaving as expected.
Follow the steps below very closely to recover your \"bricked\" Receiver.
Make sure your Receiver only powers up with a LiPo Connected.
If your receiver powers up with just USB connected, move the 5v wire of the receiver into a 5v pad that only powers up with LiPo connected.
Take a multi-meter in DC Voltmeter mode.
Plug in USB into your Flight Controller. Disconnect LiPo.
Probe/check each of the 5v pads in the Flight Controller.
The 5v pads that read 0v on the multi-meter are pads that will only power up when a LiPo is connected.
Solder your Receiver 5v into this pad.
If in the above steps, you're not able to find a 5v pad suitable for this procedure, follow the following:
Disconnect the 5v wire of the Receiver from the 5v pad on the Flight Controller.
Solder a different length of wire into any of the 5v pads on the Flight Controller.
Expose a suitable length of conductor of this wire that you can connect with the Receiver's 5v wire LATER.
If you've connected a LiPo from the previous step, disconnect it. Also, unplug the Flight Controller from your computer.
Prepare the receiver for bootloader mode.
If your Receiver have boot pads, bridge them together with solder.
If your Receiver has a button, use an alligator clip to keep the button pressed.
If your Receiver only has one Boot pad, connect it to a Ground pad.
Example Receiver with Boot Pad
Example Receiver with Boot Button
Notice
Even if your Receiver LED is only lighting up solid, DO NOT skip this step to ensure the receiver is indeed in its Bootloader State.
Connect to Betaflight or INAV Configurator and make sure you've properly configured your FC for ExpressLRS use. Set Telemetry to disabled for now.
Save & Reboot. Close Betaflight Configurator. Also, close any other App that's potentially using COM Ports.
Cura Slicer
We found Cura Slicer and possibly others like it would keep a COM port open or busy preventing successful flashing/recovery via Passthrough.
Unplug and replug the USB cable. This will ensure the Flight Controller has a fresh connection to the computer and that the COM port is not busy or in use.
On the ExpressLRS Configurator, select the Firmware Version you're trying to recover. Select your Device Category and Device Target as well, along with your usual Firmware Options.
Set the Flashing Method to Betaflight Passthrough.
Click the Flash button. Wait for the Line PASSTHROUGH DONE to appear in the Build Log and power up the receiver.
Not Seeing PASSTHROUGH DONE? (click/tap to expand)
You've probably skipped some of the steps above or you've misconfigured your flight controller. Go back and make sure to follow EVERY step.
Plug in LiPo or twist the 5v Wires together to power up the receiver (see Step 1). The receiver LED should be Solid.
Wait for the process to finish, hopefully with the Success Message. Otherwise, repeat the procedure above or try a different approach (like reflashing via FTDI/UART Adapter).
You can now power down the flight controller, and disconnect LiPo and/or USB.
Remove the boot pads bridging or connection to Ground, or, if your Receiver has a button, remove the alligator clip used to press the button.
Re-power up the receiver to verify it is back in its normal working state.
"},{"location":"quick-start/unbricking/#wall-of-text-heres-a-video","title":"Wall of Text? Here's a video!","text":""},{"location":"quick-start/unbricking/#what-about-the-tx","title":"What about the TX?","text":"
Most ESP-based ExpressLRS TX Modules either have the via UART Flashing Procedure or the via ETX Passthrough Flashing method available to them. Use any of these other methods to recover your ESP-based TX Module.
For STM-based ExpressLRS TX Modules, there's via STLink Flashing method.
ExpressLRS TX Modules are much harder to screw up during updates, more so if you're following the official Flashing Guides on this website.
"},{"location":"quick-start/webui/","title":"The Web UI","text":""},{"location":"quick-start/webui/#the-expresslrs-web-ui","title":"The ExpressLRS Web UI","text":"
The ExpressLRS Web UI is an essential part of the ExpressLRS ecosystem. In earlier versions of the project, its main use is for updating the ExpressLRS firmware and logging or debugging (on select hardware).
ExpressLRS 3.0 has further expanded the capabilities of the ExpressLRS Web UI. It is now capable of changing Firmware Parameters, including the Binding Phrase, Regulatory Domain (for the 900MHz devices), UART Inversion and more.
"},{"location":"quick-start/webui/#the-banner","title":"The Banner","text":"The ExpressLRS Web UI Banner"},{"location":"quick-start/webui/#the-options-tab","title":"The Options Tab","text":"
This tab allows users to change firmware options without reflashing their devices. It also allows the import and export of the Configuration from one device to another, useful for setting up backup equipment.
Options common to both Receivers and TX Modules:
Binding Phrase: Type in your Binding Phrase here if you want to update it from either the factory setting or from an earlier flashed setting.
It's Blank!
This field doesn't store the plain text Binding Phrase. If you see it blank like shown, do not worry. The next field, UID, has the information.
UID: As you type in your Binding Phrase in the field above, this read-only field will update with the UID translation. This is what actually gets saved in your device.
Regulatory Domain: This only applies to the 900MHz system. This field allows users to change the Regulatory Domain for their device.
What about 2.4GHz?
The EU_CE Regulatory Domain setting is a Compile-time option and the LBT code needs to be baked in for it to work properly.
WiFi \"Auto On\" Interval (in seconds): This field allows you to change how soon WiFi automatically activates when the device is powered up and it's not getting a valid CRSF signal (for TX Modules) or sync packets (for Receivers).
Receiver OptionsTX Module Options
ExpressLRS Receiver Options Tab
UART Baud: The baud rate to which the receiver will send and receive signals to or from a Flight Controller or other serially connected device. Under normal circumstances, this setting should be left at the default 420000 baud.
Exception: If you are running KISS/Kiss Ultra firmware set the receiver's UART baud rate to 400000, as KISS uses this baud rate for CRSF.
Invert TX Pin: This setting should also be left disabled or unchecked under normal circumstances. It inverts the CRSF signal coming out of the TX pin of the receiver.
Receivers that will be connected to an SBUS pad on Flight Controllers without extra uninverted RX pads should enable this setting. Additionally the command set serialrx_inverted = on will be needed in the Flight Controller configuration.
Lock on First Connection: This setting speeds up the reconnection of a Receiver and TX Module if you don't ever change your RF Mode/Packet Rate.
ExpressLRS TX Module Options Tab
TLM Report Interval: This setting controls how often Telemetry packets are sent back to the radio. 240LU is the default setting and is already fast for EdgeTX or OpenTX.
UART Inverted: Keep this enabled or checked if you're using your TX module on an OpenTX or EdgeTX Radio. The S.Port pins in External Module bays are inverted bidirectional pins.
Fan Runtime (in seconds): This setting controls how long the fan on the TX Module will keep spinning even after the current Transmit Power of the module is already Lower than the Fan Threshold Lua Script setting.
"},{"location":"quick-start/webui/#the-wifi-tab","title":"The WiFi Tab","text":"ExpressLRS WebUI WiFi Tab"},{"location":"quick-start/webui/#the-model-tab","title":"The Model Tab","text":"ExpressLRS Receiver Model Tab ExpressLRS PWM Receiver Output Settings"},{"location":"quick-start/webui/#the-buttons-tab","title":"The Buttons Tab","text":"
This section is currently only available for the RadioMaster Ranger module.
"},{"location":"quick-start/webui/#how-to-get-to-the-web-ui","title":"How to get to the Web UI","text":"ReceiversTX Modules
Put your Receiver into WiFi Mode.
Auto WiFi Onvia Lua Script
Make sure your Radio with your TX Module is Off.
Power-cycle your receiver (turn it Off then turn it back On). The Receiver LED should be blinking slowly as shown below.
Receiver LED not Blinking! (click/tap to expand)
If it has a Solid LED light, it may be in bootloader mode if you've only just wired it up. Rewire your receiver into a different uart. If you have attempted to update it before, then it could be soft-bricked. Follow the Unbricking procedure to get it back into normal working condition.
Wait for about 60 seconds or until the Receiver LED blinks rapidly indicating it is now in WiFi Mode.
Make sure the Receiver and TX Module are in sync and bound. RSSI indicators on your Radio Home screen should be visible and the Receiver LED should be Solid as shown.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, go back to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
there should be a C in the top right corner of the Lua Script indicating TX Module and Receiver are Connected.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The WiFi Running screen will briefly show up. Your Receiver is now in WiFi mode as indicated by the rapidly blinking LED.
Note
It is normal for the receiver will disconnect from the TX Module once it is in WiFi Mode. You will hear your radio announce \"Telemetry Lost\" if you have the sound pack on your Radio SD Card.
Scan for the ExpressLRS RX Access Point.
If your Receiver is previously flashed with your Home WiFi SSID and Password, and it can connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Load the Web UI on your browser using these addresses:
http://10.0.0.1/ - If you have connected to the ExpressLRS RX Access Point
Note
This IP address is also often used by some routers. Computers with an ethernet connection to their routers will find that this page doesn't load the ExpressLRS Web UI and instead loads their router or ISP modem configuration dashboards.
We recommend disconnecting from the network first or trying a different device instead, e.g. smartphone or tablet.
Note
On some devices a network login prompt might pop up. Clicking this will often show an incomplete version of the webui that won't behave as expected. Please navigate to http://10.0.0.1/ manually in your browser instead.
http://elrs_rx.local - If you have previously set your Home WiFi SSID and Password into your Receiver when you flashed it.
Note
If your browser cannot resolve this address, chances are MDNS is not set up and working on your computer or network.
Use the IP Address instead! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a which will list all the devices in the Network.
Try each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in to your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Put your module into wifi mode.
via ExpressLRS Lua ScriptExternal Module detached from Radio
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, go back to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
If the Script stopped and is showing a Syntax Error, do not worry. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware or both. It could also be due to the fact your TX module is on an earlier firmware version and you're using a more recent Lua Script.
With your TX module disconnected from your Radio module bay, power it up either via an external power source (2S) or by plugging in a USB cable into its USB Port.
Let it be for 60s and the RGB LED will turn into a Green Breathing LED pattern indicating it is now in WiFi Mode.
TX Modules with an OLED Screen will also show a message regarding WiFi mode.
Scan for the ExpressLRS TX Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it can connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Load the Web UI on your browser using these addresses:
http://10.0.0.1/ - If you have connected to the ExpressLRS TX Access Point
Note
This IP address is also often used by some routers. Computers with an ethernet connection to their routers will find that this page doesn't load the ExpressLRS Web UI and instead loads their router or ISP modem configuration dashboards.
We recommend disconnecting from the network first or trying a different device instead, e.g. smartphone or tablet.
Note
On some devices a network login prompt might pop up. Clicking this will often show an incomplete version of the webui that won't behave as expected. Please navigate to http://10.0.0.1/ manually in your browser instead.
http://elrs_tx.local - If you have previously set your Home WiFi SSID and Password into your TX Module when you flashed it.
Note
If your browser cannot resolve this address, chances are MDNS is not set up and working on your computer or network.
Use the IP Address instead! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a which will list all the devices in the Network.
Try each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in to your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/axisflying-thor/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
Axis Thor
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/axisflying-thor/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/axisflying-thor/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Axisflying 2.4 GHz
Device:
AXIS Thor 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
Locate the Boot button on your receiver, press and hold it.
Plug in your UART Adapter into a USB Port on your Computer. Release/de-press the Boot button.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Axisflying 2.4 GHz
Device:
AXIS Thor 2.4GHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Axisflying 2.4 GHz
Device:
AXIS Thor 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Axisflying 2.4 GHz
Device:
AXIS Thor 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Axisflying 2.4 GHz
Device:
AXIS Thor 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
"},{"location":"quick-start/receivers/betafpv-superd/","title":"BetaFPV SuperD 2.4GHz","text":""},{"location":"quick-start/receivers/betafpv-superd/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. As this receiver uses an RGB LED as indicator, it will appear as if the receiver is OFF when in Bootloader mode. The firmware that drives the RGB LED is inactive when the ESP Chip is in Bootloader mode, thus the RGB LED will not function when in this state.
BetaFPV SuperD Diversity Receiver, ESP-based
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/betafpv-superd/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have connected the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/betafpv-superd/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV SuperD 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
Locate the Boot button on your receiver, press and hold it.
Plug in your UART Adapter into a USB Port on your Computer. Release/de-press the Boot button.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV SuperD 2.4GHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV SuperD 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV SuperD 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV SuperD 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
"},{"location":"quick-start/receivers/betafpv-superd900/","title":"BetaFPV SuperD 900MHz","text":""},{"location":"quick-start/receivers/betafpv-superd900/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. As this receiver uses an RGB LED as indicator, it will appear as if the receiver is OFF when in Bootloader mode. The firmware that drives the RGB LED is inactive when the ESP Chip is in Bootloader mode, thus the RGB LED will not function when in this state.
BetaFPV SuperD Diversity Receiver, ESP-based
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/betafpv-superd900/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have connected the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/betafpv-superd900/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV SuperD 900MHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
Locate the Boot button on your receiver, press and hold it.
Plug in your UART Adapter into a USB Port on your Computer. Release/de-press the Boot button.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV SuperD 900MHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV SuperD 900MHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV SuperD 900MHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV SuperD 900MHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/betafpv2400/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
BetaFPV Nano BetaFPV Lite (Flat & Tower)
The images above show the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/betafpv2400/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/betafpv2400/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz Nano RX (Nano)
BETAFPV 2.4GHz Lite RX (Tower & Flat)
BETAFPV 2.4GHz AIO RX (AIOs with UART-based Receivers)
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
If your Receiver has Boot Pads instead of a Boot Button, solder the Boot Pads together or connect it to Ground. If your Receiver has a Boot Button, locate it then press & hold it.
Plug in your UART Adapter into a USB Port on your Computer.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Once the LED on the Receiver is lit up Solid, release/de-press the button on the receiver if it has one.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz Nano RX (Nano)
BETAFPV 2.4GHz Lite RX (Tower & Flat)
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
If your receiver has a boot pad instead of a boot button, make sure to disconnect it from ground or remove the solder bridge you made on step 2.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz Nano RX (Nano)
BETAFPV 2.4GHz Lite RX (Tower & Flat)
BETAFPV 2.4GHz AIO RX (AIOs with UART-based Receivers)
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz Nano RX (Nano)
BETAFPV 2.4GHz Lite RX (Tower & Flat)
BETAFPV 2.4GHz AIO RX (AIOs with UART-based Receivers)
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz Nano RX (Nano)
BETAFPV 2.4GHz Lite RX (Tower & Flat)
BETAFPV 2.4GHz AIO RX (AIOs with UART-based Receivers)
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/betafpv900/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
BetaFPV Nano
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/betafpv900/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/betafpv900/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV 900MHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
Locate the Boot button on your receiver, press and hold it.
Plug in your UART Adapter into a USB Port on your Computer. Release/de-press the Boot button.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV 900MHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV 900MHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV 900MHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV 900MHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Once you've wired up your Receiver to your Flight Controller, you need to setup the UART for Serial RX. This is usually done on the Ports Tab of your Flight Controller Configurator.
In the example below, the Receiver is wired to UART1 (TX1 and RX1 pads), and so the Serial RX column should be enabled on UART1 in the Ports Tab.
NOTE
This is ONLY an example. Set your Ports according to how your peripherals, including the Receiver, are wired up.
Example Betaflight Serial RX Configuration Example INAV Serial RX Configuration"},{"location":"quick-start/receivers/configuring-fc/#serial-receiver-protocol","title":"Serial Receiver Protocol","text":"
UART-based ExpressLRS Receivers use the CRSF Serial Protocol to communicate with a Flight Controller.
Follow the steps below to set up your Serial Receiver Protocol:
Navigate to Receiver Tab on your Flight Controller Configurator.
Set Receiver Mode or Receiver Type to Serial.
Set Serial Receiver Provider to CRSF.
Set Telemetry to Enabled.
On INAV, Telemetry can be found under the Configuration Tab.
Make sure you set RSSI Channel to Disabled if you are using an Analog FPV System, or any FPV System with MSP DisplayPort or \"Canvas Mode\" support.
Also make sure RSSI ADC is Disabled.
Note
The Location or Labels of these settings can change from version to version of your Flight Controller Configurator. Please consult your Flight Controller Configurator User Guides.
"},{"location":"quick-start/receivers/configuring-fc/#software-inversion-and-duplex-modes","title":"Software Inversion and Duplex Modes","text":"
The CRSF Protocol requires a full UART pair, uninverted and in full-duplex mode. To check for these settings, use the CLI Tab of your Flight Controller Configurator and execute get serialrx.
serialrx_inverted should be OFF; configure it with set serialrx_inverted = off.
serialrx_halfduplex should be OFF; configure it with set serialrx_halfduplex = off.
Don't forget to use save once you're done setting these up.
"},{"location":"quick-start/receivers/configuring-fc/#rc-link-preset-betaflight-only","title":"RC Link Preset (BETAFLIGHT ONLY)","text":"
For flight controllers based on Betaflight, there are 'RC Link Presets' available that configure feedforward smoothing and associated link settings based on your packet rate and usage case.
Warning
Using no link preset, or using the incorrect one for your packet rate, can result in unwanted noise and jitter in feedforward, which can affect setpoint tracking and thus flight characteristics.
To install the correct 'RC Link Preset', follow these steps in Betaflight Configurator:
Select the Preset tab
In the preset tab, select Save Backup and save a backup to a safe location before applying any preset.
Search for 'ExpressLRS' and select the Link Preset that matches your Packet Rate. If no direct match is available, choose the closest preset below your packet rate.
Read through the options by selecting the dropdown list. NOTE: These are all optional, if none of them apply to your circumstances, it is OK to leave everything unticked.
Select 'Pick' to stage the preset:
Select Save and Reboot to apply the preset:
Important
Close your Flight Controller Configurator once you've set it up for ExpressLRS. Keeping it open could prevent the next steps from completing properly, particularly flashing via Passthrough. You must also unplug the FC from USB before proceeding to the next steps to refresh the connection.
With your Flight Controller configured, you can now proceed to the next step: Checking RX Firmware Version.
"},{"location":"quick-start/receivers/diy2400/","title":"DIY 2400RX","text":""},{"location":"quick-start/receivers/diy2400/#flashing-via-passthrough","title":"Flashing via Passthrough","text":"
"},{"location":"quick-start/receivers/diy2400/#flashing-via-wifi","title":"Flashing via WiFi","text":"
Target: DIY_2400_RX_ESP8285_SX1280_via_WIFI
"},{"location":"quick-start/receivers/diy2400/#flashing-via-ftdi","title":"Flashing via FTDI","text":"
Target: DIY_2400_RX_ESP8285_SX1280_via_UART
Please consult the Hardware Repository for your particular receiver.
"},{"location":"quick-start/receivers/diy900/","title":"DIY 900RX","text":""},{"location":"quick-start/receivers/diy900/#flashing-via-passthrough","title":"Flashing via Passthrough","text":"
"},{"location":"quick-start/receivers/diy900/#flashing-via-ftdi","title":"Flashing via FTDI","text":"
Target: DIY_900_RX_ESP8285_SX127x_via_UART
Please consult the Hardware Repository for your particular receiver.
"},{"location":"quick-start/receivers/firmware-version/","title":"Checking FW Version","text":""},{"location":"quick-start/receivers/firmware-version/#why-do-you-have-to-know-the-firmware-version","title":"Why do you have to know the Firmware Version?","text":"
Knowing the ExpressLRS Firmware Version that's currently in your devices will determine whether there is a need to update to a newer version or whether you can simply get your devices bound together without updating. For newcomers in the hobby, or for those just starting with ExpressLRS, it can be a bit daunting to flash a new device.
It is still recommended that you update your gear to the latest firmware version to ensure you have all the bugfixes and latest features.
"},{"location":"quick-start/receivers/firmware-version/#receiver-firmware-version","title":"Receiver Firmware Version","text":"via Web UIvia Lua Script
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the previous step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in sync with a TX Module, power Off the Radio & TX Module first then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, go back to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
Scan for the ExpressLRS RX Access Point.
If your Receiver is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also, try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Load the Web UI on your browser using these addresses:
http://10.0.0.1/ -If you have connected to the ExpressLRS RX Access Point
Note
This IP address is also often used by some routers. Computers with an ethernet connection to their routers will find that this page doesn't load the ExpressLRS Web UI and instead loads their router or ISP modem configuration dashboards.
We recommend disconnecting from the network first or trying a different device instead, e.g. smartphone or tablet.
http://elrs_rx.local - If you have previously set your Home WiFi SSID and Password into your Receiver when you flashed it.
Note
If your browser cannot resolve this address, chances are MDNS is not set up and working on your computer or network.
Use the IP Address instead! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a which will list all the devices in the Network.
Try each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in to your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
The Banner of the Web UI should tell you the firmware version flashed into your Receiver.
The ExpressLRS Web UI Banner
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter Key to activate the Script.
If the script is stuck on a \"Loading...\" screen, go back to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll to the bottom of the page and select Other Devices.
Press the Enter Key to open the Folder.
Select the Receiver Device and Press Enter to query its parameters.
The image below shows the Receiver Firmware Version info.
Shows the Happymodel EP Receiver has 3.2.1 Firmware Version with the Git Hash 8dbbdb.
Receiver Version Line on Colored Screen Radio
Once you have determined the firmware version that's currently flashed into your Receiver, you can now decide to whether keep using it as is or update to the latest version.
Versioning Scheme
The ExpressLRS Firmware Versioning scheme is based on the semantic versioning scheme.
A Version is defined or formatted as \"Major.Minor.Patch\"
- major = major new feature and/or incompatible changes\n- minor = minor features or enhancements and/or new targets\n- patch = bug-fixes\n
That first number in the Version string should match between a TX Module and a Receiver. Examples:
a Receiver with version string of 3.1.2 will sync and work with a TX Module with firmware version 3.0.1
a Receiver with version string of 3.2.0 will NOT sync or bind with a TX Module with firmware version 2.4.0
For the latest ExpressLRS firmware version, check the Releases page in Git Hub
"},{"location":"quick-start/receivers/firmware-version/#i-know-the-version-what-now","title":"I Know the Version. What Now?","text":"I have an old versionI have a recent one
See the next page for the typical updating procedure or expand the Updating Receivers section of the Menu on the left shown below.
You can also use the Search Bar on top of this page to search for the specific Updating/Flashing Guide for your Receiver.
See the Binding Procedure to sync your Receiver with your TX Module.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/flash2400/#check-your-target","title":"Check your Target","text":"
There are more ESP8285 based RXes in the market due to massive shortage of STM32 Chips. These support WiFi updating, and can be easily distinguished with a few tricks. The simplest way to tell is if on the rear of the RX (the side without the U.fl/SMD antenna) there is a large white component with the label RainSun (pictured below). If this is not there, you have an STM32 based target, if it is you have an _ESP_ target, and can update using Wifi!
RainSun Antenna
Note
New versions of the receiver also have the PCB Wifi Antenna, and doesn't have the RainSun SMD Antenna mentioned above. These will use the same ESP-based Target, not the STM-based target.
"},{"location":"quick-start/receivers/flash2400/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX Module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
The images above show the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/flash2400/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/flash2400/#updating-your-receiver-firmware-esp-based","title":"Updating your Receiver Firmware (ESP-based)","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash ESP 2.4GHz RX
NamimnoRC Flash 100mW Diversity 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
If your Receiver has Boot Pads instead of a Boot Button, solder the Boot Pads together or connect it to Ground. If your Receiver has a Boot Button, locate it then press & hold it.
Plug in your UART Adapter into a USB Port on your Computer.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Once the LED on the Receiver is lit up Solid, release/de-press the button on the receiver if it has one.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash ESP 2.4GHz RX
NamimnoRC Flash 100mW Diversity 2.4GHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
If your receiver has a boot pad instead of a boot button, make sure to disconnect it from ground or remove the solder bridge you made on step 2.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash ESP 2.4GHz RX
NamimnoRC Flash 100mW Diversity 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash ESP 2.4GHz RX
NamimnoRC Flash 100mW Diversity 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash ESP 2.4GHz RX
NamimnoRC Flash 100mW Diversity 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
"},{"location":"quick-start/receivers/flash2400/#updating-your-receiver-firmware-stm-based","title":"Updating your Receiver Firmware (STM-based)","text":"
Attention
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
via Passthroughvia STLink
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
If your receiver powers up with just USB connected to your flight controller, unplug it. Press and Hold the boot button on the receiver (not the FC) and then plug in the USB. Release the button right after the LED turn solid.
If your receiver only powers up with a LiPo connected to your flight controller, unplug it. Then unplug-replug the USB cable to your flight controller. Do not replug LiPo yet.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash STM 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the Retry... lines to appear in the Build Log. Connect the LiPo to power up the Receiver if it only powers up with a LiPo connected.
Retry... lines will not show up if your receiver is already in bootloader mode and gets powered up by USB.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Disconnect the Receiver from your Flight Controller.
Wire up the Receiver into an STLink V2 dongle. Find the CLK, DIO, 3v3 and Gnd pads and wire them to the corresponding pins of the dongle.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash STM 2.4GHz RX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Rewire your receiver to your Flight Controller.
"},{"location":"quick-start/receivers/foxeer2400/","title":"Foxeer LNA & Lite 2.4GHz","text":"
Advisory
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/foxeer2400/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
Foxeer LNA and Lite ELRS 2.4GHz
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/foxeer2400/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/foxeer2400/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Foxeer 2.4 GHz
Device:
Foxeer Lite 2.4GHz RX
Foxeer 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
If your Receiver has Boot Pads instead of a Boot Button, solder the Boot Pads together or connect it to Ground. If your Receiver has a Boot Button, locate it then press & hold it.
Plug in your UART Adapter into a USB Port on your Computer.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Once the LED on the Receiver is lit up Solid, release/de-press the button on the receiver if it has one.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Foxeer 2.4 GHz
Device:
Foxeer Lite 2.4GHz RX
Foxeer 2.4GHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
If your receiver has a boot pad instead of a boot button, make sure to disconnect it from ground or remove the solder bridge you made on step 2.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Foxeer 2.4 GHz
Device:
Foxeer Lite 2.4GHz RX
Foxeer 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Foxeer 2.4 GHz
Device:
Foxeer Lite 2.4GHz RX
Foxeer 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Foxeer 2.4 GHz
Device:
Foxeer Lite 2.4GHz RX
Foxeer 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/geprc2400/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
GEPRC Nano GEPRC Nano SE
The images above show the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/geprc2400/#identify-your-receiver-and-flash-the-correct-target","title":"Identify your receiver and flash the correct target","text":"
Important Step!
You MUST flash the correct firmware target to your receiver in order for it to work properly. Look closely at your receiver and make sure you are select the correct firmware target. Flashing the wrong target will result in extremely poor range or failure to connect.
How to identify the correct GEPRC 2.4GHz receiver target
"},{"location":"quick-start/receivers/geprc2400/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/geprc2400/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
GEPRC 2.4 GHz
Device:
GEPRC Nano(SE) 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
If your Receiver has Boot Pads instead of a Boot Button, solder the Boot Pads together or connect it to Ground. If your Receiver has a Boot Button, locate it then press & hold it.
Plug in your UART Adapter into a USB Port on your Computer.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Once the LED on the Receiver is lit up Solid, release/de-press the button on the receiver if it has one.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
GEPRC 2.4 GHz
Device:
GEPRC Nano(SE) 2.4GHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
If your receiver has a boot pad instead of a boot button, make sure to disconnect it from ground or remove the solder bridge you made on step 2.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
GEPRC 2.4 GHz
Device:
GEPRC Nano(SE) 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
GEPRC 2.4 GHz
Device:
GEPRC Nano(SE) 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
GEPRC 2.4 GHz
Device:
GEPRC Nano(SE) 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/geprc900/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/geprc900/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/geprc900/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
GEPRC 900 MHz
Device:
GEPRC Nano 900MHz RX
GEPRC Nano 900MHz PA500 RX
GEPRC True Diversity 900MHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
Locate the Boot button on your receiver, press and hold it.
Plug in your UART Adapter into a USB Port on your Computer. Release/de-press the Boot button.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
GEPRC 900 MHz
Device:
GEPRC Nano 900MHz RX
GEPRC Nano 900MHz PA500 RX
GEPRC True Diversity 900MHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
GEPRC 900 MHz
Device:
GEPRC Nano 900MHz RX
GEPRC Nano 900MHz PA500 RX
GEPRC True Diversity 900MHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
GEPRC 900 MHz
Device:
GEPRC Nano 900MHz RX
GEPRC Nano 900MHz PA500 RX
GEPRC True Diversity 900MHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
GEPRC 900 MHz
Device:
GEPRC Nano 900MHz RX
GEPRC Nano 900MHz PA500 RX
GEPRC True Diversity 900MHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
"},{"location":"quick-start/receivers/ghost2400/#flashingupdating-your-receiver-firmware","title":"Flashing/Updating your Receiver Firmware","text":"via STLinkvia Passthrough
Note
The only way to flash the Ghost Atto/Zepto to ExpressLRS for the first time is by using STLink. This is a one-way process. There is no returning to the factory firmware after flashing.
Disconnect the Receiver from your Flight Controller.
Wire up the Receiver into an STLink V2 dongle. Find the CLK, DIO, 3v3 and Gnd pads and wire them to the corresponding pins of the dongle.
IMRC Ghost
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
ImmersionRC 2.4 GHz
Device:
Ghost Atto 2.4GHz RX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Rewire your receiver to your Flight Controller.
Note
This method can only be used to UPDATE the ExpressLRS firmware on a Ghost Atto/Zepto.
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured. Also make sure [bootloaders] are already flashed to your R9 receiver when applicable.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
If your receiver powers up with just USB connected to your flight controller, unplug it. Press and Hold the boot button on the receiver (not the FC) and then plug in the USB. Release the button right after the LED turn solid.
If your receiver only powers up with a LiPo connected to your flight controller, unplug it. Then unplug-replug the USB cable to your flight controller. Do not replug LiPo yet.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
ImmersionRC 2.4 GHz
Device:
Ghost Atto 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the Retry... lines to appear in the Build Log. Connect the LiPo to power up the Receiver if it only powers up with a LiPo connected.
Retry... lines will not show up if your receiver is already in bootloader mode and gets powered up by USB.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/hglrc-hermes2400/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
HGLRC Hermes 2.4GHz
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/hglrc-hermes2400/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/hglrc-hermes2400/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 2.4 GHz
Device:
HGLRC Hermes 2.4GHz RX
HGLRC Gemini 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
If your Receiver has Boot Pads instead of a Boot Button, solder the Boot Pads together or connect it to Ground. If your Receiver has a Boot Button, locate it then press & hold it.
Plug in your UART Adapter into a USB Port on your Computer.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Once the LED on the Receiver is lit up Solid, release/de-press the button on the receiver if it has one.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 2.4 GHz
Device:
HGLRC Hermes 2.4GHz RX
HGLRC Gemini 2.4GHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
If your receiver has a boot pad instead of a boot button, make sure to disconnect it from ground or remove the solder bridge you made on step 2.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 2.4 GHz
Device:
HGLRC Hermes 2.4GHz RX
HGLRC Gemini 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 2.4 GHz
Device:
HGLRC Hermes 2.4GHz RX
HGLRC Gemini 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 2.4 GHz
Device:
HGLRC Hermes 2.4GHz RX
HGLRC Gemini 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/hglrc-hermes900/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
HGLRC Hermes 900MHz
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/hglrc-hermes900/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/hglrc-hermes900/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 900 MHz
Device:
HGLRC Hermes 900MHz RX
HGLRC Gemini 900M RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
Locate the Boot button on your receiver, press and hold it.
Plug in your UART Adapter into a USB Port on your Computer. Release/de-press the Boot button.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 900 MHz
Device:
HGLRC Hermes 900MHz RX
HGLRC Gemini 900M RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 900 MHz
Device:
HGLRC Hermes 900MHz RX
HGLRC Gemini 900M RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 900 MHz
Device:
HGLRC Hermes 900MHz RX
HGLRC Gemini 900M RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 900 MHz
Device:
HGLRC Hermes 900MHz RX
HGLRC Gemini 900M RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/hmep2400/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/hmep2400/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/hmep2400/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 2.4 GHz
Device:
HappyModel EP1/EP2 2.4GHz RX (EP1 & EP2)
HappyModel EP Dual 2.4GHz RX (EP Dual)
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
If your Receiver has Boot Pads instead of a Boot Button, solder the Boot Pads together or connect it to Ground. If your Receiver has a Boot Button, locate it then press & hold it.
Plug in your UART Adapter into a USB Port on your Computer.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Once the LED on the Receiver is lit up Solid, release/de-press the button on the receiver if it has one.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 2.4 GHz
Device:
HappyModel EP1/EP2 2.4GHz RX (EP1 & EP2)
HappyModel EP Dual 2.4GHz RX (EP Dual)
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
If your receiver has a boot pad instead of a boot button, make sure to disconnect it from ground or remove the solder bridge you made on step 2.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 2.4 GHz
Device:
HappyModel EP1/EP2 2.4GHz RX (EP1 & EP2)
HappyModel EP Dual 2.4GHz RX (EP Dual)
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up.
The file for the EP1 or EP2 receivers will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
The file for the EP Dual will be in bin format (firmware.bin).
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 2.4 GHz
Device:
HappyModel EP1/EP2 2.4GHz RX (EP1 & EP2)
HappyModel EP Dual 2.4GHz RX (EP Dual)
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up.
The file for the EP1 or EP2 receivers will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
The file for the EP Dual will be in bin format (firmware.bin).
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 2.4 GHz
Device:
HappyModel EP1/EP2 2.4GHz RX (EP1 & EP2)
HappyModel EP Dual 2.4GHz RX (EP Dual)
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/hmes900/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX Module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
Happymodel ES900RX
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/hmes900/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/hmes900/#updating-your-receiver-firmware-es900rx","title":"Updating your Receiver Firmware (ES900RX)","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel ES900 RX
HappyModel ES900 Dual RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
If your Receiver has Boot Pads instead of a Boot Button, solder the Boot Pads together or connect it to Ground. If your Receiver has a Boot Button, locate it then press & hold it.
Plug in your UART Adapter into a USB Port on your Computer.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Once the LED on the Receiver is lit up Solid, release/de-press the button on the receiver if it has one.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel ES900 RX
HappyModel ES900 Dual RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
If your receiver has a boot pad instead of a boot button, make sure to disconnect it from ground or remove the solder bridge you made on step 2.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel ES900 RX
HappyModel ES900 Dual RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up.
The file for the ES900 receivers will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
The file for the ES900 Dual will be in bin format (firmware.bin).
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel ES900 RX
HappyModel ES900 Dual RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up.
The file for the ES900 receivers will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
The file for the ES900 Dual will be in bin format (firmware.bin).
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel ES900 RX
HappyModel ES900 Dual RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
"},{"location":"quick-start/receivers/hmes900/#updating-your-receiver-firmware-es915rxes868rx","title":"Updating your Receiver Firmware (ES915RX/ES868RX)","text":"
Attention
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
via Passthroughvia STLink
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
If your receiver powers up with just USB connected to your flight controller, unplug it. Press and Hold the boot button on the receiver (not the FC) and then plug in the USB. Release the button right after the LED turn solid.
If your receiver only powers up with a LiPo connected to your flight controller, unplug it. Then unplug-replug the USB cable to your flight controller. Do not replug LiPo yet.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel ES915 RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the Retry... lines to appear in the Build Log. Connect the LiPo to power up the Receiver if it only powers up with a LiPo connected.
Retry... lines will not show up if your receiver is already in bootloader mode and gets powered up by USB.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Disconnect the Receiver from your Flight Controller.
Wire up the Receiver into an STLink V2 dongle. Find the CLK, DIO, 3v3 and Gnd pads and wire them to the corresponding pins of the dongle.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel ES915 RX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
"},{"location":"quick-start/receivers/hmpp2400/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"Happymodel PP
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
Note
The PP doesn't have a Boot pad so there's no need to bridge any pads.
"},{"location":"quick-start/receivers/hmpp2400/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed smoothly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy (of high importance with the Passthrough Flashing Method).
"},{"location":"quick-start/receivers/hmpp2400/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia STLink
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
If your receiver powers up with just USB connected to your flight controller, unplug it. Press and Hold the boot button on the receiver (not the FC) and then plug in the USB. Release the button right after the LED turn solid.
If your receiver only powers up with a LiPo connected to your flight controller, unplug it. Then unplug-replug the USB cable to your flight controller. Do not replug LiPo yet.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 2.4 GHz
Device:
HappyModel PP 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the Retry... lines to appear in the Build Log. Connect the LiPo to power up the Receiver if it only powers up with a LiPo connected.
Retry... lines will not show up if your receiver is already in bootloader mode and gets powered up by USB.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Disconnect the Receiver from your Flight Controller.
Wire up the Receiver into an STLink V2 dongle. Find the CLK, DIO, 3v3 and Gnd pads and wire them to the corresponding pins of the dongle.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 2.4 GHz
Device:
HappyModel PP 2.4GHz RX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Rewire your receiver to your Flight Controller following the Receiver Wiring guide.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/iflight2400/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
IFlight 2.4GHz IFlight 2.4GHz
The images above show the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/iflight2400/#identify-your-receiver-and-flash-the-correct-target","title":"Identify your receiver and flash the correct target","text":"
Important Step!
You MUST flash the correct firmware target to your receiver in order for it to work properly. Look closely at your receiver and make sure you are select the correct firmware target. Flashing the wrong target will result in extremely poor range or failure to connect.
How to identify the correct iFlight 2.4GHz receiver target
"},{"location":"quick-start/receivers/iflight2400/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/iflight2400/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
iFlight 2.4 GHz
Device:
iFlight 2.4GHz RX
iFlight 2.4GHz Nano RX (smaller)
iFlight 2.4GHz 500mW RX
iFlight 2.4GHz 250mW Diversity RX (two antennas)
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
Locate the Boot button on your receiver, press and hold it.
Plug in your UART Adapter into a USB Port on your Computer. Release/de-press the Boot button.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
iFlight 2.4 GHz
Device:
iFlight 2.4GHz RX
iFlight 2.4GHz Nano RX (smaller)
iFlight 2.4GHz 500mW RX
iFlight 2.4GHz 250mW Diversity RX (two antennas)
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
iFlight 2.4 GHz
Device:
iFlight 2.4GHz RX
iFlight 2.4GHz Nano RX (Smaller)
iFlight 2.4GHz 500mW RX
iFlight 2.4GHz 250mW Diversity RX (two antennas)
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
iFlight 2.4 GHz
Device:
iFlight 2.4GHz RX
iFlight 2.4GHz Nano RX (Smaller)
iFlight 2.4GHz 500mW RX
iFlight 2.4GHz 250mW Diversity RX (two antennas)
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
iFlight 2.4 GHz
Device:
iFlight 2.4GHz RX
iFlight 2.4GHz Nano RX (Smaller)
iFlight 2.4GHz 500mW RX
iFlight 2.4GHz 250mW Diversity RX (two antennas)
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/iflight900/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
IFlight 900MHz
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/iflight900/#identify-your-receiver-and-flash-the-correct-target","title":"Identify your receiver and flash the correct target","text":"
Important Step!
You MUST flash the correct firmware target to your receiver in order for it to work properly. Look closely at your receiver and make sure you are select the correct firmware target. Flashing the wrong target will result in extremely poor range or failure to connect.
How to identify the correct iFlight 900MHz receiver target
"},{"location":"quick-start/receivers/iflight900/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/iflight900/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
iFlight 900 MHz
Device:
iFlight 900MHz RX
iFlight 900MHz Nano RX (smaller)
iFlight 900MHz 500mW RX
iFlight 900MHz 500mW Diversity RX (two antennas)
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
Locate the Boot button on your receiver, press and hold it.
Plug in your UART Adapter into a USB Port on your Computer. Release/de-press the Boot button.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
iFlight 900 MHz
Device:
iFlight 900MHz RX
iFlight 900MHz Nano RX (smaller)
iFlight 900MHz 500mW RX
iFlight 900MHz 500mW Diversity RX (two antennas)
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
iFlight 900 MHz
Device:
iFlight 900MHz RX
iFlight 900MHz Nano RX (smaller)
iFlight 900MHz 500mW RX
iFlight 900MHz 500mW Diversity RX (two antennas)
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
iFlight 900 MHz
Device:
iFlight 900MHz RX
iFlight 900MHz Nano RX (smaller)
iFlight 900MHz 500mW RX
iFlight 900MHz 500mW Diversity RX (two antennas)
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
iFlight 900 MHz
Device:
iFlight 900MHz RX
iFlight 900MHz Nano RX (smaller)
iFlight 900MHz 500mW RX
iFlight 900MHz 500mW Diversity RX (two antennas)
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/jumper-aion/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
Jumper Aion Mini/Nano
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
Take Note
The Jumper Aion Mini has its antenna near the center, beside the boot button. The Jumper Aion Nano has its antenna near the edge, with another chip beside it.
"},{"location":"quick-start/receivers/jumper-aion/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/jumper-aion/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION Mini 2.4GHz RX
Jumper AION Nano 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
Locate the Boot button on your receiver, press and hold it.
Plug in your UART Adapter into a USB Port on your Computer. Release/de-press the Boot button.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION Mini 2.4GHz RX
Jumper AION Nano 2.4GHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION Mini 2.4GHz RX
Jumper AION Nano 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION Mini 2.4GHz RX
Jumper AION Nano 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION Mini 2.4GHz RX
Jumper AION Nano 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
"},{"location":"quick-start/receivers/jumper900/#flashingupdating-your-receiver-firmware","title":"Flashing/Updating your Receiver Firmware","text":"via STLinkvia Passthrough
Note
The only way to flash the Jumper R9 Mini to ExpressLRS for the first time is by using STLink. This is a one-way process. There is no returning to the factory firmware after flashing.
Disconnect the Receiver from your Flight Controller.
Wire up the Receiver into an STLink V2 dongle. Connect + to 3v3, - to GND, C to CLK and D to DIO.
Jumper R9 Mini
Because those pins are so small one option is to only solder wires on the CLK and DIO then power the receiver with the 5v pin with an external power source. Connect - (Gnd) to both power source and the STLink dongle.
Disable 'Readout Protection'. To do this download the ST-LINK Utility and follow this quick how to video. Or alternatively under linux you can use OpenOCD.
How to video:
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 900 MHz
Device:
Jumper 900 Mini RX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Rewire your receiver to your Flight Controller. Connect RX2 and TX2 (you will need to solder on the STM32 pins; see step 2 above) to a flight controller. Configure your flight controller per the FC Configuration Guide.
Note
This method can only be used to UPDATE the ExpressLRS firmware on a Jumper R9 mini.
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured. Also make sure [bootloaders] are already flashed to your R9 receiver when applicable.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
If you have to plug in LiPo to power up your Receiver, make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 900 MHz
Device:
Jumper 900 Mini RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the Retry... lines to appear in the Build Log. Connect the LiPo to power up the Receiver if it only powers up with a LiPo connected.
Retry... lines will not show up if your receiver is already in bootloader mode and gets powered up by USB.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/matek2400/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
R24-D Diversity R24-S SMD
The images above show the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/matek2400/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/matek2400/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Matek Systems 2.4 GHz
Device:
MATEK R24-S 2.4GHz RX
MATEK R24-D 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
If your Receiver has Boot Pads instead of a Boot Button, solder the Boot Pads together or connect it to Ground. If your Receiver has a Boot Button, locate it then press & hold it.
Plug in your UART Adapter into a USB Port on your Computer.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Once the LED on the Receiver is lit up Solid, release/de-press the button on the receiver if it has one.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Matek Systems 2.4 GHz
Device:
MATEK R24-S 2.4GHz RX
MATEK R24-D 2.4GHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
If your receiver has a boot pad instead of a boot button, make sure to disconnect it from ground or remove the solder bridge you made on step 2.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Matek Systems 2.4 GHz
Device:
MATEK R24-S 2.4GHz RX
MATEK R24-D 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Matek Systems 2.4 GHz
Device:
MATEK R24-S 2.4GHz RX
MATEK R24-D 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Matek Systems 2.4 GHz
Device:
MATEK R24-S 2.4GHz RX
MATEK R24-D 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
The R9Mini/R9MM, R9MX and R9Slim+ require ExpressLRS Bootloaders to be flashed before the ExpressLRS firmware. The R9Slim doesn't have a bootloader and first time flash requires STLink.
Download the bootloader .frk file for your respective receiver. The files are as follows:
R9mm/mini: r9mm_elrs_bl.frk (14kB) or r9mm_no_btn_elrs_bl.frk (14kB) (no_btn bootloader is only used if your bind/boot button on the receiver is faulty or has gone bad.)
Copy the relevant file to your handset's SD card (You can put it inside /FIRMWARE folder for easy access).
Wire the receiver to your radio's Smart Port, as shown:
Next, flash the .frk via the S.port flashing option in OpenTX or EdgeTX (It helps if the External RF module is set to PPM mode.)
Open the System Menu on the Radio
For radio handsets with dedicated System Key, press the SYS Key.
For radio handsets with a single Menu Key, long-press the Menu Key.
Press the Page Key until you reach the SD-HC Card page.
Select the FIRMWARE folder and press Enter.
Select the .frk bootloader file then long-press the Enter Key.
Select Flash external module and press Enter
Press Enter once the Writing is complete.
Once done, unplug the receiver and your bootloader is flashed.
FYI
You only need to flash the Bootloader ONCE. After it's flashed into the receiver, you don't have to reflash it in every update.
R9Slim doesn't have a bootloader. As such, you need to flash it first via STLink.
"},{"location":"quick-start/receivers/r9/#troubleshooting-no-sync","title":"Troubleshooting No Sync","text":"
Setting the External RF module to PPM mode helps.
Check if the receiver has its LED lit up or if it's powered.
Check whether you've set your Max Bauds to 115200, especially if you're using a QX7 or an X9D (on OneBit Firmware or EdgeTX). If so, put it back to 400000 and try again.
"},{"location":"quick-start/receivers/r9/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"Wiring up receiver
Note
This will be the same wiring you'll use for flying and the subsequent firmware updates (via Passthrough). Forget the factory wiring guide!
R9Slim need to be flashed via STLink first before you wire it up to your Flight Controller.
"},{"location":"quick-start/receivers/r9/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply on INAV, Betaflight and other flight controller software.
Ports Tab should be setup so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
"},{"location":"quick-start/receivers/r9/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia STLink
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured. Also make sure bootloaders are already flashed to your R9 receiver when applicable.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
If your receiver powers up with just USB connected to your flight controller, unplug it. Press and Hold the boot button on the receiver (not the FC) and then plug in the USB. Release the button once the green and red LEDs blink alternately.
If your receiver only powers up with a LiPo connected to your flight controller, unplug it. Then unplug-replug the USB cable to your flight controller. Do not replug LiPo yet.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
FrSky 900 MHz
Device:
FrSky R9MM/Mini 900MHz RX
FrSky R9MX 900MHz RX
FrSky R9 Slim 900MHz RX (If already flashed via STLink)
FrSky R9 Slim Plus 900MHz RX
FrSky R9 Slim Plus OTA 900MHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the Retry... lines to appear in the Build Log. Connect the LiPo to power up the Receiver if it only powers up with a LiPo connected.
Retry... lines will not show up if your receiver is already in bootloader mode and gets powered up by USB.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Disconnect the Receiver from your Flight Controller.
Wire up the Receiver into an STLink V2 dongle. Find the CLK, DIO, 3v3 and Gnd pads and wire them to the corresponding pins of the dongle.
R9Mini/R9MM
R9MX
R9Slim/R9Slim+
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
FrSky 900 MHz
Device:
FrSky R9MM/Mini 900MHz RX
FrSky R9MX 900MHz RX
FrSky R9 Slim 900MHz RX (If already flashed via STLink)
FrSky R9 Slim Plus 900MHz RX
FrSky R9 Slim Plus OTA 900MHz RX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/radiomaster-rp-2400/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
The images above show the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/radiomaster-rp-2400/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/radiomaster-rp-2400/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
RadioMaster 2.4 GHz
Device:
RadioMaster RP1 2.4GHz RX
RadioMaster RP2 2.4GHz RX
RadioMaster RP3 Diversity 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
If your Receiver has Boot Pads instead of a Boot Button, solder the Boot Pads together or connect it to Ground. If your Receiver has a Boot Button, locate it then press & hold it.
Plug in your UART Adapter into a USB Port on your Computer.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Once the LED on the Receiver is lit up Solid, release/de-press the button on the receiver if it has one.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
RadioMaster 2.4 GHz
Device:
RadioMaster RP1 2.4GHz RX
RadioMaster RP2 2.4GHz RX
RadioMaster RP3 Diversity 2.4GHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
If your receiver has a boot pad instead of a boot button, make sure to disconnect it from ground or remove the solder bridge you made on step 2.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
RadioMaster 2.4 GHz
Device:
RadioMaster RP1 2.4GHz RX
RadioMaster RP2 2.4GHz RX
RadioMaster RP3 Diversity 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
RadioMaster 2.4 GHz
Device:
RadioMaster RP1 2.4GHz RX
RadioMaster RP2 2.4GHz RX
RadioMaster RP3 Diversity 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
RadioMaster 2.4 GHz
Device:
RadioMaster RP1 2.4GHz RX
RadioMaster RP2 2.4GHz RX
RadioMaster RP3 Diversity 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
Note
This is only guaranteed to work on the v3.0 of the receiver.
"},{"location":"quick-start/receivers/siyiFRmini/#flashingupdating-your-receiver-firmware","title":"Flashing/Updating your Receiver Firmware","text":"via STLinkvia Passthrough
Note
The only way to flash the FR Mini to ExpressLRS for the first time is using STLink. This is a one-way process, there is no returning to the stock firmware after flashing.
Disconnect the Receiver from your Flight Controller.
Wire up the Receiver into an STLink V2 dongle. Find the CLK, DIO,RST, 3v3(VDD) and Gnd pads and wire them to the corresponding pins of the dongle.
NOTICE
VDD is 3.3v ONLY! Do not connect 5v here!
Siyi FR Mini
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
SIYI 2.4 GHz
Device:
SIYI FM30 Mini 2.4GHz RX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
This method can only be used to UPDATE the ExpressLRS firmware on an FRmini.
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured. Also make sure [bootloaders] are already flashed to your R9 receiver when applicable.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
If your receiver powers up with just USB connected to your flight controller, unplug it. Press and Hold the boot button on the receiver (not the FC) and then plug in the USB. Release the button right after the LED turn solid.
If your receiver only powers up with a LiPo connected to your flight controller, unplug it. Then unplug-replug the USB cable to your flight controller. Do not replug LiPo yet.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
SIYI 2.4 GHz
Device:
SIYI FM30 Mini 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the Retry... lines to appear in the Build Log. Connect the LiPo to power up the Receiver if it only powers up with a LiPo connected.
Retry... lines will not show up if your receiver is already in bootloader mode and gets powered up by USB.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
If your Receiver has Boot Pads instead of a Boot Button, solder the Boot Pads together or connect it to Ground. If your Receiver has a Boot Button, locate it, then press & hold it.
Plug in your UART Adapter into a USB Port on your Computer.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Once the LED on the Receiver is lit up Solid, release/de-press the button on the receiver if it has one.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
If your receiver has a boot pad instead of a boot button, make sure to disconnect it from ground or remove the solder bridge you made on step 2.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
If this is the first time you're flashing/updating your receiver or you're updating it from a previous 2.x firmware via WiFi, first ensure that it has version 2.5.2. Once it has the 2.5.2 flashed, you can then update it to 3.x via WiFi.
If you're flashing it straight to 3.x and you're getting \"Not Enough Space\" popup during WiFi flashing, flash the receiver to 2.5.2 first, and then flash it to 3.x.
If receiver firmware is already 3.x, and you're still getting the \"Not Enough Space\" error when flashing via WiFi, make sure you are selecting the correct method in the Configurator(via WiFi, in this case). See the steps outlined below.
You can update straight to 3.x via Passthrough or via UART.
The Repartitioner is for TX only.
"},{"location":"quick-start/receivers/vantac2400/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
Vantac ELRS 2.4GHz
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/vantac2400/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/vantac2400/#updating-your-receiver-firmware","title":"Updating your Receiver Firmware","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
Plug in a LiPo if your receiver doesn't power up with just USB connected into the Flight Controller. Make sure you have some airflow blowing over your Video Transmitter (VTX) to keep it cool. You can also temporarily unplug the VTX from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Vantac 2.4 GHz
Device:
Vantac 2.4GHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
Locate the Boot button on your receiver, press and hold it.
Plug in your UART Adapter into a USB Port on your Computer. Release/de-press the Boot button.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Vantac 2.4 GHz
Device:
Vantac 2.4GHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Vantac 2.4 GHz
Device:
Vantac 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Vantac 2.4 GHz
Device:
Vantac 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
Vantac 2.4 GHz
Device:
Vantac 2.4GHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
"},{"location":"quick-start/receivers/voyager900/","title":"NamimnoRC Voyager","text":""},{"location":"quick-start/receivers/voyager900/#check-your-target","title":"Check your Target","text":"
There are more ESP8285 based RXes in the market due to massive shortage of STM32 Chips. These support WiFi updating, and can be easily distinguished with a few tricks. The simplest way to tell is if on the rear of the RX (the side without the U.fl/SMD antenna) there is a large white component with the label RainSun (pictured below). If this is not there, you have an STM32 based target, if it is you have an _ESP_ target, and can update using Wifi!
RainSun Antenna
Note
New versions of the receiver also have the PCB Wifi Antenna, and doesn't have the RainSun SMD Antenna mentioned above. These will use the same ESP-based Target, not the STM-based target.
"},{"location":"quick-start/receivers/voyager900/#wiring-up-your-receiver","title":"Wiring up your receiver","text":"
Note
There are Flight Controllers that will pull the RX pads LOW which will put the ESP-based receivers into Bootloader Mode unintentionally. A solid LED light on these receivers even with the TX Module off is a sign they are in Bootloader Mode. If this is the case, rewire the receiver to a different UART.
The image above shows the receiver pinouts and their connections. As we're dealing with a UART connection, RX on the receiver goes to a TX pad on the FC, and TX on the receiver goes to an uninverted RX pad on the FC.
See the Receiver Wiring page for a more in-depth guide and troubleshooting procedures. Some of the updating procedures below will not go through if your receiver is not wired correctly and behaving properly.
"},{"location":"quick-start/receivers/voyager900/#configuring-your-flight-controller","title":"Configuring your Flight Controller","text":"
To configure your flight controller properly, please go through Configure FC page. These settings apply to INAV, Betaflight, and other flight controller software.
Ports Tab should be set up so that Serial RX is on the UART where you have soldered the receiver.
Receiver protocol is CRSF with serialrx_inverted = off and serialrx_halfduplex = off.
The next steps will not be able to proceed properly and you'll have issues later if any of these are set differently. Once you have configured your Flight Controller software, close its Configurator and unplug-replug the USB cable from the FC or your computer to refresh the connection and you'll be ensured that the port is not busy.
Some of the following procedures will not go through, particularly the via Passthrough method; or your receiver will not be fully functional, if these settings are incorrect.
"},{"location":"quick-start/receivers/voyager900/#updating-your-receiver-firmware-esp-based","title":"Updating your Receiver Firmware (ESP-based)","text":"via Passthroughvia UARTvia WiFi
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
Power-cycle the Flight Controller.
If you plugged in LiPo, unplug it.
Unplug-replug the USB Cable from your Flight Controller or Computer.
If you have to plug in LiPo to power up your Receiver, make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 900 MHz
Device:
NamimnoRC Voyager ESP 900MHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Connect your Receiver to your UART Adapter as shown in the image below.
YES, you will need to disconnect your Receiver from your Flight Controller and connect it to a UART/FTDI Adapter.
If your Receiver has Boot Pads instead of a Boot Button, solder the Boot Pads together or connect it to Ground. If your Receiver has a Boot Button, locate it then press & hold it.
Plug in your UART Adapter into a USB Port on your Computer.
The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
Once the LED on the Receiver is lit up Solid, release/de-press the button on the receiver if it has one.
Receiver LED already Solid (click/tap to expand)
If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the UART Adapter is not being detected corrrectly. This is indicated by a Yellow Caution Triangle in Device Manager.
Common USB-to-UART Adapter chip include: CP210x, FTDI FT232, CH340 and the CH9102 (driver download pages linked).
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 900 MHz
Device:
NamimnoRC Voyager ESP 900MHz RX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
If your receiver has a boot pad instead of a boot button, make sure to disconnect it from ground or remove the solder bridge you made on step 2.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your Receiver with your Home WiFi SSID and Password or it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 900 MHz
Device:
NamimnoRC Voyager ESP 900MHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS RX Access Point. Connect to this Access Point.
If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once you have connected to the ExpressLRS RX Access Point, open up a Browser window and type in the IP Address 10.0.0.1 on the Address Bar and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 900 MHz
Device:
NamimnoRC Voyager ESP 900MHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window should popup containing your firmware binaries.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. The file will be in a gzip format (firmware.bin.gz). Use this file as is, without extracting or unzipping.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your Receiver is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Heads up!
This option is only possible if you have previously flashed or configured your Receiver with your Home WiFi SSID and Password and the device is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_rx.local and load the ExpressLRS Web UI from said address.
Put your Receiver into WiFi mode.
using Auto WiFi modeusing the ExpressLRS Lua Script
Power up your Receiver.
If you will have to plug in LiPo to power up your Receiver:
make sure you've already checked the wiring from the Receiver Wiring step.
make sure you have some airflow blowing over your Video Transmitter (VTX). You can also temporarily unplug it from the Flight Controller.
If it's already powered and connected or in-sync with a TX Module, power Off the Radio & TX Module first, then power-cycle (Turn Off, then Turn back On) the Receiver.
Let it be for at least 60s and the LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
Note
This method only works if your Receiver is already in sync and bound with your TX Module.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable RX WiFi and press Enter.
The Receiver LED will turn into either a Rapid Blinking pattern or a Green Breathing LED pattern(for Receivers using an RGB LED) indicating it is now in WiFi Mode.
My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)
Go back to the Receiver Wiring step.
If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the Unbricking procedure to recover it.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 900 MHz
Device:
NamimnoRC Voyager ESP 900MHz RX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED after a few seconds.
"},{"location":"quick-start/receivers/voyager900/#updating-your-receiver-firmware-stm-based","title":"Updating your Receiver Firmware (STM-based)","text":"
Attention
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
via Passthroughvia STLink
Make sure you have done your Receiver Wiring properly and that your Flight Controller is Configured.
Important Step!
This is an important step and guarantees updating success. If you haven't done these, GO BACK to those pages.
Disconnect and close your FC Configurator app (Betaflight Configurator, INAV Configurator, etc).
If your receiver powers up with just USB connected to your flight controller, unplug it. Press and Hold the boot button on the receiver (not the FC) and then plug in the USB. Release the button right after the LED turn solid.
If your receiver only powers up with a LiPo connected to your flight controller, unplug it. Then unplug-replug the USB cable to your flight controller. Do not replug LiPo yet.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 900 MHz
Device:
NamimnoRC Voyager STM 900MHz RX
Set the Flashing Method to BetaflightPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the Retry... lines to appear in the Build Log. Connect the LiPo to power up the Receiver if it only powers up with a LiPo connected.
Retry... lines will not show up if your receiver is already in bootloader mode and gets powered up by USB.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Disconnect the Receiver from your Flight Controller.
Wire up the Receiver into an STLink V2 dongle. Find the CLK, DIO, 3v3 and Gnd pads and wire them to the corresponding pins of the dongle.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your Receiver.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 900 MHz
Device:
NamimnoRC Voyager STM 900MHz RX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
The LED on the Receiver should return to Slow Blinking LED pattern after a few seconds.
Manufacturer-suggested Receiver UARTs, or UARTs alloted for Receivers usually have a pull-down resistor to aid with SBUS (RX pad inversion) which will result into SOLID LEDs on the ESP-based ExpressLRS Receivers. It is best to avoid those UARTs unless you know your UARTs.
Hint!
KISS FCs may label its UARTs differently. You might have to wire up the RX pin into an RX pad, and the TX pin into a TX pad. Always check your FC wiring guide/manual.
UART-based ExpressLRS Receivers use the CRSF Serial Protocol to communicate with a Flight Controller. This protocol uses two pins: one for the Control Signals and the other for the Telemetry Signals. Think of it as a two-lane, no-counterflow highway.
Here's a typical ExpressLRS Receiver pinout indicating to which Flight Controller pads each pin should be connected:
The TX pin of an ExpressLRS Receiver sends or transmits the Control Signals it received from the Radio to the Flight Controller. Meanwhile, the RX pin of an ExpressLRS Receiver accepts or receives the Telemetry Data (like Battery Voltage, Current Draw, GPS Coordinates and/or Craft Attitude) from the Flight Controller for sending back to the Radio Handset.
What's a UART? (click/tap to expand)
A UART is a pair of RX and TX pads on the Flight Controller. It's commonplace to refer to it as your Flight Controller's USB ports where you can connect different peripherals like a GPS or a Receiver. Only one device can occupy a UART and it can only do one function.
R3 and T3 belongs to UART3; RX2 and TX2 belongs to UART2. Flight Controller Manufacturers label their UARTs differently. Some use just \"R\" and \"T\" followed by the UART number. Others use \"RX\" and \"TX\" followed by the UART number.
UART is an acronym for Universal Asynchronous Receiver/Transmitter
"},{"location":"quick-start/receivers/wiring-up/#connecting-a-receiver","title":"Connecting a Receiver","text":"
Now that you have some basic info, connect your receiver to any free UART on your Flight controller. Check your Flight Controller Wiring Manual which UARTs you can use.
The GND or G pad should be connected to any Ground pad on the Flight Controller(FC)
The VCC or 5 pad should be connected to any 5v (or 4v5) pad on the Flight Controller(FC)
The TX or T pad should be connected to an RX pad of the same UART number where the RX or R wire is on the Flight Controller(FC)
The RX or R pad should be connected to a TX pad of the same UART number where the TX or T wire is on the Flight Controller(FC)
Check for shorts between pads and clean up flux or any soldering residue if you have soldered the receiver yourself.
Not so fast!
DO NOT shrink wrap or tuck away the receiver yet. We have to do some preliminary testing first!
Ensure there are no shorts on your wiring and power up the receiver.
Best to power up the flight controller with a LiPo to ensure the receiver will work normally on flight-ready conditions.
It is important to ensure there are no shorts on your wiring BEFORE you power up the system.
Observe the Receiver LED. It should have one of these behaviors:
LED Indication Status Slow blink 500ms on/off Waiting for connection from transmitter Double blink then pause Binding mode is active Fast blinking 25ms on/off WiFi mode has started. Starts after 60s. Solid on Bootloader mode is active
If the Receiver uses an RGB LED(e.g. Foxeer LNA, BetaFPV SuperD, Happymodel EP Dual), the following can be observed:
LED Indication Status Rainbow fade effect Starting Up Slow blink 500ms on/off Waiting for connection from transmitter Orange Double blink then pause Binding mode enabled Green heartbeat WiFi mode has started. Starts after 60s
If the Receiver LED doesn't light up at all, quickly disconnect the power and check your wiring.
If your receiver has the RGB LED (e.g. Foxeer LNA, BetaFPV SuperD, Happymodel EP Dual), and the receiver LED is not lighting up despite making sure it's wired up correctly, this could mean that the Receiver is in Bootloader Mode.
If your Receiver LED lights up but it's just a Solid light, it is in Bootloader mode as the chart above indicates.
My Receiver is in Bootloader Mode! (click/tap to expand)
Here are the things you can do if the Receiver is in Bootloader Mode:
Check if the Boot button on the Receiver is being pressed or if it's damaged.
If the button is being pressed or pinched, remove the cause of the pressing or pinching. Heatshrink can sometimes press a button on the receiver.
If the button is damaged, remove the button or replace the receiver with a better one. Consider asking the seller for a replacement.
If the receiver doesn't have a Boot button and instead has a Boot pad, check if the Boot pad is not connected to a Ground pad.
If the Boot pad is connected to a Ground pad, disconnect or remove the connection.
Disconnect the RX and TX wires of the Receiver from the Flight Controller. Reconnect power to the drone or aircraft. Observe the LED on the Receiver once again.
If it starts Blinking Slowly (500ms Blink Pattern), you will need to move the receiver wiring to a different UART.
If the other UART is occupied by another peripheral, disconnect it and swap places with the Receiver.
If there is no other Full UART, you can try wiring a Pull-up Resistor: Connect a Resistor (300 Ohm to 1k Ohm value; a lower value is more effective) between this UART's RX pad and either a 5v or 3.3v pad as shown below:
If you are using any of the Digital FPV systems like the DJI FPV Air Unit, Caddx Vista or DJI O3 Air Unit, and you wired or connected all six wires to your Flight Controller, you will need to remove the SBUS/DJI HDL wire.
If your receiver is behaving normally (i.e. not in Bootloader Mode), then you can power down your aircraft and proceed to the next step: Configuring your Flight Controller
Not all Jumper T Pros come with an internal ELRS transmitter. Some come with a \"JP4in1 multi-protocol module\" or \"CC2500 multi-protocol module\". This tutorial does not apply to those Jumper T Pros. Check the page you bought it from to determine which unit you purchased.
Advisory
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
"},{"location":"quick-start/transmitters/aion-internal/#updating-and-recovery-procedures","title":"Updating and Recovery Procedures","text":"via WiFi Updatingvia ETX Passthrough Recoveryvia UART Recovery Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device Target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION T-Pro 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device Target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION T-Pro 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device Target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION T-Pro 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Info
ETX Passthrough is the result of the collaborative effort between RadioMaster, EdgeTX and ExpressLRS.
It is only available on Radios with Internal ExpressLRS Modules.
Before you start, ensure you have the latest EdgeTX firmware version on your Radio. Consult the EdgeTX documentation regarding the updating process.
For the Jumper T-Pro, update it to at least EdgeTX 2.7.1 (a55aff0) for full EdgeTX support.
Hot Tip
To ensure updating success with this method, update the EdgeTX firmware on the radio to at least EdgeTX 2.7.1 (a55aff0). The EdgeTX Firmware that comes with this radio is a pre-release version.
Simplest EdgeTX Updating Procedure (click/tap to expand)
Visit http://buddy.edgetx.org/.
Select the EdgeTX version and the Radio Model you want to update from the Left-hand side column.
Click the Download .bin button at the bottom of the page.
Save the firmware file into your Radio's SD Card, inside the Firmware Folder.
Reboot the Radio into DFU/Bootloader mode.
Turn off your radio.
Press and hold the two horizontal Trim switches then press the Power button. The Screen should Light up. Let go of the buttons.
Some Radios have a different procedure, like the BetaFPV Lite Radio 3 Pro. Consult the Manual for the steps to get it into this DFU/Bootloader mode.
Select Write Firmware.
Navigate to the EdgeTX firmware file you just downloaded.
Follow the screen prompts.
Once Writing is complete, reboot the radio.
Check the Radio's Version Page to verify you have the version you need.
Also, make sure you have an internal ELRS module on your Radio. The following steps only apply to handsets with ExpressLRS-specific internal modules.
The current Model on the radio should be using the Internal ExpressLRS Module. Test this by loading the ExpressLRS Lua Script from the Tools Menu.
There's one more setting you want to make sure is set properly before proceeding.
Press the SYS Key on the Radio.
Radios without a dedicated SYS Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to get to the System Menu.
Press the PAGE Key until you reach the Hardware Page.
Scroll down until you see the Serial Ports settings.
Select or highlight USB-VCP. Press Enter and use the Scroll Wheel to set it to CLI mode if it is set to a different setting. Press Enter once more to confirm the changes.
Exit the Hardware menu by long-pressing RTN Key.
Before proceeding, you will need to disassemble the radio. You will need a small Philips screwdriver for this. Ten(10) small Philips screws keep both halves of the radio together.
Handle with Care
There are wires connecting the module to the main board of the radio, along with battery leads. Do not yank out the back cover of the radio from its front half. You don't need to disconnect the wires from the mainboard.
Once you have both halves of the radio apart, you will need to solder a piece of wire on the Boot pad into one of the momentary switches on the radio. Refer to the image below where to solder the ends of the wire.
Once the wire is soldered adequately, reassemble the radio. Tighten up the ten(10) screws to secure both halves of the radio.
Note
If you plan to use the switch as an Aux channel, remove the wire afterward. Leaving this wire connected means the Aux channel will output a constant \"High\" signal.
Now follow the next steps to get your Internal ExpressLRS Module Updated or Recovered:
Connect your powered-up Radio to your Computer via a USB Data Cable.
On your Radio, scroll down and select USB Serial(VCP) then press the Enter Key. Set your Radio aside in the meantime.
On your Computer, check whether your Radio is being recognized correctly as a STMicroelectronics Virtual COM Port device.
Important
This is a vital step and a common failure point. Pay attention.
Windows Users can use Device Manager to check whether the Radio is being recognized correctly.
Yellow Caution Triangles in the Device Manager, or any mention of <Radio Name> Serial Port means drivers aren't installed.
Download the Driver package first. Unzip/extract the contents of the package and run/execute (double-click) the installer file (VCP_V1.5.0_Setup_W7_x64_64bits.exe for Windows 10 Users).
Once Drivers are installed, check again if the Radio is now being recognized correctly. You may have to first unplug-replug the USB Cable or even reboot your computer.
You only have to do this once usually.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device Target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION T-Pro 2.4GHz TX
Set the Flashing Method to EdgeTXPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the Passthrough Init or Passthrough Done section of the log and Press the switch in the radio where you wired up the boot button and hold it until the script has connected. See the image below for the correct timing.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
If you didn't get it right and it fails, don't worry. Just retry and it should go through.
Unplug your Radio from USB.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated or you have it recovered.
Disassemble the radio. You will need a small Philips screwdriver for this. Ten(10) small Philips screws keep both halves of the radio together.
Handle with Care
There are wires connecting the module to the main board of the radio, along with battery leads. Do not yank out the back cover of the radio from its front half. You don't need to disconnect the wires from the mainboard.
Disconnect the internal module from the mainboard of the radio. The pin-out is as follows:
White wire is the RX.
Yellow wire is the TX.
Red wire is the 5v pin.
The Black wire is the Gnd pin.
Connect these four wires into your FTDI dongle or a USB to Serial Adapter: RX pin into the TX pin; TX pin into the RX pin; 5v to 5v, and Gnd to Gnd.
Before you connect the FTDI dongle/Serial Adapter to the USB port of your Computer, hold down the Boot button. Keep the button pressed until you have connected the Serial Adapter to your USB port.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device Target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION T-Pro 2.4GHz TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Attention
Incorrect or loose connections can cause this method to fail. If it does, disconnect the Serial Adapter from the USB, ensure you have the proper connection, and repeat the process. Press and hold the boot button before connecting the Serial Adapter to the USB.
Disconnect the FTDI/UART Adapter and reconnect the module back to the radio mainboard, as shown below.
Reassemble the radio (but do not put in the screws yet) and verify you have a working module once by running the ExpressLRS Lua script.
Once you've verified that your Internal ExpressLRS module is working, replace the screws and tighten things up. Chug one down and celebrate!
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
"},{"location":"quick-start/transmitters/axisflying-thor/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia UART Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Axisflying 2.4 GHz
Device:
AXIS Thor 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Axisflying 2.4 GHz
Device:
AXIS Thor 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Axisflying 2.4 GHz
Device:
AXIS Thor 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here: CP210x Drivers
Windows Users should download the CP210x Windows Drivers package for easier installation. Unzip/Extract the contents of the package and run the setup wizard.
Make sure the switch on the backside of the module is set to the leftmost position.
Note
To flash the TX itself, the switch on the back side of the module must be set to the leftmost position. To flash the TX backpack, the switch must be set to the rightmost position. For normal operation, the switch must be centered.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Axisflying 2.4 GHz
Device:
AXIS Thor 2.4GHz TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB. Return the switch in the back to \"Normal Operation\" position, center.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
"},{"location":"quick-start/transmitters/axisflying-thor/#using-the-module-on-a-dx9","title":"Using the module on a DX9","text":"
Install the latest DX9 firmware with CRSF v2 support via Serial port.
Wire up Power (VBAT & GND) as per Crossfire install instructions.
Use Signal from DX9 to S.Port pin of the Thor TX module.
Optional: Connect an external power source via XT30.
Flash the TX module with UART_INVERTED unchecked.
Adjust your Packet Rate to 250Hz using the Screen & Joystick.
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
"},{"location":"quick-start/transmitters/betafpv2400/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia UART Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz Nano TX
BETAFPV 2.4GHz Micro TX
BETAFPV 2.4GHz 1W Micro TX
BETAFPV SuperG 2.4GHz Gemini TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz Nano TX
BETAFPV 2.4GHz Micro TX
BETAFPV 2.4GHz 1W Micro TX
BETAFPV SuperG 2.4GHz Gemini TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz Nano TX
BETAFPV 2.4GHz Micro TX
BETAFPV 2.4GHz 1W Micro TX
BETAFPV SuperG 2.4GHz Gemini TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here: CP210x Drivers
Windows Users should download the CP210x Windows Drivers package for easier installation. Unzip/Extract the contents of the package and run the setup wizard.
Some TX Modules have switches to change how the USB port interacts with the different components in the module. Make sure to set it in the position for \"Flashing the TX Module via UART\".
The BetaFPV Micro modules have dipswitches at the back. Set switches 1 & 2 to On, set the rest of the switches to Off.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz Nano TX
BETAFPV 2.4GHz Micro TX
BETAFPV 2.4GHz 1W Micro TX
BETAFPV SuperG 2.4GHz Gemini TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB. Return the dipswitches at the back into the \"Normal Operation\" position.
Switches 1,2,5,6,7 should be Off; 3 & 4 should be On. Applicable to the Micro-size module only.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
If you've followed any of the steps above and still cannot get your devices flashed and updated, see this video for the explanation of why and the fix to get your devices flashed and updated (applies to the Nano modules only).
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
"},{"location":"quick-start/transmitters/betafpv900/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia UART Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV 900MHz Nano TX
BETAFPV 900MHz Micro TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV 900MHz Nano TX
BETAFPV 900MHz Micro TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV 900MHz Nano TX
BETAFPV 900MHz Micro TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here: CP210x Drivers
Windows Users should download the CP210x Windows Drivers package for easier installation. Unzip/Extract the contents of the package and run the setup wizard.
Some TX Modules have switches to change how the USB port interacts with the different components in the module. Make sure to set it in the position for \"Flashing the TX Module via UART\".
The BetaFPV Micro modules have dipswitches at the back. Set switches 1 & 2 to On, set the rest of the switches to Off.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 900 MHz
Device:
BETAFPV 900MHz Nano TX
BETAFPV 900MHz Micro TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB. Return the dipswitches at the back into the \"Normal Operation\" position.
Switches 1,2,5,6,7 should be Off; 3 & 4 should be On. Applicable to the Micro-size module only.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
If you've followed any of the steps above and still cannot get your devices flashed and updated, see this video for the explanation of why and the fix to get your devices flashed and updated (applies to the Nano modules only).
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
"},{"location":"quick-start/transmitters/betafpvlr3pro/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia ETX Passthrough Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz LiteRadio 3 Pro
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz LiteRadio 3 Pro
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz LiteRadio 3 Pro
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Info
ETX Passthrough is the result of the collaborative effort between RadioMaster, EdgeTX and ExpressLRS.
It is only available on Radios with Internal ExpressLRS Modules.
Before you start, ensure you have the latest EdgeTX firmware version on your Radio. Consult the EdgeTX documentation regarding the updating process.
For the BetaFPV Lite Radio 3 Pro, update it to at least EdgeTX 2.8.0 (f6d140e) for full EdgeTX support.
Hot Tip
To ensure updating success with this method, update the EdgeTX firmware on the radio to at least EdgeTX 2.8.0 (f6d140e, released Nov. 27, 2022). The EdgeTX Firmware that comes with this radio is a pre-release version.
Simplest EdgeTX Updating Procedure (click/tap to expand)
Visit http://buddy.edgetx.org/.
Select the EdgeTX version and the Radio Model you want to update from the Left-hand side column.
Click the Download .bin button at the bottom of the page.
Save the firmware file into your Radio's SD Card, inside the Firmware Folder.
Reboot the Radio into DFU/Bootloader mode.
Turn off your radio.
Press and hold the two horizontal Trim switches then press the Power button. The Screen should Light up. Let go of the buttons.
Some Radios have a different procedure, like the BetaFPV Lite Radio 3 Pro. Consult the Manual for the steps to get it into this DFU/Bootloader mode.
Select Write Firmware.
Navigate to the EdgeTX firmware file you just downloaded.
Follow the screen prompts.
Once Writing is complete, reboot the radio.
Check the Radio's Version Page to verify you have the version you need.
Also, make sure you have an internal ELRS module on your Radio. The following steps only apply to handsets with ExpressLRS-specific internal modules. You can find a sticker at the bottom of the box that the radio came in with containing the barcode and the radio stick mode and type.
The current Model on the radio should be using the Internal ExpressLRS Module. Test this by loading the ExpressLRS Lua Script from the Tools Menu.
There's one more setting you want to make sure is set properly before proceeding.
Press the SYS Key on the Radio.
Radios without a dedicated SYS Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to get to the System Menu.
Press the PAGE Key until you reach the Hardware Page.
Scroll down until you see the Serial Ports settings.
Select or highlight USB-VCP. Press Enter and use the Scroll Wheel to set it to CLI mode if it is set to a different setting. Press Enter once more to confirm the changes.
Exit the Hardware menu by long-pressing RTN Key.
Now follow the next steps to get your Internal ExpressLRS Module Updated:
Connect your powered-up Radio to your Computer via a USB Data Cable.
On your Radio, scroll down and select USB Serial(VCP) then press the Enter Key. Set your Radio aside in the meantime.
On your Computer, check whether your Radio is being recognized correctly as a STMicroelectronics Virtual COM Port device.
Important
This is a vital step and a common failure point. Pay attention.
Windows Users can use Device Manager to check whether the Radio is being recognized correctly.
Yellow Caution Triangles in the Device Manager, or any mention of <Radio Name> Serial Port means drivers aren't installed.
Download the Driver package first. Unzip/extract the contents of the package and run/execute (double-click) the installer file (VCP_V1.5.0_Setup_W7_x64_64bits.exe for Windows 10 Users).
Once Drivers are installed, check again if the Radio is now being recognized correctly. You may have to first unplug-replug the USB Cable or even reboot your computer.
You only have to do this once usually.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
BETAFPV 2.4 GHz
Device:
BETAFPV 2.4GHz LiteRadio 3 Pro
Set the Flashing Method to EdgeTXPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your Radio from USB.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
"},{"location":"quick-start/transmitters/diy2400/","title":"DIY 2400TX","text":""},{"location":"quick-start/transmitters/diy2400/#flashing-via-usbuart-esp32","title":"Flashing via USB/UART (ESP32)","text":"
Targets:
DIY_2400_TX_ESP32_SX1280_E28_via_UART
DIY_2400_TX_ESP32_SX1280_LORA1280F27_via_UART
DIY_2400_TX_ESP32_SX1280_Mini_via_UART
Plug the ESP32 of the DIY TX into the USB of your computer. Then select the correct target given the RF chip you chose and press Build & Flash. Further updates can be performed by building and flashing the .bin file to the external module using OpenTX.
"},{"location":"quick-start/transmitters/diy900/","title":"DIY 900TX","text":""},{"location":"quick-start/transmitters/diy900/#flashing-via-usbuart-esp32","title":"Flashing via USB/UART (ESP32)","text":"
Targets:
DIY_900_TX_ESP32_SX127x_E19_via_UART
DIY_900_TX_ESP32_SX127x_RFM95_via_UART
Plug the ESP32 of the DIY TX into the USB of your computer. Then select the correct target given the RF chip you chose and press Build & Flash. Further updates can be performed by building and flashing the .bin file to the external module using OpenTX.
"},{"location":"quick-start/transmitters/diy900/#flashing-via-usbuart-ttgo","title":"Flashing via USB/UART (TTGo)","text":"
Targets:
DIY_900_TX_TTGO_V1_SX127x_via_UART
DIY_900_TX_TTGO_V2_SX127x_via_UART
Plug the TTGo into the USB of your computer. Then select the correct target given the version you have and press Build & Flash. Further updates can be performed by building and flashing the .bin file to the external module using OpenTX.
These devices come pre-installed with a 3.x-ready firmware. You don't need to reflash these devices. You can use the Web UI of these devices to update the Binding Phrase or any of the firmware options.
"},{"location":"quick-start/transmitters/emax2400/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia UART Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
EMAX 2.4 GHz
Device:
EMAX Nano 2.4GHz TX
EMAX OLED 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
EMAX 2.4 GHz
Device:
EMAX Nano 2.4GHz TX
EMAX OLED 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
EMAX 2.4 GHz
Device:
EMAX Nano 2.4GHz TX
EMAX OLED 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here: CP210x Drivers
Windows Users should download the CP210x Windows Drivers package for easier installation. Unzip/Extract the contents of the package and run the setup wizard.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
EMAX 2.4 GHz
Device:
EMAX Nano 2.4GHz TX
EMAX OLED 2.4GHz TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
These devices come pre-installed with a 3.x-ready firmware. You don't need to reflash these devices. You can use the Web UI of these devices to update the Binding Phrase or any of the firmware options.
"},{"location":"quick-start/transmitters/emax900/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia UART Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
EMAX 900 MHz
Device:
EMAX Nano 900MHz TX
EMAX OLED 900MHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
EMAX 900 MHz
Device:
EMAX Nano 900MHz TX
EMAX OLED 900MHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
EMAX 900 MHz
Device:
EMAX Nano 900MHz TX
EMAX OLED 900MHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here: CP210x Drivers
Windows Users should download the CP210x Windows Drivers package for easier installation. Unzip/Extract the contents of the package and run the setup wizard.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
EMAX 900 MHz
Device:
EMAX Nano 900MHz TX
EMAX OLED 900MHz TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
This guide applies to all of the following HappyModel TX modules: ES24TX, ES24TX Lite, ES24TX Iron Man, ES24TX Slim Pro and ES24TX Pro Micro. Any module with \"Pro\" in the name uses the _Pro_Series target.
Advisory
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
"},{"location":"quick-start/transmitters/es24tx/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia UART Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
HappyModel ES24 Pro 2.4GHz TX for ES24TX Pro Micro
HappyModel ES24 Slim Pro 2.4GHz TX for ES24TX Slim Pro
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
HappyModel ES24 Pro 2.4GHz TX for ES24TX Pro Micro
HappyModel ES24 Slim Pro 2.4GHz TX for ES24TX Slim Pro
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
HappyModel ES24 Pro 2.4GHz TX for ES24TX Pro Micro
HappyModel ES24 Slim Pro 2.4GHz TX for ES24TX Slim Pro
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
For these TX Modules, you will have to take off the front cover to get access to the USB Port and/or dipswitches/jumper blocks.
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here: CP210x Drivers
Windows Users should download the CP210x Windows Drivers package for easier installation. Unzip/Extract the contents of the package and run the setup wizard.
These TX Modules have switches to change how the USB port interacts with the different components in the module. Make sure to set it in the position for \"TX Module Flashing via UART\".
ES24TX Full Size, Non Pro
ES24TX Lite, for Jumper T-Lite
ES24TX Slim, Iron Man
ES24TX Slim Pro
ES24TX Pro 1W
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
HappyModel ES24 Pro 2.4GHz TX for ES24TX Pro Micro
HappyModel ES24 Slim Pro 2.4GHz TX for ES24TX Slim Pro
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB. Return any dipswitches or jumper blocks to their \"Normal Operation\" position.
Reattach the TX module cover, making sure no wires are being pinched and the antenna pigtail is connected properly.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
"},{"location":"quick-start/transmitters/es900tx/","title":"Happymodel ES900TX","text":""},{"location":"quick-start/transmitters/es900tx/#flashingupdating-the-es900tx-firmware","title":"Flashing/Updating the ES900TX Firmware","text":"
Advisory
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
via WiFivia UART
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel TX ES900TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel ES900 TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel ES900 TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
You will need to disassemble your TX Module to get access to the USB Port and the dipswitches.
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here: CP210x Drivers
Windows Users should download the CP210x Windows Drivers package for easier installation. Unzip/Extract the contents of the package and run the setup wizard.
This TX Module has switches to change how the USB port interacts with the different components in the module. Make sure to set it in the position for \"Flashing the TX Module via UART\".
Set switches 5 & 6 to On, and set the others to Off.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel ES900 TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB. Return the dipswitches to the \"Normal Operation\" position (1 & 2 is On, 3,4,5,6 are Off).
Reassemble the TX Module, making sure no wires are being pinched and the antenna pigtail is connected properly.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
"},{"location":"quick-start/transmitters/es900tx/#flashingupdating-the-es915txes868tx-firmware","title":"Flashing/Updating the ES915TX/ES868TX Firmware","text":"
Attention
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
via Stock_BLvia STLink
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel ES915 TX
Set the Flashing Method to Stock_BL
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Build button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
A Temp folder will open up with the firmware.elrs file. Copy-paste the firmware.elrs file into your Radio's SD Card (preferably to the /FIRMWARE folder for easy access).
On your radio, open the System Menu.
On newer radios, you can press the SYS key to open the System Menu
On older radios, or radios that only have a menu key, long-press the Menu key to open the System Menu
Using the Page key/s, navigate to the SD-HC Card page, scroll-down and open the FIRMWARE folder where you can find the firmware.elrs file.
Highlight the file and press-hold the Enter button and select \"Flash External ELRS\". Wait for the firmware to be written.
No Sync (click/tap to expand)
Make sure you have updated the OpenTX/EdgeTX firmware of your radio to a newer version
Make sure the current model selected on the radio is set up for ExpressLRS Use. See the [Radio Preparation] guide.
With the ExpressLRS Lua Script in the Tools page, verify if the firmware version has been updated.
Disassemble your TX Module to get access to the mainboard.
Connect your STLink V2 dongle to the pads shown in the image below.
Connect your STLink V2 dongle to your Computer's USB Port. Make sure it is being detected properly.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Happymodel 900 MHz
Device:
HappyModel ES915 TX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Disconnect the STLink V2 dongle from the TX Module PCB and reassemble the TX Module.
Reattach your TX Module to your Radio and, using the ExpressLRS Lua Script, verify if the firmware version has been updated.
"},{"location":"quick-start/transmitters/firmware-version/","title":"Checking FW Version","text":""},{"location":"quick-start/transmitters/firmware-version/#why-do-you-have-to-know-the-firmware-version","title":"Why do you have to know the Firmware Version?","text":"
Knowing the ExpressLRS Firmware Version that's currently in your devices will determine whether there is a need to update to a newer version or whether you can simply get your devices bound together without updating. For newcomers in the hobby, or for those just starting with ExpressLRS, it can be a bit daunting to flash a new device.
It is still recommended that you update your gear to the latest firmware version to ensure you have all the bug fixes and latest features.
There are three methods to determine what firmware version you currently have on your Transmitter module
via Lua Scriptvia OLED Screenvia Web UI
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter Key to activate the Script.
If the script is stuck on a \"Loading...\" screen, go back to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll to the bottom of the page and you should see the Current Version flashed into your TX module.
Shows both have 3.2.1 Firmware Version with the Git Hash 8dbbdb.
Colored Screens ExpressLRS Lua Script Version Line
Mono Screens ExpressLRS Lua Script Version Line
If your External TX module is equipped with a Screen, the Home Screen should show the different parameters currently configured on the module. It will also show the current firmware version flashed into the module.
OLED Screen Version Line
Put your module into WiFi mode.
using the ExpressLRS Lua Scriptusing Auto WiFi mode
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, go back to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
If the Script stopped and is showing a Syntax Error, do not worry. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware or both. It could also be due to the fact your TX module is on an earlier firmware version and you're using a more recent Lua Script.
With your TX module disconnected from your Radio module bay, power it up either via an external power source (2S) or by plugging in a USB cable into its USB Port.
Let it be for at least 60s and the RGB LED will turn into a Green Breathing LED pattern indicating it is now in WiFi Mode.
The Auto WiFi On Interval setting controls how long the device will wait to initiate WiFi Mode when it's powered up and it's not getting valid CRSF packets.
TX Modules with an OLED Screen will also show a message to indicate it is in WiFi Mode.
Scan for the ExpressLRS TX Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also, try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Load the Web UI on your browser using these addresses:
http://10.0.0.1/ -If you have connected to the ExpressLRS TX Access Point
Note
This IP address is also often used by some routers. Computers with an ethernet connection to their routers will find that this page doesn't load the ExpressLRS Web UI and instead loads their router or ISP modem configuration dashboards.
We recommend disconnecting from the network first or trying a different device instead, e.g. smartphone or tablet.
http://elrs_tx.local - If you have previously set your Home WiFi SSID and Password into your TX Module when you flashed it.
Note
If your browser cannot resolve this address, chances are MDNS is not set up and working on your computer or network.
Use the IP Address instead! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a which will list all the devices in the Network.
Try each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in to your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
The Banner of the Web UI should tell you the firmware version flashed into your TX module.
The ExpressLRS Web UI Banner
Once you have determined the firmware version that's currently flashed into your Transmitter module, you can now decide to whether keep using it as is or update to the latest version.
Versioning Scheme
The ExpressLRS Firmware Versioning scheme is based on the semantic versioning scheme.
A Version is defined or formatted as \"Major.Minor.Patch\"
- major = major new feature and/or incompatible changes\n- minor = minor features or enhancements and/or new targets\n- patch = bug-fixes\n
That first number in the Version string should match between a TX Module and a Receiver. Examples:
a TX Module with version string of 3.1.2 will sync and work with a Receiver with firmware version 3.0.1
a TX Module with version string of 3.2.0 will NOT sync or bind with a Receiver with firmware version 2.4.0
For the latest ExpressLRS firmware version, check the Releases page in Git Hub
"},{"location":"quick-start/transmitters/firmware-version/#i-know-the-version-what-now","title":"I Know the Version. What Now?","text":"I have an old versionI have a recent one
See the next page for the typical updating procedure or expand the Updating Transmitters section of the Menu on the left as shown below.
You can also use the Search Bar on top of this page to search for the specific Updating/Flashing Guide for your TX Module.
See the Binding Procedure to sync your TX Module with your Receiver.
"},{"location":"quick-start/transmitters/flash2400/","title":"NamimnoRC Flash","text":""},{"location":"quick-start/transmitters/flash2400/#flashingupdating-the-flash-oled-firmware","title":"Flashing/Updating the Flash OLED Firmware","text":"
Advisory
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
via WiFivia UART
Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash OLED 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash OLED 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash OLED 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
Determine whether your TX Module is being detected properly as a USB-SERIAL CH340 device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here:
Windows Users will need the CH340 Drivers (Right-click, Save-as) installed (Unzip the contents of the file; Run the executable installer) for this to work properly.
For other Operating Systems, head to this site to download your needed drivers.
This TX Module has switches to change how the USB port interacts with the different components in the module. Make sure it is set as shown. This is the default position and unless you have moved it before, there's no need to open up the module.
Attention
The left position of the switch is for flashing the backpack. The right position of the switch is for flashing the TX itself. The right position is the default, so there is no need to open your module unless you need to unbrick your TX backpack!
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash OLED 2.4GHz TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
"},{"location":"quick-start/transmitters/flash2400/#flashingupdating-the-flash-non-oled-firmware","title":"Flashing/Updating the Flash Non-OLED Firmware","text":"
Attention
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
via Stock_BLvia STLink
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash 2.4GHz TX
Set the Flashing Method to Stock_BL
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Build button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
A Temp folder will open up with the firmware.elrs file. Copy-paste the firmware.elrs file into your Radio's SD Card (preferably to the /FIRMWARE folder for easy access).
On your radio, open the System Menu.
On newer radios, you can press the SYS key to open the System Menu
On older radios, or radios that only have a menu key, long-press the Menu key to open the System Menu
Using the Page key/s, navigate to the SD-HC Card page, scroll-down and open the FIRMWARE folder where you can find the firmware.elrs file.
Highlight the file and press-hold the Enter button and select \"Flash External ELRS\". Wait for the firmware to be written.
No Sync (click/tap to expand)
Make sure you have updated the OpenTX/EdgeTX firmware of your radio to a newer version
Make sure the current model selected on the radio is set up for ExpressLRS Use. See the [Radio Preparation] guide.
With the ExpressLRS Lua Script in the Tools page, verify if the firmware version has been updated.
Attention
Only use this method if the firmware has been corrupted.
Disassemble your TX Module to get access to the mainboard.
Connect your STLink V2 dongle to the pads shown in the image below.
Connect your STLink V2 dongle to your Computer's USB Port. Make sure it is being detected properly.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 2.4 GHz
Device:
NamimnoRC Flash 2.4GHz TX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Disconnect the STLink V2 dongle from the TX Module PCB and reassemble the module.
Reattach your TX Module into your Radio and, using the ExpressLRS Lua Script, verify if the firmware version has been updated.
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
Warning
The R9M Lite Pro can not be flashed via OpenTX or EdgeTX (Stock_BL method), and therefore requires an STLink v2 to flash. See the guide below
This method requires OpenTX 2.3.12 or newer; or EdgeTX 2.4.0 or newer.
Download and save r9m_elrs_bl.frk(14kb) onto the SD card of your radio, in the /FIRMWARE folder.
Flash r9m_elrs_bl.frk to your TX module:
Access the System Menu on your radio.
On newer radios, you can press the SYS key to open the System Menu
On older radios, or radios that only have a menu key, long-press the Menu key to open the System Menu
Using the Page key/s, navigate to the SD-HC Card page.
Scroll-down and open the FIRMWARE folder where you can find the r9m_elrs_bl.frk file.
Flash the frk file by holding Enter key and selecting \"Flash external module\"
FYI
You only need to flash the Bootloader ONCE. After it's flashed into the module, you don't have to reflash it in every update.
Video Guide:
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
FrSky 900 MHz
Device:
FrSky R9M 900MHz TX
FrSky R9M Lite 900MHz TX
Set the Flashing Method to Stock_BL
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Build button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
A Temp folder will open up with the firmware.elrs file. Copy-paste the firmware.elrs file into your Radio's SD Card (preferably to the /FIRMWARE folder for easy access).
On your radio, open the System Menu.
On newer radios, you can press the SYS key to open the System Menu
On older radios, or radios that only have a menu key, long-press the Menu key to open the System Menu
Using the Page key/s, navigate to the SD-HC Card page, scroll-down and open the FIRMWARE folder where you can find the firmware.elrs file.
Highlight the file and press-hold the Enter button and select \"Flash External ELRS\". Wait for the firmware to be written.
No Sync (click/tap to expand)
Make sure you have updated the OpenTX/EdgeTX firmware of your radio to a newer version
Make sure the current model selected on the radio is set up for ExpressLRS Use. See the Radio Preparation guide.
With the ExpressLRS Lua Script in the System Menu's Tools page, verify if the firmware version has been updated.
Warning
This method is an irreversible one. You will not be able to go back to FrSky firmware with this method. You have been warned!
Carefully disassemble your TX Module to get access to the mainboard.
Connect your STLink V2 dongle to the pads shown in the images below:
R9M STLink Connection
R9M Lite STLink Connection
R9M Lite Pro STLink Connection
Connect your STLink V2 dongle to your Computer's USB Port. Make sure it is being detected correctly.
Before flashing, disable 'Readout Protection'. To do this, download the ST-LINK Utility and follow this quick how to video. After such, you can now disconnect (Target -> Disconnect) and close the ST-Link Utility.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
FrSky 900 MHz
Device:
FrSky R9M 900MHz TX
FrSky R9M Lite 900MHz TX
FrSky R9M Lite Pro 900MHz TX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Disconnect the STLink V2 dongle from the TX Module PCB and reassemble the module.
Reattach your TX Module into your Radio and, using the ExpressLRS Lua Script, verify if the firmware version has been updated.
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
This method is an irreversible one. You will not be able to go back to ImmersionRC Ghost firmware with this method. You have been warned!
Video Guide(10 min):
Carefully disassemble your TX Module to get access to the mainboard.
Connect your STLink V2 dongle to the pads shown in the images below:
Wire 3.3v, GND, CLK, and DIO to their respective pins on your part from the StLink. (You can power with the StLink but in the second image, the radio is used to power the module).
Connect your STLink V2 dongle to your Computer's USB Port. Make sure it is being detected correctly.
Before flashing, disable 'Readout Protection'. To do this, download the ST-LINK Utility and follow this quick how to video. After such, you can now disconnect (Target -> Disconnect) and close the ST-Link Utility.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
ImmersionRC 2.4 GHz
Device:
Ghost 2.4GHz TX
Ghost Lite 2.4GHz TX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Disconnect the STLink V2 dongle from the TX Module PCB and reassemble the module.
Reattach your TX Module into your Radio and, using the ExpressLRS Lua Script, verify if the firmware version has been updated.
Info
This method requires OpenTX 2.3.12 or newer; or EdgeTX 2.4.0 or newer.
This method can only be used to UPDATE the firmware on an already-converted Ghost Module
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
ImmersionRC 2.4 GHz
Device:
Ghost 2.4GHz TX
Ghost Lite 2.4GHz TX
Set the Flashing Method to Stock_BL
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Build button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
A Temp folder will open up with the firmware.elrs file. Copy-paste the firmware.elrs file into your Radio's SD Card (preferably to the /FIRMWARE folder for easy access).
On your radio, open the System Menu.
On newer radios, you can press the SYS key to open the System Menu
On older radios, or radios that only have a menu key, long-press the Menu key to open the System Menu
Using the Page key/s, navigate to the SD-HC Card page, scroll-down and open the FIRMWARE folder where you can find the firmware.elrs file.
Highlight the file and press-hold the Enter button and select \"Flash External ELRS\". Wait for the firmware to be written.
No Sync (click/tap to expand)
Make sure you have updated the OpenTX/EdgeTX firmware of your radio to a newer version
Make sure the current model selected on the radio is set up for ExpressLRS Use. See the Radio Preparation guide.
With the ExpressLRS Lua Script in the Tools page, verify if the firmware version has been updated.
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
"},{"location":"quick-start/transmitters/hglrc-hermes/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia UART Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 2.4 GHz
Device:
HGLRC Hermes 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 2.4 GHz
Device:
HGLRC Hermes 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 2.4 GHz
Device:
HGLRC Hermes 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Attach your USB cable to the module while pressing and holding the recessed button at the back of the module. The location of the button is shown in the image below.
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here: CP210x Drivers
Windows Users should download the CP210x Windows Drivers package for easier installation. Unzip/Extract the contents of the package and run the setup wizard.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
HGLRC 2.4 GHz
Device:
HGLRC Hermes 2.4GHz TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
Make sure you are selecting the right Device Category (2.4GHz or 900MHz) that's appropriate for the hardware you have. You cannot flash a 2.4GHz module with the firmware for the 900MHz module and expect it to work properly. Likewise, you cannot flash a 900MHz module with the firmware for the 2.4GHz module. They have different sets of hardware.
You can damage your hardware if you do so. You have been warned!
Advisory
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
"},{"location":"quick-start/transmitters/iflight-commando/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia UART Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Categories:
iFlight 2.4 GHz
iFlight 900 MHz
Devices:
iFlight 2.4GHz TX & iFlight 2.4GHz TX V2
iFlight 900MHz TX & iFlight 900MHz TX V2
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Categories:
iFlight 2.4 GHz
iFlight 900 MHz
Devices:
iFlight 2.4GHz TX & iFlight 2.4GHz TX V2
iFlight 900MHz TX & iFlight 900MHz TX V2
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Categories:
iFlight 2.4 GHz
iFlight 900 MHz
Devices:
iFlight 2.4GHz TX & iFlight 2.4GHz TX V2
iFlight 900MHz TX & iFlight 900MHz TX V2
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Unscrew the two screws holding the Transmitter Module to the back of the radio handset. Carefully lift the Transmitter Module to get access to the USB-c port. Do not tug too much as there are wires connecting the Transmitter Module to the mainboard of the radio handset, along with the antenna cable of the module itself.
TX Module and USB-C connection
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here: CP210x Drivers
Windows Users should download the CP210x Windows Drivers package for easier installation. Unzip/Extract the contents of the package and run the setup wizard.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Categories:
iFlight 2.4 GHz
iFlight 900 MHz
Devices:
iFlight 2.4GHz TX & iFlight 2.4GHz TX V2
iFlight 900MHz TX & iFlight 900MHz TX V2
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB.
Reassemble the TX module into the Radio properly.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
"},{"location":"quick-start/transmitters/jumper-aion/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia UART Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION Nano 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION Nano 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION Nano 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here: CP210x Drivers or CH9102
Windows Users should download the CP210x Windows Drivers package for easier installation. Unzip/Extract the contents of the package and run the setup wizard.
Note
Jumper seems to have switched to a different UART adapter chip on some of these devices. They should be detected as USB-Enhanced Serial CH9102.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION Nano 2.4GHz TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
"},{"location":"quick-start/transmitters/jumper-internal/","title":"Internal Jumper TLite V2","text":""},{"location":"quick-start/transmitters/jumper-internal/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia ETX Passthrough Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION T-Lite 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Long-press the SYS Key on your Radio to display the Tools page, where you can find the Lua Scripts.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION T-Lite 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION T-Lite 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Info
ETX Passthrough is the result of the collaborative effort between RadioMaster, EdgeTX and ExpressLRS.
It is only available on Radios with Internal ExpressLRS Modules.
Before you start, ensure you have the latest EdgeTX firmware version on your Radio. Consult the EdgeTX documentation regarding the updating process.
For the Jumper T-Lite V2, update it to at least EdgeTX 2.8.0 (f6d140e) for full EdgeTX support.
Hot Tip
To ensure updating success with this method, update the EdgeTX firmware on the radio to at least EdgeTX 2.8.0 (f6d140e, released Nov. 27, 2022). The EdgeTX Firmware that comes with this radio is a pre-release version.
Simplest EdgeTX Updating Procedure (click/tap to expand)
Visit http://buddy.edgetx.org/.
Select the EdgeTX version and the Radio Model you want to update from the Left-hand side column.
Click the Download .bin button at the bottom of the page.
Save the firmware file into your Radio's SD Card, inside the Firmware Folder.
Reboot the Radio into DFU/Bootloader mode.
Turn off your radio.
Press and hold the two horizontal Trim switches then press the Power button. The Screen should Light up. Let go of the buttons.
Some Radios have a different procedure, like the BetaFPV Lite Radio 3 Pro. Consult the Manual for the steps to get it into this DFU/Bootloader mode.
Select Write Firmware.
Navigate to the EdgeTX firmware file you just downloaded.
Follow the screen prompts.
Once Writing is complete, reboot the radio.
Check the Radio's Version Page to verify you have the version you need.
Also, make sure you have an internal ELRS module on your Radio. The following steps only apply to handsets with ExpressLRS-specific internal modules.
The current Model on the radio should be using the Internal ExpressLRS Module. Test this by loading the ExpressLRS Lua Script from the Tools Menu.
There's one more setting you want to make sure is set properly before proceeding.
Long-press the SYS Key on the Radio.
Consult your Radio User's Manual on how to get to the System Menu.
Press the PAGE Keys until you reach the Hardware Page.
On this radio, a short-press on the SYS Key is equivalent to < PAGE while a short-press on the MDL Key is equivalent to PAGE > .
Scroll down until you see the Serial Ports settings.
Press the Down button.
Select or highlight USB-VCP by pressing the Down or Up Keys. Press Enter to edit the setting and use the Down or Up Keys to set it to CLI mode. Press Enter once more to confirm the changes.
Exit the Hardware menu by long-pressing RTN Key.
Now follow the next steps to get your Internal ExpressLRS Module Updated:
Connect your powered-up Radio to your Computer via a USB Data Cable.
On your Radio, scroll down and select USB Serial(VCP) then press the Enter Key. Set your Radio aside in the meantime.
On your Computer, check whether your Radio is being recognized correctly as a STMicroelectronics Virtual COM Port device.
Important
This is a vital step and a common failure point. Pay attention.
Windows Users can use Device Manager to check whether the Radio is being recognized correctly.
Yellow Caution Triangles in the Device Manager, or any mention of <Radio Name> Serial Port means drivers aren't installed.
Download the Driver package first. Unzip/extract the contents of the package and run/execute (double-click) the installer file (VCP_V1.5.0_Setup_W7_x64_64bits.exe for Windows 10 Users).
Once Drivers are installed, check again if the Radio is now being recognized correctly. You may have to unplug-replug the USB Cable first or even reboot your computer.
You only have to do this once usually.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Device:
Jumper AION T-Lite 2.4GHz TX
Set the Flashing Method to EdgeTXPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your Radio from USB.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
Make sure you are selecting the right Device Category (2.4GHz or 900MHz) that's appropriate for the hardware you have. You cannot flash a 2.4GHz module with the firmware for the 900MHz module and expect it to work properly. Likewise, you cannot flash a 900MHz module with the firmware for the 2.4GHz module. They have different sets of hardware.
You can damage your hardware if you do so. You have been warned!
"},{"location":"quick-start/transmitters/jumper-t14-t15-internal/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia ETX Passthrough Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Jumper 900 MHz
Device:
Jumper AION T-14 2.4GHz TX
Jumper AION T-15 2.4GHz TX
Jumper AION T-14 900M TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Long-press the SYS Key on your Radio to display the Tools page, where you can find the Lua Scripts.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Jumper 900 MHz
Device:
Jumper AION T-14 2.4GHz TX
Jumper AION T-15 2.4GHz TX
Jumper AION T-14 900M TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Jumper 900 MHz
Device:
Jumper AION T-14 2.4GHz TX
Jumper AION T-15 2.4GHz TX
Jumper AION T-14 900M TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Info
ETX Passthrough is the result of the collaborative effort between RadioMaster, EdgeTX and ExpressLRS.
It is only available on Radios with Internal ExpressLRS Modules.
Before you start, ensure you have the latest EdgeTX firmware version on your Radio. Consult the EdgeTX documentation regarding the updating process.
For any of the variants of the Jumper T14 or Jumper T15, the EdgeTX firmware that came with them (EdgeTX ~2.10.0) should work fine and there's no need to update EdgeTX.
Simplest EdgeTX Updating Procedure (click/tap to expand)
Visit http://buddy.edgetx.org/.
Select the EdgeTX version and the Radio Model you want to update from the Left-hand side column.
Click the Download .bin button at the bottom of the page.
Save the firmware file into your Radio's SD Card, inside the Firmware Folder.
Reboot the Radio into DFU/Bootloader mode.
Turn off your radio.
Press and hold the two horizontal Trim switches then press the Power button. The Screen should Light up. Let go of the buttons.
Some Radios have a different procedure, like the BetaFPV Lite Radio 3 Pro. Consult the Manual for the steps to get it into this DFU/Bootloader mode.
Select Write Firmware.
Navigate to the EdgeTX firmware file you just downloaded.
Follow the screen prompts.
Once Writing is complete, reboot the radio.
Check the Radio's Version Page to verify you have the version you need.
Also make sure the current active Model on the radio is using the Internal ExpressLRS Module. Test this by loading the ExpressLRS Lua Script from the Tools Menu.
There's one more setting you want to make sure is set properly before proceeding.
Long-press the Menu \"Menu\" Key on the Radio.
Consult your Radio User's Manual on how to get to the System Menu.
Press the PAGE Keys until you reach the Hardware Page.
Scroll down until you see the Serial Ports settings.
Press the Down button.
Select or highlight USB-VCP by pressing the Down or Up Keys. Press Enter to edit the setting and use the Down or Up Keys to set it to CLI mode. Press Enter once more to confirm the changes.
Exit the Hardware menu by long-pressing RTN Key.
Now follow the next steps to get your Internal ExpressLRS Module Updated:
Connect your powered-up Radio to your Computer via a USB Data Cable.
On your Radio, scroll down and select USB Serial(VCP) then press the Enter Key. Set your Radio aside in the meantime.
On your Computer, check whether your Radio is being recognized correctly as a STMicroelectronics Virtual COM Port device.
Important
This is a vital step and a common failure point. Pay attention.
Windows Users can use Device Manager to check whether the Radio is being recognized correctly.
Yellow Caution Triangles in the Device Manager, or any mention of <Radio Name> Serial Port means drivers aren't installed.
Download the Driver package first. Unzip/extract the contents of the package and run/execute (double-click) the installer file (VCP_V1.5.0_Setup_W7_x64_64bits.exe for Windows 10 Users).
Once Drivers are installed, check again if the Radio is now being recognized correctly. You may have to unplug-replug the USB Cable first or even reboot your computer.
You only have to do this once usually.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Jumper 900 MHz
Device:
Jumper AION T-14 2.4GHz TX
Jumper AION T-15 2.4GHz TX
Jumper AION T-14 900M TX
Set the Flashing Method to EdgeTXPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your Radio from USB.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
Make sure you are selecting the right Device Category (2.4GHz or 900MHz) that's appropriate for the hardware you have. You cannot flash a 2.4GHz module with the firmware for the 900MHz module and expect it to work properly. Likewise, you cannot flash a 900MHz module with the firmware for the 2.4GHz module. They have different sets of hardware.
The T20 Gemini firmware will ONLY work on the T20 Gemini. Do not Flash this target on the other T20 variants.
You can damage your hardware if you do so. You have been warned!
"},{"location":"quick-start/transmitters/jumper-t20-internal/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia ETX Passthrough Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Jumper 900 MHz
Device:
Jumper Gemini T-20 2.4GHz TX
Jumper AION T-20 2.4GHz TX
Jumper AION T-20 900M TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Long-press the SYS Key on your Radio to display the Tools page, where you can find the Lua Scripts.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Jumper 900 MHz
Device:
Jumper Gemini T-20 2.4GHz TX
Jumper AION T-20 2.4GHz TX
Jumper AION T-20 900M TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Jumper 900 MHz
Device:
Jumper Gemini T-20 2.4GHz TX
Jumper AION T-20 2.4GHz TX
Jumper AION T-20 900M TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Info
ETX Passthrough is the result of the collaborative effort between RadioMaster, EdgeTX and ExpressLRS.
It is only available on Radios with Internal ExpressLRS Modules.
Before you start, ensure you have the latest EdgeTX firmware version on your Radio. Consult the EdgeTX documentation regarding the updating process.
For any of the variants of the Jumper T20, the EdgeTX firmware that came with it (pre EdgeTX 2.9.0) should work fine and there's no need to update it.
Simplest EdgeTX Updating Procedure (click/tap to expand)
Visit http://buddy.edgetx.org/.
Select the EdgeTX version and the Radio Model you want to update from the Left-hand side column.
Click the Download .bin button at the bottom of the page.
Save the firmware file into your Radio's SD Card, inside the Firmware Folder.
Reboot the Radio into DFU/Bootloader mode.
Turn off your radio.
Press and hold the two horizontal Trim switches then press the Power button. The Screen should Light up. Let go of the buttons.
Some Radios have a different procedure, like the BetaFPV Lite Radio 3 Pro. Consult the Manual for the steps to get it into this DFU/Bootloader mode.
Select Write Firmware.
Navigate to the EdgeTX firmware file you just downloaded.
Follow the screen prompts.
Once Writing is complete, reboot the radio.
Check the Radio's Version Page to verify you have the version you need.
The current active Model on the radio should be using the Internal ExpressLRS Module. Test this by loading the ExpressLRS Lua Script from the Tools Menu.
There's one more setting you want to make sure is set properly before proceeding.
Long-press the Menu \"Menu\" Key on the Radio.
Consult your Radio User's Manual on how to get to the System Menu.
Press the PAGE Keys until you reach the Hardware Page.
Scroll down until you see the Serial Ports settings.
Press the Down button.
Select or highlight USB-VCP by pressing the Down or Up Keys. Press Enter to edit the setting and use the Down or Up Keys to set it to CLI mode. Press Enter once more to confirm the changes.
Exit the Hardware menu by long-pressing RTN Key.
Now follow the next steps to get your Internal ExpressLRS Module Updated:
Connect your powered-up Radio to your Computer via a USB Data Cable.
On your Radio, scroll down and select USB Serial(VCP) then press the Enter Key. Set your Radio aside in the meantime.
On your Computer, check whether your Radio is being recognized correctly as a STMicroelectronics Virtual COM Port device.
Important
This is a vital step and a common failure point. Pay attention.
Windows Users can use Device Manager to check whether the Radio is being recognized correctly.
Yellow Caution Triangles in the Device Manager, or any mention of <Radio Name> Serial Port means drivers aren't installed.
Download the Driver package first. Unzip/extract the contents of the package and run/execute (double-click) the installer file (VCP_V1.5.0_Setup_W7_x64_64bits.exe for Windows 10 Users).
Once Drivers are installed, check again if the Radio is now being recognized correctly. You may have to unplug-replug the USB Cable first or even reboot your computer.
You only have to do this once usually.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Jumper 2.4 GHz
Jumper 900 MHz
Device:
Jumper Gemini T-20 2.4GHz TX
Jumper AION T-20 2.4GHz TX
Jumper AION T-20 900M TX
Set the Flashing Method to EdgeTXPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your Radio from USB.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
"},{"location":"quick-start/transmitters/lua-howto/","title":"The ExpressLRS Lua Script","text":""},{"location":"quick-start/transmitters/lua-howto/#installing-the-lua-script","title":"Installing the Lua Script","text":"
Download the ELRS v3 Lua Script (you can simply right-click, save-as) into your radio's SD Card under the Scripts/Tools folder.
Access the script by navigating to your radio's System Menu.
Press the SYS Key on your Radio.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
You are now in the Tools Menu where Lua Scripts can be found. Scroll down and select ExpressLRS Lua Script.
Here's how it looks in the Tools menu (B&W and Color Screens):
Press Enter to Load it.
Stuck at Loading... (click/tap to expand)
Go back to the Radio Preparation Guide and make sure the current model is configured for ExpressLRS use.
Also set your Internal or External RF Baudrate to a higher value if the Script still doesn't load after proper configuration of your Model.
As of 3.3.0:
500Hz or faster packet rates require >400K Baudrate.
333Hz is the fastest packet rate you can use with 400K Baudrate.
"},{"location":"quick-start/transmitters/lua-howto/#understanding-and-using-the-lua-script","title":"Understanding and Using the Lua Script","text":""},{"location":"quick-start/transmitters/lua-howto/#the-header","title":"The Header","text":"
The first line, \"Header\", will show you some information about your ExpressLRS link.
Module Identifier
Shows the name of the current active Transmitter Module or Device.
Packet Counter
Shows the number of Bad and Good Packets the TX Module receives from the Radio. The second set of number should match your selected Packet Rate. e.g. If you've set your Packet Rate to 500Hz, the Packet Counter should show 0/500, which means you're not getting any Bad Packets ( 0 Bad Packets ) and only getting Good Packets ( 500 Good Packets ). Any small fluctuation is normal and often goes back to 100% Good Packets, especially when you change a setting and it's committed into memory.
Should the indicator starts showing Bad Packets, and Good Packets goes down, it isn't a good situation. Make sure your module is not overheating and it's still getting a good connection with the radio. This is most dangerous when you're armed and flying several kilometers/miles out, as this could mean a sudden Failsafe.
Connection Indicator
Shows the current RC Link status. When not connected to any receiver, it will show a dash (-); while a C shows up when bound and connected.
The Model Mismatch message will also show up to indicate you are connected to a receiver, but the model selected on your radio is incorrect. See the Model Match page for more info about Model Matching.
The Armed message will show up if you have the Arming Switch active (High, ~2000us). This is meant to warn users that changing parameters could result in a desync or disconnection with a receiver, resulting into a FAILSAFE.
If you do not meant to have your system Armed and ready for flying, make sure to toggle this switch to the Disarmed position (Low, ~1000us). Update your CH5 settings on the radio so that the output of this switch is correct (Low = disarmed; High = armed). See Switch Configs.
WARNING
Do not change parameters while ARMED. When a parameter is changed, the module goes into Parameter Commit mode, interrupting the normal loop. This could result in a desync on some hardware combination which would result in a FAILSAFE.
The Version Line, found near the bottom of the Lua Script, indicates the firmware version flashed into the Device. This is present on both TX Modules and Receivers.
From these examples:
3.3.0 - The numerical Version Number, in the form of Major.Minor.Patch.
See semantic versioning scheme for the origins of these numbers.
ISM2G4 - The Regulatory Domain set into the Device. TX and RX Regulatory Domains should match.
ae9df3 - The Git commit hash for the version or branch.
Items with > before the name is a folder that when selected shows another level of customization. TX Power, VTX Administrator, Wifi Connectivity are examples of these items.
These items will now show what is currently set for the items within. An example would be on TX Power, which will show the current Power set, and if Dynamic Power is enabled, it will show the current set Max Power, followed by the indicator Dyn.
"},{"location":"quick-start/transmitters/lua-howto/#packet-rate-and-telemetry-ratio","title":"Packet Rate and Telemetry Ratio","text":"
These are shown as Packet Rate and Telem Ratio in the Lua script, which allows you to change your performance parameters.
Packet Rate sets how fast data packets are sent, higher rates send packets more frequently and have lower latency.
The following options are available for 2.4GHz:
50Hz, 150Hz, 250Hz & 500Hz: Lora-based options. Higher means lower latency at the expense of sensitivity. Since v1.0.
F500 & F1000: Pure FLRC for lowest latency, reduced range compared to LoRa, 500Hz and 1000Hz. Details
D250 & D500: Redundant transmit FLRC modes. D stands for D\u00e9j\u00e0 Vu, 250Hz and 500Hz. Higher latency, reduced packet jitter and higher LQ. Same range as other FLRC modes. Details
100Hz Full & 333Hz Full: Lora-based 10-bit Full Resolution with 8ch/12ch/16 Switch Mode options. Details
K1000 : K modes for 2.4GHz are FSK+FEC (Forward Error Correction a.k.a self healing packets) and only available on LR1121 hardware. K modes are very similar to FLRC in their over the air properties and designed for high noise environments such as racing events. FSK Details FEC Details
DK250 & DK500 : These modes offer the same redundancy as D modes but with K modes (FSK+FEC).
The following options are available for 900MHz:
25Hz, 50Hz, 100Hz & 200Hz: LoRa-based options. Higher means lower latency at the expense of sensitivity. Since v1.0.
100Hz Full: Lora-based 10-bit Full Resolution with 8ch/12ch/16 Switch Mode options. Details
D50Hz: Lora-based Redundant transmit mode via DVDA. Details
250Hz: Only Available for GemX Devices. Details
200Hz Full : Only Available for GemX Devices. Details
K1000 Full : K modes for SubGHz are FSK and only available on LR1121 hardware. This mode is design for the highest data throughput when using protocols such as MAVLink. Details
The following options are available for GemX:
X150Hz : Crossband mode, combining 900MHz and 2.4GHz in Gemini Mode.
X100Hz Full : Crossband mode, combining 900MHz and 2.4GHz in Gemini Mode, Full Resolution with 8ch/12ch/16 Switch Mode options
GemX is a 3.4.0 feature
Gemini Crossband (GemX) is available on select hardware, requiring the LR1121 RF Chip. GemX is an ExpressLRS 3.4.0 feature. Details here.
The number following the rate in parentheses (e.g. -105dBm for 500Hz) is the Sensitivity Limit for the rate, the lowest RSSI dBm value where packets will still be received. See Signal Health for more information about the sensitivity limit.
WARNING
Never change the packet rate while flying as this FORCES A DISCONNECT between the TX and RX.
Telem Ratio sets the telemetry ratio or how much of the packet rate is used to send telemetry. The options, in order of increasing telemetry rate, are: Off, 1:128, 1:64, 1:32, 1:16, 1:8, 1:4, 1:2. A Telem Ratio of 1:64 means one out of every 64 packets are used for telemetry data.
v3.0 comes with Std and Race options. Std changes ratio depending on the Packet Rate, and Race is the same as Std, but will disable telemetry and sync while Armed.
For information on telemetry setup, see First Flight: Telemetry and Telemetry Bandwidth.
The Switch Mode setting controls how channels AUX1-AUX8 are sent to the receiver (the 4 main channels are always 10-bit). The options are Hybrid & Wide. Hybrid mode is 6x 2, 3 or 6-position + 1x 16-position, and Wide is 7x 64 or 128-position. For detail about the differences, see the Switch Configs documentation.
In full resolution modes, the Switch Mode parameter selects the number of channels to be used. Full Resolution Switch Modes
Hot Tip
The Switch Mode can only be changed when not connected to a receiver. The top right corner of the Lua script will show a - if you're not connected.
This option is only available to Gemini-capable TX Modules. See the Gemini Page for more details.
Available Options:
Gemini
Transmit on two TX antennas simultaneously at different frequencies 40MHz apart (for 2.4GHz) or ~10MHz apart (for 900MHz).
Ant 1/Ant 2
Transmit only on one antenna.
Switch
Alternate between the two Antennas.
WARNING
When using a Gemini TX with a non-Gemini receiver, you should set the TX in either Switch or Single Antenna (Ant1/Ant2) Mode.
The reason is that as the receiver only get the signal from the TX it has synchronized with, the other TX will act as a noise generator and increase both the noise floor and power consumption.
Introduced in 3.5.0, Link Mode changes the main protocol and function of the TX module.
Normal - This is the default configuration. The TX module simply sends the commands from the radio handset, and receive telemetry from the receiver and send it to the handset.
MAVLink - This option enables native MAVLink Telemetry downlink and Radio Control uplink making the TX module and radio handset to be an intermediary between a GCS and a MAVLink-capable craft. See the MAVLink page for more details.
ExpressLRS supports multiple configuration profiles, and the configuration profile is selected by setting the \"Receiver ID\" property in the Radio Handset's Model Setup -> Internal/External RF -> Receiver (number).
Model Match is used to prevent accidentally selecting the wrong model in the handset and flying with an unexpected handset or ELRS configuration. Setting this to On while a receiver is connected will make that receiver only connect with the current Receiver ID. Setting it to Off will allow a connection with any bound receiver (including those using a Bind Phrase). Both sides of the connection must agree on their Model Match setting. For a detailed explanation of how this restricts connections see Model Match.
The Receiver ID of the active model is shown after the option value.
The TX Power folder is where you can change your TX Module's Transmission Power settings. Press Enter once to access the settings and Press the RTN key to go back to the previous page.
Max Power sets the maximum power level your TX will transmit at. Selecting a power level higher or lower than your TX supports will revert to the closest supported level. The options are 10, 25, 50, 100, 250, 500, 1000 & 2000 mW. If Dynamic Power is set to Off this is the power level your TX always uses.
Dynamic enables the Dynamic Power feature. Off means that the TX will transmit at Max Power at all times. Dyn means the TX will dynamically lower power to save energy when maximum power is not needed. The options AUX9, AUX10, AUX11, AUX12 indicate that the TX can be changed from max power to dynamic power by changing the position of a switch. where switch HIGH (>1500us) = dynamic power, switch LOW (<1500us) = max power. For more information, Dynamic Transmit Power provides a deeper dive into the algorithm and usage.
Fan Thresh sets the power level the Fan should activate, e.g. if set to 100mW, then the fan should spin up if you set Max Power to 100mW with Dynamic set to OFF after a short delay. The fan will continue running for some time even after the power level goes below the threshold. Not all modules have a Fan header that benefits from the setting. . Default fan threshold is 250mW.
VTX Administrator allows you to change your VTX settings directly from your radio, and have those VTX settings be applied to any receiver you connect to. The VTX settings are sent every time a new connection is acquired, or when [Send VTX] is pressed.
Hot Tip
VTX Administrator will send the current VTX settings to the flight controller whenever the TX module detects a connection to the RX. This means that it will resend them after telemetry lost/recovered. So if you have used any other method to change the VTX power level (i.e. OSD), then that will be overridden if you lose/regain telemetry in flight.
Band sets the VTX band, the options are Off, A, B, E, F, R & L, the standard analog FPV bands. Off means that VTX Administrator will not adjust any VTX settings.
Channel sets the VTX channel, the options are 1, 2, 3, 4, 5, 6, 7 & 8 which are the standard channels in the above bands.
Pwr Lvl sets the VTX power by index, the options are -, 1, 2, 3, 4, 5, 6, 7, & 8 which are the power levels that your VTX can do. Refer to your VTX table settings on the flight controller for the exact power levels. For example a VTX may have 1 = 25mW, 2 = 100mW, 3 = 200mW, 4 = 500mW.
Pitmode the options are On & Off which allow you to quickly switch into or out of pit mode
Finally pressing the [Send VTX] button sends the configured settings to the receiver and on to the VTX. These settings are also sent every time a connection is established.
This section contains all the WiFi-related functions.
Enable WiFi will activate the TX module WiFi mode for updating via WiFi (if the TX Module has WiFi Capabilities). Visit this page for instructions on how the updating process works.
Enable RX WiFi will put the bound and connected receiver into WiFi mode to facilitate updating via WiFi (if the receiver has WiFi capabilities).
Enable Backpack WiFi will put the TX Backpack into WiFi mode (available only to TX modules with backpacks connected and updated to the new Backpack firmware).
Enable VRX WiFi will put the VRX Backpack that is bound and connected to the onboard TX Backpack into WiFi mode to facilitate updating via WiFi.
The parameters in this folder enables you to change the Backpack-related parameters.
Backpack - Turn the Backpack function On or Off.
DVR Rec - Set which Aux Channel and what channel position will trigger DVR Recording on the goggles. Only possible on FPV Goggles with VRX Backpack integration.
DVR Srt Delay - How soon should the DVR start Recording upon activation of the Aux switch?
DVR Stp Delay - How soon should the DVR stop Recording upon deactivation of the Aux switch?
HT Enable - Turn Headtracking On or Off. Only available on some FPV Goggles with VRX Backpack integration.
HT Start Channel - Starting Channel to send Head Tracking positions to.
Telemetry - Allow the Backpack to Send the Telemetry frames via ESPNOW. See Backpack Telemetry
Version - The Backpack Firmware version flashed into the TX Backpack.
This command will only work on receivers that are already in Bind Mode (indicated by two blinks LED pattern). Receivers (with version 3.3.2 and earlier) flashed or set with a binding phrase will NOT go into this Bind Mode, and thus this command will not do anything.
Devices with the same binding phrase and compatible firmware versions should automatically sync/bind upon power up.
Pressing the [Bind] button activates the binding mode for traditional binding. This does nothing for users who have configured a bind phrase and is not needed. For more information check out this page on binding.
Pressing the [BLE Joystick] selection activates BluetoothLE Joystick mode which allows connection to simulators through the bluetooth of your computer. Reboot or change models to exit this mode.
The Other Devices folder, if present, allows changing the configuration of other connected devices, such as the current receiver. It is also used to go back to the TX Module options.
The Protocol setting controls the output of the connected receiver. The following options are available:
CRSF - The regular CRSF Protocol Output. Recommended for most application.
Inverted CRSF - The CRSF Protocol inverted for use in Flight Controllers that doesn't have any other UARTs available and the only option is to connect the receiver TX pin into an SBUS pad (Inverted RX). This is the old Invert TX Pin option.
SBUS - Lets the receiver output SBUS signal for use with devices that don't support CRSF protocol, like Stabilizers, Heli Controllers etc.
Inverted SBUS - Like the above, but inverted.
SUMD - Lets the receiver output Graupner HoTT SUMD signal for use with devices that don't support CRSF protocol, like Stabilizers, Heli Controllers etc.
DJI RS2 Pro - Mainly used for the RS2 Pro Gimbals
HoTT Telemetry - Allows to use Graupner HoTT enabled telemetry sensors (Graupner and 3rd party)
MAVLINK - Introduced on ExpressLRS 3.5.0, it allows the receiver to output native MAVLink into a flight controller. See the MAVLink page for more details.
For more information, see Receiver Serial Protocols
The Protocol 2 setting is only available for ESP32-based receivers. This include the True Diversity ones like the RP4TD, Super D, Super P and EP Dual. These receivers have a second UART that can be used for the same purpose as the main UART. Note that not all of the ESP32-based receivers have the extra UART pads or pins exposed for easy use.
It has the same options as the setting above with these additional ones:
Tramp - If you want to control a VTX using Tramp protocol directly through the ExpressLRS Lua Script's VTX Admin.
SmartAudio - If you want to control a VTX using SmartAudio protocol directly through the ExpressLRS Lua Script's VTX Admin.
Off - Set when the auxiliary UART is not in use.
This setting is available on ExpressLRS 3.5.0 and onwards. See PR 2605 for more details.
The Receiver Mode setting is only available for True Diversity receivers. These options are available:
Gemini - Receive on two RX antennas simultaneously at different frequency 40MHz apart (for 2.4GHz) or ~10MHz apart (for 900MHz). Best used when you have a Gemini-capable TX Module.
Diversity - Both Antennas will be active. Receiver will switch to the antenna with better RSSI.
The Telemetry Power setting is used to adjust the telemetry transmit power of the receiver. This option is only available on receivers with a Power Amplifier.
The MatchTX setting will automatically change the telemetry output power to match what the transmitter reports it is using. In MatchTX mode, the receiver will boot at default power output (usually maximum power) until a power update is received from the transmitter, which is only available in Wide Switch Mode or any FullRes mode.
Removed in ExpressLRS 3.4, see Init Rate. The Initialization Rate setting controls the packet rate that the receiver will start checking for the Sync Packet. On boot, the receiver will listen for the Sync Packet starting with the fastest RF Mode or Packet Rate, down to the slowest, then cycles, until it finally Syncs and Binds. Setting this parameter closer or equal to the Packet Rate you've set for the TX module will allow the receiver to Bind or Connect much faster.
Team Racing allows selection between multiple connected models, failsafing all unselected models. See Team Racing
Channel (default CH11 / AUX7) TeamRace Channel - The channel that is checked on the receiver to determine the currently selected model. Has no effect if the TeamRace Position is set to Disabled.
Position (default Disabled) TeamRace Position - Which position of the TeamRace Channel activates this model. 6-position switches are supported (1-6) as well as Low/Mid/High for using a 2 or 3-position switch.
These commands allow the user to Loan/Return the model. For more information, see the Loan Model guide.
This is deprecated and removed in ExpressLRS 3.4.0 in favor of the new Binding Procedures. See the binding page for details or the Bind Storage section below.
Persistent - Binding info is kept across power-cycles.
Volatile - Binding info is forgotten after a power-cycle.
This option is available on ExpressLRS 3.4.0 and newer. See the details here.
Returnable - Introduced in ExpressLRS 3.5.0. It is used to allow models to be safely loaned from a fleet if unbound OTA. A Binding Phrase must be set for this to work properly. see PR 2744 for details.
This line shows the currently set Model ID for the receiver when Model Matching is enabled. This number should match the Receiver ID set with the current active Model on the Radio handset, otherwise, there will be Model Mismatch! See Model Match for more details.
For racing where maximum performance is a must, the 500Hz modes or faster, with the Race Telemetry mode, is ideal. Hybrid Switch Mode is also good here.
For freestyle and general everyday flying, you may use the 250Hz modes or faster, with the Std Telemetry mode. Switch Mode doesn't matter as much here. Select what's appropriate for your Flight Mode settings.
For fixed wings, we recommend using 100Hz Full Res, together with either Std or your choice of Telemetry Ratio. Switch Mode will depend greatly on how many full resolution channels you intend to use.
For Long Range applications, see the Long Range Records page and try the settings the pilots used to achieve the range. It is not guaranteed you'll achieve the same range as they are due to several factors like RF Noise in your area, your location and position and the antenna orientation on your aircraft and transmitter modules. Observe local laws and regulations.
"},{"location":"quick-start/transmitters/lua-howto/#troubleshooting-the-lua-script","title":"Troubleshooting the Lua Script","text":""},{"location":"quick-start/transmitters/lua-howto/#expresslrs-lua-script-is-stuck-at-loading","title":"ExpressLRS Lua Script is stuck at Loading...","text":"ExpressLRS Lua Script is stuck at Loading...
Go back to the Radio Setup Guide and make sure your radio is prepped up for ExpressLRS. Check that the ExpressLRS TX module is enabled - otherwise the script cannot be loaded.
Also, make sure your module has been flashed with v3.0 firmware. V3 Lua for V3.0-flashed modules, V2 Lua for v2.x-flashed modules (including some modules fresh from the factory).
For newly-acquired ExpressLRS modules, flashing via USB is the recommended update method.
"},{"location":"quick-start/transmitters/lua-howto/#i-cannot-change-the-switch-mode","title":"I cannot change the Switch Mode!","text":"I cannot change the Switch Mode!
Changing switch modes requires that the TX module and Receiver aren't connected to each other (no C in the top right corner of the Lua Script). Power off the receiver first, change the Switch Mode from the Lua script, then power up the receiver. The Switch Mode should then apply.
"},{"location":"quick-start/transmitters/lua-howto/#i-cannot-change-my-packet-rate-to-f1000","title":"I cannot change my Packet Rate to F1000!","text":"I cannot change my Packet Rate to F1000!
F1000 requires higher than 400K baud rates. First update your baud rate setting either in the Model Setup menu or in the System Menu -> Hardware, reboot your radio to ensure that the baud rate setting got applied and then change the Packet Rate.
Do note that not every handset is capable of higher than 400K baud rates. See the Radio Setup Guide for the details.
"},{"location":"quick-start/transmitters/lua-howto/#i-cannot-change-to-full-resolution-rates","title":"I cannot change to Full Resolution Rates!","text":"I cannot change to Full Resolution Rates!
As Full Resolution Rates call for an entirely different Switch Modes, you need to first disconnect the Receiver and the TX module from each other, like how you would change Switch Modes. Power down the receiver, change the Packet Rate to the Full Resolution modes, select your Switch Mode scheme and then power up the receiver or the aircraft.
"},{"location":"quick-start/transmitters/lua-howto/#vtx-admin-is-not-working-but-i-can-change-vtx-channels-via-osd-menu","title":"VTX Admin is not working but I can change VTX channels via OSD Menu.","text":"VTX Admin is not working but I can change VTX channels via OSD Menu.
As VTX Admin depends on MSP which then depends on Telemetry, ensure that you have Telemetry enabled on your FC Configuration and that you are getting more than 10 Telemetry Sensors on your Radio (Model Setup -> Telemetry page; Delete and Discover New sensors to refresh the sensor list.) Also, make sure Telem Ratio is not Off.
"},{"location":"quick-start/transmitters/lua-howto/#there-is-no-c-on-the-top-right-corner-and-im-not-getting-telemetry-in-my-radio","title":"There is no C on the top right corner, and I'm not getting Telemetry in my radio!","text":"There is no C on the top right corner, and I'm not getting Telemetry in my radio!
Make sure Telem Ratio is not set to Off. Set it to Std, or any other value other than Off.
"},{"location":"quick-start/transmitters/lua-howto/#on-v1x-i-can-choose-2w-on-the-lua-but-i-cannot-do-that-anymore-what-gives","title":"On v1.x, I can choose 2W on the Lua, but I cannot do that anymore. What gives?","text":"On v1.x, I can choose 2W on the Lua, but I cannot do that anymore. What gives?
This means your module cannot go that high or that low. The power levels you can select on the new Lua script are based on the power levels your module supports. This also applies to other options like Enable Backpack WiFi or BLE Joystick. If your module doesn't support any of these features, it won't show up on the Lua Script.
These devices come pre-installed with a 3.x-ready firmware. You don't need to reflash these devices. You can use the Web UI of these devices to update the Binding Phrase or any of the firmware options.
"},{"location":"quick-start/transmitters/rm-bandit/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia UART Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Radiomaster 900MHz
Device:
RadioMaster Bandit 900MHz TX
RadioMaster Bandit Micro 900MHz TX
RadioMaster Bandit nano 900MHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Radiomaster 2.4 GHz
Device:
RadioMaster Bandit 900MHz TX
RadioMaster Bandit Micro 900MHz TX
RadioMaster Bandit nano 900MHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Radiomaster 2.4 GHz
Device:
RadioMaster Bandit 900MHz TX
RadioMaster Bandit Micro 900MHz TX
RadioMaster Bandit nano 900MHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here: CP210x Drivers
Windows Users should download the CP210x Windows Drivers package for easier installation. Unzip/Extract the contents of the package and run the setup wizard.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Radiomaster 2.4 GHz
Device:
RadioMaster Bandit 900MHz TX
RadioMaster Bandit Micro 900MHz TX
RadioMaster Bandit nano 900MHz TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
"},{"location":"quick-start/transmitters/rm-internal/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia ETX Passthrough Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
RadioMaster 2.4 GHz
Device:
RadioMaster Zorro 2.4GHz TX
RadioMaster TX16S Internal 2.4GHz TX
RadioMaster TX12 Internal 2.4GHz TX
RadioMaster Boxer Internal 2.4GHz TX
RadioMaster Pocket Internal 2.4GHz TX
RadioMaster MT12 Internal 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
RadioMaster 2.4 GHz
Device:
RadioMaster Zorro 2.4GHz TX
RadioMaster TX16S Internal 2.4GHz TX
RadioMaster TX12 Internal 2.4GHz TX
RadioMaster Boxer Internal 2.4GHz TX
RadioMaster Pocket Internal 2.4GHz TX
RadioMaster MT12 Internal 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
RadioMaster 2.4 GHz
Device:
RadioMaster Zorro 2.4GHz TX
RadioMaster TX16S Internal 2.4GHz TX
RadioMaster TX12 Internal 2.4GHz TX
RadioMaster Boxer Internal 2.4GHz TX
RadioMaster Pocket Internal 2.4GHz TX
RadioMaster MT12 Internal 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Info
ETX Passthrough is the result of the collaborative effort between RadioMaster, EdgeTX and ExpressLRS.
It is only available on Radios with Internal ExpressLRS Modules.
Before you start, ensure you have the latest EdgeTX firmware version on your Radio. Consult the EdgeTX documentation regarding the updating process.
TX16S MK2: Update it to at least EdgeTX 2.7.0 (f79978b) or EdgeTX 2.7.1 (a55aff0).
Zorro: Update it to at least EdgeTX 2.7.0 (f79978b) or EdgeTX 2.7.1 (a55aff0). It often comes with an earlier EdgeTX 2.7.0 version (2bdd4974) which results in unsuccessful flashing.
TX12 MK2: Update it to at least EdgeTX 2.8.0 (f6d140e) for full EdgeTX support.
Boxer: The factory EdgeTX firmware should be based off an early EdgeTX 2.8.0 and wouldn't need an update.
Pocket: The factory EdgeTX firmware shouldn't need an update.
MT12: The factory EdgeTX firmware shouldn't need an update.
Hot Tip
To ensure updating success with this method, update the EdgeTX firmware on the radio as mentioned above.
Simplest EdgeTX Updating Procedure (click/tap to expand)
Visit http://buddy.edgetx.org/.
Select the EdgeTX version and the Radio Model you want to update from the Left-hand side column.
Click the Download .bin button at the bottom of the page.
Save the firmware file into your Radio's SD Card, inside the Firmware Folder.
Reboot the Radio into DFU/Bootloader mode.
Turn off your radio.
Press and hold the two horizontal Trim switches then press the Power button. The Screen should Light up. Let go of the buttons.
Some Radios have a different procedure, like the BetaFPV Lite Radio 3 Pro. Consult the Manual for the steps to get it into this DFU/Bootloader mode.
Select Write Firmware.
Navigate to the EdgeTX firmware file you just downloaded.
Follow the screen prompts.
Once Writing is complete, reboot the radio.
Check the Radio's Version Page to verify you have the version you need.
Also make sure you have an internal ELRS module on your Radio. The following steps only apply to handsets with ExpressLRS-specific internal modules. There are stickers marked with \"ELRS\" attached to your radio packaging or boxes, as well as on the JR module bays indicating the type of internal rf module the radio have.
Example Sticker On RadioMaster Handset/Radios
The current Model on the radio should be using the Internal ExpressLRS Module. Test this by loading the ExpressLRS Lua Script from the Tools Menu.
There's one more setting you want to make sure is set properly before you proceed.
Press the SYS Key on the Radio.
Press the PAGE Key until you reach the Hardware Page.
Scroll down until you get to the Serial Ports settings.
Scroll down and select USB-VCP. Press Enter and use the Scroll Wheel to set it to CLI mode if it is set to a different setting. Press Enter once more to confirm the changes.
Exit the Hardware menu by long-pressing RTN Key.
Now follow the next steps to get your Internal ExpressLRS Module Updated:
Connect your powered-up Radio to your Computer via a USB Data Cable.
On your Radio, scroll down and select USB Serial(VCP) then press the Enter Key. Set your Radio aside in the meantime.
On your Computer, check whether your Radio is being recognized correctly as a STMicroelectronics Virtual COM Port device.
Important
This is a vital step and a common failure point. Pay attention.
Windows Users can use Device Manager to check whether the Radio is being recognized correctly.
Yellow Caution Triangles in the Device Manager, or any mention of <Radio Name> Serial Port means drivers aren't installed.
Download the Driver package first. Unzip/extract the contents of the package and run/execute (double-click) the installer file (VCP_V1.5.0_Setup_W7_x64_64bits.exe for Windows 10 Users).
Once Drivers are installed, check again if the Radio is now being recognized correctly. You may have to unplug-replug the USB Cable first or even reboot your computer.
You only have to do this once usually.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
RadioMaster 2.4 GHz
Device:
RadioMaster Zorro 2.4GHz TX
RadioMaster TX16S Internal 2.4GHz TX
RadioMaster TX12 Internal 2.4GHz TX
RadioMaster Boxer Internal 2.4GHz TX
RadioMaster Pocket Internal 2.4GHz TX
RadioMaster MT12 Internal 2.4GHz TX
Set the Flashing Method to EdgeTXPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your Radio from USB.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
These devices come pre-installed with a 3.x-ready firmware. You don't need to reflash these devices. You can use the Web UI of these devices to update the Binding Phrase or any of the firmware options.
"},{"location":"quick-start/transmitters/rm-ranger/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia UART Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Radiomaster 2.4 GHz
Device:
RadioMaster Ranger 2.4GHz TX
RadioMaster Ranger Micro 2.4GHz TX
RadioMaster Ranger nano 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Radiomaster 2.4 GHz
Device:
RadioMaster Ranger 2.4GHz TX
RadioMaster Ranger Micro 2.4GHz TX
RadioMaster Ranger nano 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Radiomaster 2.4 GHz
Device:
RadioMaster Ranger 2.4GHz TX
RadioMaster Ranger Micro 2.4GHz TX
RadioMaster Ranger nano 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from here: CP210x Drivers
Windows Users should download the CP210x Windows Drivers package for easier installation. Unzip/Extract the contents of the package and run the setup wizard.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Radiomaster 2.4 GHz
Device:
RadioMaster Ranger 2.4GHz TX
RadioMaster Ranger Micro 2.4GHz TX
RadioMaster Ranger nano 2.4GHz TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
"},{"location":"quick-start/transmitters/siyifm30/#fm30","title":"FM30","text":""},{"location":"quick-start/transmitters/siyifm30/#flashing-via-stlink","title":"Flashing via STLink","text":"
Target: FM30_TX_via_STLINK
Note
The only way to flash the FM30 series is using STLINK. Luckily, their pads are pretty generous on the TX and easy to connect. This is a one-way process, there is no returning to the stock firmware after flashing.
The TX module is opened by removing the four screws on the corners of the case using a small phillips screwdriver, then two further screws to remove the circuit board once inside.
Connect wires to SWDIO, SWCLK, NRST, and GND to the header points shown in red above on the TX. Attach 5V to the VCC pad, not the 3.3V pad!
Connect the other side to a STLINK programmer
Flash using the FM30_TX_via_STLINK target
After the flashing procedure, it is safe to leave the STLINK device connected to test that the firmware is operational, but unplug the USB connection before inserting the module into your handset for testing.
Be sure your handset has the External Module type set to CRSF. See the general Troubleshooting section for other ways to determine your module is flashed and ready for flying.
"},{"location":"quick-start/transmitters/siyifm30/#updating-via-dfu","title":"Updating via DFU","text":"
Target: FM30_TX_via_DFU
Updating the TX is a lot easier and can be done via DFU without needing a STLINK.
Remove the module from your handset. \u26a0\ufe0f DO NOT plug in the USB while the module is still in the handset. There is no protection to prevent connecting the USB's power directly to your handset.
Hold the button labeled \"Bind\" on the FM30 TX. Plug in the USB. There should be an \"ExpressLRS DFU bootloader\" device in Windows Device Manager. If not, the STM32 DFU drivers may need to be installed.
Flash using the FM30_TX_via_DFU target
Note that the process always reports failure but this occurs after flashing, so check for the message \"File downloaded successfully\", not what follows it:
Download [======================== ] 97% 46080 bytes\nDownload [=========================] 100% 47340 bytes\nDownload done.\nFile downloaded successfully\nInvalid DFU suffix signature\nA valid DFU suffix will be required in a future dfu-util release!!!\nError during download get_status\n*** [upload] Error 74\n
"},{"location":"quick-start/transmitters/siyifm30/#fr-mini-rx-as-tx","title":"FR Mini RX as TX","text":"
The RX has the same RF components as the TX does, making it a possible candidate for a small ~200mW TX module. Wiring to the JR Module Bay requires only 3 pins (JR pins are starting from the top down)
JR Module Pin | FR Mini Pin | Description |--|--|--| | CPPM | None | | | Heartbeat | None | | | VMain | VIN | Use the VIN pin on the pin header (middle pin), 3.3-3.4V. Do not connect directly to handset battery voltage-- this will burn out the 3.3V regulator even at 10mW output. Use either a 3.3V boost converter (to raise voltage from 1S provided by the handset) or 3.3V buck converter (to lower 2S or 3S handset voltage). The LDO has a very small dropout voltage, so there's not much benefit to bypassing this soldering directly to the VDD pad on the programming header. Expect over 250mA current draw in practice at 100mW. | | GND | GND | Use either the GND pin on the pin header (outermost pin) or the GND pad on the programming header. | SPORT | TX2 | Use the TX2 pad on the receiver and remove the 4.7K pull-up resistor. Without removing the resistor, the module will work okay-ish as a transmitter, but firmware updates through OpenTX will fail with NoSync
"},{"location":"quick-start/transmitters/siyifm30/#flashing-via-stlink_1","title":"Flashing via STLink","text":"
Target: FM30_RX_MINI_AS_TX_via_STLINK
Note
The only way to flash the FR Mini is using STLINK. This is a one-way process, there is no returning to the stock firmware after flashing.
The flashing procedure is similar to the FM30 TX module flashing listed above but using these pads on the receiver. Use the FM30_RX_MINI_AS_TX_via_STLINK target for initial flashing.
"},{"location":"quick-start/transmitters/siyifm30/#updating-via-uart","title":"Updating via UART","text":"
Target: FM30_RX_MINI_AS_TX_via_UART
Updates are done through OpenTX's built-in firmware flashing tool.
Build the firmware using Configurator and selecting the FM30_RX_MINI_AS_TX_via_UART target. The build process will generate a firmware.elrs file.
Copy this file to the handset FIRMWARE/ directory on the SD card.
Flash the firmware to the module using OpenTX
Hold the MENU/SYS button on the handset to open the system menu
Press PAGE to navigate to the SD card browser
Scroll down to the FIRMWARE directory, and press ENTER
Find firmware.elrs and long press the ENTER key to open the context menu
Select Flash Ext. ELRS from the menu
"},{"location":"quick-start/transmitters/siyifm30/#troubleshooting-flashing","title":"Troubleshooting Flashing","text":""},{"location":"quick-start/transmitters/siyifm30/#unable-to-connect-to-the-target-device","title":"Unable to connect to the target device","text":"Unable to connect to the target device (click/tap to expand)
If the flash fails with \"Unable to connect to target device\" (not \"No STLINK found!\") it is likely your STLINK clone does not have the RST line connected, but you can trigger the needed reset manually with a little more effort. The reason this is needed is that SIYI has disabled \"Software Reset\" to protect you from stealing their firmware binary.
Verify your wiring
Make sure the TX board is powering up (the LEDs light up)
Use the STM32CubeProgrammer or STLINK GUI to connect see next step.
Before you press CONNECT. Short the RST line from the TX to GND. Press CONNECT and quickly remove the wire from the GND pad.
If it works, the GUI will tell you that the board is readout protected and must be disabled. Do this.
"},{"location":"quick-start/transmitters/siyifm30/#flash-loader-run-error","title":"Flash loader run error","text":"Flash loader run error (click/tap to expand)
Before both the TX and RX can be flashed using the st-flash utility used by PlatformIO on Linux, the STM32 chip must have its \"Readout Protection\" (RDP) disabled, which was set by SIYI at the factory to make our lives more difficult. The windows flashing utility usually automatically disables this, but the Linux utility does not. If you do not disable readout protection you'll get this cryptic error when flashing:
The only way I know of to disable the RDP is to use the STM32CubeProgrammer for Linux, or use a Windows VM / machine to use the ST-LINK.exe GUI / CLI to clear the RDP.
Click the \"Connect\" button to connect to the ST-LINK device. You'll probably get a popup error Error: Data read failed. That's normal. If it says it can't connect or no device is present, you'll have to figure that out first.
Click the \"OB\" button on the left.
Expand the \"Read Out Protection\" section.
Select RDP = \"AA\"
Click the \"Apply\" button at the bottom.
You should get a message indicating the \"Option bytes successfully programmed\". If so you're good to go. Click \"Disconnect\" at the top and flash from PlatformIO now. You can also flash directly from this GUI if you have the binaries and know their target addresses.
Insert or attach your External ExpressLRS Transmitter Module into your Radio module bay, making sure no pins are bent or missing. External ExpressLRS Modules require three (3) pins to work: VCC/VBAT, GND and S.Port/Data/Signal.
Micro External Bay Pinout Nano External Bay Pinout"},{"location":"quick-start/transmitters/tx-prep/#internal-expresslrs-modules","title":"Internal ExpressLRS Modules","text":"
Make sure you do have an Internal ExpressLRS Module on your shiny new radio. The following handsets come in both ELRS (ExpressLRS) or 4-in-1 variants; with some coming in with a third (CC2500). Only the ELRS variant works with ExpressLRS. The others will not work as they have a different Hardware incompatible with ExpressLRS.
RadioMaster TX16S Mark II (ELRS, 4-in-1 CC2500) - ExpressLRS variant will have an ELRS sticker on the box.
RadioMaster TX12 Mark II (ELRS, 4-in-1, CC2500) - ExpressLRS variant will have an ELRS sticker on the box and an ELRS sticker in the JR module bay.
RadioMaster Zorro (ELRS, 4-in-1, CC2500) - ExpressLRS variant will have an ELRS sticker on the box.
RadioMaster Boxer (ELRS, 4-in-1, CC2500) - ExpressLRS variant will have an ELRS sticker on the box and an ELRS sticker in the JR module bay.
Jumper T-Lite V2 (ELRS, 4-in-1, CC2500)
Jumper T-Pro V1/V2 (ELRS, 4-in-1)
BetaFPV Lite Radio 3 Pro (ELRS, CC2500) - A sticker with the barcode at the bottom of the box should tell you it's an ELRS variant or the CC2500 variant.
Example Sticker On RadioMaster Handset/Radios"},{"location":"quick-start/transmitters/tx-prep/#radio-operating-system","title":"Radio Operating System","text":"
ExpressLRS requires CRSFShot or Mixer Sync to ensure full support for high packet rates. You should have OpenTX 2.3.12 or newer, or EdgeTX 2.4.0 or newer; These versions have full CRSFShot/Mixer Sync support.
To determine your Radio Operating System Version, load the Version page from the System Menu of your Radio:
Press the SYS Key.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Press PAGE Key until you reach the Version Page.
System Key; Short-Press to access the System Menu Menu Key; Long-Press to access the System Menu
If you have an older version, please first update your Radio OS to at least the mentioned versions. Please consult your Radio Operating System Updating Procedure if you don't know how.
ExpressLRS highly recommends EdgeTX for the best experience and compatibility. EdgeTX has introduced options that old and new Radio handsets will benefit from, like One Bit Sample Mode (mainly for old FrSky Radios like the X9D and the QX7) and Mega Bauds (baud rates higher than 400K).
Simplest EdgeTX Updating Procedure (click/tap to expand)
Visit http://buddy.edgetx.org/.
Select the EdgeTX version and the Radio Model you want to update from the Left-hand side column.
Click the Download .bin button at the bottom of the page.
Save the firmware file into your Radio's SD Card, inside the Firmware Folder.
Reboot the Radio into DFU/Bootloader mode.
Start by turning off your radio.
Press and hold the two horizontal Trim switches then press the Power button. The Screen should Light up. Release the buttons.
Some Radios have a different procedure, like the BetaFPV Lite Radio 3 Pro. Consult the Manual for the steps to get it into this DFU/Bootloader mode.
Select Write Firmware.
Navigate to the EdgeTX firmware file you just downloaded.
Follow the screen prompts.
Once Writing is complete, reboot the radio.
Check the Radio's Version Page to verify you have the version you need.
Check this page for the EdgeTX installation instructions if you're coming in from OpenTX.
The Baud Rate is the speed to which (in this instance) the Transmitter module and the Radio Handset communicate. It is measured in bits per second. Common baud rates include 115200bps (sometimes shown as 115K) and 400000bps (sometimes shown as 400K).
A faster or higher baud rate means that the module and radio can talk much faster, further lowering the end-to-end latency of the system. However, not all radio handsets or transmitter modules are capable of higher baud rates as this is highly dependent on the hardware.
Depending on the firmware that is running on your radio handset, you can change the baud rate setting to better suit your setup.
The minimal required Baudrate depends on the highest Packet Rate you intend to run. The Baudrate should be set to:
400K (400000bps): for Packet Rates of 250Hz and lower. This setting should work on most Radios and TX Modules.
921k (921000bps): for Packet Rates of 500Hz and lower.
1.87M (1870000bps): for Packet Rates F1000 and lower.
However, there are some exceptions:
The FrSky Taranis QX7 ACCST, Horus X12S and Horus X10S cannot reliably run 400K baud rate without the Crossfire Mod.
The FrSky Taranis X9D has proven to be finicky even with the default 400K baud rate and will benefit from the One Bit Sample Mode setting and a Hardware Mod. See Troubleshooting the X9D for more details.
On other Radios, you can set the Baudrate higher than 400K but will highly depend on what TX Module you will use with it.
"},{"location":"quick-start/transmitters/tx-prep/#max-usable-baud-rates","title":"Max Usable Baud Rates","text":"Internal TX Module Max Baud Rate Notes RadioMaster TX16S 5.25M RadioMaster Zorro 5.25M RadioMaster Boxer 5.25M RadioMaster Pocket 5.25M RadioMaster MT12 5.25M RadioMaster TX12 5.25M Jumper T-Lite V2 1.87M Limited by Handset Jumper T-Pro 1.87M Limited by Handset Jumper T20 1.87M Limited by Handset Jumper T14 5.25M Jumper T15 5.25M Jumper T12 Max 5.25M BetaFPV Lite Radio 3 Pro 1.87M Limited by Handset HelloRadio V16 5.25M External TX Module Max Baud Rate Notes Happymodel ES24TX (inc. slim, nano, etc) 5.25M Happymodel ES24TX Pro/Slim Pro 5.25M Happymodel ES900TX 5.25M Happymodel ES915/868TX 1.87M STM-based BetaFPV Micro & Nano (V1 & V2) 5.25M BetaFPV SuperG 5.25M RadioMaster Ranger (Micro & Nano included) 5.25M RadioMaster Bandit (Micro & Nano included) 5.25M Axisflying Thor 5.25M EMAX Aeris OLED & Nano 5.25M NamimnoRC Flash/Voyager (no OLED) 3.75M STM-based NamimnoRC Flash/Voyager OLED 5.25M Vantac Lite 1.87M Jumper Aion Nano 1.87M iFlight Command 8 3.75M wired as external module HGLRC Hermes 5.25M HGLRC T ONE OLED 5.25M FrSky R9M/R9M Lite/R9M Lite Pro 1.87M FrSky R9M 2018 (non-ACCESS) 115K Resistor Mod for 400K QuadKopters JR & Slim 5.25M SIYI FM30 1.87M STM-based ImmersionRC GHOST 1.87M STM-based
Note
The Max Baud Rate for external modules will still depend on the capabilities of the Radio Handset.
As stated above, older radios like the QX7 and X9D(+) will require hardware mods and software tweaks, like the One Bit sampling mode, to work reliably at higher baud rates. We recommend not going higher than 400K on these radios. Set them higher at your own risk.
Newer EdgeTX radios can easily use higher baud rates without modification and we recommend using the maximum baud rate whenever you can.
My TX Module is not in this list! (click/tap to expand)
Don't be salty. That just means the maintainers are late with the updates. Newer TX modules being released are all ESP-based now. If your TX module has WiFi or Bluetooth Connectivity, then they are ESP-based, and thus, should be capable of 5.25M Baud Rate (depending on the handset).
The ADC filter is enabled by default in OpenTX and is known to cause issues with RC Command data. This can result in \"jagged\" RC command responses in black box logs, caused by sequential RC packets that have the same command value (which were \"smoothed\" by the ADC filter). We recommend turning the ADC filter OFF in OpenTX/EdgeTX.
To check and change this setting, follow these steps:
Press SYS Key.
Older Radios or those with only one Menu Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to get to the System Menu.
Press the PAGE Key until you reach the Hardware Page.
Scroll down until you reach the ADC Filter setting.
Press Enter Key to toggle it On or Off.
EdgeTX 2.7.0 (and newer) Per-model Settings (click/tap to expand)
With EdgeTX 2.7 or newer, you can set this per model (Global, On, Off) as this is helpful on Fixed Wing models equipped with PWM receivers connected to slower servos.
Press MDL Key.
Older Radios or those with only one Menu Key will need to short-press the Menu Key to access the Model Menu.
Consult your Radio User's Manual on how to get to the Model Menu.
Press the PAGE Key until you reach the Model Setup Page. On Colored Screen Radios, this should not be needed.
Scroll down until you reach the ADC Filter setting.
Press Enter Key once.
Use the Scroll wheel to select between Global(uses the setting from the Hardware page in the System Menu), On or Off.
If you're using an External ExpressLRS Module, make sure the Internal RF Module is OFF.
If your Radio has an Internal ExpressLRS Module, and you want to use it instead of an external module, then set the External RF Module to OFF, and then set the Internal RF Module to CRSF Protocol.
ExpressLRS uses the CRSF serial protocol to communicate between the transmitter and the TX module. Follow the following procedure to set it up on the currently selected Model:
Older Radios or those with only one Menu Key will need to short-press the Menu Key to access the Model Menu.
Consult your Radio User's Manual on how to get to the Model Menu.
Press the PAGE Key until you reach the Model Setup Page. On Colored Screen Radios, this should not be needed.
Scroll down until you reach the Internal RF settings. Set this to Off.
Scroll down until you reach the External RF settings.
Set the Mode to CRSF.
You can also change the baud rate setting at this point.
(Optional) Set the Receiver ID to a Unique Number.
Press the RTN Key or Exit the Model Menu
Press the MDL Key.
Older Radios or those with only one Menu Key will need to short-press the Menu Key to access the Model Menu.
Consult your Radio User's Manual on how to get to the Model Menu.
Press the PAGE Key until you reach the Model Setup Page. On Colored Screen Radios, this should not be needed.
Scroll down until you reach the Internal RF settings.
Set the Mode to CRSF.
(Optional) Set the Receiver ID to a Unique Number.
Scroll down until you reach the External RF settings. Set this to Off.
Press the RTN Key or Exit the Model Menu
No CRSF Mode Option? (click/tap to expand)
If for some reason, you cannot find the CRSF Protocol under the Internal RF Modes, set the Internal Module Type to CRSF via your Radio's System Menu -> Hardware page.
Press the SYS Key.
Radios without a dedicated SYS Key will need to long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to get to the System Menu.
Press the PAGE Key until you get to the Hardware page.
Scroll down until you reach the Internal RF settings.
Set the Type to CRSF.
You can also set the Baudrate at this point.
Press the RTN Key or Exit the Hardware Menu, and go back into setting your Internal RF module.
Note
The iFlight Commando 8 is NOT using an internal RF module for its ExpressLRS units, unlike the RadioMaster Zorro, RadioMaster TX16S MK2, RadioMaster TX12 MK2, Jumper T-lite V2, Jumper T-pro or the BetaFPV Lite Radio 3 Pro.
Set the Internal RF module to Off, and set the External RF module to CRSF protocol, as any External RF module requires.
"},{"location":"quick-start/transmitters/tx-prep/#switches-and-aux-channels","title":"Switches and Aux Channels","text":"
By default, a fresh model does not have any Aux Channels configured (Aux channels start from Ch5, with the first 4 Channels assigned to your joysticks). If moving any of the switches in your radio doesn't affect your Modes in Betaflight or INAV, this is one of the main reasons. So let's get this sorted out!
Press the MDL Key.
Older Radios or those with only one Menu Key will need to short-press the Menu Key to access the Model Menu.
Consult your Radio User's Manual on how to get to the Model Menu.
Press the PAGE Key until you reach the Mixes Page.
Scroll down and select the Channel you want to configure.
Long press Enter and select Edit and press Enter once more.
(Optional) You can name this channel however you want to remind you of its purpose.
Select Source. Press the Enter Key.
Activate or flick the Switch you'd want to use for this channel.
An example would be for CH5, which will be your Arming switch, you'd want to choose a 2-position switch.
Press the Enter Key once more to set the switch.
Press RTN Key once to exit the Channel Mix editor.
Repeat steps 3-9 until you have configured all the switches you think you will need.
Mono-Screen RadioColored-Screen Radio
"},{"location":"quick-start/transmitters/updating/","title":"Typical Updating Steps","text":""},{"location":"quick-start/transmitters/updating/#esp-based-tx-module-updating-methods","title":"ESP-based TX Module Updating Methods","text":"via WiFivia UARTvia ETX Passthrough Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
Some TX Modules would require disassembly before you can reach the USB port.
Determine whether your TX Module is being detected correctly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
Commonly used USB-to-UART chip for ExpressLRS Modules include: CP210x, CH340 and the CH9102 (driver download pages linked).
Some TX Modules have switches to change how the USB port interacts with the different components in the module. Make sure to set it in the position for \"Flashing the TX Module via UART\".
The ES24TX line of modules from Happymodel have jumper blocks or dipswitches inside the module.
The BetaFPV Micro modules have dipswitches at the back.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB. Return any dipswitches or jumper blocks to their \"Normal Operation\" position.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
Info
ETX Passthrough is the result of the collaborative effort between RadioMaster, EdgeTX and ExpressLRS.
It is only available on Radios with Internal ExpressLRS Modules.
Before you start, ensure you have the latest EdgeTX firmware version on your Radio. Consult the EdgeTX documentation regarding the updating process.
TX16S MK2: Update it to at least EdgeTX 2.7.0 (f79978b) or EdgeTX 2.7.1 (a55aff0).
Zorro: Update it to at least EdgeTX 2.7.0 (f79978b) or EdgeTX 2.7.1 (a55aff0). It often comes with an earlier EdgeTX 2.7.0 version (2bdd4974) which results in unsuccessful flashing.
TX12 MK2: Update it to at least EdgeTX 2.8.0 (f6d140e) for full EdgeTX support.
Boxer: The factory EdgeTX firmware should be based off an early EdgeTX 2.8.0 and wouldn't need an update.
BetaFPV Lite Radio 3 Pro: Update it to at least EdgeTX 2.8.0 (f6d140e) for full EdgeTX support.
Jumper T-Pro: Update it to at least EdgeTX 2.7.1 (a55aff0) for full EdgeTX support.
Jumper T-Lite V2: Update it to at least EdgeTX 2.8.0 (f6d140e) for full EdgeTX support.
Simplest EdgeTX Updating Procedure (click/tap to expand)
Visit http://buddy.edgetx.org/.
Select the EdgeTX version and the Radio Model you want to update from the Left-hand side column.
Click the Download .bin button at the bottom of the page.
Save the firmware file into your Radio's SD Card, inside the Firmware Folder.
Reboot the Radio into DFU/Bootloader mode.
Turn off your radio.
Press and hold the two horizontal Trim switches then press the Power button. The Screen should Light up. Let go of the buttons.
Some Radios have a different procedure, like the BetaFPV Lite Radio 3 Pro. Consult the Manual for the steps to get it into this DFU/Bootloader mode.
Select Write Firmware.
Navigate to the EdgeTX firmware file you just downloaded.
Follow the screen prompts.
Once Writing is complete, reboot the radio.
Check the Radio's Version Page to verify you have the version you need.
Also, make sure you have an internal ELRS module on your Radio. The following steps only apply to handsets with ExpressLRS-specific internal modules. There are stickers marked with \"ELRS\" attached to your radio packaging or boxes, as well as on the JR module bays indicating the type of internal rf module the radio has.
The current Model on the radio should be using the Internal ExpressLRS Module. Test this by loading the ExpressLRS Lua Script from the Tools Menu.
There's one more setting you want to make sure is set properly before proceeding.
Press the SYS Key on the Radio.
Radios without a dedicated SYS Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to get to the System Menu.
Press the PAGE Key until you reach the Hardware Page.
Scroll down until you see the Serial Ports settings.
Select or highlight USB-VCP. Press Enter and use the Scroll Wheel to set it to CLI mode if it is set to a different setting. Press Enter once more to confirm the changes.
Exit the Hardware menu by long-pressing RTN Key.
Now follow the next steps to get your Internal ExpressLRS Module Updated:
Connect your powered-up Radio to your Computer via a USB Data Cable.
On your Radio, scroll down and select USB Serial(VCP) then press the Enter Key. Set your Radio aside in the meantime.
On your Computer, check whether your Radio is being recognized correctly as a STMicroelectronics Virtual COM Port device.
Important
This is a vital step and a common failure point. Pay attention.
Windows Users can use Device Manager to check whether the Radio is being recognized correctly.
Yellow Caution Triangles in the Device Manager, or any mention of <Radio Name> Serial Port means drivers aren't installed.
Download the Driver package first. Unzip/extract the contents of the package and run/execute (double-click) the installer file (VCP_V1.5.0_Setup_W7_x64_64bits.exe for Windows 10 Users).
Once Drivers are installed, check again if the Radio is now being recognized correctly. You may have to first unplug-replug the USB Cable or even reboot your computer.
You only have to do this once usually.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Set the Flashing Method to EdgeTXPassthrough
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your Radio from USB.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
If you are flashing/updating your TX module via WiFi for the first time from the factory firmware, or from an older firmware, to ExpressLRS 3.x firmware, you will first need to flash it to version 2.5.2, then flash it with the Repartitioner binary file (right click, save as/save file as). Should it complain about Target Mismatch, just click Flash Anyway. Only then you can flash to 3.x firmware via WiFi.
Joshua Bardwell has a video about it here.
Updating to 3.x via UART or ETX Passthrough doesn't require 2.5.2 firmware or the Repartitioner.
"},{"location":"quick-start/transmitters/vantac-lite/#flashingupdating-your-tx-module-firmware","title":"Flashing/Updating your TX Module Firmware","text":"via WiFivia UART Manual Upload via APManual Upload via Local WiFiAuto Upload
Heads up!
This option is only possible if you haven't previously flashed or configured your TX Module with your Home WiFi SSID and Password or if it's unable to connect to said WiFi Network because the router is Off or unreachable.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Vantac 2.4 GHz
Device:
Vantac Lite 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select Wifi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Using a WiFi-capable device such as your smartphone or laptop, scan for the ExpressLRS TX Access Point. Connect to this Access Point.
If your TX Module is previously flashed with your Home WiFi SSID and Password, and it is able to connect to that WiFi Network, then the Access Point will not show up.
expresslrs is the Password for this Access Point.
Where's the Access Point? (click/tap to expand)
If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
Once connected to the ExpressLRS TX Access Point, open up a Browser window, type in the IP Address 10.0.0.1 on the Address Bar, and press Enter. The ExpressLRS Web UI will load.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Vantac 2.4 GHz
Device:
Vantac Lite 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Build button.
Once the Build process is done, a Temp folder window containing your firmware binaries should pop up.
Do not close this Temp folder because this is where you will take your firmware from in the later steps. If you are planning on using your phone or tablet to upload the firmware file later, copy the firmware file into your device.
NOTICE
With the release of ExpressLRS 3.3.0 and ExpressLRS Configurator 1.6.0, only one file will show up. Use the firmware.bin file for the next steps.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
With your module now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_tx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
MDNS is not working! (click/tap to expand) The arp CommandRouter DHCP List
Open up a Command Prompt window on your computer.
Execute the command arp -a, which will list all the devices in the Network.
Use each of the IP Addresses marked as Dynamic as a URL in your Browser until you get to the ExpressLRS Web UI.
Log in into your Router dashboard.
Check the DHCP List and look for the \"elrs\" device.
Take note of the IP Address given by your router.
Use this IP address in your Browser as the URL.
Activate the Update Tab.
If your TX Module is still on an earlier firmware version, then there's no Update Tab, and instead, you will need to scroll down to find the Firmware Update section.
Drag and drop the Firmware file from the Temp folder into the File Upload field.
You can also use the Browse or Choose File button and browse for the file yourself, especially if you've copied/moved it somewhere else on an earlier step.
Click the Update button to start the Updating procedure.
Wait for the firmware file to get uploaded and flashed into your device. It only takes a minute or two, and you will see the Success Popup Message.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Heads up!
This option is only possible if you have previously flashed or configured your TX Module with your Home WiFi SSID and Password and the module is able to connect to said WiFi Network.
MDNS must also be working so your browser can resolve the address http://elrs_tx.local and load the ExpressLRS Web UI from said address.
Press the SYS Key on your Radio to display the Tools Menu, where you can find the Lua Scripts.
Older Radios or those with only one Menu Key must long-press the Menu Key to access the System Menu.
Consult your Radio User's Manual on how to access the System Menu.
Scroll down and select ExpressLRS Lua Script.
If the script is nowhere to be found, download it from this page and save it into your Radio SD Card Scripts/Tools/ folder.
Press Enter to Load it.
If the script is stuck on a \"Loading...\" screen, return to the Radio Preparation Page and make sure you have configured your radio properly for ExpressLRS use.
Scroll down and select WiFi Connectivity and press Enter.
Select Enable WiFi and press Enter.
The WiFi Running screen will show up. Your TX module is now in WiFi mode.
Do not worry if the Script stops and shows a Syntax Error. The module is still in WiFi mode. The Syntax Error could be because you're on an older radio, older EdgeTX/OpenTX firmware, or both. It could also be because your TX module is on an earlier firmware version, and you're using a more recent Lua Script.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Vantac 2.4 GHz
Device:
Vantac Lite 2.4GHz TX
Set the Flashing Method to WiFi.
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the upload to finish. A Green Success bar will show up in the ExpressLRS Configurator.
On your Radio, the WiFi Running screen should disappear and should be back to the WiFi Connectivity Menu of the ExpressLRS Lua Script.
Long-press the RTN Key to exit the ExpressLRS Lua Script. Then reload it to check for the ExpressLRS Firmware version and verify your TX module has been updated.
Connect your TX Module to your Computer via a USB Data Cable. Best if you remove it from your Radio.
Determine whether your TX Module is being detected properly as a USB-to-UART Device.
Windows Users can check via Device Manager, Ports device grouping.
Drivers will be needed if the TX Module is not being detected correctly. This is indicated by a Yellow Caution Triangle in Device Manager.
You can download the drivers from the links below:
Windows users: CH340 Windows Drivers
For other Operating Systems, head to this site to download your needed drivers.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
Vantac 2.4 GHz
Device:
Vantac Lite 2.4GHz TX
Set the Flashing Method to UART
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Local WiFi Network Credentials (Optional. Will be used the next time the device goes into WiFi mode).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Unplug your module from USB.
Reconnect your TX module into your Radio's External Module bay.
Using the ExpressLRS Lua Script from the Tools Menu, check if the firmware version got updated.
ExpressLRS 3.5.x will be the last version to support STM32-based hardware. This includes the Happymodel PP, ES915 Tx and Rx, early NamimnoRC Flash and Voyager, FrSky R9, SIYI and ImmersionRC hardware.
The STM32 platform's limited compute resources and feature gaps (WiFi, Bluetooth, Backpacks) made for an inferior version of ExpressLRS that necessitated disproportionate maintenance burden for the Dev Team.
"},{"location":"quick-start/transmitters/voyager900/#flashingupdating-the-tx-module-firmware","title":"Flashing/Updating the TX Module Firmware","text":"via Stock_BLvia STLink
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 900 MHz
Device:
NamimnoRC Voyager 900MHz TX
Set the Flashing Method to Stock_BL
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Build button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
A Temp folder will open up with the firmware.elrs file. Copy-paste the firmware.elrs file into your Radio's SD Card (preferably to the /FIRMWARE folder for easy access).
On your radio, open the System Menu.
On newer radios, you can press the SYS key to open the System Menu
On older radios, or radios that only have a menu key, long-press the Menu key to open the System Menu
Using the Page key/s, navigate to the SD-HC Card page, scroll-down and open the FIRMWARE folder where you can find the firmware.elrs file.
Highlight the file and press-hold the Enter button and select \"Flash External ELRS\". Wait for the firmware to be written.
No Sync (click/tap to expand)
Make sure you have updated the OpenTX/EdgeTX firmware of your radio to a newer version
Make sure the current model selected on the radio is set up for ExpressLRS Use. See the [Radio Preparation] guide.
With the ExpressLRS Lua Script in the Tools page, verify if the firmware version has been updated.
Attention
Only use this method if the firmware has been corrupted.
Disassemble your TX Module to get access to the mainboard.
Connect your STLink V2 dongle to the pads shown in the image below.
Connect your STLink V2 dongle to your Computer's USB Port. Make sure it is being detected correctly.
Launch the ExpressLRS Configurator on your Computer.
Make sure Official Releases is active from the horizontal tab.
Ensure you select the Released version you want to flash into your TX module.
Select the Device Category and Device target matching your hardware.
Device Category:
NamimnoRC 900 MHz
Device:
NamimnoRC Voyager 900MHz TX
Set the Flashing Method to STLink
Set the firmware options for your device.
Regulatory Domain (Mandatory. Choose the domain appropriate for the location or country you're flying).
Binding Phrase (Optional, but Highly Recommended. Note this phrase as it should be the same on your other devices, or they will not bind or sync).
Click the Flash button.
Wait for the process to finish. A Green Success bar will show up in the ExpressLRS Configurator.
Disconnect the STLink V2 dongle from the TX Module PCB and reassemble the module.
Reattach your TX Module into your Radio and, using the ExpressLRS Lua Script, verify if the firmware version has been updated.
With the addition of MAVLink support in ELRS 3.5, it is no longer recommended to use Airport for MAVLink telemetry. Please see the MAVLink page for more info.
AirPort provides a firmware option that allows you to turn a regular ExpressLRS transmitter and receiver pair into a bi-directional transparent serial data link, over the air. A TX module can connect via USB to a laptop, and RX modules (or those flashed using RX-as-TX) can connect to a free UART on your device, as per usual. This allows for a wireless serial data link between TX and RX, as if they were connected directly via serial. Note that due to the packet size and sensitive LoRa modulation parameters used by ELRS, the data rate is relatively slow. Also, as the protocol has no knowledge of the data being transported, there is no ACK or retransmission which may result in dropped packets.
Warning
The AirPort option completely replaces the RC link, and repurposes it as a data link. If you intend to retain RC control via ELRS, you will need to run 2x TXs and 2x RXs on the ground and air, respectively. One TX+RX pair sends your normal RC link data, just as it does now, and the other TX+RX pair sends the serial data.
ExpressLRS TX module: A dedicated external TX module is required for the data link. The TX should ideally have an external USB port to make it easy to attach to a computer (assuming a computer is the desired endpoint for the data link). It is also favorable to use a module with a screen and a 5-way button, which makes packet rate and power selection easier. The TX should use an ESP-based microcontroller (for access to the WebUI).
ExpressLRS RX: Any ExpressLRS ESP-based receiver is compatible with AirPort (technically STM-based receivers can work too, but it will be harder to set up and is therefore not covered in this guide). Receivers with higher telemetry power output (i.e. 100mW telemetry power) will provide better results.
Frequency band
If you plan to use two side-by-side ELRS links on the craft (one for RC and one for telemetry), it is HIGHLY recommended to use different frequencies for each link. For example, you will see good results with RC on 2.4GHz and AirPort on 900MHz. The range will be severely reduced if both RC and AirPort are on the same frequency band.
"},{"location":"software/airport/#data-rate-vs-baud-rate","title":"Data rate vs Baud rate","text":"
AirPort uses a 64-byte buffer to queue bytes that it receives from the FC or GCS, before sending them over the air. If the buffer overflows, the entire 64 bytes are discarded. For this reason, it is VERY important to select a serial baud rate that limits the flow of serial bytes to match the maximum over-the-air (OTA) data rate.
The OTA data rate is determined by the selected packet rate. A faster packet rate will result in a higher data rate at the expense of range. The table below shows the baud rate you should use when configuring the AirPort feature.
Packet Rate Maximum OTA Data Rate (bytes/s) Baud Rate to Select 25Hz 62 600 50Hz 125 1200 100Hz 250 2400 100Hz Full Res 500 4800 200Hz 500 4800 250Hz 625 4800 333Hz Full Res 1665 14400 or 9600 500Hz 1250 9600 1000Hz 2500 19200
Once AirPort is enabled, there will be no way to access the RX settings from the LUA script. Before enabling the AirPort option, it is recommended that you bind the TX and RX normally, and (using the LUA) set the RX telemetry power output to maximum. If you already have AirPort enabled, and need to change the RX power, you will need to disable the AirPort checkbox by doing the reverse of the steps below, change the power using LUA, then re-enable AirPort.
Binding Phrases
Use a binding phrase that is different from whatever you are using for your RC link if you intend to run RC + AirPort side by side in ANY way.
TX ModulesRXes
Flash the TX Module with the latest ELRS release version (AirPort is available in v3.3.0 onwards).
Enable WiFi on the TX module. This can be enabled by inserting the TX into a handset, and in the LUA script select WiFi Connectivity -> Enable WiFi. WiFi can also be enabled via the screen + 5-way if your TX has one (while powered via USB).
Using a computer or mobile device, connect to the TX WiFi using your preferred method (hotspot or home WiFi).
Open the WebUI (10.0.0.1 for hotspot, or http://elrs_tx.local for home WiFi) in a browser.
In the ELRS WebUI, check the Use as AirPort Serial device checkbox.
In the AirPort UART baud field, enter your desired baud rate. IMPORTANT: Pay close attention to the \"Data rate vs Baud rate\" section above when choosing your baud. A good default is 9600 baud for 2.4GHz and `4800`` baud for 868/900MHz.
Click SAVE & REBOOT.
Flash the RX with the latest ELRS release version (AirPort is available in v3.3.0 onwards).
Enable WiFi on the RX. This can be enabled by powering on the RX with no TX powered and waiting for the WiFi timeout.
Using a computer or mobile device, connect to the RX WiFi using your preferred method (hotspot or home WiFi).
Open the WebUI (10.0.0.1 for hotspot, or http://elrs_rx.local for home WiFi) in a browser.
In the ELRS WebUI, check the Use as AirPort Serial device checkbox.
In the UART baud field, enter your desired baud rate. IMPORTANT: Pay close attention to the \"Data rate vs Baud rate\" section above when choosing your baud. A good default is 9600 baud for 2.4GHz and `4800`` baud for 868/900MHz.
Once you have enabled the AirPort setting on both TX and RX, they should be ready to send bi-directional serial data. If you have an FTDI (USB to serial adapter) handy, you can confirm that the link is working as expected before installing it in a craft.
Using a suitable USB cable, connect your TX module to a computer.
Open a serial terminal client, such as PuTTY, and connect to the COM port for your TX module using the baud rate you chose in the section above.
Connect your FTDI to your computer, and connect the RX to the FTDI
Open a second instance of PuTTY, and connect to the COM port for your FTDI using the baud rate you chose in the section above.
Type chars into each PuTTY window, and confirm you can see them on the opposite terminal session (i.e. typing into the TX PuTTY should result in the same chars appearing in the RX PuTTY window). If you see comms, everything is working.
Connect the RX to a spare UART on your flight controller, as per normal:
Example AirPort Receiver Wiring
Using the appropriate Configurator tool for your FC firmware, configure your selected UART with your desired telemetry protocol. For example, if using AirPort for MAVLink in ArduPilot, you would set:
SERIALN_BAUD to the baud you entered in the section above,
SERIALN_OPTIONS to 0,
SERIALN_PROTOCOL to 1 or 2 (for MAVLink v1 or MAVLink v2).
Connect the TX to a computer via USB, open the program that you intend to view the telemetry in, then connect to the COM port for your TX module at the baud you entered above. For example, if using AirPort for MAVLink in ArduPilot, you would open Mission Planner / QGC etc. and select the TX COM port, enter the baud, then click Connect.
Version 3.4+ of ELRS introduces a new option in the Backpack section of the ELRS LUA script called \"Telemetry.\" This feature allows a Backpack equipped ELRS Transmitter to forward CRSF telemetry frames to any peer that is capable of receiving ESPNOW messages. These frames can be consumed by any Backpack receivers that are bound with your bind phrase.
Sentinel Integration
This capability is particularly useful for devices like the Sentinel Antenna Tracker, which can subscribe to ESPNOW telemetry packets and read GPS data from the telemetry feed. See the Sentinel product page
ELRS transmitter and receiver with the latest firmware.
Backpack-capable receiver (e.g., in the Sentinel Antenna Tracker).
Configured ELRS LUA script on your transmitter.
"},{"location":"software/backpack-telemetry/#setting-up-the-backpack-telemetry-feature","title":"Setting Up the Backpack Telemetry Feature","text":""},{"location":"software/backpack-telemetry/#step-1-update-firmware","title":"Step 1: Update Firmware","text":"
Ensure both your transmitter and receiver are running the latest firmware. Follow the firmware update guide for detailed instructions. This feature is available in v3.4.0 onwards.
"},{"location":"software/backpack-telemetry/#step-2-enable-backpack-telemetry-in-elrs-lua-script","title":"Step 2: Enable Backpack Telemetry in ELRS LUA Script","text":"
Access the LUA Script:
Power on your transmitter and navigate to the System menu.
Execute the ELRS LUA script.
Navigate to the Backpack Section:
Scroll to find the \"Backpack\" section within the LUA script.
Select the \"Telemetry\" option.
Enable Backpack Telemetry:
Set the \"Telemetry\" option to ESPNOW.
Exit the script.
NOTE: Backpack telemetry is transmitted on the 2.4G WiFi band, via ESPNOW (this should have a very limited impact on any LoRa signals, as it is modulated via OFDM like a normal WiFi hotspot). Every telemetry message that your transmitter receives from the craft will be re-transmitted via ESPNOW. You may want to disable Backpack Telemetry to reduce your footprint on the RF noise floor when you aren't using it, especially if you are at something like a race day, where there is often contention on the RF spectrum. To disable Backpack Telemetry:
Execute the ELRS LUA script.
Scroll to find the \"Backpack\" section within the LUA script.
Ensure your Backpack receivers (e.g., the one in the Sentinel Antenna Tracker) are bound using your bind phrase. This allows them to receive telemetry data sent via ESPNOW. See the Sentinel ELRS setup guide
"},{"location":"software/backpack-telemetry/#using-the-telemetry-feature-with-sentinel-antenna-tracker","title":"Using the Telemetry Feature with Sentinel Antenna Tracker","text":""},{"location":"software/backpack-telemetry/#sentinel-configuration","title":"Sentinel Configuration","text":"
The Sentinel Antenna Tracker includes an ESP12 Backpack-capable receiver that can consume ESPNOW telemetry frames. Ensure the tracker is properly configured to subscribe to ESPNOW telemetry packets. See the Sentinel ELRS setup guide
Once configured, power up your GPS-equipped craft and establish the link between your ELRS Transmitter and Receiver. Ensure that GPS telemetry is being received on your Handset (go to the Model menu in EdgeTX, and inspect the Telemetry page to make sure you are getting GPS coordinates). The Sentinel Antenna Tracker will be able to read GPS data and other telemetry information from the telemetry feed provided by the ELRS transmitter.
"},{"location":"software/backpack-telemetry/#advanced-use-cases","title":"Advanced Use Cases","text":"
This new telemetry feature can be expanded for various applications, e.g.:
Real-time flight data monitoring.
Integration with other ESP Backpack-compatible devices.
Any Espressif ESP-based microcontroller, like the ESP32 or ESP8266 (and many variants) is capable of receiving ESPNOW frames. Custom firmware could be written to decode the CRSF telemetry and consume it in your own custom solution. See this ESPNOW guide for an example of developing using ESPNOW.
No Telemetry Data: Ensure the \"Telemetry\" option is set to ESPNOW in the Backpack section of the LUA script and that the firmware is up to date. Also check that your Telemetry Ratio is set to a value that is able to provide frequent telemetry packets. As a rule of thumb, a ratio somewhere between 1:2 to about 1:16 (depending on your packet rate) will suffice. See Packet Rate and Telemetry Ratio and Telemetry
Binding Issues: Verify that the bind phrase is correctly set and matches between the Backpack on your transmitter and the Sentinel receiver.
Interference: The Backpack Telemetry feature uses a point to point WiFi-based link to forward telemetry. The Sentinel tracker (or other Backpack receiver type) should be within 10m of the ELRS transmitter (ideally 5m or less) for good WiFi signal. Some ELRS transmitters have better Backpack WiFi antennas than others, so your mileage may vary depending on your hardware. If you are experiencing drops in the link between ELRS and the Sentinel tracker (or other Backpack receiver type), try moving the two closer, or move to an area with less WiFi noise.
Dynamic Power allows the TX module to lower its output power from the configured power level using signal information from the RX. The TX will lower power if the signal level is above a threshold (see below) and will raise power if it is not, has a low LQ, or has a sudden drop in LQ. Because Dynamic Power relies on telemetry, telemetry must be enabled. That is, \"Telem Ratio\" must be set to anything except \"Off\" or \"Race\".
Warning
Dynamic Power relies on telemetry. If no telemetry is received while armed, then the power level will be kicked up to the maximum configured power level.
"},{"location":"software/dynamic-transmit-power/#how-to-configure-dynamic-power","title":"How to configure Dynamic Power","text":"
In the ELRS Lua script, select > TX Power. There are three configurable elements.
Max Power: The output power will never exceed this power output level in any situation.
Dynamic: Three options are available.
Off: Fixed power, always set power to the configured Max Power output.
Dyn: Dynamic power is enabled.
AUX9-AUX12: Dynamic power is enabled only when this AUX channel is high, and power is fixed to the Max Power when low. Demo Video
Fan Thresh: Fan threshold. If the module has a fan, it will be enabled starting at this power level after a short delay.
Another important setting is to make sure your craft is armed on AUX1=high (~2000us). See Switch Modes for more information about AUX channels.
For non-FLRC modes, Dynamic Power uses the average signal to noise ratio (SNR) reported by the receiver. If the SNR is above a threshold, the power will be lowered by one level. SNR is used because it takes into account interference (the \"noise\" in signal-to-noise) and is not affected by receivers with LNAs, which boost RSSI dBm. The thresholds for lowering the power are specific to each packet rate. For example, 250Hz (LoRa) will lower the power if SNR is >= 9.5 but 150Hz (LoRa) will lower power if the SNR is >= 8.5.
For FLRC modes (packet rates beginning with F or D) Dynamic Power averages the last few RSSI dBm readings from the RX. If the RSSI is >= -83dBm, the transmit power is lowered by one level.
For both algorithms, the power will only be lowered if the link quality (LQ) is 95% or higher.
The opposite of the \"lowering power\" algorithm is also in place, to raise power as needed slowly such as when flying away on a long range flight. The algorithms are the same as for lowering power, except with different thresholds. Examples:
250Hz (LoRa) raise power if SNR <= 3.0
150Hz (LoRa) raise power if SNR <= 0.0
F500 (FLRC) raise power if RSSI <= -89 dBm. Note that all FLRC modes use this same limit.
To be proactive when telemetry is not received, Dynamic Power will also increase power one level for each missed telemetry packet, starting when two are missed back to back.
TX misses first telemetry packet: no action, maintain power level
TX misses second telemetry packet: increase power 1 level
TX misses third telemetry packet: increase power 1 level
...
TX receives telemetry packet: normal raise / lower conditions apply
In addition to the slow power ramp up, three LQ-based conditions will raise the power immediately to the maximum configured value.
If the LQ ever drops below the hard limit (50% LQ), the power will jump to the max.
If the LQ drops suddenly in a single telemetry update compared to the moving average. This is intended to react to flying behind a structure where the LQ suddenly takes a hit and is expected to drop further. Example: LQ is running 100% (as ExpressLRS does under most conditions) and the TX receives a telemetry packet with 80% LQ, the power will jump to the max.
If telemetry is lost entirely with the arm switch high. Any time the TX is \"disconnected\" while armed, the power will jump to the max.
Finally, if reported LQ is below 85% and no other condition has been met this period, increase the power one level.
Because dynamic power relies on information coming back from the RX to know how to adjust the power, dynamic power is only available if the \"Telemetry Ratio\" is not set to Off / Race. Any ratio will allow it to operate, but the algorithm is optimized around having at least 2x Link Statistics telemetry packets per second, which is provided with the \"Std\" telemetry option. If using a manual telemetry ratio, it is recommended to use at least the ratio suggested below.
Packet Air Rate Telemetry Ratio 1000Hz 1:128 500Hz 1:128 250Hz 1:64 200Hz 1:64 150Hz 1:32 100Hz 1:32 50Hz 1:16
On startup, the output power will be set to the lowest possible value. If telemetry is lost while disarmed, the output power will stay at the current value until telemetry is received again. This is intended to prevent everyone's TX from blasting to max power when swapping batteries.
"},{"location":"software/dynamic-transmit-power/#osd-power-display","title":"OSD Power Display","text":"
To see the current output power on your FPV OSD, enable the TX Uplink Power OSD element and set Switch Mode to Wide in the ELRS lua. TX Uplink Power is not available if Switch Mode is set to Hybrid, or on older Betaflight (<4.3.0) and iNav (<2.6.0) versions.
"},{"location":"software/dynamic-transmit-power/#edgetx-opentx-power-readout","title":"EdgeTX / OpenTX Power Readout","text":"
Alternatively, a handset special function can be used to generate an audio notification when the TX power level changes.
Set a logical switch to |\u0394|>x / TPWR / 1mW as shown in L04 below. The logical switch triggers when the power changes by at least 1mW.
For a readout when the power changes, set a special function triggered from the logical switch, and assign Play Value / TPWR / 1x (SF10 in the picture). If instead you'd prefer the power to be read out periodically, choose a switch to enable the special function, and assign Play Value / TPWR / (SF11 in the picture, with 10s interval).
Note
OpenTX has no value for 50mW in the CRSF Telemetry protocol and instead will be read as 0mW. EdgeTX versions 2.5.0 and newer have the proper 50mW readout.
"},{"location":"software/gemini/","title":"Gemini","text":""},{"location":"software/gemini/#what-is-gemini","title":"What is Gemini?","text":"
Gemini is a dual channel 2.4GHz and/or 900MHz (and potentially other low-band frequencies) transmission mode that leverages true diversity hardware to maximize LQ. This page covers single-band Gemini mode, which uses diversity hardware to transmit in multiple channels within the same band (e.g. 2.4GHz or 900MHz). There is also a dual-band mode, Gemini Xrossband or GemX, which is capable of transmitting on both 2.4GHz and 900MHz bands simultaneously. Please see the PR here for more info while the documentation is updated.
In Gemini Mode, a TX module simultaneously transmits a packet in two frequencies 40MHz apart for 2.4GHz and ~10MHz apart for 900MHz users. The packet separation used is half of the frequency domain selected and will vary a little. A true diversity Receiver is used to receive both packets simultaneously. Transmitting on 2 separate frequencies provides better interference avoidance and/or mitigation, in a similar way DVDA does by sending repeat packets sequentially on different frequencies. This means, the Receiver has an increased chance of receiving the packet. This results in a much higher and stable LQ.
Via Lua set your TX AND RX Antenna Modes to Gemini.
Use Model Config Matching to set the correct antenna mode based on the active Model on the radio. e.g. use Model 5 for single antenna receivers, Model 6 for Gemini-capable receivers.
"},{"location":"software/gemini/#introductory-video-and-testing","title":"Introductory Video and Testing","text":""},{"location":"software/gemini/#what-about-using-gemini-with-dvda","title":"What about using Gemini with DVDA?","text":"
Gemini doubles the redundancy of DVDA modes. For example, D500 sends 2 repeat packets on 2 different frequencies. When using D500 with a Gemini TX you will now have 4 packets sent across 4 different frequencies.
When using D250 which sends 4 repeat packets across 3 frequencies. With Gemini you will now have 8 repeat packets across 6 different frequencies.
"},{"location":"software/gemini/#what-are-the-benefits","title":"What are the Benefits?","text":""},{"location":"software/gemini/#freestylers","title":"Freestylers","text":"
Flying in urban environments with lots of RF noise? Gemini will help to dodge the interference and maintain a strong link.
Flying at events with 6 to 8 up racers, plus who knows how many handsets left powered up in the pits, can cause your precious link to take a hit. Gemini is an obvious choice for these environments when every packet counts.
"},{"location":"software/gemini/#lovers-of-telemetry","title":"Lovers of Telemetry","text":"
A Gemini TX has the advantage of not only sending simultaneous packets, but also receiving simultaneous packets. Or when used in single antenna mode (or switch mode) both antennas will listen for the same TLM packet, in the same way a diversity RX listens for RC packets. So your TLM link becomes stronger with fewer missed packets, even when not used in Gemini mode and with single antenna receivers.
"},{"location":"software/gemini/#airport-and-mavlink-users","title":"AirPort and MAVLink users","text":"
For data links a single missed packet can mean more than 1 missed packet. If a single packet is missed, this means the rest of the data that was received for that MAVLink packet is now wasted. As the MAVLink packet may have been split across multiple OTA packets and will not be complete. The single missed packet can turn into 10 packets missed. Gemini will help with making sure you get the highest MAVLink packet rate possible!
"},{"location":"software/gemini/#will-gemini-increase-my-range","title":"Will Gemini increase my range?","text":"
No. The packet sensitivity remains the same for the RF Mode (or Packet Rate) used. Gemini will help maintain a higher LQ to the point of failsafe. However failsafe will still happen at approximately the same distance e.g. the moon.
"},{"location":"software/gemini/#comparison-with-other-antenna-modes","title":"Comparison with other Antenna Modes","text":""},{"location":"software/gemini/#is-there-antenna-switching-with-gemini-can-antenna-1-of-receiver-talk-with-antenna-2-of-tx-if-they-are-in-the-same-polarization-during-a-flight","title":"Is there antenna switching with Gemini? Can Antenna 1 of Receiver talk with Antenna 2 of TX if they are in the same polarization during a flight?","text":"
Yes, there is antenna switching.
"},{"location":"software/gemini/#what-happens-if-i-use-a-gemini-tx-in-gemini-mode-with-a-single-antenna-receiver","title":"What happens if I use a Gemini TX, in Gemini Mode, with a single Antenna Receiver?","text":"
The Gemini TX will function as designed, in Gemini Mode. The Receiver will only get the signal from the TX it has synchronized with. The other TX, will act as a noise generator. Therefore, you should set the TX in either Switch or Single Antenna (Ant1/Ant2) Mode.
"},{"location":"software/gemini/#what-happens-if-i-use-a-gemini-tx-in-gemini-mode-with-gemini-incapable-diversity-receivers","title":"What happens if I use a Gemini TX, in Gemini Mode, with Gemini-incapable Diversity Receivers?","text":"
As above, with the Receiver antennas only getting sync from one TX. We recommend setting the TX to non-Gemini Modes.
"},{"location":"software/gemini/#how-does-a-gemini-rx-behave-when-paired-with-a-non-gemini-tx","title":"How does a Gemini RX behave when paired with a non-Gemini TX?","text":"
The Receiver will still listen on both Antennas, but only get sync on one. Both RX will send out Telemetry, but only one of them will be used.
You are flying with your buddies and your friend has crashed all his models. You'd like to be able to lend him one of yours but you can't because it's using a binding phrase, so he's relegated to being the crashed model fetcher for the rest of the day!
No longer is he destined to be running to the bando and back again fetching downed quads. You can use the \"Loan Model\" feature and lend him one of your models!
This is deprecated and removed in ExpressLRS 3.4.0 in favor of the new Binding Procedures. See the binding page for details.
"},{"location":"software/loan-model/#how-to-loan-model","title":"How to \"Loan Model\"","text":""},{"location":"software/loan-model/#on-the-lenders-handset","title":"On the lenders handset","text":"
Connect to the model you wish to loan out with your handset
Enter the LUA screen and select \"Other Devices\" at the bottom of the list
Choose the RX from the list
Select the \"Loan Model\" entry
The receiver LED should go into the bind flashing state
"},{"location":"software/loan-model/#on-the-borrowers-handset","title":"On the borrowers handset","text":"
From the main ExpressLRS LUA screen select [Bind]
The receiver LED should turn solid on, and the handset should connect to the receiver
"},{"location":"software/loan-model/#returning-a-loaned-model","title":"Returning a \"Loaned\" Model","text":"
There are a couple of ways to return a model to the owner.
The first method is for the borrower to return it from the LUA script as follows:
On the borrowers handset, connect to the \"loaned\" model
Enter the LUA screen and select \"Other Devices\" at the bottom of the list
Choose the RX from the list
Select the \"Return Model\" entry
The second method used if the borrower forgets to return the model, is as follows:
Power cycle the model 3 times in rapid succession, turning it off each time after the LED flashes on and off again.
If done correctly, the model will return to the state where it is bound to your transmitter.
Note
If the LED returns to normal flashing between reboots, the counter is reset to 0 and you must restart the process.
"},{"location":"software/loan-model/#bump-to-loan","title":"Bump to Loan","text":"
On transmitter modules with an accelerometer (such as the Axis Thor), you can loan and return a model by bumping it to another transmitter.
The process is easy - simply hold both the lender and the borrower's transmitters vertically while a model is connected and not armed and bump them together.
Note
If the borrower does not have an accelerometer, the borrower must go into binding mode manually.
Although MAVLink has been in development for some time, and has been tested by a community of early adopters using ArduPilot crafts, MAVLink support is still a recent addition. There may be unexpected bugs; Exercise due caution.
NOTE
Enabling MAVLink forces the use of Hybrid or 16ch/2 switch mode. Wide switch mode is not supported. Enabling MAVLink forces a telemetry ratio of 1:2
ExpressLRS now has full bi-directional MAVLink support, enabling native MAVLink telemetry downlink and RC control uplink. Users can now enjoy seamless integration of telemetry and RC control.
Unlike airport, you do NOT need a second RX/TX pair for RC control, since ELRS' implementation allows you to do BOTH telemetry and RC control over one link.
To start using MAVLink, you just need one ESP ELRS transmitter, and one ESP ELRS receiver. The majority of recent ELRS hardware is ESP based, and will be compatible with MAVLink. An easy way to check is, if the RX/TX have WiFi, then it is ESP based.
NOTE
If you are using an internal TX module (e.g. a TX16S with internal ELRS), you will be required to use the TX Backpack to connect to you GCS via WiFi (USB cable between the TX and the PC is not an option for internal modules). See WiFi Connectivity below.
NOTE
If you are planning to use 915/868MHz, note that the data rate will be significantly slower than on 2.4GHz. This will result in especially slow parameter downloading, and with 200Hz packet rate at 915MHz, it takes 2+ minutes to pull parameters.
"},{"location":"software/mavlink/#flashing-and-configuring-mavlink-rc","title":"Flashing and Configuring MAVLink-RC","text":"
Ensure both your transmitter module, the embedded TX-Backpack (if using WiFi forwarding), and your receiver are up to date with the latest release versions:
For the main ELRS firmware, follow the Firmware Update Guide for detailed instructions.
For the TX-Backpack, follow the Transmitter Backpack Firmware Guide for detailed instructions.
The minimum versions to use this feature are: - Transmitter / receiver firmware: 3.5.0 - TX Backpack firmware: 1.5.0
Using the guides above, flash both the RX and TX
Turn on both the RX and TX, and ensure they connect properly
In ELRS LUA script, select Other Devices, select your receiver, and set the serial protocol to MAVLink. This configures the RX to output MAVLink protocol on the UART.
Back out to the LUA scripts main menu, and select the new Link Mode option. Change it from Normal to MAVLink. This configures the TX module to send / receive MAVLink.
Configure your usual power, packet rate, etc. The telemetry ratio will be preset to 1:2 (and cannot be changed while in MAVLink mode).
(Optional) Configure Source and Target SysIDs
Power-cycle the receiver
Go to Other Devices and select your receiver
Set Target SysID to the vehicle SysID
Set Source SysID to preferred GCS SysID
Wire the RX to a free UART on your flight controller that is suitable for TLM + RC. A DMA-capable UART is recommended.
ArduPilotPX4INAVBetaflight
For the below steps, when a UART connection is mentioned, it will be written as SERIALx. Replace x with the UART number you are using.
Configure SERIALx_PROTOCOL=2, SERIALx_BAUD=460, and RSSI_TYPE=5
Connect the TX module to the computer running the Ground Control Station via a USB cable (or alternatively via WiFi - See WiFi Connectivity below)
Select the COM port on the GCS, and connect using 460800 baud
For the below steps, when a UART connection is mentioned, it will be written as SER_TELx. Replace x with the UART number you are using.
Configure SER_TELx_BAUD to 460800 8N1
Configure MAVLink with MAV_0_CONFIG to TELEM2
Configure MAVLink sending rate with MAV_0_RATE to 9600 B/s
UNSUPPORTED, CURRENTLY IN DEVELOPMENT - Released versions (up to version 7) of iNav cannot use MAVLink due the limitations highlighted in the Betaflight tab. As of version 8.0, which is currently not released yet, these limitations have been partially resolved and there is limited MAVLink support.
For testing of development version: For the below steps, when a UART connection is mentioned, it will be written as UARTx. Replace x with the UART number you are using.
In the Ports tab, set the UARTx Telemetry Protocol to MAVLink, and the baud rate to 460800. Make sure RX Serial is disabled.
In the Receiver tab, set the Receiver type to SERIAL and the Serial Receiver Provider to MAVLink. Leave inverted & half-duplex disabled.
Betaflight contains an incomplete implementation of the MAVLink protocol standard (lacking RADIO_STATUS flow control). This causes an Betaflight aircraft to saturate the bandwidth of a telemetry link using soft flow control, and renders it unusable, ergo breaking support with ExpressLRS MAVLink.
For TX modules that have an onboard Backpack, the MAVLink data can be sent / received via WiFi to a PC or tablet etc. that is running the GCS software. This provides for a cable-free solution on your handset, as it removes the need for a USB cable between the TX and the GCS device.
To setup WiFi forwarding for MAVLink:
Ensure the TX Backpack is running version 1.5.0 or later
In the ELRS LUA script, select Backpack, scroll to the Telemetry option, and change the value to WiFi
If you are NOT using Home WiFi on the Backpack, a new WiFi access point will be available to connect to. Use your PC or tablet etc. to search for and connect to a WiFi network with SSID of ExpressLRS TX Backpack xxx (where xxx will be part of your UID). The WiFi password is expresslrs. Alternatively, if you ARE using Home WiFi on the Backpack, the Backpack will automatically start WiFi and connect to your router.
Power on the craft, so that the TX and RX have an active link.
On your PC or other GCS device, open your GCS software (e.g. Mission Planner) and set the connection type to UDP. Click connect, and use the default UDP port of 14550. The GCS should successfully connect to the craft and start downloading params.
Attention!
DO NOT manually put the TX Backpack into WiFi mode via WiFi Connectivity -> Enable Backpack WiFi. It's not in the steps above for a reason. When you set Telemetry into WiFi mode, the backpack automatically starts its WiFi mode, and so, there's no need to manually kick it into WiFi mode.
When set to MAVLink mode, ELRS changes the allocation of uplink and downlink frame as follows:
Uplink frames from TX to RX continue to include stick/switch data in the standard ELRS format
Uplink frames are opportunistically replaced with MAVLink data from your GCS to your aircraft, which is limited to a maximum of 50% of the link's upstream bandwidth. In general, MAVLink from GCS to the aircraft consumes very little bandwidth, due to it being mainly GCS heartbeats.
Downlink telemetry frames from RX to TX are completely replaced by MAVLink data
Your TX converts the MAVLink telemetry into standard CRSF format which is understood by EdgeTX
ELRS uses its stubborn telemetry sender system for MAVLink messages - this system retries packets which weren't delivered, keeping MAVLink link quality high over longer distances and/or with interference.
ExpressLRS provides an integration with the MFD Crossbow and mini Crossbow antenna trackers, which wirelessly forwards the telemetry from an ELRS TX module to the Crossbow in order to track the craft.
"},{"location":"software/mfd-crossbow/#how-does-it-work","title":"How does it work?","text":"
In order to forward the telemetry data (that the TX is receiving from the craft) over to the MFD Crossbow, we have leveraged the \"Backpack\" functionality that is built-in to many ELRS transmitter modules. The Backpack allows an ELRS TX module to communicate with nearby devices using ESP-NOW, which is a peer to peer WiFi-based protocol.
By flashing the MFD Crossbow Antenna Tracker Backpack firmware to a receiver, it will now listen for ESP-NOW telemetry packets, and forward them as MAVLink (via UART) to the Crossbow.
When the main ELRS firmware receives the telemetry from the craft, it sends it to the onboard TX-Backpack device, which then broadcasts it via ESP-NOW to any Backpack receivers that are flashed with your bind phrase. The receiver on the Crossbow receives these packets, and is able to track the craft.
"},{"location":"software/mfd-crossbow/#what-do-i-need","title":"What do I need?","text":"
An ELRS transmitter module with internal TX-Backpack.
A Backpack-capable receiver - this can be an ESP-based ExpressLRS receiver, or for better WiFi performance, you can also use an ESP32 dev board, etc.
An MFD Crossbow (mini or full size) tracker
ELRS LUA script installed on your handset
A GPS-equipped craft with an ELRS receiver
"},{"location":"software/mfd-crossbow/#what-will-i-need-to-do-to-set-this-up","title":"What will I need to do to set this up?","text":"
To work through this guide, you will need to:
Update the firmware on your TX and TX-Backpack (depending on your current version)
Flash an ELRS receiver, or an ESP-based dev board as a Backpack receiver
Wire the receiver to the Crossbow
Setup the Crossbow for MAVLink protocol
Setup ELRS via LUA for telemetry forwarding on the Backpack
Ensure both your transmitter module, and the embedded Backpack are up to date with the latest release versions:
For the main ELRS firmware, follow the Firmware Update Guide for detailed instructions.
For the TX-Backpack, follow the Transmitter Backpack Firmware Guide for detailed instructions.
The minimum versions to use this feature are:
Main TX firmware: 3.5.0
TX Backpack firmware: 1.5.0
"},{"location":"software/mfd-crossbow/#select-a-backpack-receiver","title":"Select a Backpack Receiver","text":"
Select a Backpack receiver to use on the Crossbow. Most ExpressLRS receivers will work for this (STM32 receiver cannot be used as they don't have WiFi).
When selecting a receiver for this integration, the quality of the WiFi antenna (not to be confused with the ELRS antenna) on the receiver is important if you want decent range (more than 5 meters). Some ELRS receivers have a chip antenna for the onboard WiFi, which helps.
The best receiver for WiFi range is an ESP32 dev board:
ESP32 Dev Board
These can be found on Amazon for cheap, and have much better WiFi range than a standard ELRS receiver.
Once you have chosen a receiver to use, you need to determine the MCU type that it uses:
ESP8285 / ESP8266
ESP32
ESP32C3
ESP32S3
If you are using an ELRS receiver, you can look this up (for supported hardware) in the targets.json file. Click the targets.json link, and then search for your receiver (e.g. RadioMaster RP1) and note the platform that it uses:
Platform for the RadioMaster RP1
If you are using an ESP32 dev board, check the listing to see if it's an ESP32, an ESP32C3 or an ESP32S3.
"},{"location":"software/mfd-crossbow/#flash-the-backpack-receiver","title":"Flash the Backpack Receiver","text":"
Open the ExpressLRS Configurator and select Backpack in the left hand menu bar.
Select the 1.5.0 or newer Backpack Release version from the Releases dropdown.
Select MFD Crossbow Antenna Tracker Backpack under Device category
Select Generic ESPxxxx Receiver (where \"ESPxxxx\" is the platform for your receiver type) in the Device dropdown
Enter your Binding Phrase and your Home WiFi SSID and Password (Optional).
Choose your Flashing Method based on your hardware (choose from the options below):
"},{"location":"software/mfd-crossbow/#flashing-via-usbuart","title":"Flashing via USB/UART","text":"
Use this method if you have an FTDI (USB to serial converter), or if you are using an ESP32 dev board connected to the PC via a USB cable.
Ensure you have the drivers installed for your FTDI, and the device shows up as a COM port in Device Manager when plugged in.
Connect the receiver to the FTDI:
FTDI to receiver wiring
Hold down the BOOT button on the receiver / dev board, or temporarily bridge the BOOT pads if the receive uses pads instead (e.g. with tweezers) as you plug the USB / FTDI into the PC.
In the Configurator, select the UART option under Flashing Method.
Ensure you have completed the steps in the \"Flash the Backpack Receiver\" section above, then click Flash on the ExpressLRS Configurator.
Wait for the process to complete and you should see the green Success notification.
"},{"location":"software/mfd-crossbow/#flashing-via-wifi","title":"Flashing via WiFi","text":"
If you are flashing an ExpressLRS receiver, you may chose to use WiFi to flash the Backpack firmware.
Power on the receiver (with no transmitter active), and wait for it to enter WiFi mode (fast flashing LED).
If you are NOT using Home WiFi, connect to the ExpressLRS RX WiFi access point (password is expresslrs) and navigate your browser to http://10.0.0.1/?force=true NOTE THE EXTRA ?force=true ON THE url
If you ARE using Home WiFi, navigate your browser to http://elrs_rx.local/?force=true NOTE THE EXTRA ?force=true ON THE url
In the Configurator, select the WIFI option under Flashing Method.
Ensure you have completed the steps in the \"Flash the Backpack Receiver\" section above, then click Build on the ExpressLRS Configurator.
Grab the built firmware.bin.gz (do NOT extract it) and drag-and-drop it into the File Upload section of the webpage. If you are using an ESP32 based device, the filename may be firmware.bin. Drag-and-drop it into the File Upload section of the webpage.
Click Update. Wait a bit (~10s) for the \"Update Success! Rebooting...\". The AP should automatically disappear and disconnect.
WiFi ESP"},{"location":"software/mfd-crossbow/#step-2-wire-the-receiver-to-the-crossbow","title":"Step 2: Wire the receiver to the Crossbow","text":"
The receiver communicates via UART with the Crossbow, using the MAVLink protocol at 115200 baud. We need to wire the tx pad on the receiver to one of the rx pins on the Crossbow:
Crossbow Wiring Diagram
The Crossbow mini can communicate via MAVLink on RX3 or RX1, depending on which port you want to use:
Crossbow Ports
If you use the L-Port on the mini, you also get a +5V and GND source for the receiver:
Example Crossbow RX Wiring"},{"location":"software/mfd-crossbow/#step-3-configure-the-crossbow-for-mavlink","title":"Step 3: Configure the Crossbow for MAVLink","text":"
Refer to the respective user manual for your model of Crossbow in order to change the UART to MAVLink protocol, at a baud rate of 115200.
For example, on the Crossbow mini, assuming you are using the L-Port:
Long press the left button to enter the menu
Short press the left button until you get to L-Baudrate and short press the right button to enter
Short press the left button until 115200 is highlighted, and short press the right button to confirm
Short press the left button until Exit is highlighted, and short press the right button to exit
Short press the left button until you get to Protocol and short press the right button to enter
Short press the left button until L:<protocol> is highlighted, and short press the right button until it reads L:MAVLink
Short press the left button until Exit is highlighted, and short press the right button to exit. Do the same again to exit the main menu.
"},{"location":"software/mfd-crossbow/#step-4-enable-backpack-telemetry-in-elrs-lua-script","title":"Step 4: Enable Backpack Telemetry in ELRS LUA Script","text":"
Access the LUA Script:
Power on your transmitter and navigate to the System menu.
Execute the ELRS LUA script.
Navigate to the Backpack Section:
Scroll to find the \"Backpack\" section within the LUA script.
Select the \"Telemetry\" option.
Enable Backpack Telemetry:
Set the \"Telemetry\" option to ESPNOW.
Exit the script.
Your TX module is now configured to broadcast telemetry to the Backpack receiver.
NOTE: Backpack telemetry is transmitted on the 2.4G WiFi band, via ESPNOW (this should have a very limited impact on any LoRa signals, as it is modulated via OFDM like a normal WiFi hotspot). Every telemetry message that your transmitter receives from the craft will be re-transmitted via ESPNOW. You may want to disable Backpack Telemetry to reduce your footprint on the RF noise floor when you aren't using it, especially if you are at something like a race day, where there is often contention on the RF spectrum. Disabling Backpack Telemetry will cause the Crossbow integration to stop working.
To disable Backpack Telemetry (only do this if you are NOT using the Crossbow integration):
Execute the ELRS LUA script.
Scroll to find the Backpack section within the LUA script.
Select the \"Telemetry\" option.
Set the \"Telemetry\" option to Off.
Exit the script.
"},{"location":"software/mfd-crossbow/#step-5-set-the-telemetry-ratio","title":"Step 5: Set the Telemetry Ratio","text":"
The Crossbow requires frequent GPS coordinate updates in order to track the craft, and to maintain the link.
The recommendation is to use a telemetry ratio of:
1:2 or 1:4 if you are using a low packet rate such as 50Hz or 100Hz
1:2 to 1:8 if you are using a higher packet rate such as 250Hz or above
Once configured, power up your GPS-equipped craft and establish the link between your ELRS Transmitter and Receiver. Ensure that GPS telemetry is being received on your handset (go to the Model menu in EdgeTX, and inspect the Telemetry page to make sure you are getting GPS coordinates).
The Crossbow status screen should now be showing DLink:100% and GPS: should reflect the number of sats acquired. Once GPS: is greater than 6, press the right button to set home, as per the user manual.
No Telemetry Data / DLink:0%: Ensure the \"Telemetry\" option is set to ESPNOW in the Backpack section of the LUA script and that the firmware is up to date. Also check that your Telemetry Ratio is set to a value that is able to provide frequent telemetry packets. As a rule of thumb, a ratio somewhere between 1:2 to about 1:16 (depending on your packet rate) will suffice. As a troubleshooting step, try 1:2 to guarantee that the tracker is getting regular updates. For more info, see Packet Rate and Telemetry Ratio and Telemetry
Binding Issues: Verify that the bind phrase is correctly set and matches between the Backpack on your transmitter and the Backpack receiver. This should also match the bind phrase that you use for regular ELRS receivers.
Interference / Poor Range: The Backpack Telemetry feature uses a point to point WiFi-based link to forward telemetry. The Backpack receiver should be within 10m of the ELRS transmitter (ideally 5m or less if using an ELRS receiver) for good WiFi signal. Some ELRS transmitters and receivers have better Backpack WiFi antennas than others, so your mileage may vary depending on your hardware. If you are experiencing drops in the link between ELRS and the tracker, try moving the two closer, or consider using an ESP32 dev board as the receiver.
ExpressLRS stores separate configurations for each CRSF Receiver number configured in OpenTX/EdgeTX. This can be used with or without model matching - for example, a single drone being used for long-range and freestyle can have its RF params switched quickly by changing the model on the radio. The value is shown highlighted below on a TX16s.
The parameters stored per-Receiver number are:
Setting Description Packet Rate The RC update frequency (500Hz, 250Hz, etc) Telem Ratio Telemetry ratio (Off, 1:128, 1:64, etc) Switch Mode Method for sending switches to the receiver Model Match Enable the model match feature (see below) Max Power Transmitter output power level Dynamic Power Enable Dynamic Power switching
All other configuration parameters are global across all Receiver numbers. Note: not \"per receiver\" but \"per Receiver number\". For details about the configurable parameters, see Lua Configuration.
ExpressLRS uses a binding phrase, which means the transmitter will connect to any receiver built with that binding phrase. Model Match is a feature which prevents a full connection if the Model Match number does not match. In this mode, the receiver will connect to the handset, but no data will be sent from the receiver to the flight controller. This allows a user to force that the model selected in OpenTX only connects to a specific receiver, for example preventing using a quad OpenTX model definition with a fixed wing model.
The terms Receiver number (set in OpenTX/EdgeTX) and Model Match number (set in the receiver) are used interchangeably here-- they are the same.
If the Model Match option is Off, then only receivers with no Model Match number (255) can be connected. If the Model Match option is On, then the Receiver number configured in the external module configuration (as shown in the image above) must match the Model Match number stored on the receiver module for the receiver and transmitter to fully connect.
The implementation follows this set of rules for handling half connections / full connections
TX ModelMatch TX Receiver ID RX Model ID Result Off Any Off Connects / Communicates as usual Off Any A Connects but does not communicate to FC On Any Off Connects but does not communicate to FC On A A Connects / Communicates as usual On B A Connects but does not communicate to FC"},{"location":"software/model-config-match/#setting-model-match-number","title":"Setting Model Match number","text":"
Set the Receiver number to be used in the OpenTX Model Setup -> External Module -> Receiver
Be sure the receiver to be assigned is connected and has a high LQ
Use the ExpressLRS Lua to set the Model Match option to \"On\"
The receiver now has its Model Match number set to match the Receiver number and will only fully connect when using this Receiver number.
Alternatively
For WiFi-enabled RX modules, use the WebUI to set the Model Match directly. \"Model Match\" must still be set to \"On\" in the Lua config.
"},{"location":"software/model-config-match/#clearing-model-match-number","title":"Clearing Model Match number","text":"
Be sure the receiver to be assigned is connected and has a high LQ
Use the ExpressLRS Lua to set the Model Match option to \"Off\"
The receiver now has its Model Match number cleared and will connect with any configuration profile which has Model Match set to \"Off\"
Alternatively
For WiFi-enabled RX modules, use the WebUI to set the Model Match to 255 to disable matching. \"Model Match\" must still be set to \"Off\" in the Lua config.
This page contains old user_defines.txt that have been removed or superseded by new defines.
New items should be added to the top of the list so the last entry here is the oldest. The order of each entry should be [code]definename[/code] followed by the original text of the documentation, ending with a separate paragraph \"REMOVED [version] [replacement or reason for removal]\".
Enable antenna-switching diversity for RX that supports it. Safe to leave it on for hardware that doesn't have diversity except for DIY builds which did not populate the RF switch.
REMOVED 3.0. Diversity is now a receiver option, changed via Lua for devices that support it in hardware.
DYNPOWER_THRESH_UP=15\nDYNPOWER_THRESH_DN=21\n
Change the RSSI thresholds used by the Dynamic Power algorithm. If the RSSI moving average is below DYNPOWER_THRESH_UP dBm from the sensitivity limit, the algorithm will increase the power output by one step. Similarly, if the RSSI is above DYNPOWER_THRESH_DN from the sensitivity limit, the power will be decreased by one step.
REMOVED 3.0. The dynamic power algorithm uses SNR which is defined per-rate so the thresholds are more complicated than 2 defines.
NO_SYNC_ON_ARM\n
no sync on arm doesn't transmit sync packets while armed. This is useful for racing as there is less time & packets wasted \ud83d\uddd1\ufe0f on sending sync packets (one packet every 5 seconds if connected). HOWEVER if you are doing serious long range \u26f0\ufe0f, keep this disabled because, in the case of a sustained failsafe, the link can not be regained while armed.
AUX1 is the channel ExpressLRS uses to detect \"ARMED\", and this feature assumes that a low value of the arm switch is disarmed, and a high value is armed. OpenTX can invert your switch if you prefer it to be mechanically inverted. It is best not to enable no sync on the arm when you are first setting up ExpressLRS as it can be a source of confusion.
REMOVED 3.0. Replaced with \"Race\" telemetry mode, which also disables sending SYNC on arm.
These features enable lower latency \ud83c\udfc3\u200d\u2642\ufe0f and offset from the OpenTX radio to the TX. The first is lower latency which should be kept enabled. The second is more experimental and can lower the offset from the radio by tuning it as close as possible to 0, but is experimental (even in 1.0) and is best left disabled.
Both require OpenTX 2.3.12 or above. To install it, you will have to use OpenTX companion application.
Deviation radio users such as those with the T8SG v2/v3 should disable this feature.
You can also use EdgeTX.
REMOVED After 2.2.0. Sync packets were always sent regardless of if this was enabled, but the sync offset would just be wrong if it wasn't defined.
USE_ESP8266_BACKPACK\n
This enables communication with the ESP Backpack for over-the-air updates (env:FrSky_TX_R9M_via_WiFi) \ud83d\udda5\ufe0f and debugging via WebSocket \ud83d\udd0d. Uncommented by default, does not need to be changed.
REMOVED 2.0 development. Replaced with USE_TX_BACKPACK.
#-DHYBRID_SWITCHES_8\n
Changes how the AUX channels are sent over the air. The default option is Normal Mode with 8x 2-position low-latency switches. Enabling HYBRID_SWITCHES_8 changes this to 1x 2-pos + 6x 7-pos + 1x 16-pos, with only the 2-position being low-latency. In Normal Mode, all switches are sent with every packet, in Hybrid Mode, only AUX1 is sent with every packet and the rest are rotated through. Note: The switch mode MUST match between the RX and TX. A detailed explanation of the differences between the two options can be found in Switch Modes, but 1. If only two position switches are needed, and they must be updated as fast as possible: Normal Mode 2. Almost everyone: Hybrid Mode (Put ARM on AUX1)
REMOVED 2.0 development, all switch modes are available via Lua configuration. HYBRID_SWITCHES_8 is always enabled / available.
#-DENABLE_TELEMETRY\n
Enable advanced telemetry support. This option must be enabled on both TX and RX. The following telemetry messages are supported:
GPS
BATTERY_SENSOR
ATTITUDE
DEVICE_INFO
FLIGHT_MODE
MSP_RESP
Note
Increase the telemetry rate with the ExpressLRS Lua script. Increase the rate until the sensor lost warnings go away. It is normal to set it up to 1:16 with 200 Hz refresh rate.
Note
It must be enabled together with HYBRID_SWITCHES_8.
REMOVED 2.0 development, ENABLE_TELEMETRY is always enabled. Advanced Telemetry will only be sent if telemetry messages are received from the FC.
-DUSE_500HZ\n
This enables 500Hz mode for 2.4 GHz RXes and TXes. The drawback is that you have to give up 25Hz mode to add 500Hz mode. It requires OpenTX 2.3.12 or Newer, EdgeTX or a Radio firmware that has CRSFShot or Mixer Sync.
REMOVED 1.0.0-RC9, this option is now always enabled and in turn, 25Hz has been dropped/removed.
-DUSE_UART2\n
This enables integration with Jye's FENIX rx5805 pro-diversity module
REMOVED Somewhere in the 1.0.0-RC cycle. Feature removed.
-DFAST_SYNC\n
An option that adds faster initial syncing, by changing how long the receiver waits for a connection in each mode while not connected. This option is now the default, but disabling it can help to sync at lower packet rates (50Hz and below).
REMOVED 1.0.0-RC2 initial sync replaced with a full FHSS period wait
#-DR9M_UNLOCK_HIGHER_POWER \n
REMOVED 1.0.0-RC1 replaced with generic -DUNLOCK_HIGHER_POWER
#-DARM_CHANNEL=AUX1\n
If you are using a different channel than the default you need to edit \ud83d\udd25 (or you may not be able to gain sync safely - the default is listed in #DARM_CHANNEL as AUX1 which is Channel 5).
NB This feature assumes that a low value of the arm switch is disarmed, and a high value is armed. If you have the arm switch reversed it will not work correctly and the link won't be established. For this reason, it may be best not to enable no sync on the arm when you are first setting up ExpressLRS as it can be a source of confusion.
REMOVED 1.0.0-RC1 AUX1 is always the arm switch now, no longer configurable
#-DLOCK_ON_50HZ\n
LOCK_ON_50HZ locks the RX at 50Hz mode from the power-up. (Only recommended for long range, and partly redundant with the previous feature.) Merged in Pull 143
REMOVED 1.0.0-RC1 not sure why this was removed
-DAUTO_WIFI_ON_BOOT\n
REMOVED 1.0.0-RC1 replaced with -DAUTO_WIFI_ON_INTERVAL=X"},{"location":"software/open-ocd/","title":"OpenOCD for STLink","text":""},{"location":"software/open-ocd/#overview","title":"Overview","text":"
If you are using Linux then you can't use the ST-LINK utility from st.com. But fortunately, you can achieve the same effect with openocd on the Linux command line. This tutorial assumes you have an STLink v2.
Install openocd from your distro's repository. For Debian/Ubuntu use: sudo apt-get install openocd
Issue the full command:
a. For R9mm/Mini openocd -f interface/stlink-v2.cfg -f target/stm32f1x.cfg -c 'init; reset halt; stm32f1x unlock 0; reset run; shutdown'
b. For Ghost Atto/Zepto openocd -f interface/stlink-v2.cfg -f target/stm32f3x.cfg -c 'init; reset halt; stm32f3x unlock 0; flash protect 0 0 last off; reset halt; exit'
Restart your device so the disabled readout protection can take effect.
Now you can proceed with flashing your receiver. This may work on other devices or it might not.
"},{"location":"software/serial-protocols/","title":"Receiver Serial Protocols","text":""},{"location":"software/serial-protocols/#description","title":"Description","text":"
ExpressLRS receivers can communicate using a variety of serial protocols:
CRSF (Crossfire) + Inverted
SBUS + Inverted
SUMD
DJI RS2 Pro (Modified SBUS with pre-configured limits)
For R9MM and R9-Mini receivers SBUS, DJI RS2 Pro and CRSF Inverted protocols will be output on the SBUS (A2) pad. This is a hardware limitation of these receivers, as they do not have software controllable inverters.
On a serial based receiver or a PWM receiver with output pins configured for serial communication (as shown below), the protocol used for serial communication can be selected from the receiver WebUI in the Serial Protocol section.
Alternately, in the Lua script, enter > Other Devices and change the value of the Protocol field.
"},{"location":"software/serial-protocols/#pwm-receiver-serial-pin-selection","title":"PWM Receiver Serial Pin Selection","text":"
A PWM receiver may also be configured to communicate via serial on two of its pins. The exact pins will vary depending on the receiver. This can be configured in either the receiver WebUI or in the receiver Lua script.
Note
Not all pins support serial communication. Only the pins that support serial will have the option in the Mode dropdown in the WebUI or the Output Mode field in the Lua script.
Start the WebUI on the receiver and go to the Model tab. From there you will be able to select Serial TX or Serial RX on an output pin that supports serial communication.
Once you've configured the output pins to allow Serial communications you will be presented with a new section, Serial Protocol, underneath the PWM Output section. In this section you can choose the serial protocol you wish to use.
When connected to the receiver with the transmitter, enter the ExpressLRS Lua script and select > Other Devices then select > Output Mapping. In that screen select the output channel/pin that supports serial (either Serial TX or RX) and set that as the output mode. Setting one automatically enables the other matching pin for serial communications.
"},{"location":"software/serial-protocols/#second-serial-interface-on-esp32-non-pwm-and-pwm-receivers","title":"Second Serial Interface on ESP32 non-PWM and PWM receivers","text":"
Starting with firmware version 3.5 an additional serial interface (Serial2) can be assigned on any featured PWM Output or exposed pins of some non-PWM receivers to run any of the available serial protocols. Both serial interfaces can be be used simultaneously. This enables setups like running a CRSF wing stabilization unit and HoTT telemetry, Tramp or SmartAudio at the same time. Serial2 can also be used to simplify the wiring of e.g. an SBUS connection on receivers which have the first serial interface on separate connectors (e.g. RM receivers with JST connectors).
"},{"location":"software/serial-protocols/#assigning-serial2-tx-vs-serial2-rx-and-serial2-tx","title":"Assigning Serial2 TX vs Serial2 RX and Serial2 TX","text":"
Most of the supported serial protocols are uni-directional (only sending data) or are bi-directional (sending and receiving data) on one single wire (half duplex). For those protocols it is only necessary to assign a TX pin. True (full duplex) serial protocols require the assignment of RX and TX. The following list shows the configuration requirements for the supported protocols:
CRSF and MAVLINK: require Serial2 TX and additionally Serial2 RX if the device returns data (e.g. telemetry)
all others: require Serial2 TX only
"},{"location":"software/serial-protocols/#configuring-serial2-on-esp32-pwm-receivers","title":"Configuring Serial2 on ESP32 PWM receivers","text":"
Serial2 is best configured using the WebUI but can also be configured using the LUA script.
Open the WebUI as described in section \"How to get to the Web UI\" and scroll down to the PWM Output table. Any PWM Output with the blue Serial2 feature tag can be used to assign Serial2 TX or Serial2 RX.
Assign Serial2 TX. If necessary for the serial protocol you intend to run assign Serial2 RX also. In this example we want to run a protocol that only requires Serial2 TX (see above section). Choose Serial2 TX using the Mode drop down list on the desired PWM Output.
Scroll down a little further. A new line named Serial2 protocol is now available to choose the desired protocol.
Save the configuration using the SAVE button at the bottom of the page.
Restart the receiver and connect your serial device to the configured PWM Output.
"},{"location":"software/serial-protocols/#configuring-serial2-on-esp32-non-pwm-receivers","title":"Configuring Serial2 on ESP32 non-PWM receivers","text":"
Some non-PWM receivers like the RadioMaster RP4TD have spare pins exposed. The pins are configured for Serial2 by default.
Serial2 protocol selection is best configured using the WebUI but can also be configured using the LUA script.
Open the WebUI as described in section \"How to get to the Web UI\". Scroll down to line Serial2 protocol and choose the desired.
Save the configuration using the SAVE button at the bottom of the page.
Restart the receiver and connect your serial device to the configured PWM Output.
SUMD is the Graupner HoTT bus protocol used to transmit multiple channel data over a single serial line. It transports up to 16 full res channels at a rate of 100Hz and is mainly used to provide digital channel data to Flybarless Control Systems for helicopters and older Flight Controllers.
As already stated many times in this manual, ExpressLRS expects AUX1 (channel 5) to control the arm state. This may lead to a conflict using serial protocols like SUMD in conjunction with devices having fixed channel assignments. To circumvent the problem, SUMD implements a channel remapping by swapping channels 5 and 8 in its serial output:
This opens the possibility to assign a linear output channel order for channels 1 to 7 using an appropriate OpenTX/EdgeTX mixer setup.
Example: Microbeast flybarless controller without RPM governor. (Follow the Microbeast manual to setup the single line receiver mode.)
Microbeast expected channel order for SRXL/SUMD:
Required OpenTX/EdgeTX mixer setup to satisfy the Microbeast expected channel order:
"},{"location":"software/serial-protocols/#dji-rs2-pro-notes","title":"DJI RS2 Pro Notes","text":"
Here's a few things to be aware of when using this Receiver Mode:
The ELRS TX should be set to 100Hz Full, and Switch Mode to 8ch.
Channels 1, 2, 4 are Pan, Tilt, Roll
Aux1/CH5 is unused but should be set as an arm switch and left in the unarmed position (Low).
Aux2/CH6 should be a 3 way switch. From the switch center position to high/low, Rec start/stop or photos can be captured.
Aux3/CH7 should be a 3 way switch. Each of the 3 positions corresponds to Modes 1, 2 or 3.
Aux4/CH8 should be a 3 way switch. From the switch center position to high/low, Selfie or Recenter can be activated.
Rec, photos, recenter, and selfies are done by toggling the switch from the center position to high/low, and back to center in a quick 0.4s movement. With some ETX and mixer magic these functions can be improved and mapped to buttons etc.
ETX Outputs for the channels should be -100 to 100.
The HoTT Telemetry Serial Protocol allows to connect multiple Graupner HoTT Telemetry devices and intends to support the growing community of ELRS enthusiasts flying fixed wing or helicopter models by providing access to commercially available external telemetry devices without the use of flight controllers or DIY data hubs.
A typical use case for an electric fixed wing model could make use of a the electric Swiss knife SM Unisens-E to downlink flight battery data like voltage, current, consumed capacity and flight data like altitude, vertical velocity while an electric glider pilot could choose a YGE or Graupner Telemetry ESC to downlink flight battery data and a GPS/Vario to downlink flight data like GPS position, GPS speed, GPS (MSL) altitude together with barometric vertical velocity and barometric altitude.
HoTT Telemetry example setup - GPS/Vario and Voltage Module connected to a RadioMaster ER6 receiver:
Tested receivers:
ESP8285 platform
BetaFPV Nano RX 2.4 GHz
Happymodel EPW6
ESP32 platform
BetaFPV SuperD 900MHz
BetaFPV SuperP 14ch
RM ER6 (G and V variants too)
RM ER8 (G and V variants too)
Tested HoTT Telemetry devices (OEM and 3rd party):
Graupner 33600 GPS/Vario
Graupner 336001 Vario
Graupner 33631 Voltage Module
Graupner S3046 ESC +T50 (all other +T ESCs will work too)
SM GPSLogger 3
SM Unisens-E
SM Microvario (with TEK support)
YGE 35LVT. ESC (all other YGE Telemetry ESCs will work too)
VSpeak Vario Pro
X-Vario 2
HoTT Telemetry protocol is running on a multi-device capable single wire half duplex bus and requires a bus master to orchestrate the communication between the bus master and the connected devices. The ELRS receiver acts as the bus master communicating with the devices. The bus master receives selected HoTT Telemetry data to be forward to the ELRS CRSF protocol based over-the-air telemetry down link. The list of additional telemetry sensors provided shows the telemetry sensors available for EdgeTX depending on the HoTT Telemetry devices connected to the HoTT Telemetry bus:
Baro altitude (AGL)
Baro vertical speed (Vario)
GPS latitude
GPS longitude
GPS groundspeed
GPS heading
GPS altitude (MSL)
GPS number of satellites
GPS distance - possible if added as EdgeTX calculated sensor
GPS traveled distance - possible with LUA script
Batt voltage
Batt current
Batt capacity
Batt remaining
Requirements for using HoTT Telemetry:
The Serial port must be enabled. The Serial port is enabled by default on some receivers, e.g. RadioMaster ER6x/ER8x receivers. On other receivers the Serial port must be enabled using the WebUI or LUA script, see above section WebUI and Lua Script.
The Serial Protocol must be set to HoTT Telemetry, see above section WebUI and Lua Script.
On some receivers adapter cables are required.
Adapter cables
If an adapter cable is required depends on the platform the receiver is based on (ESP8285 or ESP32) and the way the serial port is designed on the specific receiver. RadioMaster uses a dedicated JST connector, on other receivers including the BetaFPV SuperP one or two of the PWM servo connectors are used.
ESP32 based receivers with Serial on dedicated PWM servo connectors like the BetaFPV SuperP 14ch:
No adapter cable is required. HoTT sensors can be directly connected to the PWM servo connector of any of the PWM pins configured for Serial2 TX (see above section).
ESP32 based receivers with Serial on the JST connector.
RadioMaster ER6x/ER8x need a JST to JR adapter. The JST pigtail RadioMaster included in the package can be used.
Caveat: the SuperP 14ch also has a JST connector but it can't be used as a Serial port, see the first ESP32 category.
Alternatively use any of the PWM pins configured for Serial2 (see above section 2).
ESP8285 based receivers:
Require a Schottky diode between Serial RX and Serial TX:
Example realization of an adapter cable with diode for ESP8285 non-PWM receivers like the BetaFPV Nano RX:
Example adapter cable setup for ESP8285 PWM receivers like the Happymodel EPW6:
SmartAudio/Tramp are loosely-defined protocols with edge cases, misinterpretations, and shoddy cloned implementations. ExpressLRS does not intend to support the vast majority of VTXes. SmartAudio was tested on a TBS Unify Pro32 HV, and Tramp was tested on an ImmersionRC Tramp HV, and both were tested with OpenVTX. It may work on other hardware, but it's not guaranteed and changes won't be made to accommodate broken implementations.
NOTE
ESP32 is the only supported platform for SmartAudio/Tramp at this time; ESP8266 RXes lack the necessary UART functionality to do this the right way, and are not supported.
ExpressLRS now has support for controlling an external video transmitter through SmartAudio/Tramp protocols. This is a powerful feature for PWM+FPV users who don't have a flight controller to manage their VTX settings.
Using serial VTX control requires at least a secondary UART TX pin assigned on your ESP32-based receiver, such as the RadioMaster RP4TD or the BetaFPV SuperP. You may need to assign a pin as Serial TX using the Lua script \"Other devices\" section, or using the RX Web UI if one is not already set up.
Ensure both your transmitter module and your receiver are up to date with the latest release versions; follow the Firmware Update Guide for detailed instructions.
The minimum version to use this feature is: - Receiver firmware: 3.5.0
"},{"location":"software/serialvtx/#setting-up-serial-vtx-control-via-lua","title":"Setting up serial VTX control (via Lua)","text":"
Open the ExpressLRS LUA script, scroll to the bottom and select Other Devices, then select your receiver.
Select Output Map, and assign an available Output Ch as Serial2 TX.
Select \"BACK\" to return to the main RX menu
Select Protocol2 and set it to SmartAudio or Tramp. This configures the RX to output SmartAudio or Tramp on the previously-selected pin.
Wire the selected Output Ch to your video transmitter's SmartAudio or Tramp pin
Select \"BACK\" to return to the main Lua menu
You can now use the ExpressLRS VTX Administrator function to control your VTX
ExpressLRS does not intend to support full VTX control, and especially not \"VTX Table\" functionality. To that end, here are some of the implementation decisions we've made in supporting SmartAudio/Tramp
Only bands A/B/E/F/R/L and channels 1-8 are supported. Custom frequencies, and non-5.8GHz VTXes don't work, and we're not interested in making them work.
These protocols support methods to confirm the settings on the VTX and update them on the controlling device (flight controller, RX). Our implementation is one-way only.
"},{"location":"software/serialvtx/#smartaudio-power-levels","title":"SmartAudio power levels","text":"
SmartAudio has 3 different ways to specify a power level: a raw DAC output value, a power output in dBm, or a \"power level\" starting from 0. We've chosen to implement the third option.
Here's the result on a Unify Pro32 HV
VTX Administrator \"Pwr Lvl\" Output power in dBm Output power in mW 1 14 25 2 23 200 3 27 500 4 29 800"},{"location":"software/serialvtx/#smartaudio-pit-mode","title":"SmartAudio pit mode","text":"
SmartAudio once again has 3 different ways to do something: pit mode is able to be specified as \"in-range\", \"out-range\", both at the same time, and a running or not flag (which is documented backwards of how it actually works). It's difficult to determine the \"right\" way of entering/exiting pitmode, and it never behaved how I expected it to in testing. YMMV.
"},{"location":"software/serialvtx/#tramp-power-levels","title":"Tramp power levels","text":"
ImmersionRC Tramp takes a completely different approach to power levels; just send the output power you want in mW. Unfortunately this doesn't match our \"Pwr Lvl\" approach from VTX Administrator, so we had to arbitrarily determine some output power levels. ImmersionRC hardware will only support the first 5; the last 3 are \"YMMV\" options for \"other\" video transmitters that support Tramp protocol.
VTX Administrator \"Pwr Lvl\" Output power in mW 1 10 2 25 3 200 4 400 5 600 6 1000 (not supported by ImmersionRC Tramp) 7 1600 (not supported by ImmersionRC Tramp) 8 3000 (not supported by ImmersionRC Tramp)"},{"location":"software/stlink-fix/","title":"PIO STLink Fix","text":""},{"location":"software/stlink-fix/#overview","title":"Overview","text":"
PlatformIO has an older version of STLink. It is unable to communicate with the STM32L MCUs on some RXs.
Paste files from \"st-link utility\" folder into \"stlink\" folder in your user PIO location C:\\Users\\username\\ .platformio\\packages\\tool-stm32duino
Put your arm switch on AUX1, and set it as ~1000 is disarmed, ~2000 is armed.
"},{"location":"software/switch-config/#summary-of-switch-configuration-modes","title":"Summary of Switch Configuration Modes","text":"
This table summarizes the switch configuration modes, available channel switch positions and resolutions, channel update rate, and packet rate as it applies to each channel or flight controller auxiliary channel (Aux). Below the table are descriptions for each option.
Channel Flight Controller Hybrid Wide Full Res 8ch Full Res 16ch Rate/2 Full Res 12ch Mixed 1 Sticks NormalRange NormalRange CRSF ExtLimits CRSF ExtLimitsH CRSF ExtLimits 2 Sticks NormalRange NormalRange CRSF ExtLimits CRSF ExtLimitsH CRSF ExtLimits 3 Sticks NormalRange NormalRange CRSF ExtLimits CRSF ExtLimitsH CRSF ExtLimits 4 Sticks NormalRange NormalRange CRSF ExtLimits CRSF ExtLimitsH CRSF ExtLimits 5 Aux 1 2-posArm 2-posArm 2-posArm CRSF ExtLimitsHArm 2-posArm 6 Aux 2 6-posRR 64/128-posRR CRSF ExtLimits CRSF ExtLimitsH CRSF ExtLimitsH 7 Aux 3 6-posRR 64/128-posRR CRSF ExtLimits CRSF ExtLimitsH CRSF ExtLimitsH 8 Aux 4 6-posRR 64/128-posRR CRSF ExtLimits CRSF ExtLimitsH CRSF ExtLimitsH 9 Aux 5 6-posRR 64/128-posRR CRSF ExtLimits CRSF ExtLimitsH CRSF ExtLimitsH 10 Aux 6 6-posRR 64/128-posRR - CRSF ExtLimitsH CRSF ExtLimitsH 11 Aux 7 6-posRR 64/128-posRR - CRSF ExtLimitsH CRSF ExtLimitsH 12 Aux 8 16-posRR 64/128-posRR - CRSF ExtLimitsH CRSF ExtLimitsH 13 Aux 9 - - - CRSF ExtLimitsH CRSF ExtLimitsH 14 Aux 10 - - - CRSF ExtLimitsH - 15 Aux 11 - - - CRSF ExtLimitsH - 16 Aux 12 - - - CRSF ExtLimitsH - PacketRates 50 thruF1000 50 thruF1000 100&333Only 100&333Only 100&333Only"},{"location":"software/switch-config/#switch-position-channel-resolution","title":"Switch Position / Channel Resolution","text":"Label Description Normal Range 10-bit or 1024 positions mapped to PWM 988us to 2012us (1 bit = 1us) CRSF Ext Limits 10-bit or 1024 positions mapped to PWM 885us to 2115us (1 bit = 1.23046875us) 64 / 128-pos The bit depth is dependent on the selected telemetry ratio. For a telemetry ratio of 1:2 and 1:4 these channels are 6-bit/64 pos. For all other ratios, these channels are 7-bit/128 pos. The 7-bit/128 positions is 12.5% the resolution of 10-bit, and 6-bit/64 positions is 6.25% the resolution of 10-bit. This may not be enough resolution for a head tracker but definitely enough for flight modes, flaps, gear, etc. 16-pos 4-bit which is good for flight modes, flaps, gear, etc. 6-pos 3-bit which is good for flight modes, flaps, gear, etc. 2-pos 1-bit for Arm, ~1000us is the disarmed state and ~2000us is the armed state (see the explanations below of why the armed state is very important for safety and performance)
WARNING
Put your arm switch on AUX1, and set it as ~1000 is disarmed, ~2000 is armed.
Note
If using a receiver with PWM outputs and you would like to use the PWM output 5 on the receiver for a servo, gear, etc. Go into the WiFi interface of the receiver and map any of the other channels to PWM Output 5. Please always still use AUX1 for the 2-pos Arm switch.
"},{"location":"software/switch-config/#channel-update-rate-versus-packet-rate","title":"Channel Update Rate versus Packet Rate","text":"Label Description Bolded This channel will be included in every packet at the selected packet rate (So a 150Hz Packet Rate = 150Hz Channel Update Rate) H Half Rate Half of the channels are included in each packet - Rate/2 (So a 100Hz Packet Rate cut in half = 50Hz Channel Update Rate) RR Round Robin These channels wait their turn to be sent in a packet (So a 150Hz Packet Rate sends a channel every 7th packet = 22Hz Channel Update Rate) 50 thruF1000 The Hybrid and Wide switch modes are only available on packet rates of 50Hz, 150Hz, 250Hz, 500Hz, D250Hz, D500Hz, F500Hz, and F1000Hz 100&333Only The Full Resolution switch modes (8ch, 16ch Rate/2, 12ch Mixed) are only available on packet rates of 100Hz Full and 333Hz Full"},{"location":"software/switch-config/#detailed-description-of-switch-configuration-modes","title":"Detailed Description of Switch Configuration Modes","text":"
Note
The switch configuration mode can only be changed when a receiver is not connected to the transmitter and when the transmitter is not armed. The mode is changed using the LUA Configuration in EdgeTX / OpenTX or using buttons, joystick, screen, etc. on the actual transmitter itself.
ExpressLRS has a few options for how switches are transmitted; Hybrid, Wide, Full Res 8ch, Full Res 16ch Rate/2, Full Res 12ch Mixed.
"},{"location":"software/switch-config/#hybrid-and-wide-switch-configuration-modes","title":"Hybrid and Wide Switch Configuration Modes","text":"
These two switch modes are only available when packet rates of 50Hz, 150Hz, 250Hz, 500Hz, D250Hz, D500Hz, F500Hz, and F1000Hz and selected.
The stick inputs (Chan 1-4) are sent with every packet at the normal range resolution of 10-bit or 1024 positions mapped to a PWM of 988us to 2012us (1 bit = 1us) which corresponds to -100% and 100% in EdgeTX / OpenTX.
The first switch (Chan 5 / AUX 1) is sent with every packet. PUT YOUR ARM ON THIS CHANNEL / AUX 1. It is used to enable safeguards and performance settings in the software and hardware. See the FAQ below. This switch is 1-bit / 2-position and is mapped to a PWM of ~1000us for disarmed and ~2000us for armed.
For the remaining 7 switches (Chan 6 thru 12 / AUX 2 thru AUX 8), only one switch is sent with each packet and is rotated on each packet (Round Robin).
In Hybrid mode, AUX2-AUX7 / Chan6-11 are 3-bit and can be used as either 2-position, 3-position, or 6-position switches or selector buttons. These are mapped to a PWM of 1000us to 2000us.
2-posSwitch 3-posSwitch 6-posSwitch Approx. ChannelInput PWM (us) ChannelOutput (us) ArduPilot Mode 1 1 1 988 1000 Mode1 (up position for 2-pos / 3-pos) 2 1192 1275 Mode2 3 1398 1425 Mode3 2 - 1500 1500 Mode4 (center position in 3-pos) 4 1602 1575 Mode4 5 1807 1725 Mode5 2 3 6 2012 2000 Mode6 (down position for 2-pos / 3-pos)
In Hybrid mode, AUX8 / Chan12 is 4-bit / 16-position and is mapped to the PWM table below. It takes 7 packets to send the complete set of switches before cycling back to AUX2. You can stack all your modes in here, Bardwell style, or get some low-res camera pan action (180 degrees / 16 = 11ish deg per position which isn't terrible). Clever math-heads might note that there's no \"center position\" (1500us) in a 16-position switch, so using AUX8 with a 3-position switch means it will come out as 1533 at the flight controller.
In Wide mode, AUX2-AUX8 / Chan6-12 are 6-bit / 64-position for telemetry ratios of 1:2 and 1:4. For all other telemetry ratios, these 7 switches are 7-bit / 128-position. It takes 8 packets to send the complete set of switches before cycling back to AUX2 (one more than Hybrid). Wide uses the 8th slot to transmit extra data to the receiver, including the current transmitter power. This is the only switch mode which can show the transmitter power TPwr on the flight controller's OSD. These behave more like traditional channels although with lower precision. You can tell you're operating in Wide mode when a switch in the middle position shows up as 1503 instead of 1500.
If using ArduPilot in Wide mode you will see that the channel outputs don't line up very well with the standard -100% (988us) to +100% (2012us) output range in EdgeTX / OpenTX when using a 6-position selector as input. Both the first two and the last two positions get binned into Mode 1 and Mode 6 respectively. To get the full 6 ArduPilot modes, go to the Outputs page on the OpenTX model setup and set the min / max for the channels to -75% / +75%.
These switch modes come in three flavors based on the number of output channels you would like and are only available on packet rates of 100Hz Full and 333Hz Full.
8ch - Channels 1 to 4 and Channels 6 to 9 are sent 10-bit, at the selected Packet Rate, along with Channel 5 (AUX1) in 1-bit (2-position) for Arming.
16ch Rate/2 - All the Channels are sent 10-bit but at half rate.
12ch Mixed - Channels 1 to 4 are sent 10-bit with Channel 5 (AUX1) in 1-bit (2-position) for Arming at the selected Packet Rate. Channels 6 to 13 are then sent at 10-bit but at half rate.
All of these 10-bit or 1024 positions are mapped to PWM 885us to 2115us (1 bit = 1.23046875us) in what is called \"CRSF Extended Limits\"
"},{"location":"software/switch-config/#faq","title":"FAQ","text":""},{"location":"software/switch-config/#why-do-you-keep-saying-put-arm-on-aux1","title":"Why do you keep saying \"put arm on AUX1\"?","text":"Why do you keep saying \"put arm on AUX1\"?
For safety and performance reasons.
SAFETY
AUX1 is sent with every packet going out, this is the most reliable way to be able to tell your model to disarm. If your arm switch is on another aux channel, it may be several packets before that switch is transmitted, and there's no guarantee that the RX will actually receive that packet. There's a non-trivial chance your model may not ever disarm if the link quality is low and it just so happens that the packet containing the arm switch is getting missed every time. Forcing the arm switch into every packet on AUX1 means that if any packet is received by ExpressLRS, it will disarm your model, not just a less than 1-in-7 chance.
It also protects against unintentional disarms caused by a corrupt packet changing the value of the arm switch to disarmed. Betaflight requires that 4x \"disarm\" commands are received before disarming to guard against this possibility. With arm on AUX1, a single corrupt packet can not disarm your model. With arm on AUX2-8, the one corrupt switch value will be sent 6 times before the value is refreshed, but the flight controller would have already disarmed by that point.
Your transmitter and receiver also act differently when \u201carmed\u201d and when \u201cdisarmed\u201d. When disarmed, the transmitter and receiver are free to adjust their communication in order to make the LUA and other configuration operations more responsive. When \"disarmed\", everything will appear to be working appropriately but none of the safeguards will be in place and performance will not be what you expect.
When IsArmed is enabled, these safeguards are applied:
All \"Button\" inputs are disabled
All \"Joystick\" (5-way buttons) are disabled
Bump to Share is disabled
VTX Admin is disabled
Integrated VTX channel change is disabled
PERFORMANCE
When IsArmed is enabled, these performance features are activated:
Dynamic Power is fully enabled
Race telemetry mode turns telemetry off
Some thermal-based fan controls are enabled
Arming is an extremely important part of the performance of the control link. Please use Aux 1 / Chan 5 as indicated. Also keep in mind that for ExpressLRS, ~1000us is the disarmed state and ~2000us is the armed state.
"},{"location":"software/switch-config/#i-use-a-3-pos-switch-for-arm-this-software-is-unusable","title":"I use a 3-pos switch for arm, this software is unusable?","text":"I use a 3-pos switch for arm, this software is unusable?
Good news, you can still use a 3-position switch to arm! However, you will need to adjust the model input / mixer settings for AUX1 in EdgeTX / OpenTX to remap the switch to be 2-position / on-off switch. If your 3-position arm switch had a second function as well, such as enabling Blackbox, just use one of the other channels to send the same switch on a second channel using the model input / mixer settings EdgeTX / OpenTX.
"},{"location":"software/switch-config/#what-about-normal-one-bit-switch-mode","title":"What about \"Normal\" one bit switch mode?","text":"What about \"Normal\" one bit switch mode?
In version 1.0 of ExpressLRS, there was also a switch mode called \"Normal\" where there were eight 1-position switches sent in every packet. This mode was removed in version 2.0 due to its unpopularity and the flash space was used for other features. Please use Hybrid or Wide modes and all of the high performance packet rates.
"},{"location":"software/switch-config/#every-time-i-change-switch-mode-in-lua-it-changes-back-is-my-transmitter-broken","title":"Every time I change switch mode in Lua, it changes back! Is my transmitter broken?","text":"Every time I change switch mode in Lua, it changes back! Is my transmitter broken?
If the Lua loads then you know its communicating with your transmitter. However, the switch mode can only be changed when a receiver is not connected and makes it appear as if the changes are not saving. This is done to ensure consistency between the RX and TX interpretation of the switch data being actively transmitted. This is a safeguard. Power down your receiver, wait for the \"Telemetry Lost\" callout, and the switch mode change will stick / save. The receiver will talk to the transmitted when it is powered up to handshake on the new settings.
"},{"location":"software/teamracing/","title":"Team Racing","text":""},{"location":"software/teamracing/#what-is-team-racing","title":"What is Team Racing?","text":"
Team Racing is a receiver feature that allows multiple models to be connected to one transmitter at the same time. Each model is assigned to a different switch position and will select that model to control. Any non-selected model is failsafed and will have its telemetry disabled.
The purpose of the receiver selection is to allow a downed model (which is physically unreachable mid-race) to be deactivated and allow the pilot to take control of another model using the same controller. In a default setup, if the pilot plugged in a new model and armed, both models will respond and arm which is incredibly undesirable. This would be used in a Team Race event such as MultiGP Mayhem.
0 or 1 active transmitters with a distinct binding phrase. \"One pilot operating their transmitter\"
Multiple receivers bound to that transmitter's binding phrase, all powered at the same time.
Pilot has the ability to direct which receiver is currently \"active\" including:
Sending channels data and LinkStats information to flight controller
Transmitting telemetry to the TX
Updating servo positions
"},{"location":"software/teamracing/#team-racing-does-not","title":"Team Racing does NOT","text":"
Allow multiple pilots (more than 1 active transmitter) to control a model. There is only one binding phrase and ExpressLRS rule is one active transmitter per binding phrase.
Support different packet rates / switch modes per model. All models use the same packet parameters.
Encourage pilots to have multiple active models flying at once, e.g. launching a model and putting it into autopilot, then switching to a second model to chase it by effectively failsafing the first via TeamRace switch.
Two configuration parameters are present in the Receiver Lua (ExpressLRS Lua -> Other Devices -> (select receiver item) -> Team Race). See ExpressLRS Lua script
Channel - The channel that is checked to determine the currently selected model.
Position - Which position of the TeamRace Channel activates this model.
No flight controller setup is needed. The receiver selection is completely transparent to the flight controller-- the channels will stop updating and it should failsafe as normal. NOTE Servos will wait 1s before switching to failsafe positions, which may be longer than normal (LQ dropping to 0 is usually faster than the 1s hard timeout).
Team Racing works in Hybrid and Wide switch mode as well as FullRes packet modes. When the receiver is in a TeamRace Mismatch mode, the LED will display the \"Model Mismatch\" blink pattern / color. The Lua will not display Model Mismatch, as telemetry will be disabled.
No VTX Admin / Control is performed when deselecting a model at this time due to the variety of ways a user might configure their VTX to go into Pit Mode: ExpressLRS VTX Admin Pit Switch, Betaflight PitMode mode switch, or USER1/USER2/pinio_box power cut. The user must still configure their method to disable the deselected VTX using the Team Race channel. For CRSF mode serial output, ExpressLRS guarantees at least one packet with the proper deselected channel position will be sent to the flight controller to handle this.
We recommend using VSCode's built-in Git client, as it requires the least 3rd party software \ud83e\udd16.
\ud83d\udd3d Download a copy of git (this is also needed for PlatformIO)
Install git, click yes to the default options (there are a LOT \ud83d\udcaf)
Important
Make sure you select this option during installation, it adds git to PATH which is necessary for VSCode cloning (the next step).
"},{"location":"software/toolchain-install/#cloning-the-repo","title":"Cloning the Repo","text":"
In VSCode open the command palette (using Cmd+Shift+P on MacOS or Ctrl+Shift+P on Windows)
Enter Git: Clone
Click that! \ud83d\udc48
Then, enter ExpressLRS Repo URL -> https://github.com/ExpressLRS/ExpressLRS.git \ud83d\udcbb
Choose a folder for ExpressLRS. \ud83d\udcc2
"},{"location":"software/toolchain-install/#selecting-the-latest-release","title":"Selecting the Latest Release","text":"
Before we can do any building, you need to select a release build of ELRS. For example, release 0.1.0-RC1. In Visual Studio Code select that tag. The location of the selector is shown below. \ud83d\uddb1\ufe0f
Click the selector, and then type in the name of the tag, in this case 0.1.0-RC1.
Once you had the time of your life setting up your toolchain \ud83e\uddf0 you are ready to Flash \u26a1 ExpressLRS to supported hardware.
"},{"location":"software/toolchain-install/#building-targets-using-platformio","title":"Building Targets using PlatformIO","text":"
\ud83d\udcc2 When you first launch Visual Studio Code, you should see the PlatformIO Home Page in a tab. Click the Open Project button. Navigate to the ExpressLRS repo directory. Navigate into the src folder (i.e. ./ExpressLRS/src/). Finally, press the Open button.
\u270f\ufe0f Edit the file ./src/user_defines.txt to define user specific variables. \ud83d\ude08 Please make sure you edit the file according to your needs!
\ud83d\udcca In the toolbar on the left, click the PlatformIO icon, which will show the list of tasks. Now, select Project Tasks, expand your desired target and select Build/Upload (depending on the method). You should see the result in the terminal.
\ud83d\ude43 If something went wrong - please check the Terminal, too. It will contain at least a hint of what the issue is. Please ask the community for further help\ud83e\uddd1\u200d\ud83d\udd27!
"},{"location":"software/toolchain-install/#updating-your-local-repo","title":"Updating your Local Repo","text":"
You've cloned the repository and are now wondering how to get new updates down the line. Then this document is meant for you! Here's a primer on how to keep your local copy of the repository up-to-date.
"},{"location":"software/toolchain-install/#method-1-the-clean-way-fetch-reset","title":"Method 1: The Clean Way - Fetch & Reset","text":"
Probably the easiest and least troublesome method, however, it'll overwrite any changes you've made to your local copy.
Open the terminal
You can either straight up open bash/cmd and navigate to your project folder or open an integrated terminal in VSCode:
Open the command palette (using Cmd+Shift+P on MacOS or Ctrl+Shift+P on Windows)
Enter: Create New Integrated Terminal
In the terminal, type: git fetch -pu && git reset --hard origin/master
This will get you the latest version and destroy any local changes you've made.
"},{"location":"software/toolchain-install/#method-2-the-lazy-way-commit-pull-merge","title":"Method 2: The lazy way - Commit, Pull & Merge","text":"
The advantage this method has over the first method is that all your changes to the user_defines.txt (or any other file, for that matter) will get merged with any new updates. There's a possibility that, if changes are too big, you could end up with a merge conflict. If that doesn't appeal to you, stick to the first method.
Commit your changes to your local repository
In VSCode open the command palette (using Cmd+Shift+P on MacOS or Ctrl+Shift+P on Windows)
Enter: Git: Commit
VSCode will tell you that there are unstaged changes and ask if you want to add them to the commit. Confirm this! This will just commit your changes to the user_defines.txt to your local repository. No worries, you're not overwriting anything on GitHub! :octocat:
Open the terminal, how-to is detailed in method 1
In the terminal, type: git pull -f
This will pull a new revision of the remote repository to your local repository and automatically merge it with your changes.
"},{"location":"software/toolchain-install/#avoid-user_definestxt-ending-up-in-a-commit-or-getting-overwritten","title":"Avoid user_defines.txt ending up in a commit or getting overwritten","text":"
Don't change user_defines.txt for setting up your local configuration. Instead create a new text file `super_defines.txt in the same location as user_defines.txt to define your local build configuration. super_defines.txt will be git-ignored and will not be part of any commits and won't be overwritten by pulls. Example super_defines.txt:
With more features being added consistently, ./src/user_defines.txt has gotten complicated \ud83e\udd37\u200d\u2642\ufe0f. So we will break it down! \ud83d\udd28
Info
This is the full list of currently supported User Defines and would help you should you intend to compile the firmware using the Toolchain or manual mode on the ExpressLRS Configurator.
This step is simple but important. Both the TX and RX NEED to have the same binding phrase or ExpressLRS WILL NOT WORK. Anyone using the same binding phrase as you will be able to control your model, so be unique. Set something memorable, and limit to alphanumeric phrases conforming to the Latin alphabet*.
Receivers flashed with firmware builds that do not have binding phrases enabled will support and require the traditional binding method. \ud83d\udcdc For ESP/ESP32 hardware, this value can also be changed through the WebUI.
This feature can, but should not be used as a model match feature (to lock a single specific transmitter to a single specific receiver). For that use, the Model Match option.
* This phrase gets md5 hashed and gets built into the binary you will be flashing.
This is a relatively simple one - enable whatever regulatory domain you are in. EU 868 \ud83c\uddea\ud83c\uddfa is compliant to the frequency but is not LBT compliant \ud83d\udc42 . Every other band is near compliant \ud83d\udc7f but may not be fully compliant for your regulatory domain.
TLM_REPORT_INTERVAL_MS=240LU\n
The TX module sends the LinkStats telemetry to the OpenTX frequently to let the handset know the connection is still active and reduce \"Telemetry Lost\" warnings. Reducing this value may reduce warnings caused by handset errors at higher baud rates. This only affects the connection from the TX module to the handset and does not do anything with the telemetry connection from the receiver. The default value is 240LU. When changing this value, suffix your milliseconds value with LU. For example, to specify a 100ms LinkStats update rate, you have to enter it like this: 100LU."},{"location":"software/user-defines/#output-power-limit","title":"Output Power Limit","text":"
UNLOCK_HIGHER_POWER \n
By default the max power of the hardware is limited to what it can safely output without extra cooling. Some hardware supports increasing the power by enabling the following option. Check the supported hardware page to see if this is available and what cooling modifications can be made. By enabling this, you are risking permanent damage to your hardware, sometimes even when you add extra cooling. For example, R9M modules will burn out without cooling."},{"location":"software/user-defines/#performance-options","title":"Performance Options","text":"
LOCK_ON_FIRST_CONNECTION\n
RF Mode Locking - When the RX is waiting for a connection, it cycles through all available rates waiting for a connection on each one. By default, ExpressLRS will go back to this mode after a disconnect (failsafe). If LOCK_ON_FIRST_CONNECTION is used, ELRS will not cycle after a disconnect, but instead, just stay at whatever rate the last connection was. This makes connection re-establishment quick, because the RX is always listening at the proper rate. This is generally what everyone wants, but there is utility in being able to switch the TX to the lowest rate to get more range to re-establish a link with a downed model, which can't happen if the RX is locked at the previous rate.
When cycling through the rates, the RX starts with the fastest packet rate and works down to the slowest, then repeats. It waits PACKET_INTERVAL * PACKS_PER_HOP * HOP_COUNT * 1.1 at each rate. Example: 4ms * 4 * 80 * 1.1 = 1.408s for 250Hz. The duration is extended 10x if a valid packet is received during that time. Even with LOCK_ON_FIRST_CONNECTION, the rate can be changed by changing the TX rate using ELRS.lua while connected, or by power cycling the RX.
FAN_MIN_RUNTIME=30\n
For TX devices with fans, FAN_MIN_RUNTIME keeps the fan running even after the power level has dropped below the configured Fan Threshold. This prevents the fan from turning on and off every few seconds if the power level is constantly changing. The default is 30 seconds if not defined, the value can be 0-254. There is always a short delay before the fan is activated, which can not be disabled. "},{"location":"software/user-defines/#compatibility-options","title":"Compatibility Options","text":"
UART_INVERTED\n
This only works with ESP32 based TXes (will not work with modules without built-in inversion/uninversion), but enables compatibility with radios that output inverted CRSF, such as the FrSky QX7, TBS Tango 2, RadioMaster TX16S. You want to keep this enabled in most cases. If your radio is T8SG V2 or you use Deviation firmware turn this setting off.
RCVR_INVERT_TX\n
This only works with ESP8266/ESP8285 based RXes. Invert the TX pin in the receiver code to allow an inverted RX pin on the flight controller to be used (usually labeled SBUS input or RXI). Inverted CRSF output. RX pin (telemetry) is unaffected. Update via_BetaflightPassthrough will not work, only via_Wifi. Note that just because this description includes the word SBUS, it doesn't mean the RX will output SBUS. It is still a CRSF protocol, only inverted, so CRSF should still be the receiver protocol selected in the flight controller software.
RCVR_UART_BAUD=420000\n
Use a custom baud rate on the receiver instead of the default 420000 baud. This is useful for a KISS v1 FC (which runs at 400000) or any other oddball baud, like 115200 for interfacing with an Arduino.
USE_R9MM_R9MINI_SBUS\n
This does not turn on SBUS protocol it simply changes the pin used for communication from those two side pins (A9 and A10) to use the pin labeled \"SBUS\" on the RX, which is inverted. This is useful for F4 FCs which only have an inverted receiver input UART RX. \ud83d\udd3c. This is only one way, so you lose the telemetry downlink to your radio as well as passthrough flashing. Enabling this turns on CRSF protocol output on the S.BUS \ud83d\ude8c pin on your R9MM/R9Mini. set serialrx_inverted = ON may also be needed within Betaflight \ud83d\udc1d for compatibility"},{"location":"software/user-defines/#network-options","title":"Network Options","text":"
AUTO_WIFI_ON_INTERVAL=30\n
\u26a0\ufe0f Must be defined if you plan to update your RX over WiFi without using a button on the RX \u26a0\ufe0f This will automatically turn the WiFi \ud83d\udcf6 on for any module that has an ESP8285 on it if no TX connection is established after N seconds from boot (the 30 is the time). This enables pushing firmware updates to the RX by connecting to its WiFi network and visiting http://10.0.0.1.
HOME_WIFI_SSID\nHOME_WIFI_PASSWORD\n
These options set Home Network Access for your WiFi-enabled hardware. With these sets, the devices will try connecting to your existing WiFi Network when you click on \"(WiFi) Update\" on the ExpressLRS Lua script (for some TX Modules) or automatically after your set interval time. Once the devices connect to your Home WiFi, the Update page can be accessed anywhere, from any device on the same network. The TX Module WiFi update page can be reached using the address http://elrs_tx.local, while the receivers' update page can be reached via http://elrs_rx.local.
WiFi mode will first try to connect to the network specified before falling back and creating a new WiFi network. The Home Network can also be modified from the website.
For TXes like the R9M, this sets if the TX only beeps one-time versus playing a startup song. Currently, it is set to play the startup song \ud83c\udfbc , but if you don't prefer it, uncomment this to turn it off. \u2716\ufe0f
For all your customization needs, use DMY_STARTUP_MELODY to define your own startup melody using the BLHeli32 or RTTTL syntax. For BLHeli32, the parameters music string and bpm are required, whereas semitone offset is optional to transpose the entire melody up or down by the defined amount of semitones.
For example, BLHeli32 melodies are available on Rox Wolf's youtube channel, some experimentation may be required though. To write your own melody, this (Sheet Music 101) and this (BLHeli Piano) are useful resources.
The build process also supports RTTTL-formatted ringtone strings. RTTTL melodies are delimited by colons : and start with a description versus the BLHeli style with pipes |. e.g. Mario:d=4,o=5,b=100:32p,16e6,16e6,16p,16e6,16p,16c6,16e6,16p,16g6,8p,16p,16g
DISABLE_STARTUP_BEEP\n
Disables beep sequence at startup of TX, but the TX will still beep when the CRSF connection is acquired
DISABLE_ALL_BEEPS\n
Disables all TX buzzer beeps at any state
USE_TX_BACKPACK\n
Enables code for talking to a connected ESP8266 backpack on the TX module, and associated Lua params. The device target should enable this automatically for devices that come with this built-in, but can be added to any device. The TX backpack allows wireless integration with VRX modules and planned telemetry mirroring over WiFi."},{"location":"software/user-defines/#debug-options","title":"Debug Options","text":"
DEBUG_LOG\n
Turn on debug messages, sent to the TX Backpack UART if available or else right out the main CRSF UART (such as on the receiver).
DEBUG_LOG_VERBOSE\n
Use to see verbose debug logging (spammy stuff)
DEBUG_RX_SCOREBOARD\n
Print a letter for each packet received or missed (receiver debugging)
DEBUG_CRSF_NO_OUTPUT\n
Don't send CRSF messages over the CRSF UART (receiver only). Used to only see logging and not logging mixed with CRSF.
DEBUG_RCVR_LINKSTATS\n
Prints a log line for every channels packet received at the RX ID,Antenna,RSSI,LQ,SNR,PWR,FHSS,TimingOffset. The ID is generated on the TX side and overwrites CH1-CH4 and increments once for every channel packet. Writes directly to Serial, and does not require DEBUG_LOG. Flash both TX & RX with this enabled to use it if the ID is required.
DEBUG_FREQ_CORRECTION\n
Enable reporting of RF FreqCorrection in receiver's SNR LinkStatistics, also decreases packet rate on Team2.4 for the additional time needed to include the packet header / enable FreqCorrection. The current FreqCorrection value will be reported in RSNR in the LinkStats scaled -127 to +127, where 127 is the maximum allowable deviation. 200kHz for Team2.4, 100kHz for Team900. Dynamic power must be OFF, or else it will adjust based on the FreqCorrection reported in SNR. Both the TX and RX must have this definition enabled otherwise they will not bind."},{"location":"software/user-defines/#obsolete-user_defines","title":"Obsolete user_defines","text":"
After performing CRC tests using the CRC-13 it was found that CRC includes parity checking so adding a separate parity check was wasteful. CRC checking has now been updated to 14-bit.
The following tests were performed using the new CRC-14 bit implementation with a polynomial of 0x372B, which gives a hamming distance of 6 in a 57-bit range. What this means is that it can detect up to 5 randomly flipped bits of a message that is 57 bits long.
Three stress tests have been performed on the 50-bit data with CRC-14. The tests create random data in 7 bytes (the first byte only has the lower 2 bits set) and then perform random bit flipping based on three styles.
Bear in mind that the CRC is not in the data and so is not subject to bit flipping.
"},{"location":"software/testing/crc-testing/#random-flipped-bits-within-14-bit-range","title":"Random flipped bits within 14-bit range","text":"
Anything over 14 is fairly useless as it will just flip bits back!
1 : 0 out of 1000000 false positives, 0.000000%\n2 : 0 out of 1000000 false positives, 0.000000%\n3 : 0 out of 1000000 false positives, 0.000000%\n4 : 0 out of 1000000 false positives, 0.000000%\n5 : 0 out of 1000000 false positives, 0.000000%\n6 : 0 out of 1000000 false positives, 0.000000%\n7 : 0 out of 1000000 false positives, 0.000000%\n8 : 0 out of 1000000 false positives, 0.000000%\n9 : 0 out of 1000000 false positives, 0.000000%\n10 : 0 out of 1000000 false positives, 0.000000%\n11 : 0 out of 1000000 false positives, 0.000000%\n12 : 0 out of 1000000 false positives, 0.000000%\n13 : 0 out of 1000000 false positives, 0.000000%\n14 : 0 out of 1000000 false positives, 0.000000%\n15 : 0 out of 1000000 false positives, 0.000000%\n16 : 0 out of 1000000 false positives, 0.000000%\n17 : 0 out of 1000000 false positives, 0.000000%\n18 : 0 out of 1000000 false positives, 0.000000%\n19 : 0 out of 1000000 false positives, 0.000000%\n20 : 0 out of 1000000 false positives, 0.000000%\n21 : 0 out of 1000000 false positives, 0.000000%\n22 : 0 out of 1000000 false positives, 0.000000%\n23 : 0 out of 1000000 false positives, 0.000000%\n24 : 0 out of 1000000 false positives, 0.000000%\n25 : 0 out of 1000000 false positives, 0.000000%\n26 : 0 out of 1000000 false positives, 0.000000%\n27 : 0 out of 1000000 false positives, 0.000000%\n28 : 0 out of 1000000 false positives, 0.000000%\n29 : 0 out of 1000000 false positives, 0.000000%\n30 : 0 out of 1000000 false positives, 0.000000%\n
"},{"location":"software/testing/crc-testing/#flipped-bits-in-a-single-sequence-at-the-random-start-position","title":"Flipped bits in a single sequence at the random start position","text":"
The number 1-30 is the number of consecutive bits that are flipped at a random starting position.
1 : 0 out of 1000000 false positives, 0.000000%\n2 : 0 out of 1000000 false positives, 0.000000%\n3 : 0 out of 1000000 false positives, 0.000000%\n4 : 0 out of 1000000 false positives, 0.000000%\n5 : 0 out of 1000000 false positives, 0.000000%\n6 : 0 out of 1000000 false positives, 0.000000%\n7 : 0 out of 1000000 false positives, 0.000000%\n8 : 0 out of 1000000 false positives, 0.000000%\n9 : 0 out of 1000000 false positives, 0.000000%\n10 : 0 out of 1000000 false positives, 0.000000%\n11 : 0 out of 1000000 false positives, 0.000000%\n12 : 0 out of 1000000 false positives, 0.000000%\n13 : 0 out of 1000000 false positives, 0.000000%\n14 : 0 out of 1000000 false positives, 0.000000%\n15 : 0 out of 1000000 false positives, 0.000000%\n16 : 0 out of 1000000 false positives, 0.000000%\n17 : 0 out of 1000000 false positives, 0.000000%\n18 : 0 out of 1000000 false positives, 0.000000%\n19 : 0 out of 1000000 false positives, 0.000000%\n20 : 0 out of 1000000 false positives, 0.000000%\n21 : 0 out of 1000000 false positives, 0.000000%\n22 : 0 out of 1000000 false positives, 0.000000%\n23 : 0 out of 1000000 false positives, 0.000000%\n24 : 0 out of 1000000 false positives, 0.000000%\n25 : 0 out of 1000000 false positives, 0.000000%\n26 : 0 out of 1000000 false positives, 0.000000%\n27 : 0 out of 1000000 false positives, 0.000000%\n28 : 0 out of 1000000 false positives, 0.000000%\n29 : 0 out of 1000000 false positives, 0.000000%\n30 : 0 out of 1000000 false positives, 0.000000%\n
Interestingly this is where the hamming distance shows any flipped bits less that HD6 is detected. Also this is where the built-in parity shows up as it detects the odd numbered bit flips.
1 : 0 out of 1000000 false positives, 0.000000%\n2 : 0 out of 1000000 false positives, 0.000000%\n3 : 0 out of 1000000 false positives, 0.000000%\n4 : 0 out of 1000000 false positives, 0.000000%\n5 : 0 out of 1000000 false positives, 0.000000%\n6 : 101 out of 1000000 false positives, 0.010100%\n7 : 0 out of 1000000 false positives, 0.000000%\n8 : 134 out of 1000000 false positives, 0.013400%\n9 : 0 out of 1000000 false positives, 0.000000%\n10 : 129 out of 1000000 false positives, 0.012900%\n11 : 0 out of 1000000 false positives, 0.000000%\n12 : 123 out of 1000000 false positives, 0.012300%\n13 : 0 out of 1000000 false positives, 0.000000%\n14 : 116 out of 1000000 false positives, 0.011600%\n15 : 0 out of 1000000 false positives, 0.000000%\n16 : 106 out of 1000000 false positives, 0.010600%\n17 : 0 out of 1000000 false positives, 0.000000%\n18 : 113 out of 1000000 false positives, 0.011300%\n19 : 0 out of 1000000 false positives, 0.000000%\n20 : 118 out of 1000000 false positives, 0.011800%\n21 : 0 out of 1000000 false positives, 0.000000%\n22 : 131 out of 1000000 false positives, 0.013100%\n23 : 0 out of 1000000 false positives, 0.000000%\n24 : 102 out of 1000000 false positives, 0.010200%\n25 : 0 out of 1000000 false positives, 0.000000%\n26 : 111 out of 1000000 false positives, 0.011100%\n27 : 0 out of 1000000 false positives, 0.000000%\n28 : 159 out of 1000000 false positives, 0.015900%\n29 : 0 out of 1000000 false positives, 0.000000%\n30 : 116 out of 1000000 false positives, 0.011600%\n
A 5hr OTA soak test was done at RSSI -108dBm (2.4GHz, 500Hz) and branch counting-flipped-bits@e3ddcc. RC data bytes were hard coded 0xAA and checked for CRC14 pass/fail, and the number of bits flipped counted.
The below table columns are the number of bits flipped, crc passed tally, crc failed tally. Where passed means a bad packet that passes the CRC check and would accepted by the RX. On the 0 row, Passed is good, Failed is where the data is good, but the CRC itself was changed by bit-flips.
The RX Scoreboard is a developer/troubleshooting feature that shows the outcome of every receiver packet cycle with a single character. Enable it with -DPRINT_RX_SCOREBOARD when compiling any RX environment and connect to the debug serial UART, usually the same as the CRSF output UART for most environments.
\u26a0\ufe0f For that reason, it should not be enabled during normal RC control operations since it will get mixed in with real CRSF data sent to the FC.
"},{"location":"software/testing/rx-scoreboard/#character-legend","title":"Character Legend","text":"Character Meaning Description R Receive \u2714\ufe0f A valid RC sticks or MSP packet was received which passes all validation T Telemetry \u2714\ufe0f Telemetry was successfully transmitted s SYNC \u2714\ufe0f A valid SYNC packet was received. Sync packets come about once every 4 seconds, or more frequently around a telemetry ratio or packet rate change _ Missing \u274c No packet was received at all yet one was expected \ud83d\udc7b . CRC \u274c A packet was received but failed CRC check"},{"location":"software/testing/rx-scoreboard/#name-origin","title":"Name Origin","text":"
The term scoreboard originated from an Apache (web server) feature that would display the state of every work as a single character in a text block. Thanks to them for the feature name and the dodecatillion web pages they've enabled serving.
In the windows search bar type env and select Edit the system environment variables
Click the Environment Variables... button and in the System variables section double-click Path and click New then paste C:\\Program Files (x86)\\mingw-w64\\i686-8.1.0-posix-dwarf-rt_v6-rev0\\mingw32\\bin. This path may be different on your system, but it is the path that mingw-w64 was installed previously and where g++.exe is located.
"},{"location":"software/testing/unit-testing/#running-the-tests","title":"Running the tests","text":"
In VSCode with the ExpressLRS project open, click on the New Terminal button in the status bar
Ensure the native platform is installed by entering pio platform install native in the terminal window.
Now you can enter pio test -e native to run the tests.
It is also possible to use the PlatformIO module and select Native/Advanced/Test in the target selection list.
Once you have Flashed ELRS onto your receivers they can be conveniently updated using the passthrough feature of Betaflight (and similar FC FW). This is a relatively simple process.
Open VS Code or the configurator and prepare to compile and upload.
Plug in your FC to your computer, but do NOT connect to the betaflight configurator.
Select env:YOUR_RX_via_Betaflight_Passthrough and hit upload.
Since 1.0.0, ESP receivers can be updated via passthrough without using the boot button as long as the firmware is not corrupted. If you're unable to get it to work, your firmware might be corrupted, in which case you'll need to temporarily turn off the telemetry feature in betaflight. If it still doesn't work, the bootloader might be messed up and the following steps should work.
Open VS Code or the configurator and prepare to compile and upload.
Plug in your FC to your computer, but do NOT connect to the betaflight configurator and do NOT power the RX. If your RX gets powered from USB, desolder the power wire so that you can manually power it up independently of the flight controller.
Hold the boot button of the RX or jump the boot jumper.
Select env:YOUR_RX_via_Betaflight_Passthrough and hit upload.
If it fails to flash (may display a success message but has errors show up above the final success output), check if it is flashing the correct COM. Sometimes an ethernet adapter on your motherboard will populate a COM port, which will confuse the script and it will attempt to flash to that COM.
The solution that could work would be manually editing the UARTUpload.py and BetaflightinitPassthrough.py files in src/python.
Another possible solution could be changing the COM to a higher number for the unnecessary COMs
Sometimes the boot jumper or button must be used while powering up the receiver.
Connect the autopilot to a PC using a USB cable and connect with a Ground Station (i.e. Mission Planner, QGC, etc).
Set SERIAL_PASSTIMO to a length of time (in seconds) that gives you enough time to connect with the sensor\u2019s configuration software. 30 to 60 seconds is a good choice
Set SERIAL_PASS2 to the number of the serial port connected to the sensor. I.e. \u201c2\u201d if the sensor is connected to Telem2/Serial2.
Be sure to set each port\u2019s baud rate appropriately using the SERIALx_BAUD parameter. The rates may be different for each port. ArduPilot will do the buffering.
Press the \u201cDisconnect\u201d button on the ground station but leave the USB cable from the PC to the autopilot connected.
Open the sensor\u2019s configuration software and connect to the autopilot\u2019s COM port. If all goes well the configuration software should work as it does when the PC is directly connected to the sensor
If the configuration fails to connect there are some things to try:
Some configuration software will not allow connecting to the autopilot\u2019s COM port by default but may have an option to display all available COM ports
If no serial messages are received from the PC the timeout will expire and SERIAL_PASS2 will revert to -1
You can also refer to the ArduPilot official docs for serial passthrough.
Build your firmware file, either via the ExpressLRS Configurator or PlatformIO. The ExpressLRS Configurator will open a folder for you where the correct firmware file was created and should be named like <target name>-<version>.bin (e.g. for the Happymodel ES24TX, the file will be HappyModel_ES24TX_2400_TX-2.0.0.bin). Meanwhile, PlatformIO should create the file within the \\src\\.pio\\build\\<target name>\\ folder.
Put your device in WiFi Updating mode. For TX modules, this is accomplished using the ExpressLRS Lua Script. Simply select WiFi Update from the script and it should start the Update Hotspot. For receivers, power the receiver and wait until AUTO_WIFI_ON_INTERVAL time has elapsed and the LED on the receiver is blinking fast.
Connect to the hotspot that the device has created. For TX modules, this hotspot should show up as ExpressLRS TX while for receivers, the hotspot will have a name such as ExpressLRS RX. They have the same password: expresslrs.
Updating on Phones (click/tap to expand)
In case your computer does not have WiFi capabilities, you can use a WiFi capable smartphone as well. Most phones will display a notification after a successful connection. This is because the phone does not recognize an internet connection. It is recommended to acknowledge this notification because the phone might disconnect again.
On iOS, the WiFi Update Page may open immediately. You can close it via the \"Cancel\" button on the top right and choose \"Use without internet\"
On Android, you may see a notification. Click the notification to open the WiFi Update Page and then hit the three dots on the top right and choose \"Use this network as is\".
Now continue with the guide below.
Note
The receivers, due to their respective sizes, don't have robust WiFi antennas and you will have to bring them closer to the device you're connecting from. The window that opens can easily be closed.
Navigate your browser to http://10.0.0.1/ and the WiFi Update Page should show up.
Using the Choose File button, navigate to the folder where the Firmware file is. You can also drag-and-drop the file from the folder window into the Choose File field.
Click the Update button adjacent to the Upload field, and the Update process should commence. A progress bar will be shown to show the status of the Update.
Once the Update process completes, a Popup should show the result of the Update. Normally, it will show the Success Message. Otherwise, some info will be shown for the reason it failed, like a wrong firmware file, old firmware or a wrong firmware file format.
DO NOT unplug/turn off the device yet. For TX Modules, wait for the Lua Script to return to its Main Screen, indicating that the TX Module has rebooted. For receivers, wait until the LED started blinking again, or you can even wait for it to activate WiFi Mode again for good measure.
Additionally, using this same Wifi Update page, you can also configure the receiver to connect to your local Wifi Network, in preparation for the other (better) methods.
"},{"location":"software/updating/wifi-updating/#method-2-home-network","title":"Method 2: Home Network","text":"
This method will only work if the device has been configured to connect to the local Wifi Network, either via the Join Network section in the Hotspot, or it's flashed with a firmware with the Home WiFi Network SSID and Password options set.
Build your firmware file, either via the ExpressLRS Configurator or PlatformIO. The ExpressLRS Configurator will open a folder for you where the correct firmware file was created and should be named like <target name>-<version>.bin (e.g. for the Happymodel ES24TX, the file will be HappyModel_ES24TX_2400_TX-2.0.0.bin). Meanwhile, PlatformIO should create the file within the \\src\\.pio\\build\\<target name>\\.
Put your device in WiFi Updating mode. For TX modules, this is accomplished using the ExpressLRS Lua Script. Simply select WiFi Update from the script and it should connect to your WiFi Network. For receivers, power the receiver and wait until AUTO_WIFI_ON_INTERVAL time has elapsed and the LED on the receiver is blinking fast.
Using your browser, navigate to the Wifi Update page. For TX Modules, this should be http://elrs_tx.local while for receivers, the URL should be http://elrs_rx.local.
Using the Choose File button, navigate to the folder where the Firmware file is. You can also drag-and-drop the file from the folder window into the Choose File field.
Click the Update button adjacent to the Upload field, and the Update process should commence. A progress bar will be shown to show the status of the Update.
Once the Update process completes, a Popup should show the result of the Update. Normally, it will show the Success Message. Otherwise, some info will be shown for the reason it failed, like a wrong firmware file, old firmware or a wrong firmware file format.
DO NOT unplug/turn off the device yet. For TX Modules, wait for the Lua Script to return to its Main Screen, indicating that the TX Module has rebooted. For receivers, wait until the LED started blinking again, or you can even wait for it to activate WiFi Mode again for good measure.
"},{"location":"software/updating/wifi-updating/#method-3-build-and-flash","title":"Method 3: Build and Flash","text":"
This method will only work if the device has been configured to connect to the local Wifi Network, either via the Join Network section in the Hotspot, or it's flashed with a firmware with the Home WiFi Network SSID and Password options set.
Put your device in WiFi Updating mode. For TX modules, this is accomplished using the ExpressLRS Lua Script. Simply select WiFi Update from the script and it should start the Update Hotspot. For receivers, power the receiver and wait until AUTO_WIFI_ON_INTERVAL time has elapsed and the LED on the receiver is blinking fast.
Set your User Defines or Firmware Options. Make sure you've selected the correct Target.
With PlatformIO, select Upload with the Wifi Target. With the ExpressLRS Configurator, click Build and Flash. Wait for the Compile to finish and you should see a section of the log like the image below:
DO NOT unplug/turn off the device yet. For TX Modules, wait for the Lua Script to return to its Main Screen, indicating that the TX Module has rebooted. For receivers, wait until the LED started blinking again, or you can even wait for it to activate WiFi Mode again for good measure.
Before we can do any building, you need to select a release build of ELRS. For example, release 0.1.0-RC1. In Visual Studio Code select that tag. The location of the selector is shown below. π±οΈ
Click the selector, and then type in the name of the tag, in this case 0.1.0-RC1.
π When you first launch Visual Studio Code, you should see the PlatformIO Home Page in a tab. Click the Open Project button. Navigate to the ExpressLRS repo directory. Navigate into the src folder (i.e. ./ExpressLRS/src/). Finally, press the Open button.
βοΈ Edit the file ./src/user_defines.txt to define user specific variables. π Please make sure you edit the file according to your needs!
π In the toolbar on the left, click the PlatformIO icon, which will show the list of tasks. Now, select Project Tasks, expand your desired target and select Build/Upload (depending on the method). You should see the result in the terminal.
π If something went wrong - please check the Terminal, too. It will contain at least a hint of what the issue is. Please ask the community for further helpπ§βπ§!
You've cloned the repository and are now wondering how to get new updates down the line. Then this document is meant for you! Here's a primer on how to keep your local copy of the repository up-to-date.
The advantage this method has over the first method is that all your changes to the user_defines.txt (or any other file, for that matter) will get merged with any new updates. There's a possibility that, if changes are too big, you could end up with a merge conflict. If that doesn't appeal to you, stick to the first method.
Commit your changes to your local repository
In VSCode open the command palette (using Cmd+Shift+P on MacOS or Ctrl+Shift+P on Windows)
Enter: Git: Commit
VSCode will tell you that there are unstaged changes and ask if you want to add them to the commit. Confirm this! This will just commit your changes to the user_defines.txt to your local repository. No worries, you're not overwriting anything on GitHub! :octocat:
Open the terminal, how-to is detailed in method 1
In the terminal, type: git pull -f
This will pull a new revision of the remote repository to your local repository and automatically merge it with your changes.
Before we can do any building, you need to select a release build of ELRS. For example, release 0.1.0-RC1. In Visual Studio Code select that tag. The location of the selector is shown below. π±οΈ
Click the selector, and then type in the name of the tag, in this case 0.1.0-RC1.
π When you first launch Visual Studio Code, you should see the PlatformIO Home Page in a tab. Click the Open Project button. Navigate to the ExpressLRS repo directory. Navigate into the src folder (i.e. ./ExpressLRS/src/). Finally, press the Open button.
βοΈ Edit the file ./src/user_defines.txt to define user specific variables. π Please make sure you edit the file according to your needs!
π In the toolbar on the left, click the PlatformIO icon, which will show the list of tasks. Now, select Project Tasks, expand your desired target and select Build/Upload (depending on the method). You should see the result in the terminal.
π If something went wrong - please check the Terminal, too. It will contain at least a hint of what the issue is. Please ask the community for further helpπ§βπ§!
You've cloned the repository and are now wondering how to get new updates down the line. Then this document is meant for you! Here's a primer on how to keep your local copy of the repository up-to-date.
The advantage this method has over the first method is that all your changes to the user_defines.txt (or any other file, for that matter) will get merged with any new updates. There's a possibility that, if changes are too big, you could end up with a merge conflict. If that doesn't appeal to you, stick to the first method.
Commit your changes to your local repository
In VSCode open the command palette (using Cmd+Shift+P on MacOS or Ctrl+Shift+P on Windows)
Enter: Git: Commit
VSCode will tell you that there are unstaged changes and ask if you want to add them to the commit. Confirm this! This will just commit your changes to the user_defines.txt to your local repository. No worries, you're not overwriting anything on GitHub! :octocat:
Open the terminal, how-to is detailed in method 1
In the terminal, type: git pull -f
This will pull a new revision of the remote repository to your local repository and automatically merge it with your changes.
Avoid user_defines.txt ending up in a commit or getting overwritten¶
Don't change user_defines.txt for setting up your local configuration. Instead create a new text file `super_defines.txt in the same location as user_defines.txt to define your local build configuration. super_defines.txt will be git-ignored and will not be part of any commits and won't be overwritten by pulls. Example super_defines.txt: