Fall at 50% throttle

Hey guys, i have a rather big problem. I have a APM 2.5 and have just uploaded 3.0.1. When i am flying at 50% throttle or just below, instead of descending my octo just falls!

All standing tuning,

MT2814-10 Tiger motorsturnigy plush 40A escs

Droidworx AD-8

12' 10x4.5 props

Please help! I keep destroying the fame each time i fly. I will try to post a TLOG when i go for the nexrt flight. Maybe my frame will no survive the next crash.

Thanks!

PS. Also, do i need to do a throttle calibrraton even if i am using a ESC programming card?

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • Ok, i managed to get out for a flight today before the rain came down. It seemed the ESC calibration may have done the trick but now i have massive amounts of yaw happening. I have a TLOG of my last flight, for some reason this flight seemed rather unstable to most flights. Ive flown many builds with the APM but it just seemed a little sluggish and unstable.

    I beleive on the AD-8 or possibly octos in general, the motors are tilted slightly one way to compensate for YAW. Can anyone explain the procedure for doing this?

    Anyway, i have not got alot of experience with using TLOGs so maybe someone could chew on this log file to see if you could find anything out of the ordinary or a bit unusual.

    Thanks!

    2013-08-13 17-15-22.tlog

  • Can someone confirm if the 3.0.1 fw has auto takeoff at around 5% throttle
  • And oh: Seeing that you have the Plush 40 Amps, I must recommend that you flash them with the BLHeli firmware. Many multicopter users will tell you that there is a large difference in stability of flight when using high speed firmware.

    Edit: BLHeli is the same as SimonK firmware, only on Silog CPUs instead of Atmel AVR CPUs. SimonK is for AVR only. BLHeli is for Silog, as is in the Plush 40A.

    http://oddcopter.com/2012/07/18/flashing-silabs-escs-with-blheli-fi...

    Get a toolstick for a few bucks off Ebay.

    /Magnus

  • I would certainly try the ESC calibration from the Missionplanner/APM if you have not done so. Using a programming card does nothing for calibration, just edit settings?

    The ESCs need to learn what range the APM is working in. Not knowing that will produce among other errors, exactly what you are describing.

    Try that first, then come back and let us know. :)

    If you dare, you might try holding the copter down to the ground, applying throttle up and down and seeing of the behaviour is better after calibration. That might give you an indication of whether the problem is fixed, and spare you a frame.

    KR

    Magnus, Sweden

This reply was deleted.

Activity