Hey everyone, I set up my quad with Ardupilot Methodic Configurator, literally following every step of the checklist, and on my very first flight it hovered rock-solid in Loiter at 10 m with no issues. But after flight number two—same battery, same props, freshly calibrated accel and compass—I climbed to 10 m in Loiter mode and let go of the sticks, and it started gently oscillating side to side and even made random yaw corrections of around 10–20°, despite a rock-steady GPS lock (RTK injected) and no compass or GPS errors in the DataFlash log. The wind was moderate and gusty (around 17 km/h), so I expected a bit of drift, but this felt way too aggressive. I’ll attach the video and logs—if you give any advice to solve the problem, it would be amazing. Thanks!
You are not supposed to use loiter flight mode before reaching step 23.
Post a .zip file with all the files from the ArduPilot methodic configurator vehicle configuration directory.
I’ve uploaded that ZIP to the same Drive folder I shared earlier. I just wanted to test my notch filter and PID gains, that’s why i used loiter mode. If it causes a problem , I am not going to do it again.
On file 15 the MOT_THR_MIN parameter has been set to 4.
That is very wrong!
Set it to 0.04 and fully redo step 15!
Hi Amilcar, Actually this parameter is not available on my full parameter list that’s why i see N/A sign next to it on methodic configurator. Also I cannot see the parameter on Mission Planner too. There might be any name changes for parameter or something. I use latest methodic configurator and also latest ardupilot firmware but i see N/A sign a lot. Is There anything I do wrong or is it a common issue?
on a drone are rapid, unwanted vibrations, often caused by bad tuning, loose parts, or wind.Yaw driftt means the drone slowly rotates left or right without inputed usually due to compass issues, IMU drift, or motor imbalance.
Fixes Calibrate compass and IMU, check PID settings, and inspect hardware.
There is something wrong!
Which FW version are you using?
I use ArduCopter V4.6.0
Perhaps what’s very wrong is MOT_THR_MIN is a Rover parameter…
I think i did everything as it should be but there is something obviously.
These are also not Arducoper parameters. In Arducopter ATC_ACCEL_MAX has roll, pitch and yaw parmeters.
They are all Rover parameters.
@amilcarlucas Why is this happening my firmware is copter but i see rover parameters. The weird thing is drone flies anyway. I think i need to do all the things again!! How can i prevent this error.
Did you accidentally selected a rover template when you started the AMC project?
The master (latest, not yet released) version of AMC no longer allows that, but on older versions you could do that.
Actually I did it on purpose i selected the closest setup to my drone’s setup. AMC already reads Cube’s firmware by itself because of that I thought that it is not gonna be a problem. What is the correct way to start an AMC? I guess Blank will be fine.
I realized something even if you select everything blank or take from FC options, it takes values from template anyway so you have to select a template that perfectly matches to your setup. I think you should add a option to start configurator totally blank without any template.
