Developer

ArduCopter-3.0.1 released!

ArduCopter 3.0.1 has been released and is now available in the Mission Planner, firmware.diydrones.com, GitHub and the new Downloads Area.

Warning #1: Compass calibration and reducing interference is far more important than with 2.9.1b

Warning #2: GPS glitches can cause sudden and aggressive position changes while in loiter mode.  You may wish to reduce the Loiter PID P to 0.5 (from 1.0) to reduce aggressiveness (see image below of where this gain can be found in mission planner).

Warning #3: optical flow is not supported but will be back in the next release (AC-3.0.2 or AC-3.1.0).

Warning #4: loiter turns does not maintain altitude.  This bug will be fixed in AC-3.0.2.

Warning #5: This release has only been lightly tested on Traditional Helicopters.

Improvements over 2.9.1b include:

  • Inertial Navigation for Loiter and Auto meaning much more accurate control (Randy,Leonard,JonathanC)
  • 3D navigation controller follows straight lines in all dimensions between waypoints (Leonard,Randy)

         WPNAV_SPEED, WPNAV_SPEED_UP, WPNAV_SPEED_DN, WPNAV_ACCEL allows configuring speeds and acceleration during missions

  • "compassmot" to compensate for interference on compass from the pdb, motors, ESCs and battery.  (Randy,JonathanC) (Set-up video here)
  • Safety improvements:
    • simple Tin Can shaped Geo Fence
    • pre-arm checks to ensure all calibration has been performed before arming (can be disabled by setting ARMING_CHECK to zero).  (video description here)
    • GPS failsafe - switches to LAND if GPS is lost for 5 seconds
    • stability patch improvements to stop rapid climbs in very overpowered or overtuned copters
  • Circle mode improvements including "panorama" when CIRCLE_RADIUS set to zero (Randy,Leonard)
  • SONAR_GAIN parameter added to allow better tuning of sonar surface tracking
  • CH8 auxiliary switch (same features as CH7)
  • works on PX4 (some minor features still not available) (Tridge,PatH)

How to upgrade:

1. Make sure you are using Mission Planner 1.2.59 or newer (get it here)

2. Click on the MissionPlanner's Hardware, Install Firmware screen.  The version numbers should appear as "ArduCopter-3.0.1", then click the appropriate frame icon and it should upgrade as per usual.

3. Reduce the Loiter and Alt Hold PIDs if you have modified them from the defaults.  The modified PID values for the 3DR frame can be seen in the image below.

Note: Nav parameters have been combined with Loiter so do not be concerned if you can't find them.

3691038784?profile=original

4. Although not directly related to this release, if you purchased an APM prior to March of 2013, update your PPM encoder to the latest firmware (instructions here).

5. Try out the new version in stabilize mode first, then alt-hold, then loiter and finally RTL and Auto.

Numerous How-To videos are available:

Special Thanks to Marco, DaveC and the large number of testers on the pre-release thread who put their copters at risk during the extended testing period.  Some of their videos can be found here, here, here, here, here and here.  Thanks also to MichaelO for the MP changes required for this release.

All feedback welcome.  Please put your questions, comments (good and bad!) below.

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

Join diydrones

Email me when people reply –

Replies

  • Randy, I was reading this 6 month old post

    https://github.com/diydrones/ardupilot/issues/249

    You said it was fixed, but just wondering doing a mission with waypoints is it safe to go 10m/s, by setting WPNAV_SPEED to 1000, I see it can even go to 2000, Id like to try, but do not want to fly to the ground :)

  • Upgraded to rc5 today on my octo and was messing with the armed motor speed parameter. I don't remember what it was set to initially but I think it was 100. I slowed it down to 70 and then even tried 50 but I would just get some clicking noise from one of the escs or motors even set to 70. Even when I changed it back to 100 and wrote parameters I had the same behavior. It seems that the new setting doesn't stick right away. I restarted the APM and changed the settings again and eventually got it back to what it was. Are the values listed in the full parameters the only ones you can use or can you input 90 for example? I was hoping for a slower spin but the way it is now set to 100 is fine. Does it require a reboot for the settings to take effect?

  • Can someone post a link to the changes since 3.0.1. I thought I saw a post a few pages back but not finding it now.

  • I'm in the middle of upgrading an octo that I prefer to not have a surprise with :) I always do a save parameters before doing an upgrade and then do a compare. I don't do an erase first unless necessary. This time I noticed some differences I'm not use to seeing. Should I carry any of these over besides the battery capacity?

    param1.png

    param2.png

  • Hello,
    Today I made ​​the test with AutoTune fw 3.1.RC5, everything was perfect the test lasted about 4 minutes with excellent final results. I saved the new parameters, and then I flew both Stabilize and then AltHold Loiter, everything was perfect very stable and maintains the height in AltHold in a wonderful way. Good work boys.
    I had a hint of wobble as you can see in the video and in shape and at the end of the second log.
    the first log is more Autotune test flight.
    In the second log is the wobble.
    Thank you for your work.

    Greetings

    Video

    3692865760?profile=original

    2013-10-25 17-05 2.log

    2013-10-25 17-07 3.log

  • Moderator

    I'm having compass issues again with v3.1rc5.

    The resolution is described here in this issue.

    Randy, would it be possible to please get it included in rc5 beta and/or the final release?

  • I've made another test with autotune, but the new result wasn't as good as the previous one, horizon was wobbling when flying straight. Maybe because when I was autotuning, I needed to reposition my copter some more times.
    One strange thing (or maybe not), ROLL/PITCH rate PID are differents, but STAB P is the same for ROLL/PITCH, so I was wondering why this one is not also different ?
    I tried also to disable CLI (#define CLI_ENABLED DISABLED), but after you can't download any logs. Is it possible, when CLI is disabled and LOGGING enabled, to have a minimum of CLI to allow log's downloading ?

    2013-10-24 19-49 1.log

  • File 3

    2013-10-24 16-56-41.tlog

  • The files...

    2013-10-24 18-38 7.log

    2013-10-24 18-26-19.tlog

  • Leonardo or Randy, I almost updated to the new beta today after having 6 successful flights without the surging problem. Then on my 7th flight it showed up again. I'm including the logs here. In the last part of the flight I was trying to provoke it and shooting around and on one of those hard pitch movements it did the surge also. Otherwise it would just randomly do it while trying to maintain a hover.
    I think I've attached the right logs but if you don't find the problem let me know and I will upload another one. If this is the right log then it happens right in the first 30 seconds and all through the test.
    The third attachment is an extra tlog just incase the other one isn't the right one. I'm pretty sure the flight is in the first two attachments but let me know if it's not and I will upload the other files.
    BTW, what data field are you viewing in the log browser to see the problem?
This reply was deleted.

Activity

Jose Araujo liked Jose Araujo's profile
Aug 29
spencer harvey liked spencer harvey's profile
Jul 9
More…