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 Alex,
I don't want my flight batteries drained while doing essential ground based tasks, that is why I do it as above.
As I said, never had problems, yet :-)
I see your point. Yes it is a good way to keep the flight packs fresh. I never thought that way.
What type of ground test you perform? Did they require the motors to spin?
Hi Alex,
This is on a fixed wing.
I check the HUD, GPS lock, load or check the mission, different modes, briefly run the motor.
Yes, can be done with the normal flight pack, difference is, if there is a problem, the quad might crash < 15 minutes away, the plane 120 minutes away, at three times the speed :-)
Hi Martin. I'm guessing you're running the two packs in parallel? If so why dont you just wait for the gyros to calibrate before you plug the 2nd battery in...?
Yes that was my solution too, worked fine as long as I remembered to do that.
What are people doing if the battery is mounted underneath, and the copter also needs to be turned upright before the cal starts.
Is there usually enough time ?
@Andre,
Good idea, I've had that problem before too but didn't realize that I was the cause of it. I'll wait to plug in the 2nd battery from now on!
@Christian, @Thomas, I had just bought a new uBlox M8N GPS receiver. i understand that baud rate and SPI has to be changed before i connect it. can u pls share how to change these settings on new M8N GPS before connecting to Pixhawk GPS port. is there a utility for changing the GPS settings. i think baud rate has to be 38400
uBlox has free software for testing and setting up of gps modules. You will need an FTDI cable.
http://www.ublox.com/images/downloads/Product_Docs/u-centersetup_v8...
Hi Randy,
I noticed in the Datalogs produced by v3.2(rcX) has dropped the FMT line for "MOT" (for motors). Was there a reason behind this? It was very useful for detecting how many motors were attached even when no logging was taking place for the motors.
For example, from v3.1: FMT, 11, 11, MOT, hhhh, Mot1,Mot2,Mot3,Mot4 = 4 Motors, or FMT, 11, 19, MOT, hhhhhhhh, Mot1,Mot2,Mot3,Mot4,Mot5,Mot6,Mot7,Mot8 = 8 motors.
Is there another way of detecting the number of motors in the datalogs?
Cheers
Kev
Kev,
The info is all still there but it's been renamed from MOT to RCOU (i.e. RC Out) to make it consistent with Plane.
-
78
-
79
-
80
-
81
-
82
of 373 Next