Warning #1: PX4/Pixhawk users upgrading from AC3.1.5 (or earlier) may need to re-do their compass and accelerometer calibration because AC3.2 also uses the backup compass and accels. Pre-arm checks have been added to ensure this has been done.
Warning #2: on the APM2.x the logs must be downloaded using MAVlink instead of the terminal.
AC3.2-rc14 is now available for BetaTesters through the mission planner’s Beta Firmwares link. The full release notes can be found in ReleaseNotes.txt and changes from -rc13 can be seen below.
Feel free to raise issues found during testing on this discussion or in the new support section in the APM Forum.
It’s a big release with “the onion” restructure and a bunch of new features (including these 57 closed items) so we need to re-test almost everything including all flight modes, all mission commands and all the new features. Marco and I will be maintaining (and adding to) this testing list. Issues reported will first be checked by Jonathan, Marco and I and then confirmed bugs/issues will be put on the github issues list (and then hopefully fixed).
Thanks especially to the beta testers who put their copters at risk testing each release. Enjoy!
Changes from 3.2-rc13
1) Safety Features:
a) fail to arm if second gyro calibration fails (can be disabled with ARMING_CHECK)
2) Bug fixes:
a) DCM-check to require one continuous second of bad heading before triggering LAND
b) I2C bug that could lead to Pixhawk freezing up if I2C bus is noisy
c) reset DCM and EKF gyro bias estimates after gyro calibration (DCM heading could drift after takeoff due to sudden change in gyro values)
d) use primary GPS for LED status (instead of always using first GPS)
Replies
Head up about tricopters, i have already found the tail rotor has so much yaw authority that motor direction does not matter, slap on whatever props you prefer as it will still fly very well, you don't have to adjust yaw pids but can increase them if you feel any effects from using the same rotation on all motors.
During this maneuver tricopter yaws CCW about 15° than corrects. Also, during automissions, during discend, copter would rotate CCW then autocorrect.
+1
Perhaps the best of both worlds is to make the tail rotor rotation a parameter that defaults to CCW, but can be changed to CW if you have the props?
Like: INV_TAIL_ROTOR=0 -> CCW | INV_TAIL_ROTOR=1 -> CW
Artem,
Do you mean the mot-spin-when-armed feature or the throttle feedback before take-off in alt-hold, loiter and pos-hold?
I've had a look at the Tri mixer and it doesn't appear to use the yaw with any of the motors. The yaw is only applied to the tail servo. So really, there's no requirement to make any of the motors CW or CCW in particular.
Hi Randy,
I believe (correct me if I'm wrong Artem) that he means the use of motor spinning torque as means for yaw (like on quads). Is it correct that arducopter uses that even on tricopters, where yaw should be done by the tail servo? Otherwise, why the requirement for CCW tail motor on tricopters?