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
(I have 2 APM's and 2 PixHawks on quads)
Thank You?
http://copter.ardupilot.com/wiki/table-of-contents/
Everything you need is on this site. Go to "ArduCopter" menu and it will drop down with locations of interest.
I'm pretty sure this is related to the accel limits that have been added. I think it will be more responsive when -rc3 goes out which should be within the next 24h. Until then you should be able to increase the ATC_ACCEL_RP_MAX and ATC_ACCEL_Y_MAX. Doubling them should be no problem.
Christian,
did you tried the Turnigy dlux ESC? seems to do a nice job. I did add opto isolation to separate power / noise and sensitive electronics. Seems ok. Standard software on the Dlux 70 A
Christian,
I guess you were thinking of this quad? LOL (see photo)
medium-Quad-1.jpg
i think all those fine tuning the PIDs of copter must put a dummy load of gimbals + camera before they begin tuning. the PIDs would be different with and without camera specially THR_MID and to some extent roll and pitch P because the expected camera weight being below the CG of craft. this would save a repeat of tuning flights after installing camera and gimbals.
Sounds like your THR_MID may not be set right with the added weight of the gimbal and camera. Might be worth a shot to tinker with it. Instructions here: Setting Throttle Mid
Randy,
I saw have some problem about message is "Bad Gyro Health" on Mission planner is every time when first armed only with 3.2-rc2. I don't know it is a bug or not? But, I still can nice flight is no problem.
Alright, just had an interesting experience. Still shacking a bit ;) Mostly my own fault i suppose. I was manually pid tuning my new build with the micro VR brain 5.1 and 3.2rc2. Kalman filter on. I had just altered some settings and armed the quad. After a few seconds it shot up. I had no more control. It then landed but the motors where still turning. I tried to disarm to no avail. It then decided to take of again and fly a bit around the house at an altitude of about 8 meters and finally crashed on the roof. I had tried to put it in Loiter while this was happening. I took a look at the logs and well it is my fault i guess. It seems i lost RX and it tried to go in RTL mode. I was inpatient and armed to fast without GPS lock it seems. Now the strange thing is that my arming check parameter is set to Enabled. I was under the impression that this should disable arming until a valid 3Dfix.
Also, take a look at my altitude reading. Is this correct? I did put foam on the baro but the board is mounted without a case so it is also possible that there is still prop wash getting into the barometer.Anyway, lesson learned that i should always do a range test. Even if the RX has been used successfully on another model.
Second lesson learned. I should not rely on prearm checks for GPS lock. Btw this build is an acro Quad without telemetry radio but it has a Lea6 gps and a compass.
Please take a look at my logs to see if my analysis is correct.
2014-07-11 14-36-48 7.bin.log
-
209
-
210
-
211
-
212
-
213
of 262 Next