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
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!
I'll relook at vibrations. I've been using the Copter 3.3 Vibration tool in mission planner. I'd assume that motor bell slop would show up as vibration.
Looks like a tlog, if you've got a dataflash log I'll take a peek at it. If it really is baro noise, then it's a known issue on the to-do list here but there's no guarantee we can do anything about it in software actually. The best solution is a physical change to the frame. Here's the diydrones discussion on this topic.
I'd greatly appreciate it. What I notice is a very noisy IPD which looks to be caused by a very noisy baro. At least in comparison to the wiki.
Using the 3.3 vibration tool it looks like my vibrations are acceptable.
Here's the .log:
It would and mostly the Z axis
I think the issue you linked to is a "Climb" issue and his is a "drop" issue. I've always had a climb issue since back in the old APM days and not just APM but even my old MultiWii boards. And to be honest. I have always kind of liked it :)
yes, your vibs looks good, It's look different than my vibes problem
Hey guys, I have a Y6 running 3.3.2 and today I decided to test its max carrying capacity, by adding about 3kg payload bringing total weight to about 8kg, it was flying fine with 6-7kg I designed it to carry, however at 8kg It constantly wanted to rotate CCW. I've checked RCOut logs and it looks like motors 2,4,6 were at 1700, while motors 1,3,5 were at 1400. Does it suggest that I should be runni g bigger props at motors 2,4,6?
This is actually a really interesting question. You need to increase the drag for a given RPM. Increasing the diameter of 2, 4, and 6 may do this. But with the interaction of the upper and lower props it is very hard to say.
So a long story short, I don't know but I am really interested to hear what happens when you try different things. You can increase the pitch on the lower props, you can try increased diameter on upper or lower props, or you can increase the CV on the lower motors.
Let us know how you go!!!
Thanks leonardt, I've ordered a few 1655 cf props from china, will test with both - upper and lower. Btw, did you mean KV (CV)?
The scarse info on coax setups I was able to find suggests that lower props should have larger diameter. Inceasing the pitch is usually not enough.
I'm have a bit of an issue on my 960 hex with inconsistent compasses. It shows up on pre-arm quite often and requires several compass calibrations to settle in regardless of where it is or if it armed previously at that location. Compass offsets are always different every time I calibrate and below 400. The setup is the same as my 550 quad and my 690 hex that have remained set unless I change hardware. The only difference is that I have doubled the distance of external compass to airframe. This thing has 3 to 4 times the power draw as the little guys so I expected it to be more sensitive but I'm getting tired of doing the calibration dance with such a large, heavy partner. It always flies perfectly in loiter or position hold once armed. To be clear, when looking at compass offsets on the parameter list, is compass 2 the external and "compass" the internal? And would COMPASS_LEARN be something to try?
Pixhawk, Zubax GNSS module