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
There is a tab in the log window for clearing logs.
Hi Masam, i am using the "latest" AC 3.2-rc1. So far, it's handling the copter nice. However, when i tried to download the Data Flash Log via Mavlink, it says "Timeout on read - Get Log" and the signal strength of the Mavlink as shown on the HUD goes from 100% down to 4%. Is this an issue with the MP or the firmware slowing down the telemetry data? Thanks...
I too am having exactly the same problem. The radios are 20 cms apart and the "Timeout on read - Get Log" error message pops up and signal drops straight to < 20% ( random ) and continues to go down and then takes a good 2-3 minutes to ramp up to 95%-98% - Never 100%.
I have also noticed very frequent drops i.e. No Data received whilst quad is in air and within 30-40 meters of GCS telemetry module.
I have tried 3DR ( SiK v1.9 ) radios as well as RCTimer ( SiK v1.7) ones - same problem. So it is not a radio hardware or antenna problem.
Running AC 3.2.1 and MP 1.3.34
Does anyone have any clue?
Disabled ECC check and downloading log works and no timeouts. But the radio range is still a problem.
Thanks so much Masam.
AC3.1.5-rc1 has replaced AC3.2 in the Mission Planner's Beta Firmware's link.
This is just for the next two days while we test this patch release to AC3.1. Discussion of this patch release are over on the AC3.1 release thread.
AC3.2-rc2 will be back in the Beta Firmwares link in a couple of days.
AC3.1.5-rc1 not include hybrid mode. I've tried this afternoon. Waiting for ac3.2. Thanks randy
Hi Randy, did you removed hybrid mode on 3.1.5-rc1 ? today I've tried the 3.2-rc1 and I think everything is working and no problem, I tried stibilize, loiter, holdalt is good, and hybrid is perfect, also waypoint with autotakeoff, RTL, Guided and autoland is working well. and then this morning I upgrade to 3.1.5-rc1 and the hybrid mode is gone. I think AC3.1.5-rc1 is updated from 3.2-rc1
Yudi,
Yes, we've had to take a short break from testing AC3.2 so that we can test AC3.1.5-rc1. AC3.1.5-rc1 is actually a step backwards from AC3.2-rc1. We have to release a patch to the current official version (AC3.1.4). AC3.2-rc2 will be back in a couple of days. Discussion of AC3.1.5-rc1 is over on the AC3.1 release thread.
Does 3.1.5 RC1 include Hybrid mode?
-
355
-
356
-
357
-
358
-
359
of 373 Next