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!
Also, I don't think that the dip earlier in the flight necessarily rules out bullet connector, esc or motor issues. It could have been failing at that point.
Coincidence... commenting that out should not have changed anything in your flight.
Keith, do you have the .log (not the tlog) from that flight?
How do I get the ".log" file?
I haven't powered it up since the incident.
If you downloaded your tlog from the board, it should be in the same folder as the tlog was. That folder is the Mission Planner folder under logs.
Attached is my .log file. This is very confusing to read and understand what to graph.
I'm almost convinced it is a hardware, electrical problem, or noise.
I've searched around on the forum but couldn't find material to try and understand how to use the ".log" and ".tlog" to help me get my head around what happened.
Keith, I just took a look at your log. Unfortunately your Attitude logging must not have been enabled for this flight because I don't see any of that info in there.
Also, don't give up on the logs. The first several times that I looked at them it was all greek, but it will soak in eventually.
Just found something! The I2C translator on my magnatometer board was loose.
I was checking the sensors in the Mission planner terminal viewer and the compass was not operating.
Could this cause my issue?
I've loaded 2.5 in my DIY quad flying +, and a friend's X, heavy unknown quad, and other than having to fiddle a bit with the TRIM-THROTTLE to get it to Alt Hold, I think this code is a winner, as stability goes.
Will try all the other functions later this week.
Thanks again team !
Ch 6 can be set to 'Relay' in Mission Planner. Does this toggle any output on APM2? Where in the code can I grab ch6 'relay' to toggle an output like camera shutter?
I have been flying so much I haven't had time to reply. Great work dev team. This is a fantastic leap forward.