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

I have attached a few log files. Looking into rerouting power to the motors, cleaning up the installation, looking in to metal work, etc, as well.


Well, it's been a while since I've hijacked a thread, and since I am currently very happy with APM and 2.7.4 and the upcoming fixes I thought I'd go way off topic, just to keep you entertained... 

Although I suppose it is on topic cause next time I'm swapping the naza for an apm :)

Leave it escape, you have it poor beast locked in four walls


   Is anyone else having problems assigning channels for gimbal servos.? I'm using apm2 and the latest code from the mission planner.

  I'm don't want to use channels 10 and 11 as i believe they are limited to 50hz whilst all the other channels will go to 490hz(hope this is right?)

  Anyway i've tried changing them from the gimbal set-up page and the parameters list, but the servos only work when they are assigned to 10 and 11! (and seem very slow)

   Any help would be much appreciated, i want to use high speed digital servos on my new quad

   It's an interesting design I've got high hopes for, i recommend a look!

  Thanks all, looking forward to flying this new code!

Very interesting design, using the battery to counterbalance the camera.  But that looks like an awful lot of mass for a servo to handle.

Muse/madness - good stuff for this type of footage.. :)

Christian would you please post your dataflash .log file for this flight.  Thanks

MTEK 3329 

Where do I get this?

Hey all, 

Didn't want to start a new thread for this as it's a very basic question, but what is the variable used inside ArduCopter to find the current roll angel?

The one that shows as 'roll' under APM Planner. 


(Also is there an easy way for me to determine what the variable names are inside the ArduCopter code based off their description is in the APM Planner (i.e. somehow seeing the APM Planner code to determine what they are calling to find the value)?

This type of cardan must use two independent gyroscopes for better result.

Standard upgrade balance PTZ,with 2 axis Gyro structure,(needn't control by flight control board,1 single axis gyro or dual axis gyro is ok

Dave I read that the best is the top motors spin at 93% of the bottom motors. This was taken from and extensive study NASA did in the 60 to 70 on coaxial prop affect. What I did was use 800kv motors on top and 880kv on the bottom. It did seem to work better.

Reply to Discussion



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