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
It is important to calibrate your ECS, the easy way is all at once
http://copter.ardupilot.com/wiki/initial-setup/esc-motor/
and do the full harware calibration
http://copter.ardupilot.com/wiki/initial-setup/configuring-hardware/
Alas, I have done both many times, but thank you! I have calibrated the ESC, per both the "all at once" and the "individual" procedures prior to flying with 3.1.5, and they worked normally, and it flies perfectly. I did not think they need to be re-calibrated just because I load 3.2-rc3 or -rc4, so I then load 3.2-rc3 or -rc4 and they do not work. I then reload 3.1.5, without ESC re-calibration, and they work. If I re-calibrate ESC with 3.2-rc3 or -rc4 loaded, by either method, the calibration appears to work, but the strange motor behavior is still there when I connect LiPo and try to fly. I am fairly sure the ESC re-calibration worked when -rc3 or -rc4 were loaded because I can reload 3.1.5 without re-calibration after trying (and failing with) -rc3 or -rc4 and the ESC behave normally and it flies perfectly. The ESC simply do not work properly when -rc3 or rc4 are loaded.
that happens because the default pwm output values are a little bit different on each version, so when you power the copter with the new version, the ESC don't like the new values
Hi Mike,
There really shouldn't be any need to re-do the calibration from 3.1.5 to 3.2. No offense to Javier but as far as I know, there should be no changes to the pwm being output with each version.
I wonder if it's possible that it's tripping over an arming check. If you connect it to the mission planner and then arm it (without the battery connected) does it arm?
Yes, just checked again, it always arms via MP without LiPo, no warning messages.
I have since been able to get it to arm and fly twice (out of 50 tries) by some combination of holding down the safety switch for a period of time when and after connecting the LiPo. It does not seem to be deterministic, or I have not found the correct pattern. I can tell when it will work because of the beeps. No beeps, no work, 2 beeps, it flies!
When it flies it is amazing, hats off to the Dev's!
Hi Mike, i am just curious... when you fly do you first connect to the Mission Planner via telemetry? Simple because, i think if the copter doesn't arm there should be message in the Mission Planner showing why arm can not be done....ex: bad compass health, magfield, etc.
Hi Randy. Thanks for updated wikis and 3.2r4. I have put in several hours of flight time using Pixhawk+EKF in both my hex and quad and have enjoyed every minute of it..Fantastic..
I purchased a MB 1242 IC2 sonar but using the parameter values in the wiki and connected to the IC2 connection strip along with the compass and ext LED. There is no indication of function under the MP status tab with sonarrange and sonar voltage both 0.. I wired the 1242 with shielded cable and the noise filter..
I guess my question is-- rc4 capable of IC2 sonar?
Sandy
Hi Edward,
your params seem good but I think you should not use a noise filter with the I2C one as noise filter is designed for analog sonar.
As you can find in the I2C wiki, wiring is direct on the I2C port...
http://copter.ardupilot.com/wiki/common-rangefinder-maxbotixi2c/
And normally both I2C and analog will work with 3.2-rc4.
J.
-
268
-
269
-
270
-
271
-
272
of 373 Next