As an avid multi-copter enthusiast I need to ask one simple question .......
Why is it that the DJI NAZA and WOOKONG systems work 99% tuned 'straight out of the box' for most combinations of motors, ESC's, frames and combinations - but the APM project needs sooooo much tuning to achieve a similar result?
Am I being very naive here, or just plain practical??
Hi Dale, you can't compare APM with the DJI products, two different "development philosophy".
DJI come from a military technology, have brought their expertise in the field of "consumer" minimizing parameterization, APM by a team of enthusiasts.
APM offers many advantages, the user savvy enough can configure your setup and under certain conditions it fly better than a product DJI, its Achilles heel is the speed of the processor (16 MHz only), with this speed is unthinkable to obtain a stability comparable to pure flight board that install processors 10 / 50 times more powerful.
But the advances in the V3 release that will come out shortly lead APM Copter able to compete with expensive commercial products, it lacks an easy interface in the Planner and the work would be complete imho.
With PX4 and VR Brain (the new powerful board) you can get the same performance of the DJI products, with a good tuning I have shown in my video that this is possible.
Thanks for your original advice to post on diydrones.com.
I've learned more practical advice and answers to some seemingly obvious questions on this thread than I have trawling through the many forums of seemingly self-appointed experts for many months now.
Thanks everyone for all for your replies to my question(s) - keeping it simple and factual is a bonus - I'm sure it's also helping others to learn and understand some of the fundamental issues and hurdles faced by the APM project vs the commercial alternatives!
Keep up the postings everyone - knowledge from this thread is proving informative ...... and useful! I find broadcasting excessive knowledge of a subject can sometimes get in the way of what most of us really want to achieve - which is simply 'good reliable flying time'!
You are right about Naza and Wookong systems working great without need for tuning. They are impressive in position hold and altitude hold, and fly real nice.
But with latest versions of APM Copter firmware it is not necessary to do much tuning if you only want a good flyer. For my preferences I always lower stab P (3.8) and rate P (0,13) a little bit before first flight and it works without further tuning.
I did put my Phantom with Naza in position hold side by side with my TBS Discovery with Arducopter 3.0.0-rc5. I think they behave very similar. Arducopter parameters are default except lowered stab P and rate P. And Phantom has pretuned parameters from factory special for that model.
You can still see Phantom is more stable at position hold. But they are very similar, and APM may improve with tuning of PIDs. Both are great Flight Controllers. Which to choose depend on what you want to do with your multicopter!
yes but apm is not reliable like dji..there are bugs ;)
Are you sure it is less reliable ? Less reliable in witch conditions ?
I did flew version 3.0 release candidates during 20 hours without any crash on a hexa copter, testing all modes including acro with 90° banking, auto mission and auto landing, at speed as high as 24 m/s, ascension speed as high as 10 m/s, descend speed 16 m/s. This is quite good results for me.
I have another Hexa machine with a camera, 5.3 kg weight, flying arducopter since version 2.0 with an APM 1.4, never crashed. I did manufacture a big Octo, 9 Kg, APM 2.5, no crash. Only changed two PID parameters from defaults. I don't see the point with the tuning complexity myth. More a machine can be tuned very fastly in flight with a 3DR telemetry radio. This is for custom machines. For stock machines, default parameters are just working.
It's open source, there is an issue tracker, a Git repository, hardware price is low, you can contribute and help to find and solve bugs, or help to complete and rework Wiki pages for version 3.0 if you are comfortable with wikis.
As a human i like bugs and i have bugs myself. I like to find them and find solution to kill them, and discuss about that with the Ardupilot community. I did spent quite a lot of time testing v3.0, watching closely for safety issues and hardware problems detection, discussing and writing patches to solve a couple of them. I would not be able to do that with commercial projects and for me Arducopter is great for most tasks.
The Dev Team did work hard and the result will be for sure a 3.0 release with safety as a primary concern and a new first-class nav controller. The enhancements list is long for this version.
A non negligible amount of crashes are caused by hardware issues or user omissions. V3.0 will lock a percentage of those, forbidding arming or switch to auto mode. This will certainly rise the perceived Arducopter reliability.
Version 3.0 rc6 will certainly enter public availability through Mission Planner in a couple days for more generalized testing so that some small adjustments can be done before the final release for a smooth transition. When public 3.0 rc6 will be out, we'll certainly have new interesting DJI / Arducopter comparisons here :)
it wasn t a critical, i love my apm and i am very impressive for the price.
@titeuf007: mmmm where? :-)
In any system there are bugs, don't think that the DJI products are exempted.
The advantage of APM Copter is in being able to find them through all the logs, impossible with DJI Naza or WKM.
In case of crash is always possible to know whether the problem is, hardware or software, in the second case the bug is found and then fixed.
I "try" to coordinate the group of testers of ArduCopter about a year and I assure you that the problems are greatly decreased in this year, almost non-existent, some bugs on automatic were virtually all found and resolved, the user that can fly in Stabilize always brings home his quad whole.
When I joined the ArduCopter group remember that every day I was wondering if I could bring my quad intact at home, now I wonder if it crash for software bug.
My last crash was last year, for a big bug found and then fixed after this attempt.
The flights that I have with ArduCopter assets from that event are over 3000, without a single crash or fly-away.
I think "APM Copter V3" is a really milestone release, another world respect the previous version, surely there will still be some thing to fix but is unlikely to happen that someone in an emergency is not able to land the quad own safe.
all normal users like me see you hard work and we can only say you a big THANKS for this great project
Thanks but I don't have any merit, the whole team did! :P
I started with a DJI F550 Hex and a Naza + GPS. I could never get it to hold a course lock, it would always yaw left no matter how I tweaked the gps position. Every time I flew it, I was nervous because it wouldn't lock and I couldn't enjoy it. However, the altitude hold is pretty amazing, but eventually I started having issues because I fly on the coast in cold windy weather and it suffers from some similar barometer issues as APM.
As soon as I put in APM it flew like it was on rails, this was with 2.8.*.
On an F450 frame/motors APM flies great on default settings! Alt hold is still a little finicky.
However, my 3dr Y6 was pretty rock solid on with the settings provided by 3dr, even though I was using slightly faster motors.
NAZA is nice for basic beginner flying or basic aerial photography. APM is needed for more advanced configurations (don't think Naza supports y6 or many of the other odd frame types that APM does) Naza does not support dual pilot/cameraman gimbal control which APM does. Naza does not support telemtry and GCS control from android devices.
Wookong has more features than NAZA< but costs more than 3x what APM does...
I know this is an old post, but it almost appears as if the APM is over-correcting for the drift, and ending up having to correct again? Am I wrong?