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
Hi Randy,
Thank you very much for the explanations very clear on the EKF error occurred during the flight. Yes I am using a VR μBrain and there is the pin for the current measurement. Ok for the suggestion to set the COMPASS_MOTCT = 0 will do this test. The GPS ublox M8 is already installed on a tower of 7cm and is the power board for a total of 13cm, I will try to raise more than a few inches not think it's possible more (cables permitting).
I would like to know if you can since you've peeked in the log an opinion on the setting of the quad, if you can improve the setup.
Great job Team
regards Fabio
go to Help, Check for BETA Updates
Uploaded AC3.2 rc14 on Pixhawk.
It looks stabilize roll P and pitch P forced to zero.
I am not sure already reported here.
..and I believe there is an issue with the ch6 tuning in that when ch6 is zero, the parameter that is being tuned will always be set to zero regardless of what the "Min" value is set to. There's an item on the to-do list to sort this out. sorry!
@Lior
Thanks. I have forgot about CH6 setting. It becomes OK after removing CH6 setting.
@Randy
Actually, there is very minor inconsistency of software for the handling of parameters on CH6 tuning.
But, it is very minor.
@ultrojo,
Great video (except the rough landing).
I'd need to see a log file to know why that happened. There are three possibilities that spring to mind:
1. the LAND_SPEED is set too high
2. the WP_SPEED_DN is set too high
3. the barometer drifted a lot over the flight so the vehicle didn't slow to the LAND_SPEED early enough to slow the vehicle's before it hit the ground.
Alex,
Ah yes, you're right. Another possibility is a baro disturbance near the ground. There was a tri-copter report a few days ago in which baro alt drop by 4m when it came close to the ground.
Just put RC14 on my tricopter. Redid all my calibration and im getting "prearm check fs_thr_value" warning for my prearm check. my throttle off pwm is 982 and on is 993. Failsafe is set to 984. Any ideas?
I would use my frsky x8r with sbus for failsafe but even though MP shows the the pwm change from the x8r with its failsafe being set it wont engage the flight mode so im stuck doing it with mp
I pushed my trim to max and redid the radio calibration and im good. Thanks! Maybe this is something that could be addressed?
There is nothing to address, the code is doing what it should. Instead of adjusting the tx trim, you may consider setting the throttle travel (on the "servo's" page in the FrSky to a lower number, say 80% ) so that at center trim, the pulse widthis 1000 (1ms) or more at minimum... and make sure it doesn't go over 2000 (2ms) at full throttle. You will need to redo the radio call in the APM set up once you do this.
Steve
-
44
-
45
-
46
-
47
-
48
of 262 Next