Reasons for Failed Connection to APP

For Android devices, the Android system requires location permission and the Bluetooth switch to be turned on to connect to any Bluetooth device. Therefore, before connecting to the SpeedyBee application, you should turn on these two switches.

Please make sure to turn on the APP before connecting the Bluetooth or WIFI

The first possible reason for a failed connection could be, the disabled UART

Connect to the PC-based configurator and check if the communication serial port is disabled. It is on the Port page, where you can enable Serial Port MSP (Baud Rate: 115200).

Please kindly follow/confirm the following steps to ensure proper functioning:

1. Ensure that the flight controller can start up properly and connect properly to the PC-based Configurator.
2. Check if the USB socket on the flight controller is loose; make sure it is securely plugged in.
3. If it is a complete drone, try powering the drone by using the battery first, and then, connect the adapter to rule out insufficient power supply due to high-power-consuming devices within the drone.
4. Ensure that the distance between the flight controller and the smartphone is not too far; try getting closer.
5. Make sure that the remote controller is NOT turned on during the connection process, as it may interfere with the connection. Please turn it off.
6. Verify if the correct firmware is flashed; for example, an F405V3 flight controller with an F405WING firmware wrongly installed; Try re-flashing the correct firmware and then connect again.
7. Test whether the app can connect successfully with a different flight controller.
8. Check if the Bluetooth on the phone is occupied, for example, connecting the earphones;
9. The flight controller firmware supports Betaflight, EMU, and iNav. Please make sure that your flight controller firmware belongs to one of these types.

The reasons for a failed connection of F405 Wing or SpeedyBee eFLY-BLE could be,

1. the Ports Page > Uart 6 (Baud Rate 115200) is disabled, which should be enabled in the Configurator;

2. the firmware of the FC is not INAV, but Ardupilot, F405 Wing requires the firmware of INAV;

3. The flashing green light indicates a Bluetooth connection; while the flashing white light a WIFI connection;

4. If this is the second new flight control connects for the first time, you need to tap the yellow add button on the home page to connect the new device;

5. if you have connected via WIFI, there should be a card of this FC on the home page; click the card, tap the setting, save after connection, and then try to connect the FC;

Possible reasons for OTG not connecting:

1. The OTG is connected in reverse. The OTG cable should be connected to the phone, and the USB cable should be connected to the flight controller.
2. There is an issue with the OTG or data cable. Try replacing it with another data cable.
3. Theoretically, flight controller firmware like BF, iNav, and EMU are supported. Please ensure that your flight controller firmware is one of these types.

If the BT NANO 3 or Meteor LED cannot connect to the app, you can try the following steps:

First, connect to the PC configurator for parameter adjustment. In the port settings, enable the corresponding serial port. For example, if you've soldered the BT module to serial port 6 on the flight controller, you'll need to enable MSP for serial port 6. Afterward, you should be able to connect the BT module.

If the problem persists, please send logs in the "Contact Us" section of the app, and provide a video of the connection process (including LED status on the flight controller, phone model, and system version), as well as close-up and focused photos of both sides of the flight controller to help us identify the issue.