Hey guys, Im needing some help tuning filters. Was doing some tuning of my octa, set static notch filter, good flight. Tried setting harmonic filter, heavy oscillations on pitch, resulting in minor crash. Reflashed firmware, calibrated, and autotuned. need some guidance on filters. vibes are a little rougher than they should be. cube flight controller is mounted with 3d foam mounting tape. Any Help would be greatly appreciated.
Please read the dynimic notch filter instructions again and post pre, and post notch data from a static and from a dynamic flight.
Yeah, I read it. I set it up, and the airframe crashed. Apparently, I did not set it correctly. Bird is currently worth over 10 grand. Not worth the risk currently. Hence me asking for help…
Post a link to the flight log of pre filter data so we don’t have to guess at the peak info in the FFT graph.
Pre filter FFT data is in the first screenshot.
Sure, but with the flight log you can use cursors to determine parameters. Looking at the screen is a poor substitute. But up to you.
As per the docs, I am supposed to use the fft data. I’ll head out to get wifi, living in the mountains kills internet options for me. If we need full logs, why tell us to use fft in the documentation?
I’m simply asking if you want to post a link to the flight log so someone can help you by reviewing the FFT themselves. A screen shot is insufficient to do so.
You’ll need to post your config if we are to be of any help + pre/post filter pictures. Your picture basically shows that your copter has a motor noise peak - just like every other copter on the planet.
I understand that. I simply posted what the docs said to use. I will post a full log as soon as I can.
full log. i believe this is the correct file.2020-08-31 08-42-57.log.param (18.0 KB)
Log File C:\Users\rekcd\AppData\Local\Temp\tmp94F7.tmp.log
Size (kb) 108566.69921875
No of lines 1045066
Firmware Version V4.0.3
Firmware Hash ffd08628
Free Mem 0
Skipped Lines 0
Test: Autotune = GOOD - [+] Autotune 24345-970827
Test: Brownout = GOOD -
Test: Compass = WARN - WARN: Large compass offset params (X:-236.28, Y:227.55, Z:-113.84)
WARN: Large compass offset in MAG data (X:-236.00, Y:227.00, Z:-113.00)
mag_field interference within limits (8.26%)
Test: Dupe Log Data = GOOD -
Test: Empty = GOOD -
Test: Event/Failsafe = GOOD -
Test: GPS = GOOD -
Test: IMU Mismatch = GOOD - (Mismatch: 0.25, WARN: 0.75, FAIL: 1.50)
Test: Motor Balance = GOOD - Motor channel averages = [1620, 1616, 1553, 1549, 1552, 1548, 1618, 1619]
Average motor output = 1584
Difference between min and max motor averages = 72
Test: NaNs = FAIL - Found NaN in CTUN.DSAlt
Test: OpticalFlow = FAIL - FAIL: no optical flow data
Test: Parameters = FAIL - ‘MAG_ENABLE’ not found
Test: PM = FAIL - 126 slow loop lines found, max 7.95% on line 186501
Test: Pitch/Roll = GOOD -
Test: Thrust = GOOD -
Test: VCC = UNKNOWN - No CURR log data
That’s a parameter file. Need the .bin log file.
And the Auto Analysis tool is not up to date and of little value.
Alright, I though it mayhap been the param file. Live and learn. I tried auto analysis just out of sheer hope.will re upload. Thanks for all your help.
BTW-That parameter file shows no configuration for static or dynamic notch. Looks like default parameters. These should be set 1st before doing anything with notch filters.
that is correct, it is a fresh reflash, 1 of 5 cubes. i know the bird flies, so i slammed out an auto tune, just to get base lines. the covid killed my job (company completely closed). so i kinda got screwed into pushing the bird. full param log follows.2020-08-31 08-42-57.log.param (18.0 KB)
Configuring the initial tuning parameters (which is the baseline) before running Auto Tune is the preferred route.
And that’s the same parameter file. Post a link to the .bin log file from the Flight Controller. If you can attache it directly here it’s not the right file. Place it in a cloud service and link to it.
I followed the tuning docs the last time… bird had heavy oscillations right off the bat. If I use stock settings, it flies. Ive flown this exact setup for 2 years now. Only new addition is 4.0.3… This is literally the only flight controller I have issues with. Since the log viewer shows 4 separate logs to upload, maybe give us a hint on what you guys need…
A log showing the notch configured with the problem you are referring to
notch is no longer configured. as explained, i do not understand how to properly set them up. my attempt crashed my bird. logic says, defer to experience. i posted what the docs said to use to set the filtering.
logs are pulling up fragmented.
hope this is the correct file
Getting nowhere here. That folder you linked to doesn’t exist.
Set these parameters and make another simple hover flight in Alt Hold for a minute or so and post a link (a share link) to that .bin log. Perhaps delete all other logs from the flight controller before doing it so it’s obvious which log is this flight.