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
Besides what has been said by Trent Russell there's something very strange on your vibration log that occurs right after you said you changed to PosHold. If you see the clipping that jumps at that time, I would say that something physical came loose and from that point forward the copter was trying really hard to keep up.
I know that now might be almost impossible to trace back where the physical fault might have occurred but look carefully at what might not be crash results.
Hi! This is a question specially for Leonard and I think and the answer might be a good addition to the Wiki.
Let say I have a copter that I know the PID should start at 10 for stabilize Pitch and Roll and 0.25 for Rate Pitch and Roll. I remember that those values are near the previous ones that I had on the same copter but I had to clear the eeprom and I forgot to back up :-(.
Does it help and speed up the process if I start with that?
Maybe this can be extended to a second autotune if the values that are setted in a previus one are not too accurate?
Thanks so much for the help
Hi Bernardo,
Yes you can manually add those values and Autotune will start there. It will also speed the process up considerably. That is why a second Autotune will run significantly quicker than the first.
The main reason I run a second autotune after I successfully finish my first is because poor tune on one axis can mess with the results of the other axis a little. The second Autotune runs relatively quickly (I always wait for good conditions for the second tune) and gives me confidence I have close to the optimal result.
This is great info! I did not thought about the second autotune right after the first one but is a logical thing.
I know the default PIDs are really conservative (or maybe they are thought for small overpowered copters) but I have a large octa and even though it flies at 30% throttle, I have to almost double the original ones.
Please consider adding this info in the wiki. Many people like me sometimes makes a clean install on a copter and we almost know what values are optimal and we need autotune to polish the numbers.
Thanks for your great work
Leonard, you refer to wait for good conditions for the second tune; on your first tune what conditions you choose? . my cuestion is because I wait for calm day to tune, but I need to fly with wind; It's better if I autotune with the same conditions that I want to fly? It's possible to do autotune with windy conditions? Thank's
Hi Cala,
No, it is defiantly NOT better if you autotune in the same conditions you want to fly. I understand your reasoning but Autotune will give you the best results for both windy and calm conditions when tuned in calm conditions.
On my first tune I will still look for the best conditions I can but I will sometimes compromise to get a reasonable starting point. Generally I can find some good conditions, at least once a week, early in the morning or in the evening where I live.
Thank's Leonard, I'm going to try the double autotune, nice tip.
I must say my initial tests with 3.3-rc10 running totally stock everything on my beater quad with a Hawk Lite is one of the better firmware revisions I have run in a really long time. Rock solid. Alt-Hold is working well, Loiter is back to being like it is hanging from a string and RTL worked flawlessly each time I used it. Awesome work!
Use X and it should be front left motor goes clockwise then front right goes counter clockwise then rear right goes clockwise and rear left goes counter clockwise and are ordered as it shows Starting front left and going clockwise around the frame 3-1-4-2
Hi VP,
Not sure what you mean about the bitmask, I recommend using 157693.
You are correct about the axis numbers.
-
186
-
187
-
188
-
189
-
190
of 449 Next