Arducopter 2.7.2 is now in the mission planner and in the downloads area Some positive reports on testing can be found in this discusssion by John Hanson.

Note: just as the release was going out an issue was found re support for the all Camera Gimbals on the APM1s (it doesn't work) and with 3 axis gimbals on the APM2 (2-axis works ok but not 3).  If you're one of these people, please wait for 2.7.3 which will be out shortly. 

 

UPDATE: 2.7.3 is now in the Mission Planner

 

Functional Improvements over 2.7.1:

  • Fast waypoints (Jason) - if the turn angle between two waypoint the copter is less than 60 degrees it does not slow down
  • Navigation improvements and logging including switching to filtered location for distance calculations (jason)
  • Flip improvements - more aggressive and flexible flip code based on attitude instead of timing (Jason)
  • Improved camera control - you can now control any axis (roll, tilt, pan) with any rc channel.  it probably makes most sense that you will use 6 but others are possible too.  Unfortunately these changes required we change the set-up procedure so the mission planner gimbal set-up screen needs to be modified again.  Please refer to the AC_Camera wiki page for how to manually set-up the gimbal (Amilcar)
  • Flybar acro mode for TradHeli (Robert)
  • "Fast gains" - allows strong correction of attitude using accelerometers while the quad is stationary on the ground but relies more on gyros while flying (Tridge, Jason)
  • Baro filtering improvements (Tridge)

 

Bug Fixes:

  • DMP timing fix (Randy) - the MPU6000's dmp unit was inadvertantly turned on and caused timing delays in the main loop- xbee bricking issue (Craig / Tridge)
  • Dataflash fixes (Jason)
  • Engine ticking - was a combination of roll/pitch rate D term being too high and the dmp timing fix above (Randy, Emile)
  • Faster heading correction on start-up - resolves issue with simple mode getting incorrect heading if you took off very soon after start-up (Tridge)


Code Cleanup:

  • Increased maximum number parameters (Tridge)
  • Formatting changes to code (Pat)
  • Replaced "int" with "int16_t" everywhere (Randy)


As per usual PIDs are optimised for the 3DR/Jdrones quad with 850 motors and 10" props. If you're using more powerful motors/props and are seeing bad flight behaviour in stabilize, start by turning down Rate Roll P in 25% steps.

There is still some question on whether the default Roll/Pitch Rate P (0.175) is high enough (it was 0.185 in 2.7.1) and also some people feel the Throttle Rate should be higher (currently 0.300 but some say 0.330 or even much higher would be better).

Please feel free to report issues you find in the discussion below and/or add them to the issues list.

Thanks and enjoy!

Views: 52777

Reply to This

Replies to This Discussion

AHA!

Found my problem.  the servo cable from the Rx to the APM for CH-6 was backwards.

so, Dani - which parameters should I tune first to match your ALT-hole performance?

Also check your compass calibration/declination. If these are off it is always heading in slightly the wrong direction and this can end up in a diverging circle. 

Hi Stephen,

as stated in the wiki FAQ: "My copter increasingly swings up and down in alt hold. It eventually get's down to the ground: Your THROTTLE_P is too high or low. You don't need a lot of P to do alt hold. Think of how much you move the throttle to hold alt perfectly. Not much! That's what you need P to do. I will ramp up as your battery goes lower to make up the difference."

In my case I lowered the THROTTLE_P.

Just play with it.

Dani

Thanks Dani.  I really do appreciate your assistance and advice.

I did use the Wiki for reference, but there is no "THROTTLE_P" in any of the MP screens.

I did set CH6 to "CH6_THR_HOLD_KP".  The CH6 knob changed the "Altitude Hold P" in the ArduCopter Config Screen.  It also presented as "Altitude Error" in the "ArduCopter Pids" screen.  And in the "Parameters List" screen it is the "THR_ALT_P" parameter.

Can you see why this is confusing to someone not intimate with the software?

On the ALt-Hold mode, I was able to tweak the above parameter (CH6_THR_HOLD_KP, Altitude Hold P, Altitude Error,or THR_ALT_P.  Pick one as they all appear to be the same parameter), and I got the ALT-Hold mode where I am happy.  

I am not afraid to tweak other parameters, but figuring out which parameter name to tweak is not trivial when they all go by different labels.

Guys need help over here: http://diydrones.com/forum/topics/apm-2-5-level-gets-corrupted-logs...

looks like a bug or defect on APM 2.5 on the auto trim. please read and check the logs.

Need to know if this needs to be RMA or just waiting for code fix.

What should the LAND flight mode do? Should it just descend and land wherever the Quad is? Is it at all tied to GPS?

Good question, Ive only tried it when included in an autopilot mission plan. I went to look it up in wiki, but its not listed in the flight modes which is strange.

http://code.google.com/p/arducopter/wiki/AC2_ModeSwitch

I would assume that because its an auto pilot functions it would be using the GPS and probably in combination with the barometer. Just my guess though.

You could probably test if by turning off the GPS and then see if "Land" will make it land using the barometer only.

I've played with the land mode a few times - It slowly drops the copter until it's on the ground. I've got a hexa and have had it hop after touching the ground 2-3 times before settling, so I haven't played with adjusting it yet.

I have a sonar installed, and have been told in the past that it uses the mix of baro and sonar (if available)

I would happily update the wiki if we can get some more info about its' function..

That's what I expected it to do. Maybe I have something set incorrectly, but while it usually does what you describe, sometimes, it actually seems to send the quad upward. Very weird.

Have you had it hovering when switching to land? If it doesn't start from hover, it wont know what throttle value to start reducing from..

Usually, I am going from alt hold to land ( because I have trouble judging descent rate visually). It seems to mostly work when down low, but often when higher up, it seems to want actually go up.

In the code of do_land function, there is a call:

   set_next_WP(&current_loc);

so as I understand it makes loiter with descent.

Reply to Discussion

RSS

Groups

Season Two of the Trust Time Trial (T3) Contest 
A list of all T3 contests is here. The current round, the Vertical Horizontal one, is here

© 2019   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service