Version 2.4 of the ArduCopter code is now available in the AP Mission Planner and in the downloads area. Although not as big a change as the 2.3 release, it still includes a respectable number of enhancements and bug fixes.
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.
Thanks go to the numerous contributors including users and their detailed bug reports, developers and testers. Hopefully all together this will add up to a nice smooth release!
As per usual, please post your comments, issues in this discussion. For enhancement requests for future versions, feel free to add them to the issues list. Note: you can "star" an issue to receive emails when someone comments on the item. On the dev side it helps us because we can get an idea as to which feature requests are the most popular by sorting by the number of people how have starred each issue.
Good evening Jean Louis
I checked it is ok, I do not understand is that ArduCopter v224xp2works ok but ArduCopter v2.4.1xp2 does not allow me the connection, may be it is the use by the IMU (USB cable), I do not have cable FDTI, or when a problem with windows 7, as for any errors during compilation or transfer; I have yet many wanted to tryyour improvement because it is always a great satisfaction.
Thank you again for your help
re hello jean louis
I have verified (# define HARDWARE CONFIG_APMAPM_HARDWARE_APM1) this line is ok, the compilation goes well,but still a problem connecting with Mp? thank you
Chapelat Daniel, edit APM_PID_JLN.h and you should have this line at the beginning
#define CONFIG_APM_HARDWARE APM_HARDWARE_APM2
#define CONFIG_APM_HARDWARE APM_HARDWARE_APM1
I'm using it with APM1 and I don't have any problem connecting.
Hello Rui Manuel
Thank you I try your advice and I would like to inform you, I'm starting with arduino and I'm embarrassed to seek advice in permanence!
Thank you to all that is really exciting
No problem, I know it may be a bit tricky in the beginning specially if you haven't worked with arduino before :)
Good evening Rui
Reassures me your indulgence!,
I just ask one more time JLN which is also very nice to me!
So, I have been flying JLN’s update with the DCM fix and have had some success. My leans were much mitigated and stable mode felt pretty solid. However, after a brain-dead mechanical error on my part, I had a motor out situation and crashed just a few feet above the ground. Anyways, I repaired that issue, changed two props, and started flying again without any tuning changes. Post crash, I now have the twitching phenomenon that plagued us back in the v2.3 days.
Now, this is probably a hardware issue, given my crash (note: only had a few quick flights prior to the crash. I don’t recall twitching, but it may have been there just not as pronounced. I am trying to find the logs). The reason why I think that it possibly could be software related is that when I reduce the Stab D and Rate D terms to 0 (previously, .010 and .004 respectively), the twitching is mitigated. This seems similar to v2.3 problem/solution prior to the software.
I realize this fix is still very alpha and no one recommends flying it.. Again, it’s probably hardware related, but some peculiarities give credence to the chance of it being software. Please don’t waste too much time trying to investigate because I would not want to dilute anyone’s efforts to get the next release working well. It’s really just an FYI in case it truly is an issue with the code. I will try to deep-dive it more tonight and post any findings
For a hardware related twitch, are there any checks or tests I can do to find the issue? All my connections seem good. I have yet to re-calibrate the ESCs, but that was my next step.
you could check if all the motors are well tighten and aligned and the motor stands and the arms, if any arm may have come loose causing it to give a few milimiters front and back, or if an arm is bend or any piece loose that may cause changes on the center of gravity... that's all I can remember if it's hardware related post crash.
Hmm.. I will double check. I have had my fair share of crashes, so nothing is really true anymore. But I have been flying like that for a while with no twitching. My gut tells me it's a electronic or software issue rather than out of CG. It even twitches when holding it in my hand. Twitching goes away when the d terms are eliminated
I have the same problem with 2.4.1 (actually, saturday trunk more or less). Twitching with increased Rate_D. It's a real pity because higher Rate_D makes it react so much better to external forces and correct back when stick input is gone. I can also mitigate it by reducing Rate_P but that makes it very lean. I need more resolution in Rate_D - something like 0.0035 would be perfect :/
From the postings here I got the impression that JLN solution for auto-landing works better that the one currently pushed (2.4.1) - is that correct? (have not tried it myself)
If yes, will JLN auto-land code be included in next release?