Fair enough but since my FC and frame are also a decade old, I thought there is method to that wisdom
Mount as I suggested and do a test flight (in stabilize). Look at the VIBE values in the log. If they are less than 15 across the board, you are good. If there are spikes, share the log, and we can suggest mitigation techniques, the first of which is always securing loose wires and anything that could vibrate in the rotor wash.
Your frame is indeed less than ideal, but that doesnât mean we should start with band-aids.
Okay sure, thanks. I got less than 10 for pitch and roll and I think below 15 for altitude (canât inspect the logs right now) with the earplugs. Anyway Iâll try with the new mounting now 
Youâre at ~8-20 across the board. Secure those wires leading to the autopilot a little better. They are pretty free floating.
1 Like
Actually I had them tightly clamped at the bottom right arm except for one temporary ground wire (for the gps). But yeah youâre right, I guess I cut a little too much slack
Can someone send the default PID values? I donât know if I messed up but now with the new build I get potential thrust loss on althold, but no problem in stabilize. But I donât seem to be losing altitude during the âthrust lossâ period
AMC shows you the default of each parameter in itâs mouse over tooltip.
And if the parameter has the default value itâs presented in cyan. So itâs very fast to see which parameters are not default
1 Like
Didnât understand the simulation part. I havenât read the docs but as I currently understand, it is mostly to check the software functionalities and wonât model things wrong with my hardware right?
Why not? Mission Planner Simulation
It wonât simulate your particular drone but you can simulate different failures and how it act with settings you have. I just thought that you can check default pids and settings there but it also visible in full parameters list.
1 Like
This. Just do this.
All other solutions mentioned here, while valid, are several steps more complicated than simply referencing whatâs already available in your connected Mission Planner session.
The parameter default values are different for each FC board. You can only get them by extracting them from YOUR flight controller.
AMC does that automatically for you.
The vibration is due to one motor shaft being slightly bent. Thereâs also some free play of the shaft, like if I fully tighten the propeller, I can rotate the prop a bit to either side even while holding down the motor bell. I guess Iâll have to replace the motor if I cant straighten the shaft. The bit of free play might not be a problem right?
Okay, thatâs interesting. Why would it depend on the FC? I wouldâve thought it would only depend on the firmware version?
Nope. It depends on both.
Okay Iâm just asking because this piqued my curiosity. Why should the PID gains change with FCs? Shouldnât it only be depending on the build and the software?
The default gains do not change per board. Other default (primarily hardware oriented) parameters do.
Itâs possible one might find that the OPTIMAL tune changes on a per board basis due to measurement differences. Youâd have to be pretty dialed in to notice this.
1 Like
Like @Yuri_Rage said, PID default values do not change, but other parameters do.
Some change depending on the compile options. Some might change if you overwrite their value while compiling.
Thatâs correct, but you need to know parameters names. Novices usually use GUI and configure PIDs in Extended Tuning tab, but itâs not clear what parameters are really changed, it would be good to have the real parameter name if you hover over label, same as you get description if you hover over value itself.