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
I tried to do a mission using the auto take-off (rc3) and it just flipped forward, broke all props :(
The surface was pretty flat but not perfect as I am up in the mountains.
Ed,
2014-07-17 10-00-33.log
The auto take off was more like an auto decent
I have had the same ...I had chunky carbon fibre props on so we were fine in terms of broken props.
The copter takes off fine in Stabilise and runs its auto mission without a problem, but sometimes with an auto takeoff the copter will roll heavily at a very few cm from the ground and crash.
Now I take off in stabilise and then switch to Auto.. I am trying to find the logs from Saturday but did a lot of flying its like searching for a needle in a haystack!
I also notice that the barometer altitude drifts with time. I wonder if the copter is armed for a long time and pressure changes this could be causing some sort of anomaly. Is the barometer reset at arming or at power on. I would suggest that reset at arming may be a better option?
Great great work guys can't stress how amazing this project is!
Andy
Hybrid mode rc3 the more I throttled up the more it just landed, I went stab > hybrid > throttled up > throttled down : issue came in when I tried to throttle up again it just kept landing till it gently touched down almost like it was in an RTL mode...the more I throttled up the more it just ignored me.
2014-07-17 09-32-16.tlog
Your tlog shows 0,15% of the flight in stabilize and then RTL mode until the end.
Do you have a log rather?
oops...looks like I hit my altitude geofence limit of 200m. This one is solved but my other one below that flipped and took out $40 worth of Graupner props still baffles me :(
I just loaded 3.2 RC3 beta onto my PixHawk in Mission Planner 1.3.7 build 1.1.5307.24027.
The LOG_BITMASK is still not displaying anything in MP (The field looks blank).
I believe I have it set to the RC2 default settings (I did a clear and reset all parameters when I had first loaded RC2).
After looking at the flight modes I was wondering if there is a mode that allows manual flight, like a Althold, loiter, positionhold, drift or sport while also having a ROI or position of interest...
If not I will be happy to begin development possibly it can be configured as a add on mode basically adding a mode overlay something like simple mode with the orientation set on the interest area rather than the original orientation from take off... I have read the modes several times, I could have missed it...
In operation a switch or assignment to a specific channel to at during any flight mode... However I cannot see how it could operate without GPS
Tearig,
No, I'm afraid that Loiter and Hybrid mode don't support ROI in AC3.2. If you wanted to add support for ROI in these modes it might help to look at how it's done for guided mode (see control_guided.pde). There's a call to "get_auto_heading()" which would do it I think.
Hi Randy,
When the software changes become released ... What is the timing for "manuals" to get updated.
BTW can you please list the link(s).
Thank You.
-
296
-
297
-
298
-
299
-
300
of 373 Next