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!
May be off topic, but I'd like to stress the issue of compass interference. I just recently re-assembled my new Alien 680 build by swapping out the KDE ESC's that I just could not get to work right with AC. In went the HW Quattro and it has zero issues. Go figure.
So I'm going through the motions and EKF is yelling at me again. Looked at the graphs (love that feature) and there it was; compass into the orange. Drat. The mast is 6"+ from the top of the frame, the main power is underneath. Huh? I demag all steel screws. The rest are non-mag SS.
Then I noticed a live 12v JST connector for the gimbal poking out through a slit on the top frame. Hmm. Tucked it down inside the frame, EKF is happy, I'm happy. Does that sound logical or just coincidence? Are compasses that sensitive?
by the way, I have performed current calibration prior to this by doing this method:
1.Fully charge your lipo
2. Immediately fly your multi for at least five minutes
3. Land and disconnect the lipo from the multi
4. Immediately, charge your lipo unti full using a smart charger with display (capable of displaying total current used for charging the lipo to full capacity).
5. Connect your FC to mission planner using usb cable and open the Battery monitor sub-tab in Initial Setup>>Optional Hardware tab
6. Look at the Amperes per Volt value
7. Go to Flight Data tab and download data flash logs
8. Review the log file and check the CurrTotal
9. Calibrate the current sensor by adjusting the Amp per volt to actual values. Do the math:
New Amp per Volt = Amp per volt * Total Charge / CurrTotal
10. Type the new Amp per Volt value on the box provided in mission planner for the calibration.
I tried to use battery_voltage2 and current2, readings get to Pixhawk but scaled wrong?
I received 15355V, tried to scale it to 15,3V but then I only get 15V. Using a standard power module connected to ADC 3.3V.
Want to use 2 batteries in parallell and monitor each via separate power modules?
Great job with the new version....
I've never tried to monitor two batteries but it should work if you make most of the BATT2_ parameters the same as the equivalent BATT_ parameters. We don't us the measurements from the second battery monitor for anything (i.e. battery failsafe) but I think you should be able to see the values in the Mission Planner (or other GCS perhaps) as "battery_voltage2", etc.
can you help me analyze my log?
You are right I can see some values in MP but as I wrote I cant scale them correct without loosing the decimals?
My settings for batt2:
BATT2_MONITOR -> 4 (Analog Voltage and Current)
BATT2_VOLT_PIN-> 13 (in MP A12 not sure if this is right since it is numbered 13 in the Picture in wiki)?
BATT2_CURR_PIN-> 14 (in MP A13 not sure if this is right since it is numbered 14 in the picture in wiki)?
And I have only connected pin 3,4 and 6 from Power module, and they are connected to ADC 3.3V on pin 2,4 and 5 and in that order.
I've got a few lidar lite units, but a whole group of new lidar modules coming out. Check this out http://www.lightware.co.za/shop/en/home/45-sf40c-100-m.html
We really need a way to integrate these sensors into auto missions. So I'm keeping my fingers crossed lol!
I will try to recreate the compass interference warning. This wire is off the 12v step down regulator, and my understanding is when there is no return path for the current, an exposed wire can emit radiated EMI. No?
It's normal that I start autotune with
and after autotune I have
I will be interested to hear your results. I can't see enough EMI from a low voltage open conductor to cause compass interference.
Yes, these parameters are tuned on autotune routine. How are your copter flying with them?