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
Grounded to WHAT ?
This topic surfaces, gets beaten to death, and surfaces, again, a few months later.
If it is RF(radio frequency) interference, it will ONLY affect either the RX, or the GPS, or both.
If you effectively shield those from the interference, you also effectively shield them from the signals, they are SUPPOSED to receive........
So get rid of the cheapie vidcams and vid tx's.
THAT is why all electronic devices are supposed to be switched off on passenger aircraft :-(
The magnetometer is ONLY affected by CHANGING magnetic fields, that is why you have to do COMPASSMOT.
So, that is why DJI puts the magnetometer on one leg, others put the mag on a stalk, far away from heavy current wires.
Yeah, I've only been in the RF game for 40 years.....
Are those apm and pixhawk on different copters? If yes, most likelly you have a noise problem, potential sources are noisy powersupply and/or the vTx especially if it is 1.2ghz
The only way to know for sure would be to roll back to 3.15 on the pixhawk and try it.
Swapping between an APM 2.6 and a Pixhawk does not isolate whether it is a firmware or hardware issue, it doesn't really prove too much.
If the same issue occurs when you fly with the pixhawk on 3.15 then the issue is with your pixhawk or a connector between it and the GPS.
If it does not occur when you fly on 3.15 it means it is either a firmware issue or could be an intermittent fault.
The key to effective fault finding is to always only change one thing in between tests.
Another factor to consider is Solar Storm activity. The last couple of weeks has shown a roller coaster of solar activity and when the K-Index hits 5 like it did last evening for a while, there's a good chance your GPS will have difficulty receiving all the satellite signals.
Question you need to ask yourself is,
1. What is the K-Index
2. Did you fly both APM units during the same time the K-Index was elevated.
There may be other reasons you are loosing lock on your GPS or it could be satellite interference.
I use K-Index Monitor for my Android phone.
A quick update on where we are with AC3.2. rc13 will go out on Friday or Saturday and will include fixes to issues that have come up in the past two weeks including:
In terms of what's left, there's not much (see below) so we will give it one more week then rename the firmware to "AC3.2" and ask the wider community to use it. Then 2 weeks later (if all goes well) we will make it the official version.
i) Ray reported his trad heli is getting stuck in the final stage of landing
ii) double check Pomaroli's report about crash during back-flip with ACRO Trainer enabled
iii) a number of items on the AC3.2 to-do list but I think we will move these all to AC3.3.
iiv) update the wiki
v) investigate any crashes reported here
Thanks again to all for your testing!
Thank you Randy - the community owes you and all the devs + testers a great deal. I am new to all this but can see how much time and dedication is needed. It is much appreciated.
thanks randy
i like the way that development is taking..more testing before official release is very a great thing!
Thank's too, great work :)
@Randy ,I use pixhawk and px4flow on loiter,the firmware is not arducopter,but not success.
-
91
-
92
-
93
-
94
-
95
of 373 Next