Developer

ArduCopter-3.1 released!

After months of testing AC3.1 is finally available in the Mission Planner and GitHub.

Warning #1: If the vehicle is left landed (but armed) while in AltHold or Loiter mode for more than a few seconds, the vehicle may suddenly jump into the air the moment the pilot raises the throttle above zero.  The reason is the baro altitude may fall while the vehicle is sitting on the ground.  In AC3.2 this bug is fixed because we reset the target before take-off.

Warning #2: Motors will spin (slowly) by default as soon as the copter is armed!  You can switch this feature off by setting the MOT_SPIN_ARMED parameter to zero.

Warning #3: if you see "Bad Gyro" on the HUD then you may have a blown 3.3V regulator.  See this thread for details.

Warning #4: if you use a sonar set the SONAR_GAIN parameter to 0.8 or lower

Warning #5: Trad Heli users should now connect their main rotor ESC to APM's RC8 output

Warning #6: Trad Heli BUG causes loss of collective control in ACRO mode if swash type set to flybarred (i.e. not flybarless).  Will be fixed in AC3.2.

 

The major improvements over AC3.0.1 are (full list here):

1. Pixhawk support (Tridge & PX4 development team)

2. Autotune of Roll and Pitch gains (Leonard/Randy)

3. Drift mode (Jason)

4. Improved Acro (Rob/Leonard) and new Sport mode (Leonard)

5. Arming, Take-off, Land in Loiter or AltHold

6. TradHeli improvements (Rob) including:

a) support for direct drive tail rotors

b) smoother ramp-up of main rotor

c) reduced collective for better control in stabilize mode (STAB_COL_MIN, STAB_COL_MAX params)

7. Support for SingleCopter (Bill King)

8. Performance improvements resolve AltHold troubles for Hexa & Octacopters

9. Safety Improvements:

a) GPS Glitch detection (Randy)

b) Motors spin when armed (Jonathan Challinger)

c) crash detector shuts off motors if copter flipped for 2secs

d) batt failsafe option to RTL instead of LAND, gps failsafe option to trigger AltHold instead of Land

e) more pre-arm checks of inertial nav speed,

10. Bug fixes:

a) optical flow working again (although performance is still not great because not integrated with inertial navigation)

b) ROI working (use DO_SET_ROI command)

 

How to upgrade:
Click on the MissionPlanner's Initial Setup >> Install Firmware screen.  The version numbers should appear as "ArduCopter-3.1", then click the appropriate frame icon and it should upgrade as per usual.

Special thanks to Marco and the many beta testers on the AC3.0.1 thread who put their copters at risk during the testing of this new version and uncovered many problems so that you don't have to!  Here are some of their videos: loiter in wind, patio sonar, autotune, autotune2, roi, beach, acro, vrbrain, tricopter, train spotting, radio failsafe, the tree, double loiter

 

If you haven't seen it recently, please check out the ArduCopter wiki.

 

Feel free to post comments below and we're going to use the new APM Forum for support issues so please post your support requests there.

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

Join diydrones

Email me when people reply –

Replies

  • Major milestone today!

    I flew my first ever autonomous mission using my OpenPilot Revolution, running the Virtual Robotix port of AC 3.1 RC5 / VRBrain to the Revo (thanks Stefan!). I was super nervous, as I've never released control of my quad to anybody or anything else. It worked! The flight used different altitudes, delays, a loiter circle, and RTL. I had between 9 and 11 satellites, with an HDOP of 1.7-1.3. It landed 1m from its takeoff point. Awesome!

    z-axis: ArduRevo 1st Autonomous Flight 2014-01-08 from Brit Davis on Vimeo.

    z-axis_1st_AutonomousFlight_MissionPlanner_FlightPlan.jpg

    z-axis_TestQuad.JPG

    Taranis and Nexus 7.JPG

  • Hi Guys, i've just had my first flight on 3.1 stabilize is fine and drift (love it) works great. However althold, loiter and RTL all when switched make my quad rapidly descend. (I have an external mag configured and tested) and 2.9.1 was never an issue. Could one of you kind gentlemen please take a look over my log file (attached) and tell me what could be my issue.

    Here's a video of the crash, towards the end is the moment where it switches to RTL and I didn't get it into stabilize mode quick enough. https://www.youtube.com/watch?v=mJ5jVtLIpvg

    hmLyJm1.jpg

    TIA Drew

    2014-01-08 16-58.log

    2014-01-08 16-58.kmz

    2014-01-08 16-58.log.gpx

  • I like the new version.  On my Trex 450 I can take off, go to another point, land, take off again, RTL and land automatically.

    It's a little scary to watch because on the first land there was a good crosswind and the heli sat on the upwwind skid for a two second eternity until it decided to take off again.  It did it over and over and I think it's just being smart.

    If I put a loiter delay between the land and Take off waypoints,will it sit there nicely until the time is up (maybe even on one skid)? I'm reluctant to try.

  • Hi all, I finally got around to giving AC3.1 a good thrashing on the weekend. I put it through about 2 hours of flight time, here's some observations, mostly general feedback rather than support so I'll post it here rather than the forum, though I might follow up on some things there.

    1) Two thumbs up for 'Spin when armed'. I was skeptical but after one or two flights it feels perfectly natural now and it definitely does the job of commanding more respect for an armed copter. For example I forgot to hit record on the GoPro before arming one time, usually I wouldn't bother disarming and just reach through the prop area and hit record, but with the slow spinning props it was clear I should shut down properly before going near it

    2) And three thumbs up for Auto Tune, wow! I knew I still had some tuning to do on my quad, but never bothered to spend the time learning the arcane art to get the last 10%. After auto-tune it is a whole new beast, *super* tight and responsive and much less wobble on descent. It was a touch too aggressive in pitch so I de-tuned that just a little then pumped up the expo on my transmitter so that my control inputs were smooth again with the much tighter response. It is amazing to be able to click the pitch trim up and down a notch and see the copter flick to a slightly new angle with each click, so tight!

    Two little things I noticed though:
      2a) I initially had some pitch trim on the transmitter which prevented it starting the auto tune until I reduced the trim to get back into the deadband. We should add a note about this to the auto tune wiki page. I imagine the auto-tune process could be adversely affected by an out of trim copter too?

      2b) The autotune procedure tweaked my gains accurate to 4 decimal places but I noticed when saving out the config from Mission Planner that it only retains 3 decimal places. I've added an issue to the MP issues list on github about this (https://github.com/diydrones/MissionPlanner/issues/295).


    3) Tested DO_LOITER_TURNS and ROI as part of a complex auto mission, they work as advertised, though I was initially caught out by needing a separate ROI command between each waypoint. Although the command is documented that way, I think it makes a lot more sense for it to be persistent as mentioned by a few people here: https://github.com/diydrones/ardupilot/issues/569. Though if it were persistent you'd need a way of cancelling ROI to revert to normal look ahead yaw.

    4) Tested geofence, it works as advertised, though on one fence break the copter flipped over almost backward and lost a lot of height, almost crashed. Log attached, you can see at line 18122 the pitch goes to 83 degrees and it drops. The geofence ERR message is just before that on line 18100. I tried reproducing that both with geofence as well as by manually switching from STAB to RTL in aggressive forward flight, but didn't see it happen again.

    5) A couple of disarm issues/inconsistencies: 

    5a) after letting a geofence initiated RTL proceed through to an automated landing and automated disarming, I later couldn't re-arm, and it took me a minute to figure out that I was still in RTL mode. I think it would be better if copter always switched back to STAB as part of the automated disarm routine, to return to a known state where you can re-arm again. Anyone agree?

    5b) when you land in an AUTO mission it winds down the props to 'spin when armed' speed but doesn't auto-disarm after 15 seconds. The LAND command is documented that way, but it is a different post-landing behaviour to other modes, and that is more apparent now with spin when armed. I would hope to be able to do a one-way mission where it lands land and disarm safely at the end. Is there a parameter to configure this, or some way of invoking a disarm at the end of an auto mission?

    6) New Acro mode is pretty awesome, but I think the default ACRO_RP_P gain should be a lot higher. My first flips were pretty scary as I watched it slowly rolling through inverted even though the stick was jammed all the way over. After increasing ACRO_RP_P to 7 it felt much better and safer to flip. Also, I noticed that when using CH7/8 for the Acro trainer switch it doesn't seem to actually update the ACRO_TRAINER parameter, so you can't refresh in MP and verify you've got the trainer mode set up correctly before using it. It would likely end badly if someone thought they had it in acro trainer mode 2 (limited and self-levelling) when it was actually set to 0.

    7) I thought Drift mode would be another simple/trainer mode I wouldn't be interested in, but it was great fun rocketing around without having to worry about keeping your turns coordinated. This is a pretty big deal for newcomers I think - in no time at all they can be ripping around the sky like a pro in this mode. Nice work Jason!

    2014-01-05 12-30 - Capilano and geofence and acro.log

  • TUNING GUIDE

    Hello guys!

    I was watching the Marcos Robustini's Videos a lot of times, and I'm impresed how works his hexa!

    So i'd like have a guide or any idea what parameters change and how to get a rock solid loiter as his hexa.

    Best Regards!

  • Hello today killed his quadrocopter _-OO-_
    today fell, before the fall was an oddity убераю gas % to 40 to decline and he knocked engines, let the gas up to 60% he started and stopped and started to take off clears up again to 50-40% again, jamming

    2014-01-07 17-07.log

    2014-01-07 17-05-16.tlog

    https://storage.ning.com/topology/rest/1.0/file/get/3692914904?profile=original
  • Distributor

    Hi Randy, happy 2014!!!

    I just updated my PX4 to AC3.1 and after that I have no data from my spektrum satellite receiver  when I try to do the radio calibration (the biding led on receiver is orange that means found TX)

    Could be any incompatibility with the new firmware? Do you have noticed the PX4 satellite receiver port was tested on AC3.1 for anyone?

    See you,

    Guto

  • I am upgrading to the 3.1 from 2.9-Is there a list of parameters that need to be adjusted as you suggested in 3.0 version?

  • What Parameter tells you that the aircraft hit a failsafe in the Logs? Thanks

  • Maybe a bug... Flying mostly development code, I've flown 3.1-rc7 with my newly build tricopter. All flies very well, but in Loiter, when trying Macro's trick to let the copter spin using Yaw, the motors sort of shut down and copter went to ground. Releasing yaw, let copter recover and continue loiter at original height. First I thought that copter could not maintain height when too much yaw applied, but also when trying with very little yaw, the same thing happened. When doing the same trick in Stabilize mode, copter behaved normal.

    Maybe this was fixed in the final release. Since weather is really bad here, I didn;t try that yet.

    If weather gets slightly better I'll try again and will also try the quadcopter. Maybe some other tri-copter fliers are able to test the same (Macro) trick.

    Regards,

    Walter

This reply was deleted.

Activity

DIY Robocars via Twitter
Sunday
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
DIY Robocars via Twitter
May 11
DIY Robocars via Twitter
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Noticed my car zigzagged in last run. It turned out to be the grass stuck in the wheel and made the odometry less accura…
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Test my car. RTK GPS worked great. Thanks @emlid for their support. https://t.co/EkQ6qmjmWR
May 8
DIY Drones via Twitter
RT @chr1sa: @kane That's @diydrones circa 2009. Still have a box of those Canon cameras that we used to strap into planes, just like this.…
May 3
DIY Robocars via Twitter
RT @chr1sa: Our next @diyrobocars race is going to be outside at a real RC racetrack in Fremont on May 28. Fully autonomous racing, head-to…
Apr 30
DIY Robocars via Twitter
RT @f1tenth: Our Spring 2022 F1TENTH course @PennEngineers is coming to an end with a head-to-head race as a big finale. So proud of our st…
Apr 26
DIY Robocars via Twitter
RT @DanielChiaJH: I wrote a thing! Throughout the development of my @diyrobocars car I've been using @foxglovedev Studio to visualize and d…
Apr 23
DIY Robocars via Twitter
RT @SmallpixelCar: My new car for high speed. Low body, everything ( @NVIDIAEmbedded Jetson Xavier NX, @emlid RTK GPS, IMC) under the deck…
Apr 23
DIY Robocars via Twitter
Apr 21
DIY Robocars via Twitter
RT @f1tenth: F1TENTH Race training setup @PennEngineers for our upcoming ICRA2022 @ieee_ras_icra competition. @OpenRoboticsOrg @IndyAChalle…
Apr 21
DIY Robocars via Twitter
RT @fatcatFABLAB: Proud to be hosting a restarted DIY Robocars NYC Meetup April 26. Come by if you want to talk about and race self-driving…
Apr 17
More…