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
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!
Try first holding the safety switch down and powering up the hawk. If this fails backup your SDCard and format it Fat32 and then see if it doesn't completely the boot cycle. Try flashing back to 3.1.5 and connecting via console and do an setup/erase and setup/rest
I only notice that your current had fairly periodic spikes to 0. Seems like periodic ESC glitch. Check your CURR pllot.
Have no idea for the reason.
Thanks for taking a look at the log! It does seem there is a power issue. I have a dual battery setup and I'm now wondering if one battery is loosing connection? They have separate power leads to the distro board and I only have one battery being monitored by diy power module. I have seen the compass variance error happen randomly with it just sitting on the ground not armed but I guess this could still be the issue. Guess that is where I will start looking.
Thanks again. Open to any other recommendations.
When you say "on the ground" is this on concrete? I've seen rebar play havoc with the compass' and it goes away when I move it over to the grass..
Nope, on grass. Just weird because I've never had an issue like this before.
I would suggest disabling the internal compass as it doesn't use it anyway even if the external fails. FYI it may or may not have anything to do with 3.3. I have had to do the compass calibration and then the compass mot a couple times before I stopped getting that error even with 3.2. Did you re-do the compass calibration when you went to 3.3? It might juts be finicky like mine [ and many of them ] and unrelated to 3.3. But if your certain the external is fine might want to just disable the internal and issue solved.
I will give this a try but the current drops are still bothering me. What is strange is that the voltage doesn't really change, only the current dips. Also, compass 1 mag X and Y clearly show a deviation coincident with a current drop but compass 2 (pixhawk internal correct?) shows no deviation.
I have redone compass calibration and compass mot with no difference on both external compasses.
I've attached a screenshot that clearly shows the above and I have attached another log showing a longer flight with greater issues. This log is from the csgshop M8N XL, so this behavior is present with two different external compasses.
If any devs are interested here's a 3.4 log. I have a couple days free I'm gonna do more... also compare with 3.3 in loiter. Seems like it's not as good in loiter / pos hold as 3.3 but hard to tell with just 3 flights.