ArduCopter 2.7 Released!
In just a short while, ArduCopter 2.7 will become available for download in Mission Planner. As we worked on ArduCopter 2.6.1, we saw that it had several new and compelling features (as well as many bug fixes and improvement) so it was decided to make this a major version release.
A full list of changes is here, but they include:
New and Improved:
- NEW: 3-axis camera stabilization
- NEW: AP_Limits library: Altitude limits and geofencing.
- NEW: Automatic Flip (Roll axis) is now enabled on Channel
- NEW: GPS lag estimator
- NEW: the quad first rise vertically to the "ALT_HOLD_RTL" altitude (if declared) when engage RTL
- Better altitude control in ALT_HOLD and better altitude transitions
- Better loiter, rtl and auto missions, especially with the new 3DR uBlox GPS. Check out my video above!
- Better yaw control
- Better DCM implementation, resulting in noticeably smoother flight
- Better velocity control in Auto missions
- Etc
Bugfixes:
- Fix to dataflash erasing, which should resolve an issue some users were having
- Fix some MAVLink commands
- Fix Circle command
- Fix some units
- Etc
Notes:
Cheers,
Marco
Replies to This Discussion
-
Permalink Reply by Manfred Dickgiesser on -
Thanks for the answer, Marco.
I have no autodeclination or auto compass calibration.
I placed an issue concerning the compass.
But is there any way to increase the sensor sample frequency concerning the problem with the vibration and resulting aliasing, attitude drifts?
-
Permalink Reply by Alex on -
Hello
I have a problem in the APM1. In firmware 2.7 reversed the tilt axis of gimbal. On the 5th exit (Pitch) Servo reacts to the deviation of the axis Roll. And on channel 6 (Roll) Servo reacts to the deviation Pitch. In firmware 2.6 all fine. In what may be the problem? Thank you.
-
Permalink Reply by Jim Kahl on
-
I'm having a similar issue with the APM2. If I move the copter in either pitch or roll, my gimbal reacts in both pitch AND roll. The gimbal reacts as if the quad is set like a +, even though I'm configured as an X. The motors act just as they should in an X configuration. This happens in both 2.7 and 2.71. It worked very well in V2.6. In addition Geofence has all sorts of stuff greyed out in the Mission Planner since V1.20 of the planner. Geofence setup seemed to work in 2.7 until the planner update came along. I'm still bench testing, and it's quirky enough that I'm afraid to fly it yet.
-
Permalink Reply by Jim Kahl on
-
Gimbal issue resolved. I had to set the MNT_STAB_YAW parameter to 0. It had defaulted to a 1.
-
Permalink Reply by Jeff Milay on -
Same issue here as well. What I noticed is, If I go into "Camera Gimbal" settings, it sets my default MNT_STAB_YAW to 1. If I go to "Parameter List" and set it to 0 (write parameters) it will stay. But if I go right back to "Camera Gimbal" it will reset it back to 1.
-
Permalink Reply by estebanflyer on -
nothing fixes the pitch and roll mixup in mine... i follow the parameters list changes, tried with yaw at 1 or 0 and it still mixes the axes... I am clueless
-
Permalink Reply by Jeff Milay on
-
Esteban, when you change MNT_STAB_YAW in the Parameter List to 0 and write parameters, move the copter around and let us know how it reacts immediately after doing that.
-
Permalink Reply by estebanflyer on
-
Hello Milay! Thank you for replying and helping out.
When I change MNT_STAB_YAW to 0 nothing happens. I tried combining this change with CAM_Y_FUNCTION to 0 or to 1 but nothing changed.
Another observation: If I disconnect any of the two channels, leaving only one connected, this channel works fine. As soon as I connect the second channel back, they get crossed. This way, I'm never able to get pitch and roll right, they are always mixed.
I hope I explain myself good enough: I have ch5 connected to pitch and ch6 connected to roll. If I disconnect ch6, the pitch servo moves responding to pitch, which is right. As soon as I connect ch6 they get mixed. It's as if the problem comes when I connect both channels at the same time. Both channels run fine by themselves.
-
Permalink Reply by Jeff Milay on
-
I noticed this same issue as soon as I went to 2.7. It took an erase and reset. Then I reloaded 2.7 and all worked perfect. Give this a try and reapply your parameters and hopefully you will be rockin'!!!
-
Permalink Reply by estebanflyer on
-
i tried that twice.....
-
-
Permalink Reply by Jim Kahl on
-
After changing the MNT_STAB_YAW parameter to 0 - do NOT go back to the Geo Fence menu again. If you do, it will flip the parameter back to 1 again. If for some reason you do have to go back there, finish up by then going back to parameters and flip it back again. Better yet, until it gets fixed, make all of your Geo Fence parameter changes in the parameters menu. Don't forget to hit write parameters after entering all of your changes.
-
Permalink Reply by estebanflyer on
-
I'm not touching geo fence. Do you mean Camera Gimbal?
Social Networking
Top Content
Contests
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.A list of all T3 contests is here.
Groups
-
Moderators
24 members
-
Japan ArduCopter Group
58 members
-
ArduCopter User Group
1355 members
-
ArduRover User Group
207 members
-
Documentation Editors
52 members
Advertisement
© 2013 Created by Chris Anderson.
Powered by
