Copter-3.3 beta testing

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!

I think rc7 is a best firmware to the date. I will try to play with my hex tomorrow.
Quad i played with today, and i could not make any control combination input to make it do anything wrong.

Only issue i see is still with gps glitches when drone reaches the ground, it sometimes starts reajusting rtl position inches away from the soil, catches ground by its landing gear and flips. I think it is due to an error in baro readings or gps data - i noted sometimes altitude reading goes totall wrong saying, like, 3m altitude when i lower it down to just under 1m height, but it is hardware. Unless we get good reliable sonar there is probably little to nothing that can be done to make drone know it is inches away from the surface.

Yet this issue happened only once. All other functions were great. Lift off is straight and smooth. No wandering about after lift off. I got it 100m into air, swapped to simple mode, flew all 6 modes, it landed back in rtl 30cm away from take off spot.

Gps super simple mode still sometimes flips controls but as i stopped using it - simple mode seems to work just fine. Ma be super smle mode is not even worth keeping if it is impossible to prevent controls direction invert at close range.

My 9yr old son flew it too, and is absolutely blown away. :)

May be there is something bad in there. But compared to positive things i think it is a best firmware to the date. I crashed once in rtl as drone started readjusting position close to ground and got caught by landing gear but i think it is hardware, plus, it only happened once. I wish i had more time to help write this, but, so far it looks to be a truly great code. It is way better than old 3.2 and response to controls is really nice.

I will try to link it with new banggood 3d storm32 gimbal, will see how that goes.

Replies

- Developer
  
  Randy > DG June 30, 2015 at 10:21pm
  
  DG,
  
  Thanks for the testing & report.
  
  I had a quick look at the logs and I don't see any particular issues. The vibration levels (see VIBE message) are pretty average. X-axis is higher than the other two (normally Z is the highest) but in any case, the levels are not terrible.
  
  As you suspected, the vehicle entered RTL while it was in Guided mode probably because the connection to the tablet failed. I would have expected Tower to cry out "lost connection with vehicle" but that's really up to the GCS developers. Although the vehicle would have updated it's status to "CRITICAL" and sent that to the GCS, with the telemetry link down, it would not have gotten through.
  
  The vehicle does seem to climb from 4m to 10m at the beginning of the RTL. I suspect if it was given a bit more time it would have completed the regular RTL cycle. There's no record of the vehicle attempting to go into RTL a second time. It looks like you're not using ch5 flight mode switch to control modes, so perhaps it was switched using Tower? in which case, with the telemetry link down, that wouldn't work of course.
  
  The voltage and current recorded in the logs appears reasonable with the voltage dropping slowly from about 16.6V to 14.8V during the flight. The current seems strongly correlated with the throttle output and is at a reasonable 20apms most of the time.
This reply was deleted.
- Developer
  
  Randy June 30, 2015 at 7:03pm
  
  @Heddn,
  
  I think the reason for you crash is the same as why people were crashing with -rc6. Master does not yet include the patch that resolved the attitude issues found in -rc6 because the fix affects plane and rover so I need to get the plane/rover guys agreement first (Tridge and Grant). Hopefully we can get that into master soon, until then, stick with -rc7!
  - T3
    
    Thorsten > Randy July 2, 2015 at 4:37am
    
    Randy,
    
    I thought that this patch solved it:
    
    https://github.com/diydrones/ardupilot/commit/686b1137fa18713124868...
    
    Maybe he just missed it...
  - Paul Atkin > Randy June 30, 2015 at 8:28pm
    
    I think rc7 is a best firmware to the date. I will try to play with my hex tomorrow.
    Quad i played with today, and i could not make any control combination input to make it do anything wrong.
    
    Only issue i see is still with gps glitches when drone reaches the ground, it sometimes starts reajusting rtl position inches away from the soil, catches ground by its landing gear and flips. I think it is due to an error in baro readings or gps data - i noted sometimes altitude reading goes totall wrong saying, like, 3m altitude when i lower it down to just under 1m height, but it is hardware. Unless we get good reliable sonar there is probably little to nothing that can be done to make drone know it is inches away from the surface.
    
    Yet this issue happened only once. All other functions were great. Lift off is straight and smooth. No wandering about after lift off. I got it 100m into air, swapped to simple mode, flew all 6 modes, it landed back in rtl 30cm away from take off spot.
    
    Gps super simple mode still sometimes flips controls but as i stopped using it - simple mode seems to work just fine. Ma be super smle mode is not even worth keeping if it is impossible to prevent controls direction invert at close range.
    
    My 9yr old son flew it too, and is absolutely blown away. :)
    
    May be there is something bad in there. But compared to positive things i think it is a best firmware to the date. I crashed once in rtl as drone started readjusting position close to ground and got caught by landing gear but i think it is hardware, plus, it only happened once. I wish i had more time to help write this, but, so far it looks to be a truly great code. It is way better than old 3.2 and response to controls is really nice.
    
    I will try to link it with new banggood 3d storm32 gimbal, will see how that goes.
This reply was deleted.
- Michael June 30, 2015 at 12:26pm
  
  Something magnetic nearby perhaps. I have magnetic tool holders on the wall by my workbench and if I place my quad to close, I get the same errors. Actually anything magnetic in proximity will cause that error.
- This reply was deleted.
  - Andy Piper June 30, 2015 at 1:15pm
    
    I find sometimes MP does not report the offsets until you refresh the parameters.
Erwin Quilloy June 29, 2015 at 6:56pm

I flown my quad with Rc6 last saturday, everything seemed to be ok, except for the landing, my quad almost tilted upon triggering land. :)

by the way, which version of mission planner can you recommend, the official update or the beta update?
- Erwin Quilloy > Erwin Quilloy June 29, 2015 at 7:58pm
  
  same here, as soon as I read that note, I updated to rc7.but still havent tested it yet
- DG > Erwin Quilloy June 29, 2015 at 7:39pm
  
  Note on the first page:
  
  http://diydrones.com/forum/topics/copter-3-3-beta-testing
  
  I am using rc7, very cautiously.
  - Andy Piper > DG June 30, 2015 at 1:19pm
    
    I did a couple of long flights with rc7 this evening. Everything seemed fine. No different to rc5 that I could tell. Was a little windy and it held position well.

of 449

This reply was deleted.

Discussions

Copter-3.3 beta testing

Replies

Activity