Version 2.5 of the ArduCopter code is now available in the AP Mission Planner and in the downloads area!
The default PIDs are optimized for a 3DR/Jdrones quad with 850 motors and 10" props. If you're using more powerful motors/props, start by turning down Rate Roll P in 25% steps.
While some testers have reported very good flights with the default PIDs, some have reported that this release is a little "sharper" due to the DCM improvements and have found they needed to:
reduce stabilize P by 10% (i.e. 4.5 -> 4.2)
reduce stabilize D by 30% (i.e. 0.15 -> 0.10)
increase rate D from 0 to 0.001
Tuning loiter can be tricky. Refer to the discussions which will appear below for more community feedback on what parameters work best.
Please post your feedback in this discussion. For enhancement requests and bug report, please add them to 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.5 but tell us anyway!).
Thanks for this release go to the developers (both in the core team but also those who have provided bug fixes through the issues list) and also the community members who participated in the previous release thread and provided some great detailed information in the form of issue reports and logs which allowed us to nail some bugs!
Theo it's a long shot, but perhaps try doing individual throttle calibration on each ESC? Or perhaps one motor is faulty and not running at the same RPM as the others?
Is there a video of this occuring? It would be musch easier to work out if there was?
Perhaps starting with a close up of the components and the props, then of the machine being armed and throttled up until the spinning starts?
Hi Guys....yip prop pitch was all the same ...escs individualy calibrtated.......even when as far as to check the props individualy using an optical tacho all where withing about 20 rpm of each other......same setup flies 100% with wookong m........waiting for 2.6 to be pushed to planner will try on quad and might just chuck it back on the octo...will keep you posted...
That's very weird Theo. Are you using an APM1 or 2 ? If it's an APM1, try to re solder the magnetometer board because a small ammount of vibration may be inducing bad contact in the I2C bus wich agravates in time. I can't remember anything else.
Hey Guys Thank you for your help, considered all and the substantial investment in frame motors etc etc etc.......i bit the bullet and stuck a wookong M on her.....and im happy to report solid as a rock......apm1 i do believe and agree with Duran that in the not to distant future will outperform...most if not all the Propriety FC out their........when that happen i know that i can get rid of the Wookong and atleast get my money back (Got a good deal.......will be flying apm on my quad.......lot cheaper replacing a $20 frame should it all come tumbling down....for what ever reason....
that said, i am super impressed with what the devs have done and love flying the apm on my quad.........
ill post some pics and video of the "mistress" soon..
i'm using fw 2.5.5 and my quad fly very well. Only one question... there is a way to set a min altitude? (i'm using sonar). Because i fly in fpv, many time i go too much down and in fpv is hard to see the altitude, so if i set a min alt like 1,5 meter i can fly without difficulty.
you could set up a geo fence - turn it on after takeoff and turn it off to land.
hi has any one got the apm2 board working with minim osd and xbee 900 i can get them to work seperatly but onlt xbee works when plugged in together to get osd to work on its own i have to reverse tx and rx but not with xbee ????
many thanks stuart
could you say me if i can enable geofence function from mission planner? or i must enable it in the code?
Geofencing for ArduCopter (and more generally for all vehicles) is currently in testing for a planned release in the next month or so.
I will be creating documentation in the wiki, which will show you how to set up and use fencing.
Stand by, it is almost ready!
thanks so much !
Hi, I'm now fairly sure the cause of the strange flip I reported here is a software problem that was introduced between 2.5.3 and 2.5.5.
I flew my quad today while downgraded to 2.5.3, with the same (PID) parameters as 2.5.5 and the flip/roll was gone. After I upgraded to 2.5.5 (from the mission planner, again with the same parameters as in 2.5.3) the flip effect is back again.
I never flew 2.5.4 so I don't know if it is in that software too.
Should I report this as a bug?