Version 2.6 of the ArduCopter code is now available in the AP Mission Planner and in the downloads area!
Updates to MavLink 1.0 means you will need to use "ArdupilotMegaPlanner10.exe" to connect. If you've updated your mission planner recently you should find this executable in the directory where the mission planner is installed.
The above video is done using a prototype 3dr ublox GPS which seems to have better accuracy than the standard mediatek.
Improvements over 2.5.5 include:
- MavLink 1.0 support (use with ArdupilotMegaPlanner10.exe) [Tridge, Craig]
- Stability improvements especially during level hover [Jason]
- throttle range improvement (higher min and max) [Jason]
- improved standard Loiter PIDs [Alan, Heino, Jason, Angel]
- dataflash erase speed up ('+' messages removed but it only takes 6 seconds now) [Tridge]
- Copter LEDs [Robert Lefebvre]
- RTL loiter stage target set to home to improve final landing position [Jason]
- flip & acro improvements [Jason]
- circle mode target improvement for ground station [Jason]
- Auto Approach [Adam Rivera / Marco]
Bug fixes include:
- UBLOX driver fixes (lock should now be more reliable) [Tridge]
- enable mavlink messages during dataflash erase which resolves issue in which new APMs fresh from the factory appeared unresponsive [Tridge]
- proper printing of lat/lon values in dataflash logs [Randy]
- removed duplicate GPS reads [Jason]
- resolve flooding of telemetry link with low-battery warnings [Tridge]
- RTL bug would land if rtl_approach_alt was more than 1 [Jason]
- WP Radius could not be set larger than 1.3m [Jason/Randy]
Tuning:
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.
This time we spent some time optimising the loiter PIDs. Tuning loiter can be tricky so please refer to the discussions which will appear below for more community feedback on what parameters work best.
All feedback welcome below. Enhancement requests and bug reports can be put into the arducopter issues list. When possible please include logs (tlog and/or dataflash) and tell us whether you're using APM1 or APM2 and what version of the software you're using (presumably 2.6 but tell us anyway!).
Happy flying!

Also, I believe Auto Approach is new in this release as well (courtesy of Marco and myself).
Adam,
Oops! sorry about that. Added above!

Courtesy of you, Adam... thanks! :-)
Permalink Reply by hemanthtguru on June 17, 2012 at 12:40am I have ublox GPS; but how do I connect to a APM 2 which already has a GPS on it....
I am hoping to get the same accuracy of the demo videos done by randy

Permalink Reply by Michael Pursifull on June 17, 2012 at 1:06am hermanthtguru: see http://diydrones.com/forum/topics/jumper-s-for-apm2-onboard-gps
Permalink Reply by hemanthtguru on June 22, 2012 at 2:14am where can find description about Auto Approach; or can some explain it here
Permalink Reply by Derek Ernewein on July 9, 2012 at 6:19am No one seems to be answering, so I'll do my best...
From what I can find it is to do an automatic approach to a specific height before a manual landing.

Permalink Reply by Michael Pursifull on July 9, 2012 at 1:34pm Hope this helps ... The code sets the designated approach altitude. It tests to be certain that we're not below the target approach altitude, otherwise it just loiters. It heads for the designed approach altitude while holding the current waypoint location. There are a few other sanity checks. You can review the code here for yourself to interpret what happens:
static void do_approach()
{
// Set a contrained value to EEPROM
g.rtl_approach_alt.set(constrain((float)g.rtl_approach_alt, 1.0, 10.0));
// Get the target_alt in cm
uint16_t target_alt = (uint16_t)(g.rtl_approach_alt * 100);
// Make sure we are not using this to land and that we are currently above the target approach alt
if(g.rtl_approach_alt >= 1 && current_loc.alt > target_alt){
wp_control = LOITER_MODE;
// just to make sure
land_complete = false;
// landing boost lowers the main throttle to mimmick
// the effect of a user's hand
landing_boost = 0;
// A counter that goes up if our climb rate stalls out.
ground_detector = 0;
// hold at our current location
set_next_WP(¤t_loc);
// Set target alt based on user setting
set_new_altitude(target_alt);
} else {
set_mode(LOITER);
}
}

Permalink Reply by Michael Pursifull on July 9, 2012 at 1:41pm If you've got a good approach alt set, and a loiter timer set, then you'll be interested in this bit from ArduCopter.pde.
if(loiter_timer != 0){
// If we have a safe approach alt set and we have been loitering for 20 seconds(default), begin approach
if(g.rtl_approach_alt >= 1 && (millis() - loiter_timer) > (RTL_APPROACH_DELAY * 1000)){
// just to make sure we clear the timer
loiter_timer = 0;
set_mode(APPROACH);
}
// Kick us out of loiter and begin landing if the loiter_timer is set
else if((millis() - loiter_timer) > (uint32_t)g.auto_land_timeout.get())
{
// just to make sure we clear the timer
loiter_timer = 0;
set_mode(LAND);
...

Mike: Thanks for picking up the slack here. This code has changed a bit in trunk since 2.6, but the functionality is the same. The loiter_timer var gets set automatically after a successful RTL. loiter_timer is not user defined. All the user needs is an APPROACH_ALT defined and it will descend to that altitude after the RTL has completed.

Derek: Sorry about that. I will be documenting it in the Wiki after our next minor release. The auto approach code has changed since this release, but the functionality remains the same. The idea is that if you have an approach altitude set between 1 and 10 meters, the copter will descend to that altitude after RTL instead of landing. This was added because some people do not trust auto landing on their bigger copters or for expensive AV equipment. I hope that helps!

yeah! soldering and testing boards for customers right now! this will be a lucky one!
pushing 2.6 on this one for tests! happy!!!
Will try to give it a flight test this weekend and report here as usual.
Dany
Season Two of the Trust Time Trial (T3) Contest has now begun. The fourth round is an accuracy round for multicopters, which requires contestants to fly a cube. The deadline is April 14th.693 members
1298 members
7 members
48 members
24 members
© 2013 Created by Chris Anderson.
Powered by
