FlightOne F.A.Q
Check our Frequently Asked Questions
The configurator keeps rebooting
  1. Verify that you’re using the matching configurator and firmware versions
    1. Example: 575.1 configurator version with 577 firmware version
  2. Flash firmware in DFU mode use its matching configurator
    1. Follow DFU flashing guide
  3. If the configurator reboots during radio setup
    1. Make sure there are no shorts
    2. Make sure your arm switch is setup in your radio properly
  4. If the configurator is rebooting during the ESC or Motor direction wizards there are three prosibilites
    1. You have a somewhere in your build. Check for shorts. Usually there are micro (super tiny) strands of wire bridging somewhere. It’s highly recommended you desolder everything, reflow pads, and clean everything with denatured alcohol.
      1. Also, use a multimeter in continuity mode across connections points to verify there are no ground shorts. – If you don’t know how to do this, watch a YouTube video on how to use a multimeter.
    2. One of your ESCS is corrupted ( or the MPU is not working)
      1. Check for short circuits
      2. Check for damaged MPU chips – we’ve seen several with pads bridged and chipped MPU’s
      3. Do a “1wire read” in the console
        1. Remove props
        2. Go to the console
        3. Connect battery
        4. Type “1wire read” without the quotes
          1. Type:   1wire read
        5. Copy and paste what is returned in the console to a .txt file, google doc, or word document.
        6. Check to see if anything escs show up as unreadable (m0, m1, m2, m3)
          1. If they show up as unreadable you can swap ESCS between motor outputs and see if the unreadable issue follows the ESC or stays on the motor output.
            1. ie.: Move the signal wires from the M3 to M4 Pads. Then Move M3 to M4 Pads Re-run 1wire read. Does M4 now show as unreadable?
            2. Unreadable will show like M4: unreadable
            3. If it shows up as ÿÿÿÿÿÿÿÿÿ or something similar, this is a firmware that is corrupted or not matching. Please manually reflash your ESCs.
          2. If it follows the ESC then you have a corrupted ESC, broken ESC, or short on the ESC/pwm output.
      4. Make sure your signal and ground wires are going to the correct places on the flight controller
        1. For diagrams please go to https://raceflight.com/support/#pinout_section
      5. Post high resolution, clear, focused, and up close pictures of your flight controller and ESCs.
    3. Once we receive the pictures, we “may” choose to send you a coupon code for the damaged replacement program if none of these things fixed your issues. This is not Guarantee.
  5. Your USB may be having connectivity issues
    1. Try another USB Cord
    2. Try another USB port
    3. If you wiggle the USB cord while it’s attached to the flight controller does the flight controller disconnect or reboot in the configurator?
      1. You may try reflowing the USB port or you can send us a picture of the board with a hole drilled in it (or something similar to confirm the board is unusable)
      2. Then send us a copy of the receipt of original purchase.
      3. If the flight controller was not already replaced under the Damaged Replacement Program (DRP), we will get you a coupon code for said DRP.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

*