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
If I recall correctly WPNAV_UP and _DN used to control the climb rate in althold, this no longer seems to be the case in v3.3, what controls it now?
Hi Greg,
Sorry about your crash....
I had problems with Qbrain in other platforms (32 bit boards.)
I spent one month to understand the problem….really hard….…. After more than 20 crashes, I simulated the problem on the ground …. With physical support one axis platform
And the problem occurs without “loops” too…. With fast commands
So.... maybe is a similar problem.... “frequency”… I don’t know…
and with old APMs boards no problems....
Video with Q Brain (look the video description) 1 year ago….
https://www.youtube.com/watch?feature=player_embedded&v=yKyrdje...
Video afters change Q Brain
https://www.youtube.com/watch?v=sRT8Hpk0kqU&feature=player_embe...
Looking at the Alt hold performance on a breezy day for RC10 it looks like the Alt graph line is following the DAlt better than the BarAlt. does this mean the accelerameters are out performing the Barometer under these conditions or is it an avalible trust issue making Alt look better than Baro Alt?
What could be done to improve the alt hold in this case?
Just for reference I will post the IMU, Vibe and RCO graphs.
Hi Wes,
DAlt is what the controllers are being told to do. Alt is the estimated altitude the controller is using and trying to make equal to DAlt. BarAlt is the raw output from the Baro before it is combined with the accelerometers.
I believe we can do better in this area than we are currently.
Trent,
I'm really not aware of any changes that would cause that kind of behaviour. As far as I know when the throttle stick is moved just above the top of the deadzone (for example) it will command a very small climb rate, not 20% We can look into this but the log would be good to see first when you get a chance to upload.
Hi Greg,
Sorry to hear about your burnt ESC. I don't believe there is anything that has changed that could cause this to happen.
@ Greg
I believe that when you land and disarm you "accept the auto tune" and these values will be used onward. (this is why some people, including myself, just do one axis at a time.)
You said " Decided to land and disarm due to low battery warning." So good or bad you saved the new PID values at that point.
I could be wrong but it worked that way until RC-8 or 9.
Perhaps you could place back your saved parameters before this auto tune and do one axis at a time.
Henri
Hi Henri,
Autotune only saves if has completed the tune. That means it needs to successfully complete all requested axis before it will save the tuned pids.
@leonardthall
Please could you confirm:
example:
Bitmask: 0:Roll,1:Pitch,2:Yaw
VALUE MEANING
0 None
1 Roll
2 Pitch
4 Yaw
If I select only the roll axis (1) to be auto tune. Then subsequently take off in alt hold and activate autotune until it finishes this axis, Following land and disarm. Is the new PID for this selected roll axis stored or not?
Thank you.
Henri
-
173
-
174
-
175
-
176
-
177
of 449 Next