Something wrong with APM plane support?

We notice other people with different platforms but similar problems, without solve and no more answers from Tridge; I crash two times in loiter and RTL and now I’m fear to fly my plane, i’m waiting a new version but I’m realy don’t know what is happening, is something that we are doing wrong?, is there a difficult bug that you can´t solve yet? or support problems?, We are going to be patient to have a solution but please tell us the true to not spend more time trying to configure and money repairing if the problem is the firmware.
Thank’s

I have to second this. Is there something we should know about? I described a problem I ran into a month ago in a detailed post complete with logs etc. and did not get one reply. I am aware that the devs are busy people, but it seems most people have been left hanging lately. Why?

Remember all the devs are volunteers and do this as a hobby or interest, they don’t have to do anything and don’t have to provide support to anyone. They also have busy lives and full time jobs.

There is a new version coming and some major optimizations have gone in so maybe they’ve been busy out testing.

There are a few odd things with v2.78b but it flies the majority of planes without issue. Most problems are user error or bad setup. Too high expectations of what a cheap autopilot, developed part-time, can do is also a problem.

Thank’s Dyer for your answer, I know there is a cheap autopilot and gives me more than i expected :smiley: , developers made a great job here and, as I said, we are patient to wait but is important for me to read that there’s some issues not solved yet, so, perhaps its owr problem because in the five planes with different configurations and sizes we have similar problems, if we can help you testing or something else please let me know (not programming, not know nothing))

You say you’re having the similar problems with 5 planes. Describe the problems you’re having?

Here Martin Lere try to explain the problem viewtopic.php?f=96&t=6025 ; sorry we have little difficult to explain correctly because english isn’t our native language, if you need more logs or an special one please tell us.

The current v2.78b is not perfect but until something else comes along we have to live with it. I have my own issues with at least one of our planes but my personal plane flies really well with very few issues. We tried formation flying again this past weekend with two planes and they both flew well for two hours without major problems.

Sometimes a small change can affect the plane in a large way, we had LIM_PITCH_MAX too low so with that set at 25° things are much better, increasing PTCH2SRV_RLL also made a positive influence. TECS_SPDWEIGHT set to 0.5 can help sometimes too so try and see.

An idea of the changes coming are all the new EKF parameters in the Wiki: plane.ardupilot.com/wiki/ardupla … Parameters, some new stuff may only work on Pixhawk based boards though.

Thank’s Dyer, I’m going to try this; thank’s for the changes comming news too :smiley:

Pleasure, I hope you have more success.

It is true that all developer are volunteer. But I do not understand if 3D Robotic had invested million of dollar, expanding their factory, why they left this all important software development to " volunteers" I don’t think selling all the hardware to us and give us buggy firmware is a good idea to further promote this great product.
I also cannot understand why develop lot of new function in every new update but ignore to produce a solid and stable firmware for us to use in daily basis.
I start with 2.69 and had use it to map more than 20000 Ha of land without issue. But the recent updating process has not been good for me.
Can we improve the stability of the firmware rather than new function and features in every update?

[quote=“KeeyenPang”]It is true that all developer are volunteer. But I do not understand if 3D Robotic had invested million of dollar, expanding their factory, why they left this all important software development to " volunteers" I don’t think selling all the hardware to us and give us buggy firmware is a good idea to further promote this great product.
I also cannot understand why develop lot of new function in every new update but ignore to produce a solid and stable firmware for us to use in daily basis.
I start with 2.69 and had use it to map more than 20000 Ha of land without issue. But the recent updating process has not been good for me.
Can we improve the stability of the firmware rather than new function and features in every update?[/quote]

3DR pours money into supporting software development.

The new functions and features are what the developers (many of which are volunteers) are using to support their own projects. We all have our planes flying well and reliably. APM won AVC, APM won OBC. So, it seems the problem is not us. What is your specific problem?

I have been very bad about keeping up with the forum lately, as I’ve been doing a lot of new development ready for a new release.
I’m trying to catch up on forum issues now.
Cheers, Tridge

tridge; I guess you are much more updated on Arduplane status.
I’ve been using a build based on 2.73 for a very long time because it worked so well, and I did not had time to test newer builds equally well for my use.
Besides improvements and pixhawk support, is there something I need to watch out for in 2.78b ?
(yes I’ve read every release note on forum, I am asking for known problems)

BTW: It would be nice if there were one place that contained a release-log , preferably in the git.