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 Randy,
I have set mot_thr_mix_max to 0.9 and tried again. same result. I have added log for my last small try. I will try to find the problem in log file
1.zip
Hi Alp,
It might be worth trying
INS_GYRO_FILTER,40
RATE_PIT_FILT_HZ,40
RATE_RLL_FILT_HZ,40
That may have been the problem. I can clearly see your roll being the dominant cause but your pids shouldn't really cause it unless you have changed your cell count or esc settings.
by the way there is no problem on my cell count and esc settings with rc8. rc8 was realy cool works with my hardware.
Hi Alp,
Yeh, sorry, I have no idea why this stopped working for you.
Re-flash the rc9 and set suggested parameters. Everythings look good now.
At this time a cat helped me about Copter-3.3 rc9 beta testing :)
https://www.youtube.com/watch?v=f2kdS7f2WbQ
I installed rc9 on my 250 quad, and it fly's great.
So, it's not an issue on all 250 size frames.
What may be the reason I do not see Emergency Stop in Ch7 nro Ch8 options? I use 3.3 RC9 and newest (non-beta) Missionplanner.
Will be loading rc9 on my basher tomorrow morning and flying afternoon. Did you have to adjust yaw pid?
Question about the landing gear.
When does the landing gear retract and when does it deploy when set to auto?
Currently when I take off, I have to manually retract it by flipping the switch, then I set it to auto and I see it deploy when it lands or when RTL activates. I haven't seen it auto retract, is there a certain height that it retracts?