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

        • eCalc, at least for data @hover, is way off. I don't know what they did, but comparing their current version to that of earlier ones,  anyone trying to use it for a build right now will not be getting accurate estimates

          When I set up my latest quadcopter a few months ago, eCalc estimated for 13x5.5 props, KDE 2814xf-515 motors and AUW of 2240g, @hover throttle position would be <45% IIRC which is pretty close to reality.  Now it says with the exact same configuration except 15x5.5 props @hover throttle position is 55%  !!! 

          That is absurdly wrong.

          CHrT4we.png

          On my Y6 eCalc says hover current draw is 38A, when actual is <28A.

          I've contacted eCalc to review their new version because right now it is completely unreliable.

    • Hi Igor,

      3.80v per cel. Means that your charger was in a storage mode.
      It is the ideal voltage to store LIPO battery's for a long time, but for flight your cell voltage should be at 4.20v per cell.

      The best way to charge is by using the Balance Charge mode, which Charges.al Cells to 4.20v
      It should never go over this voltage !

      Ok forget it, you started with this value of 3.80v, so forget my comment.

      Erik
      • Hi Erik,

        Thx for your answer.I wasn't clear enough, when I measured my battery after the flight it was 3.80V per cell. The battery  was fully charged (4S 16.8V, 4.20 per cell) when I started my flight.

    • Hi Igor,

      Please show us your log file.

      • Unfortunately I can't.

        All my logs are gone, wtf?

        It seems that my complete logs folder is wiped out. No logs whatsoever.

        I do have a backup of my old logs on my server, but I didn't copied the latest files.

        Damn!

        How is it possible? Is it MP fault?

        Now I will never know what happened... :-(

    • I have had the same experience twice, but I got the logs. When examine them I saw that the fc tried to correct but the motor did not respond, so I thougt motor or esc failure? Changed motor but after 2 more flights the same thing happens, so now I have ordered new esc to see if that will fix the problem? It was Engine 2 on my quad that did not respond to the fc so it went to the left and down...

  • Randy,

    Do you think that the mode switch channel remapping will be available for PixHawk in the final release? I am waiting on this feature for my Phantom Clone with a PixHawk FC. 

    Thanks

    Joe

    • No, I don't think it's going to make AC3.3. I could probably do it without too much trouble, but we've pretty much reached a "feature complete" stage and no feature additions are going in.  Just cleaning up any remaining bugs.

      And I still have a fair amount of work to do just getting Heli working right again.

      • Roger that. 

        Thanks for the update. We appreciate all the time the Dev team puts into this project. 

        Thanks

        Joe

  • Hi

    Some pages of the website say that the firmware to control a CoaxCopter is available and others not?
    what about it?
    What electronic card should I use for a CoaxCopter: PX4 or PixHawk?

     

This reply was deleted.

Activity