you are right. After good experiences with NAZA I became fun of the concept and the Features of APM. But after one year with over 50 Testflight during 7 hours to tune the AltHld the best Result was +/- 2m. And this only with reducing the…"
If you have a Hexa try with Dataflashlog setting: disable all.
After this I had no more such Spikes. (Also in Pitch and Roll Axis)
My be AMP is to busy with more than 4 Motors and all the Logs (Dataflash an Teleterie)
"I think there is nothing to solder, this PCB works from 3 to 5V. But you should check, if the Compass from 3DR has the same chip (HMC5983) else the Data Protocoll is not the same and will not work with APM 2.5
Nothing new. I had a lot of such surprises see below.
Command to descend produced a turn right.
Peaks with no command and jumps back.
Try to disable the Dataflash Logs. After this I had no more such "implemented"…"
Above gave me a new Idea to solve my poor AltHold I tried to tune since one year during 5 hours test flight.
I disabled all Dataflash Logs exept CTUN (to check BaroAlt)
And it was a miracle. My copter holds the altitude and it is now…"
"Thank you Randy,
In the Image below my "best" Result in Alt Hold after Month of Tuning.
Now I have no more Ideas what to try because every combination of Values already tested.
Here the blue line is Throttle Rate from 3.0 (left)to 6.0…"
What is the Default you mean for Throttle rate P
After loading 2.01 it is at 0.0
In the Tuning guide is mentionned .35 (0.35?)
And in the full Parameter list of MP ist listet under the Options: 1.000 ... 8.000
"I have the same Problem with AltHold. Variations sometimes +/- 2m, sometimes more.
Vibrations lower than recommeded in the Wiki, APM on rubber foam.
Trying to tune Alt Hold since 6 month, 4 hours Testflight with different Parameters.
"Randy, thank you for the rappid answer.
Because I'm surching since 6 month, during 4 hours test flights the reason for great variations (3m) in AltHold
I used this PID's in the log.
Below you can see how it is possible to find strange…"
Some PID's (Selected for Ch6) are not in the dataflash log even the Group PID is selected for the logs.
e.g. Stabilize P. Attached Param file and the log.
Michael told me thats not a Problem of MP.
I had the same effect.
Select in MP the Tab Terminal, then the green Tab on the left side Connect APM, wait the end of the text.
then delete logs, enter
This will delete all logs.
Then type Exit, enter,
Disconnect at the right…"
You did a great Job.
After 4 hours and 40 Flights in the air with frustrating results I finally came to your method.
But now I'm with Rate Roll/Pitch D at 0.025 and nothing to feel with fast oscillating.
Failsafe with low battery Limit is difficult, because: Flat discharge courve, variying with current consumption . RTH could be to early or to late.
My Proposition: Selectable remaining battery capacity i.e. 30% to start failafe . This…"
I made exactly the same experience. Now,after 30 testflights during more than 3 hours, I can hoover and I have the couriage to moove a Little bit left and right etc. Compared with Wookong M a huge difference in stability.
yes it is the correct one. But that is the Problem. You can see in the Param File, that PID Stabilize P is selected. In this case Firmware 3.01 has a bug. This effect can be reproduced, also with some other PID's. (APM at PC via…"