After months of testing by the beta-testing team and no significant issue during the soft release, Copter-3.3 has been released. You can load this version onto your vehicle using the Mission Planner or APPlanner2's Install Firmware screen.
As mentioned previously, this version and all future versions of Copter only work with fast CPU boards like the 3DR Pixhawk (and compatible) boards, VRBrain, NAVIO+, etc. Slower CPU boards (i.e APM2.x) can continue to load Copter-3.2.1 from the MP/AP2.
Support issues should be reported in the APM Forum. Enhancement requests and confirmed bugs should go into the GitHub issues list. The wiki has been mostly updated but if you spot missing items please report them to the wiki issues list.
The full set of changes can be seen in the Release Notes but the highlights are below.
Known Issues/Warnings:
- users will need to re-calibrate their accelerometers because of 5c (accelerometer range increase).
- FrSky telemetry users must set SERIAL2_PROTOCOL to "3" and reboot the board to enable FrSky telemetry like in previous versions
- this version corrects a long standing issue in the HDOP reporting so values will appear about 40% lower than previously but this does not actually mean the GPS position is better than before.
- TradHeli is still in beta testing so it remains on AC3.2.1 for now.
Changes vs Copter-3.2.1
1) EKF replaces DCM/InertialNav for attitude and position estimation which provides more feedback and robustness in case of sensors failures
2) Control improvements:
a) battery voltage compensation should maintain control as voltage drops
b) current limiting can be used to reduce the maximum current requested to reduce strain on battery and ESCs
c) air pressure compensation should reduce need for re-tuning when flying at different altitudes
d) improved throttle curve should reduce wobbles during descents
3) AutoTune for yaw
4) Cameras & Gimbal improvements:
a) SToRM32 gimbal support
b) do-mount-control mission command allows controlling absolute camera mount angle during missions
5) Vibration resistance:
a) real-time reporting of vibration levels by clicking on Vibe field on HUD (also recorded to logs)
b) noise weighted average of accelerometers used to weight IMU towards the one exposed to less vibration
c) accelerometer range increased from 8G to 16G to allow use in higher vibration environments (i.e. reduced "clipping")
6) Other:
a) improved landing on slopes
b) retractable landing gear support
c) channels 9 ~ 12 can be used as auxiliary switches (like ch7, 8)
d) PX4flow (optical flow) support in Loiter
e) Brake flight mode (stops vehicle quickly but requires GPS)
f) allow GPS, Telemetry, SToRM32 gimbal to be connected to any telemetry/serial port
g) Lidar-Lite V2 support
h) bug fix to RCMAP - remapped channel's MIN, MAX were taken from incorrect parameters meaning all channel ranges had to be the same
7) Tricopter tail servo parameters (MOT_YAW_SV_MIN, MAX, TRIM, REV)
8) Safety items:
a) crash check triggers with 30deg lean angle error (for 2 sec) even if pilot's throttle is non-zero
b) modified pre-arm checks to ensure good quality GPS and compas data
c) lost copter alarm (hold both sticks down and right)
d) motor interlock & emergency motor stop features on auxiliary switches (ch7 ~ ch12)
e) RTL_CLIMB_MIN parameter allows forcing vehicle to always climb a few meters at beginning of RTL
f) LED flashes green quickly if disarmed with 3D lock and SBAS
Thanks to Marco and all the beta testers who risked their vehicles so we could iron out issues and ensure a more reliable firmware for the wider community. Here are some of their videos:
ChrisN #1, #2, Paul Atkin #1, #2, #3, Gervais #1, #2, #3, Gleb Falaleev #1, #2, Pomaroli, Michael, Robert Baumgartner, De Le, Robert Baumgartner, Robert Navoni, Maciej Karpinski
Comments
@TriTran, no need to recalibrate anything is upgrading from Copter-3.3.
Did it work earlier or is this first build? Is Mission Planner HUD NORTH real NORTH compared to handheld physical compass reading? It should be real NORTH and when you turn copter to pointing real EAST should HUD show pointing EAST as well.
For first build and if heading test above is not correct I'd recommend start to investigate compass orientation. Some compass modules don't show forward arrow therefore correct direction must be set on Mission Planner manually. One way is to investigate your module orientation which could be challenging or alternatively by trial and error. Just pick one on the list (start from top of the list) and try compass calibration as many times until NORTH is real NORTH and its heading turns correctly. There are good instructions for calibration on Wiki which might save some time on calibration.
Randy
yesterday i fly with 3.3 fw. you're right, high vibration and take off and landing very faster, lose control. Maybe hardware issue ? problems with pixhawk ?
@triTran,
The IRIS with short legs has a "known issue" with high vibration especially if the little screws that attach the legs are screwed it so far that they bump into the motors. It's really a hardware issue instead of a software issue. I think you'll see the same thing happens with Copter-3.2.1. I'd expect Copter-3.3 to be better but in any case, use the long legs, I always do!
Hi Randy
My iris+ fly uncontrollable crazy with legs small. it was good fly with tall legs. what problems with it ? any idea sir ?
i'm running on a S900 with GPS M8n.
This is my log: https://www.dropbox.com/s/4h53o34qiit3maa/2015-10-26%2018-35-33.log...
I got some errors: EKF and Vibe are red in hud. And "error compass variance".
@Randy, dealing with odd situation. Have 3 Pixhawks and can not connect to MP in flight data screen. Parameters get stuck loading BUT I can connect in initial setup or config-tuning. Same issue on all 3! Any ideas?
@Henri, yes, so that's really the MP perhaps not knowing which board you're using or it doesn't use that knowledge to display which version is actually available. I tested it a couple of weeks ago and in the end, it actually uploaded Copter-3.2.1 to my APM2.6.
-
1
-
2
-
3
-
4
-
5
of 9 Next