Follow these steps to troubleshoot:

1. Check the Video Transmission Wiring

• Analog VTX: Connect the VIDEO signal wire. The flight controller's built-in OSD chip overlays the OSD information onto the video feed before transmitting it to the goggles via the VTX.
• Digital VTX: Connect the RX/TX wires to the flight controller with the correct cross-connection. If connected straight (e.g., VTX's RX to FC's R1), OSD information will not be transmitted.

2. Check the Connector Pins
If the VTX and flight controller use connectors, check both sides for bent pins. Bent pins may cause signal issues and prevent OSD from displaying.

3. Check Port Settings

• Analog VTX: Enable VTX (IRC Tramp) under Peripherals. Some analog VTXs use VTX (TBS SmartAudio) instead.
• Digital VTX: Enable MSP and VTX (MSP + DisplayPort) under Peripherals.

4. Check OSD Settings

• First, confirm and select the correct video format: PAL/NTSC for analog VTX, HD for digital VTX.
• Secondly, make sure the OSD information items that need to be overlaid are selected and saved.

5. Check CLI Settings

• Analog:
  set osd_displayport_device = AUTO → save
• Digital:
  set osd_displayport_device = MSP→ save

6. DJI Air Unit Specific Settings

• Set Goggles Control Protocol to Normal.
• Set the goggles Canvas layout to Wide.
• Update both the Air Unit and goggles to the latest firmware.

7. Reset and Reconfigure
If the issue persists, restore the factory/default settings and reconfigure the VTX-related settings. For RTF kits, reflash the corresponding preset parameters first.

Shipping times for each product vary based on availability. The availability of each product is displayed when you place an order at https://shop.iflight.com. If your order contains multiple products, the estimated shipping time will be based on which product needs the longest. We generally do not split orders, but we will ask customers if they want to ship the products that are in stock first.

Estimated Time

1. In stock: You should plan for at least 2-3 business days from the time your order is placed until it is shipped. Please also keep in mind that the number of days refers to "business" days, which is Monday through Friday.

2. Back-ordered: Usually it will take 2-3 weeks to ship out.

3. Pre-order: We will ship it within 3~4 weeks.If the time is extended due to force majeure, or if it can be shipped in advance, we will notify you.

Out of Stock: We will contact you within 48 hours. Please note that shipping may be delayed during.

ELRS receivers support five binding methods. Most methods put the receiver into double-flash binding mode, except binding via the Betaflight Configurator and Binding Phrase. Choose any method based on your setup.

1. Power Cycle via USB 3 Times
   Power the flight controller through USB three times. The receiver must be connected to a 5V power source that is powered by USB.
2. Power Cycle via Battery 3 Times
   Connect and disconnect the flight battery three times to enter binding mode.
3. Hold the BOOT Button
   Press and hold the BOOT button on the receiver to enter binding mode.
4. Set an ELRS Binding Phrase
   Set the same Binding Phrase on both the transmitter and receiver to bind them automatically.
5. Bind via Betaflight
   Open the Receiver tab in Betaflight Configurator and click Bind Receiver.

Orders will be shipped by FedEx, UPS or DHL. We are unable to ship to PO Boxes. Due to air transportation restrictions, it is recommended to purchase no more than two batteries per order. For orders from areas such as Alaska, Hawaii, puerto rico or the central mountainous regions, delivery time will be slightly longer.

We offer free air post shipping on orders of $100 or more. If your order does not qualify for free shipping, the shipping fee will be shown on the address-filing page once the order is settled. The following countries do not have air post transportation channels yet：Alaska, Puerto Rico, Guam, Hawaii, Cyprus, Iceland, Iran, Kazakhstan, Maldives, Pakistan, Philippines, Sri Lanka, Costa Rica, French Polynesia, etc.

The issue is usually related to the USB port, cable, driver, or firmware. Follow these steps:

1. Check the USB Port
   Make sure the USB cable is connected to the flight controller’s USB configuration port, not another USB port on the aircraft. Refer to the product manual if needed.
2. Check the USB Cable
   Make sure you are using a USB cable that supports data transfer, not a charging-only cable. You can also try another USB port on the computer. If the issue persists, try connecting to a different USB port on your computer to rule out port conflicts.
3. Check for Loose Connections
   If the connection repeatedly disconnects and reconnects, try another USB cable. If the issue persists, the flight controller’s USB port may be damaged.
4. Check the Flight Controller Driver
   Open Device Manager and check whether the flight controller appears under Ports or Universal Serial Bus Controllers. If necessary, update the driver or reinstall it using Zadig. If the Configurator still does not recognize the flight controller after using Zadig, return to Device Manager and run "Update Driver" again.
5. Check Firmware Compatibility
   Make sure the Betaflight Configurator version is compatible with the flight controller firmware. For example, Betaflight 4.5.5 requires the corresponding Configurator version, while firmware 2025.12.2 / 12.1+ requires the appropriate newer Configurator.
6. Check the Firmware Target
   If the wrong firmware target was flashed, the flight controller may fail to connect normally. Hold the BOOT button while connecting USB to enter DFU mode, then flash the correct firmware target.
7. Check for Hardware Damage
   If the LED does not light up and the flight controller’s MCU becomes abnormally hot after connecting USB, the MCU may be damaged. Contact after-sales support for further inspection.

Notification

After the order is shipped, you will receive a notification email containing the tracking number. You can click the link and skip to the express company’s official website to check your package shipment status.

Tracking Your Order

1. Log in to your iFlight account and look at your order history.

2. Contact iFlight Support (Send emails to sales@iflight.com)

Normally, the aircraft should play five startup beeps: the first three are the ESC self-test, followed by two flight controller beeps. Use the missing beeps to identify the affected component:

• No last two beeps → Flight controller troubleshooting

• No first three beeps → ESC troubleshooting

• No sound or LEDs → External power troubleshooting

Flight Controller Troubleshooting

1. ESC/Motor Protocol Not Selected

If the FC LEDs work normally and Betaflight connects, but there is no FC startup sound, select DSHOT300 or DSHOT600 under Motors → ESC/Motor Protocol, then save.

2. MCU Short Circuit

If the FC has no LEDs, cannot connect to Betaflight, and the MCU becomes unusually hot, the MCU may be damaged. Contact after-sales support.

3. Power IC Failure

If the FC works normally via USB but only passes the self-test when the battery is connected simultaneously, the power IC may be damaged. Contact after-sales support.

4. Incorrect Firmware

If only the red LED lights up and the FC cannot connect to Betaflight, hold the BOOT button while connecting USB to enter DFU mode, then flash the correct firmware target.

5. Peripheral Short Circuit / Bent Pins

Disconnect external devices one by one and test after each removal. Also check all connectors for bent pins. If the self-test resumes after removing a device, that device may be faulty.

6. FC–ESC Cable Not Connected

Check whether the 8P cable / BORG cable between the FC and ESC is properly connected.

ESC Troubleshooting

If the first three ESC beeps are missing, remove the FC and power the ESC separately. If there is still no startup sound, the ESC may be faulty. Contact after-sales support.

External Power Troubleshooting

1. Anti-Spark Module Fuse Blown — D25 Only

If there are no LEDs or sounds after power-up, check the external anti-spark module. A blown fuse can prevent the entire aircraft from powering on. Contact after-sales support.

2. Low or Depleted Battery

Try a fully charged or known-good battery. If the aircraft powers on normally, the original battery may be too low or depleted.

Unsure how to select an iFlight FPV drone matching your flying style? Whether you are a new pilot, content creator, long-distance explorer or filmmaking professional, the practical Buyer’s Guide covers the current product lineup to support your purchasing decision. Link

This is usually caused by motor/propeller installation or flight controller settings. Check the following:

1. Check Motors and Propellers

• Motor direction: Verify that each motor spins in the correct direction. Match CW motors with CW props and CCW motors with CCW props.
• Propeller orientation: Make sure the props are installed in the correct direction and are not upside down.
• Motor order: Confirm that the motor numbers match the motor layout in Betaflight. If inconsistent, drag the motor icon on the "Motor Test" page to match the actual position on the frame (recalibration of motors is required after adjustment).

2. Check Flight Controller Settings

• FC orientation: The arrow on the flight controller should point toward the front of the drone.
• Accelerometer calibration: Calibrate the accelerometer with the drone placed level and stationary.
• Frame type: Make sure the correct frame configuration, such as X or Plus, is selected.

3. Check Radio Control Settings

• Channel direction: In the Receiver tab, throttle should increase from around 1000 to 2000 when pushed.
• Stick center: With the sticks centered, channels should be around 1500.
• Factory/RTF parameters: If the configuration has been modified, restore the correct factory parameters and reconfigure the drone.

Continuous or abnormal beeping is usually caused by low voltage, radio disconnection, or incorrect settings. Follow these steps:

1. Check the Buzzer Wiring
   For models with an external active buzzer, check that the wiring is correctly connected and secure.
2. Check Battery Voltage
   A low battery may trigger the low-voltage alarm. Charge or replace the battery and test again.
3. Check Radio Connection
   Make sure the transmitter and receiver are properly connected. A lost or weak signal may trigger the buzzer.
4. Disconnect Betaflight Properly
   After changing parameters in Betaflight, click Disconnect before unplugging the USB cable to ensure settings are saved correctly.
5. Check Buzzer Settings
   Verify the buzzer parameters and channel settings in the flight controller. Check the OSD warning messages after arming to identify the cause.