Developer

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!

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

          • Back when I was working with Kev on his awesome APM Log File Analiser http://www.rcgroups.com/forums/showthread.php?t=2151318 we ran into a few boards that showed USB connected even in flight. I had the issue myself a couple of times but I was able to get rid of the error [at least on my old APMs] by doing a full erase of the eeprom and re-flashing the ArduCopter firmware and re-calibrating. It was common enough that he put in some hooks to look at the issue directly and post the error in the Analyser. http://www.rcgroups.com/forums/search.php?searchid=51531995&que...

            I don't remember what the reason was to be honest but you might contact bionicbone [Kev] about the issue. I no longer see it being reported in the app though so I don't know :(

            • Hi Craig,

              The issue was a bug in my analyser because the USB bit moved around through the different versions of ArduCopter, for exmaple:

              v3.1.5: uint8_t usb_connected       : 1; // 15      // true if APM is powered from USB connection

              v3.2: uint8_t usb_connected       : 1; // 13      // true if APM is powered from USB connection

              Since my code always used bit 13 so when users where using v3.1.x  I was actually looking at one of a pair of bits that reports the status of the CH8 switch - thus giving random reports.

              The bug was fixed some time ago, the latest version of the APM Log File Analiser  works with 3.1.x and v3.2.x versions, for other versions then this the bit is ignored. Its a simple add once v3.3 is released or if we are sure the bit will remain at position 13.

              For info: I only check the DU32 bit, the new one in the POWR data is not yet reviewed.

              Regards

              Kev

              • Thanks for the clarification :) Looking forward to the new builds. 

            • Developer

              It was a while ago but I think we discovered that it was an error in the log analyser - it was looking at the wrong bit perhaps because of an ardupilot software update that moved the bits around in the dataflash message.

      • Developer

        Hi Paul,

        The Yaw autotune is more aggressive now as we were getting very low values on the ATC_Accel_Yaw and the result was very slow yaw response. The downside of this is that high powered copters can give a little jump on each autotune test or when applying yaw.

        The solution is to reduce the ATC_Accel_Yaw value until you don't get a jump anymore.

        • I confirmed what was the issue with jerky yaw. I flew yesterday on the single glacier 45C pack, 5000mah.

          today I loaded double pack and did autotune this way - and it completed perfectly setting drone to the optimal attitude, it is as smooth as it was before.

          I guess when it is underloaded, with 6 4006 620kv motors it is too much thrust for autotune to generate best results.

  • Connecting power to  pixhawk with 3.3

    My quad has the lipo and power connector at the bottom of the quad, meaning I have to turn the quad 180 degrees for connecting the power en then turn around and put on the ground

    Can this be done wile the pixhawk led is white or is this a nogo situation?

    when is the sensor calibrating starting when power is connected?

    • Developer

      Peter,

      The critical time is when the LED is flashing red and blue.  That's when it's doing the gyro calibration and during that time the vehicle shouldn't be moved.

    • Until 3.2.1 is calibrated when armed; I didn't read that this change to 3.3

  • Auto-Tune fly away.  I just completed a fresh build 960 hex and have flown it several times on rc7 with very good performance in stabilize, loiter, alt hold, land and rtl.  The vehicle did not exhibit any problems at all, in fact it flew remarkable well with default PID's.  It remains a question why I even did an Auto-Tune at all, but that is where it all went wrong.  It did the initial twitch right and corrected then twitched left and drifted off about 10 meters, then rolled right and flew off about 30 meters before I switched off AT and hit RTL.  It came back without a hard landing but this is my first shot at a heavy and it made me pucker a bit.  If someone could take a look at the log I would appreciate it, I'm a little nervous to take it up again until I understand what happened.

    http://www.mediafire.com/download/likq7xv3icks18p

    Thanks, RB

This reply was deleted.

Activity

T-MOTOR liked T-MOTOR's profile
15 hours ago
DIY Robocars via Twitter
RT @gclue_akira: 柏の葉で走行させてるjetracerの中身 #instantNeRF #jetracer https://t.co/giVvuE4hP7
Jul 4
DIY Robocars via Twitter
Cool web-based self-driving simulator. Click save when the AI does the right thing https://github.com/pncsoares/self-driving-car
Jul 4
DIY Robocars via Twitter
RT @donkey_car: Human-scale Donkey Car! Hope this makes it to a @diyrobocars race https://www.youtube.com/watch?v=ZMaf031U8jg
Jun 25
DIY Robocars via Twitter
Jun 25
DIY Robocars via Twitter
Jun 16
DIY Robocars via Twitter
RT @GrantEMoe: I won my first @diyrobocars @donkey_car virtual race! Many thanks to @chr1sa @EllerbachMaxime @tawnkramer and everyone who m…
Jun 13
DIY Robocars via Twitter
RT @gclue_akira: JetRacerで自動走行したコースを、InstantNeRFで再構築。データセットは別々に収集 #jetracer #instantNeRT https://t.co/T8zjg3MFyO
Jun 13
DIY Robocars via Twitter
RT @SmallpixelCar: SPC 3.0 Now the motor also works. This car is doable. I just need to design a deck to mount my compute and sensors. http…
Jun 13
DIY Robocars via Twitter
RT @SmallpixelCar: My new car SPC 3.0. https://t.co/CKtkZOxeNQ
Jun 7
DIY Robocars via Twitter
RT @SmallpixelCar: High speed at @diyrobocars thanks @EdwardM26321707 for sharing the video https://t.co/o4317Y2U1S
Jun 7
DIY Robocars via Twitter
RT @SmallpixelCar: Today at @RAMS_RC_Club for @diyrobocars. Used @emlid RTK GPS and @adafruit @BoschGlobal IMU. Lap time 28s https://t.co/R…
May 28
DIY Robocars via Twitter
May 15
DIY Robocars via Twitter
May 14
DIY Robocars via Twitter
May 13
DIY Robocars via Twitter
RT @f1tenth: Say hi to our newest #F1TENTH creation for @ieee_ras_icra next week in Philly. It’s going to be huge! 😎 🔥 @AutowareFdn @PennEn…
May 13
More…