Don’t see much difference in energy level per axis, x and z are around 55, y around 40, in FTN1.
Would it be better to set notch filters at fixed values instead of using dynamic fft to set them?
Don’t see much difference in energy level per axis, x and z are around 55, y around 40, in FTN1.
Would it be better to set notch filters at fixed values instead of using dynamic fft to set them?
Hello @andyp1per ,
My Quadcopter have strange vibration motor problem on the ground before installing propeller.
I suspect the vibration arise from the “wrong” parameter setting of my Arducopter (latest stable version), but I don’t understand what is root cause of the problem.
The motors are good with no vibration when I did running test using servo tester (Motors already installed on the Tarot 680 pro Frame when I did running test the motor using servo tester).
So the vibration arise during testing on STABILISED MODE and Throttle still lest than 30%. Vibration disappear when I increase the Throttle higher.
I did RADIO (R/C) Calibration and ESC Calibration before doing the testing.
I did the Alt A : Initial Parameter setting according to the documentation.
I did hover test on this condition, and it hover good, but visually I could see that there is vibration problem.
Here is data of my Quadcopter:
Could you advise what are possibilities of this Vibration Problem ?
Here is the bin log file.
https://onedrive.live.com/?id=5F767B9E38DE7C1D!109&cid=5F767B9E38DE7C1D
Thank you very much for any advise.
Hi @andyp1per ,
Thank you for you quick response… Yes you are right, but the Big question is what is the root cause? I add more info here, that there is no vibration when I use servo tester to all 4 motors running simultaneously. The motors are running smoothly, frame is rigid… Then This is The Key: When in Stabilize mode (without propeller) Motors are NOT running smoothly (when throttle below 30%). This generates Vibration. This NOT normal. I never have this problem using previous Firmware… This my new built quad. I just finished Two similar quad and have same problem using the latest stable FW… So I suspect there is something wrong with parameter setting… Could you please check my parameter setting?
From that graph, it looks like the signal transmitted to the Esc is not smooth. Why ?? Is it because of the R/C signal problem?
Thank you…
No idea, it may simply be that you have the props off
Hello @andyp1per ,
I have solved the Vibration problem by adding Aluminum plate in the middle of the frame to make it more rigid. I also add vibration damper. However I have another problem about the Battery remaining Indicator that shows very fast current consumption which is NOT consistent with “battery consumed” indicator on the same display. Any idea how to solve this problem? I have tried to increase the total battery capacity parameter, but problem still exist.
I have created new thread about this Battery Indicator Problem here:
Looks a lot better. Y is tracking the best so you could try setting FFT_HMNC_PEAK = 5 to track the pitch axis exclusively
LOL
Ok, will do that. You think i can keep it like this now?
I can’t see anything obviously wrong with the log other than my bad algorithm
Should i keep the notch on or turn it off and wait for your next iteration?
Keep it. But please can you turn on batch logging so that we can see the noise.
set INS_LOG_BAT_OPT= 2 ??
Yes, but also INS_LOG_BAT_MASK=7 for a Cube Orange
INS_LOG_BAT_OPT= 2
INS_LOG_BAT_MASK=7
Anything else? I got a bit lost on the wiki about collecting vibration samples.
I am not really sure if opt 1 or 2, 1 is prefilter and 2 is post?
The settings you have there are correct
Ok great, will try to make a flight as soon as the snow melts
Thank you very much.
Kindly
Steve
Link to Bin below
This should be off-topic when asking but it is very nice if some of you guys can have some time to point out the differences between these 2 parameters:
I have been used INS_HNTCH_ENABLE and examined the imu batch log so far.
Moreover, there are something I can not find in my log such as SnY, SnZ…
This is my FFT config:
Sample log file: https://drive.google.com/file/d/1AeC3pDAwHfZdnwQbEoiEvbVkVydomkrn/view?usp=sharing
It is highly appreciated if you can point out where did I get wrong.
Thanks in advance.
Vu.
First notch is tracking the 160Hz peak well. Second notch not so much. It doesn’t look much different to your previous results however.
I think the real problem here is that it is bouncing between picking up 2 and 3 peaks (FTN1.FH) and that makes the tracking harder.