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
Thanks for the response steve. Another question. whats the problem with exceeding 2000? My taranis hits 2006.
Thanks
Jeff
The timing of the rc pulse stream can experience problems if the pulse width exceeds 2ms. This happens because the 2ms pulse hasnt ended before the next pulse starts. This problem can occur in the ppm stream decoded in the pixhawk or in the rc reciever.
To see this in action use a exuhf module in the taranis if you set a few chanels to more than 2ms you can change flight mode (ch5) by moving channel 4 (rudder).
The last thing you want in anything that flies is unreliability. Keeping each pulse in your pulse train between 1 and 2 ms helps keep the rc link reliable.
Steve
Hi. If we use SBUS, is there any problem? Or it is just with PPM?
Steve,
I tried to reproduce this issue today with an 8channel FlySky transmitter and D4R-II FrSky receiver but was only partially successful. I was able to cause a radio failsafe (i.e both APM and Pixhawk were unable to read the ppmsum stream) but I wasn't able to change the value of ch5. Any extra advice on how to cause ch5 to change?
BTW, in any case it's a serious issue (with the FrSky TX/RX) and should be documented somewhere on the wiki (which I will do).
I noticed this with the Exuhf in my Taranis. If channel 4 (rudder ... used for arming and disarming) is moved all the way right (more than 2ms) then mode on the HUD (and OSD) would change to RTL as the Pixhawk lost sync on the PPM stream.
The issue is simply that the pulse width range in the pulse train is finite and if the pulses are outside the spec range, (2ms max) unpredictable things can happen. individual manufacturers deal with very wide or very narrow pulses differently, some much better than others, but if you dig through the tech documentation, most will warn you against having all pulses "high" or all pulses "low" at the same time as the receiver can have difficulty with framing if you do this. In the real world, this is very rare. It is more common that a single pulse (one of the 8 or 12) will be too wide which steps on the timing for the subsequent pulse.
When you look at the pulse train on a scope, its obvious when the pulses are too wide on a single channel, the timing generally goes bad for the whole frame.
Steve
I had no idea about this 2ms limit and it's not good!
I'll test and if this is really the case we need to document and add a pre-arm check.
Thanks for pointing this out.
oh wow. Yeah im at 1995 and 1011 now.
Thanks!
Jeff
http://youtu.be/xGoawE6aQv8
Here is a short video of loitering my 800 trad heli in winds gusting to 20 knots. I'm happy with the performance. Any comments?
Question. While flying splines, I have noticeable jerks at each waypoint. I've tried turning down WPNAV_JERK, ATC_RP_ACCEL, and Rate. What is the magic parameter that can help smooth WP transitions???
803213 ekf 2000.param
Ray,
Looking good.
Yes, I'm afraid unless you set the waypoint speed low (5m/s) it will jerk at each waypoint. We won't be fixing that in the initial AC3.2 release at least. Maybe with AC3.2.1 but certainly for AC3.3 it'll be sorted.
Thanks!
-
45
-
46
-
47
-
48
-
49
of 262 Next