Battery- 12s 16 amp solid state battery lion 10c discharging
Autopilot- Cuav v5+
Maximum take of weight including payload – 8kg – currently without payload-6.3kg
Am facing CPU overload error
Flight test: when flying stabilize mode no CPU warning , if am flying alti-hold CPU waring coming every 10 second then, loiter mode CPU waring coming every 2 second.
Even in alti-hold if am moving forward altitude drop then if I left stick again slowly altitude gaining even same thing happening in loiter mode also.
Thanks xfacta in urgent I did not notice as per your recommended I have corrected it now in loiter mode cpu overload not coming but I have flyed in heavy wing 10m/s once came cpu waring but after that not came even for altitude drip I have changed PSC_ACC_P= 0.30, PSC_ACC_I= 0.6. after that altitude dip changed while cruising only 1 to 2 meter after leaving the stick or braking time 2 to 5 meter dip and gaining 10 to 11m/s. but one time to heavy wing I have floon 12 m/s vibration crossed 50+ even I think 60 then sudden ekf 1 lean change came then I left the stick. Sometime in heavy wind in head wind 111 to 12 m/s vibration increasing the problem majorly accrue in head wind. I have attached flight log also but I did not change u mentioned another parm INS_ENABLE_MASK,3 my model 127 is the default value but cpu usage while flying up to 70 percentage load. I want main think I have reduced and changed filter values also. And gyro f-20 aceel f- 20. Now I want to reduce more cpu load and to solve altitude drop atleast 0.5 meter
It looks like altitude issues are because the baro is affected by propwash or wind, so see if you can protect the flight controller a bit more. There is a wind compensation routine you can work through to improve the baro.
I cant see anything specific for the CPU load, except trying INS_ENABLE_MASK,3
I would return INS_ACCEL_FILTER to 10 but this is not critical, nor related to altitude or CPU load issues.
You might as well set INS_HNTCH_ENABLE,0 since it’s not doing anything and the frequency would have been wrong anyway.
You can set PILOT_THR_BHV,7 to suit your spring-centred throttle stick
You should definitely set exactly these battery values:
If you skip these there will be a crash because of it - seen it so many times. All of us think “I know what I’m doing with this battery, I can monitor it myself” and when things get busy or you are distracted that is when your battery will have a bad day and the copter wont be able to save itself. Been there done that. You had MOT_BAT_VOLT_MIN wrong too which can affect the motor/thrust scaling.
