Cuav V5+ flight controller running on AC 4.3.6 Plus configuration.
i am facing CPU overload warning while flying the drone .i have used Hobbywing 4in1 60A esc for my drone and ESC input protocol chooses is Dshot600.
i also facing vibration cliping and more compass variance .i have done Magfit for compass optimizations’ but still no help on compass interference suffered. CUAV Neo V3 gps is placed well out of battery and ESC source of interferes but still more pain on compass performance.
drone operated at 6s liion battery .
here is the drone look like:
Vibrations are definitely too high, you’ll need to address that before anything else.
Even check if that cover is vibrating or maybe setting up some resonance.
Have you got a photo of the flight controller mounting and wiring?
Despite that the copter is flying reasonably and the position is accurate.
I cant see what is causing the CPU overload. Do you use the CAN buses?
Try disabling the drivers CAN_P1_DRIVER,0 CAN_P2_DRIVER,0
and try updating the bootloader
If you can do a flight with turns and circle we can use MagFit to adjust some compass settings, particularly the compass/motor values.
I think your HNOTCH settings are incorrect based on your prop size.
Set these for the next flight:
INS_LOG_BAT_MASK,1
INS_LOG_BAT_OPT,4
and I think these will end up being about:
INS_HNTCH_FREQ,60
INS_HNTCH_BW,30
I think your DSHOT outputs are not working, there’s no RCout message in the log to indicate which outputs are DSHOT or otherwise. Try setting
SERVO_DSHOT_ESC,1
and see what Messages say when you reboot the flight controller.
thank you for your comments.
here is the flight controller mounting and wiring images and i don’t think canopy(cover) make this much vibration.its just 0.5mm carbon sheet layer.
yes, still my drone flying well in all flight mode even though its suffered from lot of vibration and compass interference i want to fix these two main issue to perform more perfect.
i have disabled both CAN drivers and rebooted the flight controller. But still i can see the CPU load is 65% even drone disarmed . previously also same percentage of CPU load so disabling CAN drivers doesn’t make sense.
i have done this also.in the previous attached log you can find 8Mb file with done the figure of eight in LOITER mode .then i performed below Magfit
Excellent. It wasnt in the logs and I thought recent updates added this message to .bin logs too.
Have you got a recent log with
INS_LOG_BAT_MASK,1
INS_LOG_BAT_OPT,4
or just do a new flight. Because 90Hz is around the frequency expected for 10inch props.
For yours to do 90Hz would mean they are running near 100% all the time. I think all the oscillations are confusing this.
You can leave those parameters set until everything is completely finalised.
Definitely revisit the flight controller mounting.
Maybe use anti-vibration double-sided foam just at the corners. I find if you use square blocks then overall you get different damping on X and Y axis = not good. You need to use blocks that are similar proportions to the shape of the flight controller. So damping is equal in all directions. This may take a bit of experimentation.
Or solid-mount the flight controller!
Also secure the wiring, especially the GPS cable - they are sort of heavy and stiff compared to the other wiring. I strip back an extra inch of the insulation on the GPS cable so the small wires have more flexibility.
Check and secure any other wiring not shown in those photos too.
Once the cover is mounted, as a test, just stick a couple of bits of masking tape or similar from it’s side to the base plate, so it’s definitely not vibrating and see what effect that has. As a permanent solution you could stick a couple of bits of thin foam in key places on the base plate so the cover wont vibrate once it’s screwed down.
You wont get better tuning until the vibrations are fixed. And with the current situation there will be excessive battery drain and motor and ESC life will be shortened.
