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
To complete my tests of 3.1.2 to 3.2.1 to 3.3-rc10's Auto tune I need a little help with 3.3-rc10
3.1.2 took about 3 minutes so 1 battery is fine. 3.2.1 took about 8 minutes so one battery barely made it. Now 3.3-rc10 is going to take even longer and my beater quad only gets about 10 minutes on a battery so I need a little run down on how to do it on 3.3-rc10. I know you can set a bitmask to only perform part of the test but my question [which I asked about 100 pages back] is how do I know that particular part of the test is complete and do I do the same as before which is once it is complete I turn off auto tune, switch to stab, then land and disarm. Is it the same now? Will it just stop doing the dance so I know that part is complete and then I do the same then switch the bitmask for the rest of the tests and repeat?
Hi Craig,
Set Autotune_Axis to 1 for roll, 2 for pitch and 4 for yaw.
Run through it normally, the copter should stop twitching and give you a tone to let you know you have finished.
You should never have turned off Autotune as that means your values aren't saved.
When Autotune finishes, simply land without changing mode at all or switch to Stabilize and land. Only after you disarm should you turn Autotune off. You can then carefully take off to test your tune of that axis. You can then change batteries and your axis to tune and repeat.
Thanks. I've always done as I said though and it has always saved the new pids. But I will leave AT enabled and land and disarm as that is your recommendation.
What is the bitmask if I want to do say pitch and roll in one shot and then yaw on the 2nd lipo?
Hi Craig,
That would be 3 and then 4.
Hi Leonard. Can you check my post on Autotune a couple of pages ago? I think we can get good info from you. Thanks!
Tried Auto mission today with tower and could plan the mission but could not take off. As soon as I touched the Auto takeoff button the copter switched to auto mode and shutdown. It worked just fine using the transmitter. This worked with the previous version of 3.3.
I also think my Pixhawk is going bad as when I first plug it in I get bad AHRS. If I unplug the unit and plug it back in it's fine. It only does this the first time I use my IRIS.
It is my understanding (and experience) that seeing "bad AHRS" on startup is due to the momentary lag as EKF is starting up (mine always clears momentarily) . I only started seeing it back when I first started EKF logging.
I got that every now and then on rc-9 but do not seem to get it on rc10. Also after you unplug your lipo use a paper clip or something to short the leads on your connector to fully discharge your MR as some have said this solves the issue.
You might want to be careful about your wording when posting advice like this in case someone interprets it wrongly and explodes their battery :)
I do get your point though.
-
228
-
229
-
230
-
231
-
232
of 558 Next