Welcome to PhantomPilots.com

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

Flyaway - but didn't get too far

Discussion in 'General Discussion' started by careysb, Sep 1, 2013.

  1. careysb

    Joined:
    Jun 26, 2013
    Messages:
    108
    Likes Received:
    1
    Fortunately I was out in a field. I flew it out a couple of hundred feet and then I noticed it wasn't behaving according to the controls. I was trying to bring it back for a landing by watching its behavior as I manipulated the controls. I managed somehow to bring it back but the flight path was very erratic and the landing very hard. (GPS & Home Lock). :(

    Tried again another day; same thing, only this time hit a tree. I made sure that I gave the GPS as much time as it needed to lock on to the satellites. Hmmm, I didn't' get a single green LED, what I got was green-green-pause-(repeat). :(

    So, up until this my flights have been uneventful

    I'm trying to think back to what had changed between the good flights and the bad. First, I added the ARRIS CM2000 gimbal. I don't really think this is it because I ran a single test flight after that and it behaved nicely. Next flight I had tweaked some settings on the Phantom.

    [​IMG]

    I had put pitch and roll at 100%, yaw and vertical at 70%. This was the setting for the first flyaway.

    So I put pitch and roll back to the original 125% but left the yaw and vertical at 70%. This was the settings for the second flyaway, though the second fly away was no where near as erratic as the first flyaway.

    Apparently the pitch and roll tweaks added to the problem. I'm not sure that the yaw and vertical had anything to do with it. I'm not sure what the green-green LED lights mean. And I'm not 100% convinced that the gimbal didn't have anything to do with it.

    Help!
     
  2. mikrob

    Joined:
    Jun 29, 2013
    Messages:
    98
    Likes Received:
    0
    I have always got a green/green blink with no reds...never a single green blink. GPS has always worked. Once I had a flyaway with the double green but I found the Phantom.
     
  3. careysb

    Joined:
    Jun 26, 2013
    Messages:
    108
    Likes Received:
    1
    I don't know where the 125% setting came from, perhaps when I upgraded the firmware (honestly, I didn't change those settings). So I went back in and clicked the 'default' button which set every thing to 100%, drove out to the open space and tried again. Much better! I think I'm still going to keep it close to home for a while just in case. I'm also going to have to balance the props after running in to that tree.
    Just maybe this will help someone else with a flyaway problem.
     
  4. MrMediaGuy

    Joined:
    Jul 31, 2013
    Messages:
    171
    Likes Received:
    1
    125% is the stock setting. The "default" settings just set everything to 100%, but they aren't the stock settings for the Phantom. Those are:

    125/125/100/100
    125/125

    Even so, changing the gains a bit might cause some erratic wobbles, but it's very unlikely that would contribute to a flyaway unless they were *so* far out of whack that the NAZA couldn't compensate and hold a position. And *if* that happened (still unlikely), you're talking in the 200%+ range.

    I only mention this because if you have had two almost-flyaways, I think something else is to blame besides the gain settings, so I wouldn't want you to get too complacent.
     
  5. careysb

    Joined:
    Jun 26, 2013
    Messages:
    108
    Likes Received:
    1
    Thanks for the comparison of 'stock' vs 'default'.
    Yes, I'm still concerned and vigilent. Don't know when I will finally be able to say it's fixed.
    Still suspicious of the ARRIS gimbal.