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
Nope, not a bug. I think the real reason for this is lost to the mists of history. At some point somebody had to decide if 1000 pwm was "nose down" or 2000. There is no right or wrong answer to that question.
3.3 FOR WIDER USERSSS!!!!!!! :D :D :D
http://diydrones.com/profiles/blogs/copter-3-3-ready-for-wider-use?...
Just installed RC11 on my extended f550 (I ran earlier 3.3 RC's, but went back to 3.2.1 up until now). I re-calibrated everything, and am getting a PreArm: GPS Horiz Error as soon as I try to arm (I can see previous attempts reporting 6.1, 6.0 and the latest at 5.1). I have reported 10 sats and a DHOP of 1.4. I appreciate that EKF is not satisfied with the GPS fix, but wonder how I would be able to improve this given the DHOP value and sat count I have is about the best I can get. I'd really like to be able to use PosHold. Any advice plz?
The GPS Horiz Error was shortly followed with a GPS Speed Error. The sat count eventually went up to 17 and a DHOP of 1.0 and I was able then to arm without issue. I am using the dreaded M8N on a small pole/mount which is sitting well away from the other electronics and power, elevated about 4" above the arm to which the mount is attached. Something like this:
Thanks for the info - do you have a photo at all?
Anyone else have any issues with ROI? Or downloading dataflash logs? I just updated from rc12 to the official 3.3 release. Made several flights documenting local flooding due to "blood moon". One flight had issues... When I roi'ed the end of a pier, ending the ROI was unsuccessful. I could tell the ROI changed, but it did not turn to face the next waypoint, quad faced 180 and continued mission until I RTL'ed. I wanted to post a DF Log, however, the log that I thought was the correct one, just shows me sitting in the same spot, no flight data!!! Here is a video and wpt file. Will re-test after batteries finish.
https://www.dropbox.com/s/m649eqdxhs7rlqh/GOPR3236.MP4?dl=0
garden city flood 2.txt
If I have a copter with LidarLite on it and fly a Auto mission and set the height to 25 m in mission planner will it use the Lidar to keep the height on 25 m above the ground?
I use to fly in areas where there is no terrain data so it would be nice if I could use the Lidar to keep the altitude over ground.
Alf,
No, I'm afraid the lidar-lite altitude is not used during missions. We're looking to add Terrain Following during missions using the google maps altitudes to Copter-3.4 and we've discussed also incorporating the range finder altitude into that but I can't make any promises yet.
It's slightly more complicated than it seems because for a proper solution we need to allow the pilot to specify what altitude they want to be used during the mission (i.e. alt-above-home, alt-above-sealevel, alt-above-terrain) which affects a number of parts of the system including the GCS, the mission command storage and finally the vehicle position controllers.
Hi Randy!
For thoose who fly in an area without google maps altitude (for me Storlien, Sweden) and not so flat landscape it would be a great help to be able to set desired altitude to be used by Lidar, and then just plan the route.
Is it possible to implement it as a security parameter in auto to not go below ground altitude xx m. reported by lidar?
Holding my thumbs for that it will be implemented in future releases for this great product.
Not to mention it is just plain cool!
Randy, do you already have a Lidar lite or does somebody need to send you one?
-
120
-
121
-
122
-
123
-
124
of 449 Next