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
After the second mission I could not get a rearm at all even after several minutes.
MP only showed a "Disarmed" message on screen.
I will have to wait until this evening to review the logs.
I was wondering it this had happened to others as well.
I'm trying to track down some compass issues on a AUAV-X2. If I disconnect the external compass on rc12, COMPASS_EXTERNAL still always says "1" after I reboot. I tried setting manually and it always gets reset. This is supposed to be autodetected on a pixhawk - anyone else see this behaviour? The compass IDs also do no get reset - are these determined at calibration time or on boot? I had assumed boot, but maybe its only calibration?
What are COMPASS_EXTERN2 and COMPASS_EXTERN3?
Different question. If I calibrate the internal compass on its own I get offsets of (52, -104, 327), if I calibrate them together I get (-15, -32, 127). How can this be? I would expect the values to be close-ish, but they are miles apart!
Both times I had a good set of data points and the output is relatively stable if I rerun the calibration.
Or is this more a mission planner question?
Andy,
I agree with you that there shouldn't be any difference to the compass calibration results depending upon how the compasses are calibrated (how many, in what order, etc).
.. and as you guessed, it's more of a mission planner question I think. The compass calibration logic is completely within the mission planner. For Copter-3.4 the calibration will be moved to the vehicle (it's already in master).
>COMPASS_EXTERN2 and COMPASS_EXTERN3?
that is apparently a support for multiple redundant compasses that would be awesome if it worked - but as all external compasses units in the gps receivers sit on same hardware address nothing of that works.
I am still on rc10 but if I disconnect gps with external compass it for sure sets compass external parameter to 0.
Never mind - I had pulled the GPS cable so the compass was connected but not powered (I'm guessing).
Disconnecting the compass does result in the external parameter being set to 0.
Popping in here to say that 3.3 rc12 ran great on my IRIS+. Granted I was not able to test every single mode and function but out of the modes I was able to fly in ,AltHold, Sport, PosHold, Circle everything went smooth. First flight no gimbal. took off fine. Got to a good altitude and let AutoTune run. AutoTune complete. Ran tests in AltHold, PosHold, Sport, Circle, Land, all good no issues IRIS+ was 100% spot on. Second flight gimbal attached. Launched fine. tested same flight modes, all good. No issues, IRIS is solid. Had 12sat 1.4hdop on both flights. Had my ground station up and running but I was flying IRIS+ a few feet away so I wasn't see what the HUD was displaying.
I would post my logs but the issue of "Error receiving log list" that other's have run into is prevalent. I have tried some of suggestions that were previously posted but I am still receiving the error....I will continue to try and figure this anomaly out.
Todd H
Oh and thank you to all the testers and programmers. I don't think that can ever be said enough.
Today I test for first time 3.3 rc11, two short flight to test the new controller, with standard params no tune yet and some wind; when I download the logs I find that RTL appears two or tree times but I didn't switched, I was near the copter and no failsafe err appears, I check PWM values and looks well, What can be happened?
2015-09-22 17-22-20.log
2015-09-22 17-39-30.log
Hi Cala,
If you look graph "Battery Issues" from the pull down in the log analyser, you can see strange drops in the VOLT reading (It actually goes negative). VOLT drop whenever there is a spike in THROUT (Maybe a battery issue). It seems that when both THRIN and VOLT goes low you get the RTL. It is very short as it seems that once the VOLT go back to normal so does your flight mode.
What power module are you using? Is it 6S?
I might be wrong but are you sure that you are not reading CURR as VOLT and VOLT as CURR? You volt values seem more like current readings (Goes up and down with THR) and the CURR values look more like battery voltage (Starts high and decreases over time).
When VOLT goes low but THRIN is high you do not seem to get the RTL. I might be wong but it seems to be the only common thing I could see.
I don't think that you are actually getting a voltage drop but you power module is reporting a bogus value.
I think you can change the pins in the config to swap these around.
Also, it seems that the first part of your flight is before the EKF is completely happy.
The latest MP has "ekf VEL tune" in the graph option pull downs. If you look at this you can clearly see when the velocity innovations IVE, IVN, IVD start.
I have been trying two different ways to avoid this:
1: Wait until I can arm with the Fence enabled
2: Arming in Poshold. (I usually take off and land in STAB but use this to check)
I think that either method requires both a good 3D GPS lock but also waits for the EKF to be happy with position and velocity comparisons between the IMU and GPS. Not sure if it is the Gyro's settling or the GPS velocities taking time to match up.
I have also noticed that if I land and take off without disarming the EKF noise is a bit higher. I think it may be due to GPS velocity measurements when the frame is landed (ie motionless) but GPS still registers small position shifts.
This does not seem to cause flight issues but I think it does affect things such as the origin setting. I have been playing it safe by making sure that the EKF is completely happy before taking off. It take a couple of minutes first time round but after that it is almost immeadiate.
Hope that helps!!
-
171
-
172
-
173
-
174
-
175
of 558 Next