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!
I tried many reboots and change of batteries - same result. It definitely coincided with my upgrade to 3.3.2rc, but now is gone again. I guess I'll have more concrete proof if its now fine at the field.
I'd be surprised if level was set at arming - that can't be level at all!
The limits are enforced by the mission planner but only on the extended tuning screen. If you adjust them using the full parameter list (or full parameter tree) screen then it's possible to set them to whatever you like.
If it's a heading hold problem then adjusting the yaw parameters is more likely to help. So for example, on the Extended Tuning screen (of mission planner), the Stabilize Yaw, and Rate Yaw parameters.
The compass's effect on the heading is quite slow, it's really most the Z-axis gyro that controls the heading so it makes sense that re-calibrating the compass didn't help much.
I had a crash today.After the first flight (about 17min) I decided to had another flight. The copter was in hover and just increased the throtle (In pos.hold mode about 3-4 meters from ground) with out any other input the copter leaned right and it fell to the ground like a rock.
pixhwak with copter v.3.3.3
Any advice setting up the Z1 Tiny 2 in APM Mission Planner? What gimbal type do you select? (I assumed servo since that's the type of input that the tiny 2 would accept from a normal receiver). For whatever reason when I try to connect the input pins for the Z1 Tiny 2 to my Autopilot (driven by ppm from receiver) it just buzzes and doesn't care about what inputs I'm giving from my radio. If plug it in directly to the receiver it behaves like it should (slews to where I have my radio set to).
Thanks in advance,
of course level is not set on arming....
Randy,when can we expect 3.4 in mission planer....is this thread dead or what(no post for 7 days),do i need to follow whats new somewhere else?
just had a look here: https://github.com/diydrones/ardupilot/milestones
The AC 3.4.0 milestone is only 27% complete. I guess now that a lot of developers have had their support withdrawn by 3DR the dev speed might be slowed down a lot. I'm not sure really what's going on. In the end it is an open source project and therefore has no real 'deadlines' to meet.
It is a shame, though. I was eagerly awaiting the EKF2 and boat take off. I tried flying master under controlled conditions and it worked great. But I'm too scared to fly master in the wide open.
I've been flying 3.4 since Dec without issue. Although if anythings been done since Dec I guess the experience could be different.
I'm not getting any Bata versions showing up on the MP after clicking "Beta firmwares" .
I worked around taking off from a boat by arming my quadcopter on land, and keep the battery connected (it will soon disarm if not touching the throttle stick), then departure on boat. When I reach the site I want, re-arm the quadcopter. I did not use RTL, out of concern the drone might go back to where it was armed, but set the last waypoint where taking off, then land it in loiter mode.
I was using pixhawk AC3.2
I'm installing A Lightware SF30/B Sonar on my Pixhawk, will APM work OK ?