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
Greg,
Thanks for testing. The flight looks pretty ok - hard to see the toiletbowling so maybe that's another log or perhaps it's very subtle. The heading estimates from DCM and EKF appear to stay within 10degrees of each other and the ATT's ErrYaw is always quite low (0.15) so it shouldn't be toilet bowling much.
I don't have any extra advice for the M8N, perhaps others do.
Using 3.3rc8 I'm getting and error in Mission Planner - Error Compass Variance
Seems like others have seen this issue, but I've not found a solution yet in this thread. Is there a fix for this problem, or is this recognized as a problem yet?
Thanks,
Scott...
If you have some dataflash logs that would be good as well. I've seen this compass variance come up a few times as well on the thread but so far, no logs! Best to set Logging-while-disarmed checked in the LOG_BITMASK selector in MP.
log file
Randy, hope this helps. See embedded link to my log file... Also attempted to attach...
Scott...
2015-08-17 20-35-58 5.bin
When you get your error compass variance messages usually your pixhawk will have a flashing yellow LED. Pick up your copter and move it a little bit. This usually fixes the error and allows the pixhawk to arm and continue a normal flight. This is the only workaround I have found for this problem aside from removing power and plugging it back in until a fix can be produced.
When do you plan to fix this? This is easy. Annoying to see it every time ...
Yah it's been that way for a while and should be an easy fix for Mr. Osborne but I have a feeling he has his hands full just keeping up with all the changes in the RC firmwares :)
ArduCopter 3.3 rc8
What is the correct value to put in FLTMODE1,2,3,4,5,6 for obtain Auto-Tune-Flight-Mode?
I see that:
0:Stabilize 1:Acro 2:AltHold 3:Auto 4:Guided 5:Loiter 6:RTL 7:Circle 9:Land 10:OF_Loiter 11:Drift 13:Sport 16:PosHold
Maybe autotune is 8, or maybe 12, or 14, or 15?
I know that you can not do by using the GUI in the planner, but you can only do by editing the "Full Parameter List".
I also know that I can set AutoTune by CH7. But I do not want to do it by CH7. I would like to test it by using only a 6CH radio.
It is not a flight mode at all. You need to set it to either channel 7 or channel 8. oh looks like it is possible now with 3.3 and the new MP
Yes, that's right. It is actually a flight mode in AC3.3 (in AC3.2.1 it was not a flight mode).
-
273
-
274
-
275
-
276
-
277
of 558 Next