Warning #1: an issue has been found with Tower's Pause button which can cause the vehicle to fly to an old position if the vehicle has not sent a position update to Tower in some time.
Warning #2: Copter-3.3.2 fixes a bug found in Copter-3.3.1's desired climb rate initialisation which could lead to a sudden momentary drop when switching from Stabilize or Acro to AltHold, Loiter or PosHold.
Warning #3: Copter-3.3.2 fixes an issue found in Copter-3.3.1 which could lead to hard landings in RTL or AUTO if the WPNAV_SPEED_DN was set too high (i.e. >400 or 4m/s) and/or the WPNAV_ACCEL_Z was set too low (i.e. <100 or 1m/s/s).
Warning #4: a bug was found in Copter-3.3 which could cause a sudden crash if you abort a Take-off initiated from a ground station. Video description is here. The bug is fixed in Copter-3.3.1 so we recommend upgrading.
Note #1: AC3.3-rc8 corrected a long standing bug in the HDOP reporting. HDOP values will appear about 40% lower than previously but this does not actually mean the GPS position is better than before.
Note #2: if upgrading from AC3.2.1 the vehicle's accelerometer calibration needs to be done again.
Note #3: set SERIAL2_PROTOCOL to "3" and reboot the board to enable FrSky telemetry like in previous versions.
Note #4: the wiki will be updated over the next few weeks to explain how to use the new features
Copter-3.3.1 is available through the mission planner. The full list of changes vs AC3.2.1 can be see in the ReleaseNotes and below are the most recent changes since AC3.3.
Sadly this version (and all future versions) will not run on the APM2.x boards due to CPU speed, flash and RAM restrictions.
Changes from 3.3:
1) Bug fix to prevent potential crash if Follow-Me is used after an aborted takeoff
2) compiler upgraded to 4.9.3 (runs slightly faster than 4.7.2 which was used previously)
Changes from 3.3-rc11:
1) EKF recovers from pre-arm "Compass variance" failure if compasses are consistent
Changes from 3.3-rc10:
1) PreArm "Need 3D Fix" message replaced with detailed reason from EKF
Changes from 3.3-rc9
1) EKF improvements:
a) simpler optical flow takeoff check
2) Bug Fixes/Minor enhancements:
a) fix INS3_USE parameter eeprom location
b) fix SToRM32 serial protocol driver to work with recent versions
c) increase motor pwm->thrust conversion (aka MOT_THST_EXPO) to 0.65 (was 0.50)
d) Firmware version sent to GCS in AUTOPILOT_VERSION message
3) Safety:
a) pre-arm check of compass variance if arming in Loiter, PosHold, Guided
b) always check GPS before arming in Loiter (previously could be disabled if ARMING_CHECK=0)
c) sanity check locations received from GCS for follow-me, do-set-home, do-set-ROI
d) fix optical flow failsafe (was not always triggering LAND when optical flow failed)
e) failsafe RTL vs LAND decision based on hardcoded 5m from home check (previously used WPNAV_RADIUS parameter)
Thanks for your testing!
Replies
Hi,
currently i'm running a pixhawk on ac3.2 firmware.
I'm interested on using this ac 3.3, but it has been rolling from rc1 through rc6 and still on beta version.
Is it save for me using this ac 3.3 rc6 now? I'm not a newbie but nor an expert as well.
arga,
No, -rc6 is not safe it seems so best to at least wait for -rc7.
Hi Winston,
I have been looking at your log. Repost your issue then reply with a link and I will chat to you there.
Thanks Leonardthall!
Winston,
Sorry about your crash. This looks like an AC3.2.1 log.. Please remember this is the AC3.3-beta testing thread. I know it's hard to find support sometimes but it muddies the waters to post this here.
I apologize Randy, is that yesterday I was flying with Arducopter 3,3-rc5 and thought I could post the problem here, though I'm sure it was not a firmware problem ..
Sorry ...
Winston,
Nah, I shouldn't be such a stickler especially considering in this case you sacrificed a copter during beta testing. Hopefully Leonard can sort you out, if he needs backup I'll have a look.
Robert, Winston,
Very sorry about your crashes.
I've looked at your logs and it looks like the EKF's coming up with bad attitude estimates for roll, pitch and yaw - or at least they inconsistent with the older DCM by >10degrees. This is likely what's causing the out-of-control feeling you're getting. Obviously this is pretty serious so I've posted a warning above to ask people to stay on -rc5 until we figure out what's going wrong and publish fixes. Worst case we will roll-back to -rc5 until we figure it out.
RobL had an issue with his helicopter as well and during that analysis Paul mentioned there was a change in the gyro offset learning - that would be consistent with this problem.
Yes, something is badly wrong! If you plot the learned offsets against the compass inconsistencies you can see that the learned offsets vary hugely and almost randomly. You can also see that the inconsistencies rise with the variation. (I'm not sure if it's relevant but I see a similar oscillation but on a much smaller scale with rc5 and EKF_GBIAS_PNOISE set to 10x it's default)
-
385
-
386
-
387
-
388
-
389
of 558 Next