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!
I tried my first fpv flight today with 2.5.3.
WIth the addition of a Gopro and Video TX the quad was rather unstable with the extra weight.
Which parameters should be trimmed when flying with more weight?
Some other things I noticed is that quad sometimes had a strong backwards lean after a couple of minutes flight which wasn't there when lifting off.
Also when I can get to quad to hover nicely, after a couple of seconds it goes up or down resulting in throttle compensation.
Flying APM1, MT2814, APC 11x4,7, 5000mAh 30C, X650 V frame
Concerning the hovering I also noticed that when enabeling Alt hold for a while the quad stays at the correct height (sonar) and then starts to slowly yo yo.
Vincent what are your current parameters? I am very curious becase I think the standard ones have to be tweaked a little to get a good reliable flight.
I think you missed something...
Well i fly with default parameters and flies good with a 1,6kg frame. But adding the gopro + video tx is rather unstable.
have the same frame.
0,145 pitch rate,
throttle trim 348
thr max 900.
the other parameters for defects. fairly stable with little wind to keep very small jump height due to uneven weed
engines and propellers XAircraft 10x4.5. apm 1, code2.5.3, 10 amp Turnigy esc, 2650 45c, LV EZ4, contour hd camera, and other a transmitter connected to 5.8GHz 200mw.
weight 1,350kg autonomy 10 minutes....
thx Norman, Your quad is lighter than mine.
I'll try to play arround with PIDs when it stops raining ;-)
Hey again guys! First off, thanks again to all who make thise code possible and put in the hard work!!
We are having some very strange issues with our big octo builds, we've got two octos, one using 25A and the other 45A esc with APM1, I've never had any issues with APM1 and octo builds, but with BOTH these we have had weird ESC issues on motor3, both on motor3 !? As soon as we power up, the motors do their normal beep beep, but 3 has a delayd fast beep beep beep beep and then the normal tone.. When throtteling up smoke comes from ESC3 ???!! on both systems the same thing happened ?? So my thinking is, as these are all brand new esc, and never had any issues before, prehaps it's a code thing due to new motor changes for octos ??
Any ideas guys, this is pretty troubling
There's surely nothing in the code or to do with APM that could make an ESC smoke?
Sounds like dud ESC's (chinese imports, hobbywing, turnigy?) coincidentally installed on the third arm.
The only reason smoke is going to come out is that you somehow overloaded the BEC. If you aren't using a power distro board that isolates the 5volt power coming from the ESC BEC (regulator) then it's highly likely when the other motors begin to draw some serious amperage and those motors aren't working (the beeps due to wrong input signal or other issue) suddenly you have a high current ground loop or 5 volt loop and something has to give. It's known there were different wiring diagrams and connections for octo.
Again, this is a wiring problem, either not isolating the BEC (the middle pin of every ESC but 1) and or a massive ground loop when the current comes unbalanced.
Yes you have a code/wring problem too with those two motors but the wiring is what caused the smoke, not the code.
You can send invalid signal to an ESC all day long and as long as that signal isn't above 5 volts, it's basically impossible to cause smoke to come out.
I've warned in another thread that just this type of thing could occur when using different ESCs and then just plugging them into the APM board thus tying all the BECs together and the BECs being different designs and part numbers fight each other to maintain the 5 volt power to the APM. Clearly this is the most likely cause of your issue. Being that on APM1 the signal pins on an octo were not in a bus row like APM2, your wiring isolated those BECs and you just didn't even catch it.
Thanks for the replies. I've build a few big octos and know the system inside out, it's def not a wiring issue as I only have signal wires from ESC going to APM, and +- into a power disto circuit, as with all my other copters. The reason I thought it might have been code is a possible new code change which left out octos (this happened before when they brought out a new version, they did motor section re-code and no1 remembered to check the octo/hex settings, I was first to try fly with octo, which did not work ;) )
I've replaced the ESC and all working now, altough still getting a delayd start up tone from the same new ESC, 7 motors beep together, but 3rd channel is late.... ??
Coinsadance that two octos do the same on same channel ? perhaps.