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
Another question: What do you think about reducing the RC_Speed?
Hi Leonardt,
thanks for the quick reply! The vibrations came from the motors/escs. I´d like to reduce the vibrations before making another autotune.I thought it was better with low PWM setting but you say no.So I will reconfigure the blheli escs again tomorrow. Can you please give me a hint how to visualize these vibrations?
Or did you mean the spikes within one second?
Cheers
Gregor
Completed auto-tune (pitch/roll) today and ended up with 0 P values. Did I do something incorrectly?
2015-06-14 10-23-30.zip
Hi Robert,
Sorry for the late reply.
The results of your autotune are:
Roll Rate P = 0.226
Roll Rate I = 0.226
Roll Rate D = 0.012
Roll Stab P = 14.4
Pitch Rate P = 0.508
Pitch Rate I = 0.508
Pitch Rate D = 0.021
Pitch Stab P = 11.25
So I don't see how a zero got added to your tune. Which values have zero in them?
Thanks Leonard, I even more confused now. I believe I saved the tune parameters and when checked on MP (both tuning and full parameter list I got 0 values after several refresh. After your response connected again now I can see different P values (0.163 both roll and pitch P) that does not match with the tune result either... furthermore, is not RATE_PIT_P and RATE_ROL_P limited to 0.3 max ? .. so Pitch Rate P = 0.508 ? In your list above both RLL and PIT P and I has the same value too.
@leonard
Were you able to take a look at my Auto Tune logs from this discussion?
http://diydrones.com/xn/detail/705844:Comment:2018277
Not to sound impatient, but I won't take it up again the way it is.
Thanks.
Hi dev, I have been following the dev. here http://firmware.diydrones.com/Copter/2015-06/
Up til now there has been updates on the "latest but the last update is 8 june.
Is it placed elsewhere or?
in github I can see there has been changes.
Just of curiosity/ Goran
I don't think there are nightly builds per say, i think Randy or one of the devs actually triggers a compile after testing alot of new changes in dev, or else there would be alot of nightly crashes.
hi! What does the "EKF Variance" prompt on my HUD means?
-
339
-
340
-
341
-
342
-
343
of 449 Next