1 ### The Legal Stuff ###
3 # The use and operation of this type of device may require a license and some countries may forbid its use entirely.
4 # It is entirely up to the end user to ensure compliance with local regulations. No claim of regulatory compliance is made. In most cases a HAM license is required.
5 # This is experimental software/hardware and there is no guarantee of stability or reliability. USE AT YOUR OWN RISK
7 # HOW TO USE THIS FILE: https://www.expresslrs.org/1.0/software/user-defines/
8 # SIMPLY SEARCH WHICH DEFINE YOU NEED HELP WITH
11 ### BINDING PHRASE: ###
12 # Uncomment the line below to use a hardcoded binding phrase
13 # Leave commented to use traditional binding
14 #-DMY_BINDING_PHRASE="default ExpressLRS binding phrase"
17 ### REGULATORY DOMAIN: ###
19 # Domain is used to define correct frequency band for 900MHz hardware.
20 #-DRegulatory_Domain_AU_915
21 #-DRegulatory_Domain_EU_868
22 #-DRegulatory_Domain_IN_866
23 #-DRegulatory_Domain_AU_433
24 #-DRegulatory_Domain_EU_433
25 #-DRegulatory_Domain_FCC_915
27 ### PERFORMANCE OPTIONS: ###
29 #unlocks >250mw output power for R9M and Happy Model ES915TX (Fan mod suggested: https://github.com/AlessandroAU/ExpressLRS/wiki/R9M-Fan-Mod-Cover)
30 #-DUNLOCK_HIGHER_POWER
35 #-DFEATURE_OPENTX_SYNC_AUTOTUNE
37 -DLOCK_ON_FIRST_CONNECTION
39 # For TX devices with fans, FAN_MIN_RUNTIME keeps the fan running even after the power level has
40 # dropped below the configured Fan Threshold. This prevents the fan from turning on and off every
41 # few seconds if the power level is constantly changing.
42 # Default is 30 seconds if not defined, value can be 0-254.
45 ### COMPATIBILITY OPTIONS: ###
47 # Invert the TX/RX half-duplex pin in the transmitter code. Handset external
48 # modules are almost all inverted. ESP32 targets only
51 # Use a custom baud rate on the receiver for a KISS v1 FC (which runs at 400000) or any other oddball baud
52 # If not defined, will default to 420000
53 #-DRCVR_UART_BAUD=400000
55 # Invert the TX pin in the receiver code to allow an inverted RX pin on the
56 # FC to be used (usually labeled SBUS input or RXI). Inverted CRSF output.
57 # RX pin (telemetry) is unaffected. Update via_BetaflightPassthrough will
58 # not work, only via_Wifi. ESP8266/8285 targets only
61 # Use the SBUS **pin** on R9MM receiver hardware, which is inverted.
62 # Does not output SBUS protocol, just inverted CRSF.
63 #-DUSE_R9MM_R9MINI_SBUS
65 #-DTLM_REPORT_INTERVAL_MS=320LU
67 ### OTHER OPTIONS: ###
69 -DAUTO_WIFI_ON_INTERVAL=60
71 #-DHOME_WIFI_PASSWORD=""
73 # Enables code for talking to a connected ESP8266 backpack on the TX module, and associated Lua params
74 # The device target should enable this automatically for devices that come with this, but can be added
80 # Disables the startup tune and crsf connect/disconnct do beep-boop
81 #-DDISABLE_STARTUP_BEEP
82 # Startup is beep-boop, and crsf connect/disconnct do similar
84 # Startup plays you own custom tune and crsf connect/disconnct do beep-boop
85 #-DMY_STARTUP_MELODY="B5 16 P16 B5 16 P16 B5 16 P16 B5 2 G5 2 A5 2 B5 8 P4 A5 8 B5 1|140|-3"
87 #Comment this to disable diversity function
90 #If commented out the LED is RGB otherwise GRB
93 ### Debugging options ###
95 # Turn on debug messages, if disabled then all debugging options (starting with DEBUG_) are disabled
97 # Use DEBUG_LOG_VERBOSE instead (or both) to see verbose debug logging (spammy stuff)
100 # Print a letter for each packet received or missed (RX debugging)
101 #-DDEBUG_RX_SCOREBOARD
103 # Don't send RC msgs over UART
104 #-DDEBUG_CRSF_NO_OUTPUT
106 # These debugging options send extra information to BetaFlight in the LinkStatistics packet
107 #-DDEBUG_BF_LINK_STATS