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
H Style
Your frame looks to be extremely similar to mine (Xplorer Pro 500, see http://www.rcgroups.com/forums/showthread.php?t=1994987) - isolated sections and all. Have been flying it with APM 2.6 and now PixHawk, firmwares from 3.1.xx to now 3.2RCxx. Absolutely rock-solid - I have always upgraded FW, started with default PIDs and then auto-tune, maybe 10 times in the meantime. Never a problem
BUT I have always used frame type X - not H
Maybe worth giving that a try ?
Yes very similar. Josh posted some settings that I'm going to try tomorrow. #2880
I used H just because the picture of the frame on Frame Setup was most similar. All my other quads use X style. I could change to V but don't want to take it apart just yet. What problems did you find, if you set it to H style?
I plan to build a Cinetank too (with an APM). What is the difference between these configurations and what are the avantages of one over the other ?
I didn't see that! Well they are almost unreadable but I will try them.
http://flyingcinema.com/media/cinetank_apm_pid.jpg
Today I was trying the ArduCopter 3.2-rc4 01-Aug-2014.
Unfortunately the Spektrum Satelite was not working anymore. Back to 3.1.5 It was fine again.
Andre: I am having similar issues. Mine worked fine through -rc2, but it will not work with -rc3 or -rc4. What are your symptoms? When did it stop working? I am back to 3.1.5, but I really need sonar...
Mike
I only tried 3.1.5 and 3.2-rc4. With rc4 there were absolutely no receiver signals. Also in MissionPlaner I could´t find anything to enable the satellite or similar.
I was only trying the rc4 because of this Issue: HDOP mixed up with PDOP I thought It would be solved in rc4 but it is not!
Using MP version 1.3.7 build 1.1.5307.24027
APM 2.6 Rx: FrSky D8R-XP reflashed with the 27 mS software in CPPM mode.
APM 2.6 with software 3.1.5 RCMAP for the first 4 channel works fine can remap the first 4 channels without problem.
Then erase and reflash APM with V 3.2-rc4: RCMAP is confused and it is impossible to remap the first 4 channels?
I think this is an "undocumented feature"
I'm trying 3.2-rc5 and can't remap my sbus channels with rcmap feature, no effect after setting, restarting, reconnect, and the same wrong channels are moving.. super frustrating.
-
188
-
189
-
190
-
191
-
192
of 262 Next