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

        • Developer

          Hi Randy Bachtell,

          I am very sorry to hear your copter was destroyed. I am afraid that I gave you bad advice. The redundancy of your hex appeared to be tolerating the motor loss. I suspect it was the specific advice to increase the Thr_Min that made the difference.

          This is definatly motor sync problems and is often caused by Simon K esc's. Sometimes it can be fixed with settings on the ESC, other times it requires different ESC's.

          Again, I am very sorry for your crash and the bad advice I gave you that contributed to it!!!

          Please PM me if you have any questions or help and I will do my best to help.

          • Certainly not your fault, whenever I look back on an incident I always wonder why I did what I did. This is another case of suspecting the firmware and being operator error. Artem helped with ESC research so when I build again I should be in better shape. 3.3rc7 has been working extremely well on all three of my other birds, thanks to all of you guys for the hard work.
            Pardon my ignorance but not sure how to PM you. I would like to contact you for advice on the rebuild and not jam up the discussion.

            Thanks to all,
            RB
          • Man, I've experimented with SO many simonk/blheli ESCs/6s/high pole count motors... I can tell you one thing.... both blheli and simonk can be made to run smooth with those motors, however, at 6s, the measures both blheli and simonk take to keep up sync, take huge toll on ESCs and require adequate ventilation. In some of my experiments, where I limited mount of airflow over ESC to none, 40A rated ESCs heated up all the way to 112 deg. C (yes, C) on ly at 6amp load.  The best ESCs I found so far for the 6s+high pole count/low kv motors are Hobby Wing  xRotor Pro 40A. regular xrotors 40a are good as well, but the pro ones on the same motors/props/battery/frame/flight controller give noticeably better wind performance and reaction time and allow to run higher PIDs, while remaining at ambient temperature. 

            • +10 on the HW XRotor 40A ESC's.  Every HW ESC I have ever used has been good, and the Xrotors are fantastic. I use them on a large Octo with 15" props running 6S on 320kV motors. Never a sync problem and they only get barely warm, even with zero airflow stuff inside the booms.

    • Haven't seen your logs, but it sounds awfully like sync loss :( ..... Did you bench testsed you ESC/motor/prop/lipo combo beforehand? During ATT firmware request very fast and large throttle changes, many simonk/blheli ESCs combined with h high pole count motors could loose sync, also are you running the gnd wires from each ESC back to pixhawk? 

  • Someone else's VIBE messages looked very different mine, here are mine:

    3702038941?profile=originalZ seems awfully high, and yet I don't see unusual vibrations on the IMU in the Z-axis and it flies fine. No clipping. Is this normal?

    • Developer

      Hi Andy,

      In my experience so far the Z vibrations are much worse than the X and Y. And these look ok.

      Staying below 10 most of the time is good. Spikes up to 40 seems to be ok. Anything averaging around the 20 to 30 mark is nasty and spikes above 60 is in danger of clipping.

    • I'm seeing very high vibe numbers also on my 450 quad. Yet the IMU Accel numbers don't look that bad. It seems to be flying OK but then, this is the only one I've ever flown so I have nothing to compare it to. Maintaining constant altitude in Stabilize is really challenging so maybe it's due to the high vibe figures?

      Screen Shot 2015-07-01 at 4.36.43 PM.png

      Screen Shot 2015-07-01 at 4.33.00 PM.png

      • Developer

        Hi Roger,

        When flying in Stabilize you arn't using the accelerometers for anything other than the calculations of your roll/pitch/yaw angles.

        Are you using a smooth throttle stick or do you still have the ratchet on. This is one of the big reasons some people have trouble with throttle control.

        • Leonard:

          Actually I just checked & I do have a light ratchet effect on the throttle, so I'll get rid of that.

          Thanks!

This reply was deleted.

Activity