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
Congratulations to all the people involved in this release!
Will there be support for *12 configuration (Coaxial Hexcopter configuration) in future releases? I think this option is a possibility on the pixhawk?
Is SBus RSSI input 0-5v working with 3.2 and the pixhawk?
How about PWM RSSI?
Matthias' notes will get analog working for you.
I don't think we support PWM RSSI yet.
@Matthias,
Thanks for the fix. I've updated the parameter description so hoepfully it'll be easier for the next person (once the mission planner next picks up the parameter value changes)
http://copter.ardupilot.com/wiki/common-pixhawk-overview/
Virtual Pin 103: RSSI (Received Signal Strength Input) input pin voltage (SBus connector output pin). This is the voltage measured by the RSSI input pin on the SBUS-out connector (the bottom pin of the 2nd last servo connector on the 14 connector servo rail).
Modify RSSI_PIN to 103
http://copter.ardupilot.com/wiki/arducopter-parameters/#Receiver_RS...
Modify RSSI_RANGE to 5.0
http://copter.ardupilot.com/wiki/arducopter-parameters/#Receiver_RS...
Just tested Hybrid mode, as a NAZA and APM flyer I am so happy its coming...but...
I started in Stabilize, flew a bit, flipped to Hybrid and my TBS Pro darted off across the street, I put it back into stabilize and it came home, no crash but a little scary. Glad it headed away from me and not towards me :-) In my NAZA if GPS(Hybrid) does not have enough sats it simply defaults to Alt-Hold then auto switches to GPS mode when all the sats have been captured, not saying thats the issue but just not sure what it is.
TBS Disco Pro, APM 2.6, 3dr gps, 3.2 rc1
I know wheres the log. I tried, but it wont come up with the option, see screenshots
HDOP was okay
You can also see where it took off when I changed to mode 16 (Hybrid)
We can see here the Copter rolls away its target position instead of maintaining it.
You had no stick Input and the GPS was great so, maybe, check a compass issue.
If the copter thinks he's goind to North but actually flies to South, that could, imo, bring that kind of behaviour.
Please give another try to hybrid and also Loiter.
Check as well your param values.
-
362
-
363
-
364
-
365
-
366
of 373 Next