Warning #1: an issue has been found with Tower's Pause button which can cause the vehicle to fly to an old position if the vehicle has not sent a position update to Tower in some time.
Warning #2: Copter-3.3.2 fixes a bug found in Copter-3.3.1's desired climb rate initialisation which could lead to a sudden momentary drop when switching from Stabilize or Acro to AltHold, Loiter or PosHold.
Warning #3: Copter-3.3.2 fixes an issue found in Copter-3.3.1 which could lead to hard landings in RTL or AUTO if the WPNAV_SPEED_DN was set too high (i.e. >400 or 4m/s) and/or the WPNAV_ACCEL_Z was set too low (i.e. <100 or 1m/s/s).
Warning #4: a bug was found in Copter-3.3 which could cause a sudden crash if you abort a Take-off initiated from a ground station. Video description is here. The bug is fixed in Copter-3.3.1 so we recommend upgrading.
Note #1: AC3.3-rc8 corrected a long standing bug in the HDOP reporting. HDOP values will appear about 40% lower than previously but this does not actually mean the GPS position is better than before.
Note #2: if upgrading from AC3.2.1 the vehicle's accelerometer calibration needs to be done again.
Note #3: set SERIAL2_PROTOCOL to "3" and reboot the board to enable FrSky telemetry like in previous versions.
Note #4: the wiki will be updated over the next few weeks to explain how to use the new features
Copter-3.3.1 is available through the mission planner. The full list of changes vs AC3.2.1 can be see in the ReleaseNotes and below are the most recent changes since AC3.3.
Sadly this version (and all future versions) will not run on the APM2.x boards due to CPU speed, flash and RAM restrictions.
Changes from 3.3:
1) Bug fix to prevent potential crash if Follow-Me is used after an aborted takeoff
2) compiler upgraded to 4.9.3 (runs slightly faster than 4.7.2 which was used previously)
Changes from 3.3-rc11:
1) EKF recovers from pre-arm "Compass variance" failure if compasses are consistent
Changes from 3.3-rc10:
1) PreArm "Need 3D Fix" message replaced with detailed reason from EKF
Changes from 3.3-rc9
1) EKF improvements:
a) simpler optical flow takeoff check
2) Bug Fixes/Minor enhancements:
a) fix INS3_USE parameter eeprom location
b) fix SToRM32 serial protocol driver to work with recent versions
c) increase motor pwm->thrust conversion (aka MOT_THST_EXPO) to 0.65 (was 0.50)
d) Firmware version sent to GCS in AUTOPILOT_VERSION message
3) Safety:
a) pre-arm check of compass variance if arming in Loiter, PosHold, Guided
b) always check GPS before arming in Loiter (previously could be disabled if ARMING_CHECK=0)
c) sanity check locations received from GCS for follow-me, do-set-home, do-set-ROI
d) fix optical flow failsafe (was not always triggering LAND when optical flow failed)
e) failsafe RTL vs LAND decision based on hardcoded 5m from home check (previously used WPNAV_RADIUS parameter)
Thanks for your testing!
Replies
is your x2 modified with a "resistor mod" by any chance?
No, none mod.
mine is not.
in my opinion this 'mod' is very problematic as contact patch for soldering there is way too small for a mass of a typical non-integral resistor and it is just asking for a future trouble.
I flew with RC9 yesterday and have to say if is far more vibration resistant than RC8 was!
I know my quad is not the greatest example, but as it has issues that show up readily it is a good example of the softwares tolerance to user over sight.
Yes, I have ordered some of the HK orange foam and found that I have 2 motors with signifigant bell play, maybe the cause of the Z issues I have been having.
I have been having problems with uncontrolled climb out when ever speed increases with with both 3.2 and 3.3r8.
Yesterday with 3.3r9 I was able to fly as fast forward as the quad could go, right to the point of not having enough power to maintain altitude with out any uncontrolled climbing!
The quad was flying well enough to run an auto mission which worked with out any noticeable issue.
Loiter was better and alt hold also.
Attached is a log of both and RC8 and RC9.
2015-08-20 21-32-53 5.bin
2015-08-12 17-13-06 9.bin
Thanks Wes!!!
That is great news!!!
I think I found the smoking gun on my Z vibration issue. I had two motors with about 0.020 of bell play.
I copied leonardthall's motor pin press and removed the play. The results were dramatic!
The most improvement is seen in the RCO graphs.
Vibe also shows improvement.
IMU is telling.I read through the Arducopter pages and found no mention of bell play as a vibration problem. I think it would be worth while to add a note or two about it as the effect of play has a surprising impact on performance.
RC9 was able to handle this level of Z vibration acceptable while RC8 could not.
With the bell fix my quad is flying better than ever!
Sounds like invaluable information for the wiki. I'm looking forward to the good read.
Wes, I also had bad vibration issues on my 680 hexa and found just one of the motors to have a tiny bit of bell float /play. I used a vice and sockets to remove that play and as you have seen, the vibes are now within execrable levels. I reported it here: http://diydrones.com/forum/topics/pid-help-required-video-example
I agree on making it better known how bell play effects the vibes. Nice work on the clamp BTW!
Congratulations Wes!!!
I am sure that will be added to the Wiki. Your help here has been invaluable!!!