Replies to This Discussion

DeveloperPermalink Reply by Randy on March 22, 2012 at 6:05am

Marc,

     Hmm...we seem to be having a number of troubles with the altitude hold in 2.5 even though the code has hardly been changed from 2.4.1.  The issue is that your THROTTLE_TRIM parameter needs to be higher.  The default is 350 which is apparently far too low.  Try bumping it up to 450 or 480.

     Sorry about your crash, i hope it wasn't broken too badly.

Permalink Reply by Marc on March 22, 2012 at 6:36am

Hello randy,

thanks for the reply have a look at the crash, glad i built a tough frame :)

heres the vid: http://www.youtube.com/watch?v=kG_VJiR_o3I

 

regards

will try the throttle trim higher as you advise.   many thanks

Permalink Reply by Marc on March 22, 2012 at 12:54pm

Randy,

can i ask haveyou had any reports of not being able to connect to the apm?

i have to keep on a old version of mission planner 1.1.50 and my apm connects to laptop no problem, any version of mission planner after that it will not connect at all it gives me "no heartbeat"

 

regards

 

DeveloperPermalink Reply by Randy on March 22, 2012 at 5:04pm

No, i haven't seen many reports like that. Are you sure you have selected the baud rate and com port on the top right of the planner?

Permalink Reply by Marc on March 23, 2012 at 1:20am

hello randy,

yep com and baudrate is correct its weird just works perfectly on mp 1.1.50

 

regards

 

Permalink Reply by Marc on March 25, 2012 at 8:12am

hello randy,

 

i increased the throttle trim to 480 and it still drops not as quick though is it safe to increase to 680?

 

regards

 

DeveloperPermalink Reply by Randy on March 26, 2012 at 7:51am

If you upgrade to 2.5.3 your problems will likely go away.  But if you want to stick with the code you're using, it's fine to keep on increasing that number by 50 degree increments until you get to a number that works.  If you really need to push it as high as 680 then that means that your quad is underpowered for all the stuff you have on it.  Maybe  you need a lighter battery or something...

 

One thing is that if you do need to put the throttle trim as high as 680, it may be that you're out of the deadzone for the throttle..so the code will think you want the quad to climb.  So you may find that you need to get into a hover, click on altitude hold, then reduce the throttle back into the deadzone (i.e move your throttle stick back to the middle).

 

Hope this helps, good luck.

ModeratorPermalink Reply by Adam AKAV8R on March 26, 2012 at 12:03pm

Is it still the case in the new 2.5.3 that if you hover for a few minutes, land and disarm that it sets this value automativally once you resume flying?  Also, will it save this value after powering down or battery change or does the process need to start over again?

 

I'm flying a 3DR with APM 2 Purple using default 3DR parameters and have had the same issue with my quad copter falling out of the sky when switching to Alt Hold or now Loiter.  Any help would be appreciated.

 

Adam

DeveloperPermalink Reply by Randy on March 26, 2012 at 4:39pm

Adam,
That should be fixed in 2.5.3. If you have logs i can take a look.

ModeratorPermalink Reply by Adam AKAV8R on March 26, 2012 at 4:59pm

Randy, Thanks for the update.  Let me run this by you,  When I updated my mission planner yesterday I then updated to the latest arducopter firmware then loaded the param file.  Do I need to worry about the Throttle_trim setting in the param file or is what your saying that the copter will self adjust as you fly to the proper setting?

DeveloperPermalink Reply by Randy on March 27, 2012 at 7:02am

As long as you fly around for about 10 seconds in hover it should be ok to not bother updating the throttle trim value.

ModeratorPermalink Reply by Adam AKAV8R on March 27, 2012 at 7:33am

Got it thanks Randy!

• ‹ Previous
• 1
• 2
• Next ›
• Page