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.

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 MarcoDaveC 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 hereherehereherehere 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.

Views: 385386

Reply to This

Replies to This Discussion

Bruce, Detlef.

Thanks for testing this. It's an important problem and we must find the real cause of it.

I do not think that this is a board tolerance issue, because we are far from the limit at 8 Mhz (the specified limit is 20 Mhz) and the SPI signal quality / timings on my board was very good. So good that i don't think that some boards could be bad enough to cause problems.

I would be interested to know how you are powering the APM board, and ask you if possible to redo the 8 Mhz test with a 5V BEC connected on a PWM input connector.

Thanks,

Olivier.

No problem.  I'll hook up a BEC to it this evening and report back!  

Thanks Olivier,

-Bruce

Hello Oliver,

Usually I feed the APM over the PWM outputs with a "Turnigy 3A UBEC w/ Noise Reduction". JP1 is closed (over a switch) and I jumpered the onboard fuse F2 and diode D1 so Vcc & 5V have all the same levels. The UBEC makes ~5.1V while my USB port is pretty much exact at 5V.

I have the problems either way if powered with USB or with UBEC. If I use USB (JP1 open) nothing else gets power in my setup - that's how I did the logs for Randy. I even disconnected the GPS while testing. I assume that external interference can be excluded in such case. I have a second board powered over USB (no peripherals connected) that doesn't show those issues so I assume my USB port is good to power the board without causing any problems. Could the wiring of the external compass cause some issues? I haven't tried to disconnect it.

Here are some pictures of my quad: http://youtu.be/LUXqf2vNyXY - GPS and compass sit on the top level.

Regards,

Detlef

I'm flying Acro with RP 10 now. :)

I didn't find it hard to control, I was actually pleasantly surprised.  Though, I don't know if I could do precision flying with it.  Could try a D/R switch too.  I have one set up, but didn't use it yet.

Hello. Today i test 3.1-rc5 on my quad X. 450 Size, 1000kv motors.

Autotune very good. More stability on fast land and more stability with sticks drop.

I have some questions:

1) What indicates YELLOW led in APM 2.5 (near blue GPS and red)?

2) I try Acro and i do not recognize the new behavior... Very strange and not habitually. If i fly only roll or pitch - then all ok, but i fly roll and pitch - then autorotation and fast fall. If i release sticks - then copter not stay horizon and fly down and side. I not see this behavior in 3.0.1. Please give instructions how i may do behavior how in 3.0.1

3) Battery "FailSafe" text always show in Flight data screen. I off checkbox in failsafe and alarm but i see this message again.When i off battery sensor (simple 2 resistors) in Additional hardware - then message off in Flight data. It bug or feature?

Hey Steve, any info on the machine?  It'll help Leonard when he sees this.  

I've got a quad which won't tune, and the only thing we can figure is the frame is too flexible.

Steve, if this is DwarfStar, it wouldn't surprise me to find out that it's just too flexible to auto-tune properly.  Especially since you're using the long arms.

I should talk to you about beta testing my new design. ;)

oh!  is it a 1000mm octo made of foam?  haven't seen that yet, but I'm in! :)

Heh, I was trying to do that with my Nerf quad, hit 25 m/s, kissed 28 once.  Takes a bit of room to get up to speed, and when flying manually you run out of room easily.

I actually tried changing the Angle Max parameter to allow 60°, but that didn't go so well.  I think Angle Boost was adding too much throttle, and/or it was just too much power for this frame to handle as it started behaving really badly so I had to reduce the angle to 50, now it's manageable. 

Bruce, Detlef, another interesting test to complement the BEC power supply test would be to disconnect every devices on the frame that could generate high frequencies in the Megahertz range or eat a lot of current on the APM power supply, for example video cameras, transmitters, servos and things like this.

There is quite a low probability that they could cause troubles on the APM but it's better to fully isolate the APM first so that we can narrow down the problem faster being sure that it is not caused by an external device interaction.

Thanks,

Olivier

Hi,

Is APM 1 supported or even tested with AC 3.1?? I'm still using 2.91B and like to update when 3.1 comes out.

Regards

Jani

Duh.. I meant 3.0.1. (Fumble fingers in action :)

Reply to Discussion

RSS

© 2019   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service