Questions from a new Arducopter owner

I received a new prebuilt Arducopter last week from Udrones and I am having some problems getting ti to fly with the stability that I am expecting.

I am partially there, but I need some help.  I have been pouring over all the information I can find, but some nagging issues seem eluding me, I can't seem to find the answers.

The Arducopter arrived with the standard blue motors, 20 Map ESC's The 2.5 MP, a Sonar sensor, The 3DR Radio kit and everything wired, and set up from Udrones.  I installed my radio receiver (Spectrum AR8000), installed, installed the Mission Planner, did the update, got it working on the USB port and got it working with the Radio (FT232 driver).

Here's the problem I have. In Flying mode "stabilize", initially I have a lot of drift, It flew exactly like a Heli that just has conventional gyro stabilization, which now I understand is what it is supposed to do, but It had a lot of bias, and even with no wind, would move pretty aggressively rather than stay in one spot. So I set up my other flight modes, position and loiter.

Positon hold seemed to be better but it still tried to wander and needed constant control of throttle to keep it at a particular altitude. Ok, so I guess that is somewhat normal except that I would expect it to hold its location better than it does. So then I tried the Loiter mode. In Loiter mode, it immediately begins climbing, and only if I drop the throttle to 0 does the climb stop. 

In testing that mode, I have learned to put the throttle back up to mid stick and then switch back to stabilize quickly.  

Then I found that in stabilized mode, by adjusting the trims for pitch and roll, I could get the Arducopter to remain fairly stable although I have to be very active on the throttle stick to maintain altitude. 

I ran the level routine with my ArduCopter completely level, with the trims back to neutral and tried a test flight again, and I still had to adjust my trims to get it to hover in in spot. 

I think I can deal with that, and will have to learn about adjusting the PIDS to get the stability I want.

1. Which brings me to this question: can I save my entire configuration before I start attempting to find tune the PIDS, so I can revert back to factory by reloading the configuration without having to re-install?

I started to try and figure out why it wants to climb when I switch to Loiter mode;  I wonder if the Sonar/GPS/BARO  combination is somehow needing to be tweaked, or if there is a faulty hardware, or setting. In the Mission Planner, under Advanced Params..

2. I notice that AHRS_BARO_USE is disabled "0"   Is that right?

3. the next parameter: AHRS_GPS_GAIN is set to 0, is that right?

Should those be enabled and set?

It seems to me that these settings might be relevant, but I am new to all this.

As a test, I have disable the Sonar, and I want to try a test flight to see how this affects the altitude stabilization, but unfortunately the winds right now are gusting beyond 20 MPH, so not a good time to test fly.

Here is the config that I have right now, does this look right for default PIDS for a new aducopter 2.5? the loiter Rate P seems higher than Pitch/Roll P values, but what do I know, none of these are messed with, are they correct starting points?


If someone could help me understand this, thanks in advance!


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

Join diydrones

Email me when people reply –


  • Some questions about failsafe

    When in the failsafe setup screen, there are two checkbox's one is labeled:

    "throttle failsafe"

    the other is labeled: 

    "throttle failsafe action"


    By default "throttle failsafe" was unchecked and 'throttle failsafe action" was checked.

    I set up failsafe for my radio so that channel three goes below 975 if the transmitter is turned off.

    I want that condition to trigger RTL.  I think i have done that right. but:

    I don't understand the labels for the options in the failsafe setup screen, how are they to be used? I would also like to have a switch on the transmitter like my landing gear switch to trigger RTL.  

    Not knowing what I am doing, I have checked the "throttle fail safe" hoping that is correct, but what the heck is "throttle failsafe action" ???

  • Ok, sounds like a good plan..


  • Finally got to work on getting my week old Arducopter dialed in. I have a stock new Arducopter with the blue motors (AC2830-385m 850kv) with the stock esc.s the APM 2.5, with 2.8.1 uploaded and the 3DR Arducopter param file with no changes, except for toggling AHRS_BARO_USE to enable (I don't know, but I guess this should be enabled if you want to add the barometer sensor data to the auto altitude hold calculation.

    Still, i have the problem I have had since the beginning. as soon as I turn on loiter, it climbs aggressively. I have to react going back to stablilize right away to stop its climb (If I were at the flying field I could let it go a bit).

    But I'm puzzled, what do I do to trouble shoot this. Altitude hold seems to be working fairly well, (until I enable the Baro, it wasn't maintaining altitude I believe, (I've tried so many things I'm not sure)

    anybody got any ideas?

  • For saving configuration you can go to advanced parameter list screen, then there is an option to save.  That way you can restore at any time.  Note it will restore everything including dynamic compass calibration values, radio limits etc..

    For the 'baro use' option I also have mine set to zero but I still get baro.  Probably just an exotic option safe to ignore.  I also have gps gain set to zero without issue.

    For the altitude control issue, try changing your throttle rate to values between 0.1500 and 0.6000 .  You can do this using the channel 6 option which is highlighted in your picture.  Just select the value you want to change from the list (the names are a bit cryptic) and be very sure to set the minimum and maximum values correctly.

    Then, assign a dial on your transmitter to a spare channel (say channel 8).  Then connect channel 8 on your receiver to the 6th channel on the APM.  You can then adjust the parameter during flight by moving your dial.  I would suggest starting by tuning throttle rate p and rate roll p.  They are the most noticable.

    Another note, be careful to refresh values from the flight controller when you are modifying the channel 6 options in mission planner.  I believe there is a bug (it might be fixed) where some of the fields get blanked out if you hit save in the wrong order.  To be safe I recommend refreshing the screen after all changes.  It has the extra benefit of showing you the exact value your channel 6 dial is pointing to.

This reply was deleted.


DIY Robocars via Twitter
RT @donkey_car: Human-scale Donkey Car! Hope this makes it to a @diyrobocars race
Jun 25
DIY Robocars via Twitter
Jun 25
DIY Robocars via Twitter
Jun 16
DIY Robocars via Twitter
RT @GrantEMoe: I won my first @diyrobocars @donkey_car virtual race! Many thanks to @chr1sa @EllerbachMaxime @tawnkramer and everyone who m…
Jun 13
DIY Robocars via Twitter
RT @gclue_akira: JetRacerで自動走行したコースを、InstantNeRFで再構築。データセットは別々に収集 #jetracer #instantNeRT
Jun 13
DIY Robocars via Twitter
RT @SmallpixelCar: SPC 3.0 Now the motor also works. This car is doable. I just need to design a deck to mount my compute and sensors. http…
Jun 13
DIY Robocars via Twitter
RT @SmallpixelCar: My new car SPC 3.0.
Jun 7
DIY Robocars via Twitter
RT @SmallpixelCar: High speed at @diyrobocars thanks @EdwardM26321707 for sharing the video
Jun 7
DIY Robocars via Twitter
RT @SmallpixelCar: Today at @RAMS_RC_Club for @diyrobocars. Used @emlid RTK GPS and @adafruit @BoschGlobal IMU. Lap time 28s…
May 28
DIY Robocars via Twitter
May 15
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