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
Paul,
No that issue must be different. More likely to be a mission planner issue although it's hard to be sure.
hi, you never know could be solar particles because of solar flares. they were predicted for this year. christian by the way which connector of pixhawk do u connect the second compass. i guess *- rc3 has provision for three external compasses.
Hi people,
I've been flying and updating my 3DR quad since day one, now suddenly I'm having big problems :-(
After the new firmware/software update.......
1: In Mission Planner, my quad now has a 90 degree compass offset.
2: In Mission Planner, although I can connect with the 3DR radio, Mission Planner cannot see the modem in the setup screen.
What am I doing wrong here ?
Oh, the Beta version of Mission Planner does not give Compassmot in the CLI anymore either....
Sorry, APM 2.5
Test report AC3.2-rc3: I did auto mission with Do_set_roi. The flight is rather smooth and nice except that when ROI started, there's a brief oscillation in both roll and pitch as shown in line numbers 2731 up to 2957. Please see attached log. Thanks
2014-07-20 17-27-36.log
Hello Christian,
I had a similar problem after a few meters the signal decreased until you log out, after searching I found the antenna connector of the modem unsoldered with small cracks on welds.
I believe that with the vibrations create these cracks, I soldered the connector and everything is back to normal.
your could be this type of fault.
greetings
thanx randy, i think that would be great if the mission planner can show which GPS is being used at a specific time. that way we can compare the performance of different GPSs. is there any similar parameter for second compass? i understand secondary compass has been enabled in rc3.
I had test 3.2-rc3 is Position Hold mode when have strong wind with Pixhawk. It have very stable.
Hi fellow flyers, is there any parameter to be enabled when using dual GPS in UART port 4/5 of pixhawk. also is there any parameter for dual compass to be enabled. which port needed to be used for second compass. i intend to try dual GPS and compass on pixhawk on coming sunday. i understand that AC3.2-rc3 supports dual compass and dual GPS.
Ravi,
If you go into the full parameters list in the mission planne you should see a GPS_TYPE2 parameter. Set that to "2" to enable a second Ublox attached to Serial 4/5. There's also a GPS_AUTO_SWITCH parameter which will control whether it sticks with the main GPS or tries to use the backup (it switches depending upon the num satellites and hdop I think). The integration of the two GPSs is not super smooth yet, really both should be merged into the EKF and the one that best matches the current estimate should be used but that'll come in a future release.
Anyway, interested to see how it goes.
Christian,
Thanks for testing. The compass calibration works off the raw compass values so the results shouldn't change depending on whether EKF Is enabled or not at the time. The heading being different is a bit of a mystery to me but it must be how DCM vs the EKF are processing the data internally.
Yes, good point about the GPS. I was also thinking it would be nice if we could see the locations reported by both GPS in the mission planner somehow. Eventually I suspect there's won't be a primary GPS but rather the EKF will consume both and use a weighting to control how much of each it uses. Anyway, feel free to put your requests into the ardupilot or mission planner to-do list. With your request it will require changes in both places, but the ardupilot would be the first place to change.
-
204
-
205
-
206
-
207
-
208
of 262 Next