This tool generated firmware binary files for ExpressLRS receivers with preconfigured firmware options.
The configurator works like a wizard. You will be asked a series of questions and the correct configuration will be generated based on your answers. Everything will be explained so you that you understand the implications.
Only some options can be pre-configured by this tool. There are still some options that can only be edited through the web-UI or through the Lua transmitter script.
For combat robotics usage, this tool provides a dedicated firmware with some extra safety related and performance related features. This tool can ensure that those features are enabled by default.
ExpressLRS firmware files are actually consisting of the firmware binary, plus a few chunks of JSON appended to the end of the binary. This tool is simply taking a pre-built first half and changing the second JSON half. The JSON is actually where most of the configurable items are saved.
ExpressLRS is an open source project (link to soure code) and uses the GNU GPL v3 license (link to full text). The firmware files generated by this tool falls under the same license.
Because of the wide range of compilation options available for ExpressLRS firmware, the firmware binary is built on-demand on this web-server's backend. If your particular set of compilation options have been built before, then the firmware binary would be generated pretty quickly. Otherwise, it will be built on-demand and this will take time. This server is running on a potato, seriously, it has one CPU core and 512MB of RAM, a Raspberry Pi has 4 cores and a few GB of RAM.
If you already have a firmware file, you may load it here, and the configuration will be extracted from it. This is completely optional.
Important Note: depending on where this file came from, the configuration wizard may not be able to determine all the required information. Please still go through every single step to make sure everything is correct
Which version of the firmware should be built? (only version 3.3.0 and later supported)
| Choose an official ELRS released version: Loading...
| |
| A special build with features related to combat robotics. (link to source code) List of extra features:
| |
| Use the file you've specified in the "Load Prev Config" tab |
Select the receiver hardware you are targeting.
| Tiny nano receivers with 4 pins meant to connect to a flight controller. These use the ESP8 microcontroller and transmit using the 2.4 GHz frequency band. There are no fancy features. | |
| Choose the receiver from a giantic list, if you click this option, a list will appear below. | |
| Shrew ESC, choose between: | |
| Shrew Zero is a ELRS receiver with 8 PWM pins that are also capable of DSHOT300, and the receiver can be powered with up to 60V. | |
| Use the file you've specified in the "Load Prev Config" tab | |
| You want to edit the raw JSON. A field to edit the final JSON is provided later. Please choose another option that closely matches your hardware first. |
| ELRS will become an access point. Use your phone or computer to directly connect to the Wi-Fi access point. | |||||
ELRS will connect into your home Wi-Fi. Please provide...
|
| Baud Rate | |
AirPort allows you to turn a regular ExpressLRS transmitter and receiver pair into a bi-directional transparent serial data link, over the air. Official documentation: https://www.expresslrs.org/software/airport/ |
PWM pins are useful for controlling servos and ESCs without any flight-controllers involved.
| Use default settings based on the receiver selection | |
| Nano style receiver modified to output 3x PWM signals (click here for more info) | |
| Nano style receiver modified to output 2x PWM signals and 1x serial port output (click here for more info) | |
| Shrew ESC and Shrew Zero has dedicated PWM pins. , which is safer | |
| Enter the list of PWM pins below: Note: when a pin is in this list and is also used by another function, such as "serial_tx", the tool will automatically resolve the conflict by removing the conflicting item (example: remove "serial_tx"). Note: for the RadioMaster RTD-4/RP4TD, the two extra pins on the side are pins 5 and 18. |
Important Note: If you have selected the combat robotics firmware, then all PWM pins will be initialized with a no-pulse failsafe mode for maximum safety out-of-the-box. The combat robotics specific firmware also features servo stretching, but it will not be enabled by default.
Appologies, it is not possible to modify the fine details about each individual PWM pins. That section of configuration data is stored in emulated-EEPROM and is not a part of the firmware at all.
Important Note: This means if you are not using the combat robotics firmware, please double check your PWM failsafe settings afterwards. They may have defaulted to an airplane-friendly failsafe setting.
Below, you can edit the raw JSON data that is about to be embedded into the saved firmware file.