Welcome to PhantomPilots.com

Sign up for a weekly email of the latest drone news & information

P3 Firmware Turned off before firmware update complete?

Discussion in 'Firmware' started by wischmi2, Jan 10, 2016.

  1. wischmi2

    Joined:
    Jan 10, 2016
    Messages:
    2
    Likes Received:
    0
    I got my advanced and was updating the firmware. Light on gimbal was blinking as expected, red and green. Came back maybe 10-15 min later and light was solid green. Figured it was done and turned phantom off. Loaded up txt file and it just said updating... Or something like that. It didn't say success or anything like that. However when I load up the app it lists the firmware as 1.6.4. Did it complete or not?? I did a test with no propellers indoors and it acts like it takes off fine. When I formatted the card again and tried to update again the phantom is just doing the startup sequence lights and gimbal light is solid green.
     
  2. Mako79

    Joined:
    May 16, 2014
    Messages:
    3,418
    Likes Received:
    568
    Location:
    Sydney Australia
    Its a pity that you formatted the card. The card would contained logs on the update.
    It looks like you have done the firmware update correct. Remember to do batts and controller.

    Anyways, if it didn't complete then just put it back in and keep going. That's what my girlfriends says :)
     
  3. stujol

    Joined:
    Nov 8, 2015
    Messages:
    52
    Likes Received:
    16
    If it says 1.6.4 you are updated. I use the gimbal light to tell if it is completed or not. Solid green you are good to go, solid red means it failed. If you enable hidden folders on your pc there is a hidden folder called MISC, in there there is a folder called log. In that folder there is a file named P3X_FW_LOG_AB or close to that depending on your model. That has alot more information than the txt file on the root of the drive.
     
  4. wischmi2

    Joined:
    Jan 10, 2016
    Messages:
    2
    Likes Received:
    0
    Thanks for the feedback. Yes I think it's ok, the log file that I looked at was in the root directory so maybe I wasn't looking at the final log file.