Developer

ArduCopter 2.6 released!

Version 2.6 of the ArduCopter code is now available in the AP Mission Planner and in the downloads area!

 

Updates to MavLink 1.0 means you will need to use "ArdupilotMegaPlanner10.exe" to connect.  If you've updated your mission planner recently you should find this executable in the directory where the mission planner is installed.

 

The above video is done using a prototype 3dr ublox GPS which seems to have better accuracy than the standard mediatek.

 

Improvements over 2.5.5 include:
     - MavLink 1.0 support (use with ArdupilotMegaPlanner10.exe) [Tridge, Craig]

     - Stability improvements especially during level hover [Jason]

     - throttle range improvement (higher min and max) [Jason]

     - improved standard Loiter PIDs [Alan, Heino, Jason, Angel]

     - dataflash erase speed up ('+' messages removed but it only takes 6 seconds now) [Tridge]

     - Copter LEDs [Robert Lefebvre]

     - RTL loiter stage target set to home to improve final landing position [Jason]

     - flip & acro improvements [Jason]

     - circle mode target improvement for ground station [Jason]

     - Auto Approach [Adam Rivera / Marco]

 

Bug fixes include:

     - UBLOX driver fixes (lock should now be more reliable) [Tridge]

     - enable mavlink messages during dataflash erase which resolves issue in which new APMs fresh from the factory appeared unresponsive [Tridge]

     - proper printing of lat/lon values in dataflash logs [Randy]

     - removed duplicate GPS reads [Jason]

     - resolve flooding of telemetry link with low-battery warnings [Tridge]

     - RTL bug would land if rtl_approach_alt was more than 1 [Jason]

     - WP Radius could not be set larger than 1.3m [Jason/Randy]

 

Tuning:
PIDs are optimised for the 3DR/Jdrones quad with 850 motors and 10" props.  If you're using more powerful motors/props and are seeing bad flight behaviour in stabilize, start by turning down Rate Roll P in 25% steps.

This time we spent some time optimising the loiter PIDs.  Tuning loiter can be tricky so please refer to the discussions which will appear below for more community feedback on what parameters work best.
 
All feedback welcome below.  Enhancement requests and bug reports can be put into the arducopter issues list.  When possible please include logs (tlog and/or dataflash) and tell us whether you're using APM1 or APM2 and what version of the software you're using (presumably 2.6 but tell us anyway!).

 

Happy flying!

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

Join diydrones

Email me when people reply –

Replies

  • CDN..reallly....finally.

    Whats your store link?

     

  • Anyone tried this to shield magnetometer? I'm thinking to put this on the bottom and top of my apm.

    http://www.ebay.com/itm/Ultraperm-80-Magnetic-Shielding-MuMetal-Mu-...
  • now flying my AMP 1 with firmware 2.6 but did not last a minute in the air. I need to know if they can review the log and tell me what happened. I appreciate the help I can give. is urgent

    2012-06-20 19-11-33.tlog

  • ok.. My APM1 hasn't recorded any logs since I loaded 2.6.  How do I fix this?

  • Hi folks,

    I'm in an awkward position. I'm just completing a Y6 build (my first build, actually) and I'm starting to do some initial testing. My setup is as follows:

     

    Scarab YSiix airframe, 775kv motors, GWS HD-9050x3 props (3 blade, 9"x5" - balanced), 2650 4S, APM2 on AC2.6

     

    I have been running some tethered hover tests (light fingertip pressure to keep it in position) and I noticed that it was twitching randomly, mainly in the roll axis when one or the other of the front pods (2-3 or 1-5) seemed to do a momentary jerk up or down. Didn't notice it so much in pitch.

     

    Rather than tearing it apart and soldering all the motor connectors (that will come, but after I've confirmed everying is behaving properly), I started looking at the logs. I'm new to this, so it took some time to get familiar with the information, but it appears that the servo outputs to the front pods were experiencing random spikes (high and low) that appear related to spikes in the x accelerometer and x gyro IMU.

     

    Since I've never done this before, I'm not sure where the problem lies. Is this just a normal tuning issue (Rate Roll P, perhaps), or is this an indication that there is something amiss, either in the wiring of the copter, or in the sensors on the APM2?

     

    Logs are attached.

     

    Thanks!

     

    Brian.

  • I posted this earlier but I got no response and I feel this is a really significant issue and would really appreciate some input on it.

    Basically when you go into any automatic mode, the manual override serves to offset the set point for whatever auto function(s) you are in, this means that the least bit of stick displacement from center (or throttle from position alt hold was engaged in) causes continuous movement of set point causing continuous movement of copter in direction of displacement.

    Especially for the throttle, this means you are often going slightly up or down in alt hold mode.

    But it can also cause slow continual horizontal displacement if stick doesn't exactly return to dead PWM center.

    I think an adjustable dead band for the manual over ride might be the solution.

    Maybe it's already in there, but having an adjustable dead band for the manual over ride on auto modes seems like it would be a really big help.

    In Alt hold, I often end up with the Quad continuing to rise or fall slowly, and I have a very strong feeling this relates to my throttle being just slightly displaced from the point where I put it into Alt Hold which would act to move the altitude at which it was held.

    Possibly similar results on Loiter horizontally (drift). If there was a little bit of dead band this could be eliminated as even a a possibility, if it was parameter list adjustable, even better.

    For the throttle you could dynamically establish the dead band center point at the throttle position where alt hold was engaged, for the other axes, fixed stick center would probably be OK.

    The throttle is a particularly problematic example because if you use any Yaw control, you are bound to displace the throttle slightly.

    If I'm completely off on this please let me know. and please let me know what you think in any case.

  • is there any reason why my copter drop drastically in alt if i sw to alt hold or loiter with APM2 and 2,6 firmware.

  • Hello,

    at first many thanks to the Dev-Team, since i started in Sept. last year with a pre-finished Hexa by JDrones  with  2.6  now i feel the first time really save in the air with my lawnmower.

    My question:

    Pls. can anybody explain exact the difference between "Simple" and "Supersimple" ?

    And what happens, when i enabled the "Supersimple" - Option in MP  and switch with CH7  to "Simple" ?

    Thanks a lot for your answers

    Rolf

  • I'm having big problems with my compass now. It will spin, and move eratically, which makes my copter unflyable, however when I do a CLI compass test, it shows that it is fine every time. Does anyone have any ideas?

    http://diydrones.com/forum/topics/compass-spins-and-behaves-eratically

  • Just a thought,

    Maybe it's already in there, but having an adjustable dead band for the manual over ride on auto modes seems like it would be a really big help.

    In Alt hold, I often end up with the Quad continuing to rise or fall slowly, and I have a very strong feeling this relates to my throttle being just slightly displaced from the point where I put it into Alt Hold which would act to move the altitude at which it was held.

    Possibly similar results on Loiter horizontally (drift). If there was a little bit of dead band this could be eliminated as even a a possibility, if it was parameter list adjustable, even better.

    For the throttle you could dynamically establish the dead band center point at the throttle position where alt hold was engaged, for the other axes, fixed stick center would probably be OK.

    The throttle is a particularly problematic example because if you use any Yaw control, you are bound to displace the throttle slightly.

    If I'm completely off on this please let me know. and please let me know what you think in any case.

This reply was deleted.

Activity

Joseph Udofia liked Joseph Udofia's profile
yesterday
DIY Robocars via Twitter
Jan 28
DIY Robocars via Twitter
RT @Heavy02011: ⁦@diyrobocars⁩ : A Home-brew computer club* for Connected Autonomous Driving. talk at #piandmore ⁦@PiAndMore⁩ on Jan 23rd h…
Jan 23
DIY Robocars via Twitter
RT @a1k0n: New blog post! Deep dive into my ceiling light based localization algorithm which runs in 1ms on a Raspberry Pi 3: https://t.co/…
Jan 23
DIY Robocars via Twitter
Great new guide to using @donkey_car https://custom-build-robots.com/donkey-car-e-book-en
Jan 23
DIY Robocars via Twitter
RT @chr1sa: The next @DIYRobocars virtual AI race is tomorrow morn at 9:00am PT. You can watch live on Twitch https://www.meetup.com/DIYRobocars/events/275268196/
Jan 22
DIY Robocars via Twitter
New version of Intel OpenBot! This resolves many of the issues with the first version, including a much smoother tr… https://twitter.com/i/web/status/1352395636369313798
Jan 21
DIY Drones via Twitter
Using ArduRover with an RTK GPS https://ift.tt/2N9I3RO
Jan 18
DIY Drones via Twitter
Jan 18
DIY Robocars via Twitter
Jan 18
DIY Robocars via Twitter
Jan 15
DIY Robocars via Twitter
Jan 15
DIY Drones via Twitter
Jan 14
DIY Robocars via Twitter
RT @Heavy02011: @diyrobocars : A Home-brew computer club* for Connected Autonomous Driving on Jan 23rd, 2021 https://www.meetup.com/Connected-Autonomous-Driving/events/275728684/ #Meetu…
Jan 14
DIY Robocars via Twitter
Jan 14
DIY Robocars via Twitter
RT @Heavy02011: ⁦@diyrobocars⁩ Autonomous Driving Assembly at #rC3. join us at https://rc3.world/rc3/assembly/diyrobocars-f1tenth/ ⁦@f1tenth⁩ ⁦@DAVGtech⁩ ⁦@DWalmroth⁩…
Jan 11
More…