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
Stuart
Hi stubugs,
thank you for your answer.
Can you share your param please, so i can see if there something is wrong.
My tarot 650 has 380Kv 15x5,5 @6S4000 with rtfhawk and NEO-M8N GPS with HMC5983 from CSG.
Thanks
Sven
heres my para but my 650 has a 4s 8000 390kv motors with 17 inch props
stuart
dpixhawk.rar
heres my para but my 650 has a 4s 8000 390kv motors with 17 inch props
stuart
dpixhawk.param
I have a new tarot 650 too with rc12 yet, I do autotune and correct stab pitch and roll a llittle and good results, today y try with strong winds and fly well, less stable than calm day but firmly; I have 460kv motors and 15*6.5 cf props and 3s batt, but few test yet; try autotune it's great
Hi Cala
i have tried a autotune a few days ago.
link
But it does not work properly.
sven
Hi
today i have test a few things to get the Tarot fying well.
First i have done load the autotune parameter from rc13 flight. Then i do some Rate Roll P mod with CH6 to get good parameter. The second thing i have tried, is setting up the GPS/ Compass modul higher to reduce MAG interference. Now it is 10cm away from the hawk and 14cm away from the ESC and ESC cable.
Flying in Stab and AltHold is ok Altitude is a little bit unstable, but it was verry windy today.
But when i switch to PosHold Mode the copter drift away like beginn of toilet bowling. I have no Idea what i can do now. Mabay could it be a GPS or HMC5983 Problem?
Are they really full supported by 3.2 rc14?
Here is the latest log where i try poshold a lot of times.
Hope someone can help.
Regards
Sven
might be the compass is in the wrong orientation, I had that problem with my external HMC5983. and it toilet bowled to the ground a year ago.
If its in the wrong direction you do not have to move it but can use a COMPASS_ORIENT param. etc
I have a value of 8 which is Roll180 altho I have PX4 (sensor upside down) and not a Pixhawk
Check the HUD in MP and see if it follows correctly.
I have not analysed your log tho.
Did you have telemetry? Just curious if seeing the correct compass heading in the HUD is a way of confirmation the orientation is correct. It would seem so..
Here is the Logfile upload was not ok
2014-11-02 16-52-49.log.zip
-
72
-
73
-
74
-
75
-
76
of 373 Next