I need some clarifications to better understand this flight mode,
please correct what I miss understand,
Position Control is like DRIFT mode in Arducopter. Flying with a gps mode but quite aggressively.
Releasing the stickt, will break the copter in the air and it change the mode to HOLD (LOITER)
All Parameters in the Multicopter Position Control (MPC) tab, affects the Position Control Mode.
What I expect of this flight mode is, sporty flying with gps “security” and when releasing the stick a perfect steady copter in the air (almost no movement).
At the moment it look like a crazy horse when I release the sticks. In both modes HOLD and Position Control
My thoughts about this problems,
maybe the copter is constantly overshooting and try to get the perfect spot. Is it possible to make the radius larger? So it dose not have to be corrected if he stays in this radius.
I played around with those values, but not big success. It was a bit calmer but not what I need because it is still constantly correcting his position.
That’s what I try to find out. So in Stabilized it flies like a charm. Perfect hover and even aggressive flying is mastering properly. Altitude controle is okay, in my opinion it could holt the hight better, but I imaging this could be a tuning matter.
In Position control I had about 10-13 Satellites and an hdop of 0.8. So this should not be a problem.
My knowledge about position control and all the settings is quite limited and that’s why I opened this thread because I need and want to understand it.
@LorenzMeier this issue is still open right? You said a betta release will fix it, right? I didn’t fly since last week so I’m waiting for your new version.
Hi Guys I have experienced the same issue today on a machine.
Flying 1.4.1 Stable version that I took from the standard version in QGC.
Flies perfectly in Stabilized mode, Altitude mode but when I switch to Position Mode, it starts doing wierd thing and flies all over the place. Not stable in position.
I did few things, swapped the Pixracer, the GPS, cables, unplugged arming switch, buzzer, etc. Nothing has improved there. What is weird is that we have built 2x identical machines, the other one is OK. The only difference is that the other machine is using 4x different motors.
If it can help, I never had this issue using 1.4.1 RC1, I will try it again tomorrow if it’s not raining :-/
Regards,
pturcotte
I will check this for sure. What I don’t understand is when I use 1.4.1RC it works, when I am using Arducopter 3.4RC2 it works. That’s why I am not sure.
It’s not a vibes issue, otherwise it would be very bad in Stabilized as well. @LorenzMeier wrote that’s a software problem and a fix will be released soon. Hope I didn’t miss understand him.
Just to make it clear, I will not put my pixracer on damping pads. In my opinion this is not necessary
@Sn0west@xuefengleng2016 We have no indications there is anything wrong with position control, it rather seems to be a tuning issue on your end. How can we help you with better tuning instructions to get it right?
For what it’s worth, I’m convinced this is a definite problem and should be taken seriously. The behavior shown in the video published above started immediately after updating to v1.4.1 from v1.4.1rc. I waited for v1.4.2 to see if the problem persists, and I’m afraid it does. Recallibration and adjusting tuning sliders does not solve it, but going back to 1.4.1rc does. My craft is an F550 clone with pixhawk hardware.
The symptoms and circumstances pricing the surging behaviour are described perfectly in the postings above.
