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
Steve,
I missed this message but here are some belated answers:
- the take-off command does not need a lat or lon set. these won't be used even if provided in the command.
- land accepts a lat/lon but it's not required. If you set them it will first fly to that location and then land there. If not provided it will land at the current lat/lon.
- you should be able to open up the mission's .txt file and change the regular waypoint command id "16" to the spline id "82". Of course I always do this through the mission planner's flight planner screen by changing the drop-down.
I've been flying quad following setup by ArduCopter3.2 rc9, EKF on and off.
After auto-tune in the calm weather, the quad becomes shaky.
Stability of position hold mode is incredible that almost no move, just 10 inch cubic error.
Motors: MultiStar #4108-600KV
Propellers: 14inch -carbon
FC: Pixhawk-original 3DR parts
Speed Control: MultiStar 45A / SimonK
LiPo: Zippy 4S-20C/3000
Fram: Based on Zion-enroute parts
Hi Randy, I have just upgraded to rc9 and now I am getting just Alt Disparity warning on arming and I cannot arm. What do I need to change to fix this?
ok, got it flying by deselecting EKF. It is only very random. It allows me to arm most of the time with EKF selected.
Tested, stab, loiter, pos hold and drift. All very nice apart from Drift as drift apples the brake sometimes during forward flight .
hi AC 3.2 user, i strongly suggest that you balance the props precisely. the difference is tremendous. the damping tapes are not well tuned to the frequency of vibrations (and resonance) which results in many type of errors.
I'm not shure if a issue, I program a radio swich to land with 3.15, I try and all works perfect, I try with my new Tarot650 and again good, today I change trottle params as you recommend to this vers as standard and when I try again, motors stop to spin, I try with the other cuad and same problem, can someone confirm this? or only I made a mistake, Thank's.
The new trottle params are better for my cuads thank's for all work here. :)
Cala,
Are you testing with AC3.1.5 or AC3.2? This thread is really only for AC3.2 beta testing issues.
I think you're saying that after adjusting the throttle parameters as they've been adjusted for -rc9 (i.e. THR_RATE_P to 5.0, THR_ACCEL_P to 0.5, THR_ACCEL_I to 1.0), the vehicle doesn't disarm when landing? It's very possible you're right. A person from 3DR reported the same thing and we looked into it and it was related. This was an attempt to reduce the jumpy throttle a couple of APM2 users have reported but it hasn't helped so if people are seeing landing problems we will probably revert the params back to what they were for AC3.1.5 'cuz it's hurting and not helping.
Yes, testing with 3.15 because I'm not an expert flyer, using the stable releases for the moment (but anxious for new things ;) ) , my copter was little nervous so I change params that you mention and goes better but, with the copter flying, I switch to land and the motors stop in the air, (aprox3-4 mts alt) I can switch again to stabilize and motors begun to spin again and avoid crash damages (good luck), (the new one was near the floor)
I'm not shure if post here or at 3.15; I posted here because I used TRH3.2 changes when I detect the problem, please move or delete if you consider better at the other post.
I might have had this problem this evening. I did an RTL and my quad landed properly but I'm not sure that it wasn't going to spin up again. I stuffed it into stabilize and took off so I'm not sure if it was me or something the FC was trying to do. APM 2.6 and rc9. If this sounds like the problem and my logs would be helpful let me know and I'll upload them tomorrow. I don't have time tonight.
Hello Randy
today I have tested RC9.
Pixhawk
Loiter - OK very well
Stabilize - OK very well
altholt - OK very well
Spline WP OK
pos.holt OK
ROI OK
takeoff OK
EKF like before very flatly
canal 7 countries functions in Loiter, altholt
does not function in Pos.holt.
This becomes the best version I has ever flown.
Thanks to the DEV team and Randy
-
194
-
195
-
196
-
197
-
198
of 373 Next