Hi all..
After several successfully flights with 3s lipo and standard PID settings i decided to change out my 3s with 4s 5000mAh batteries.
But something stranges happen during waypoint flight in AUTO mode.
It was set to climb 150meters in a 1km flight path. Everything started just fine, spot on and i was really happy with the result due to the wind and gust.
When the Hexa was almost at 150mtr height, it suddenly smacks the throttle to the max 100% and the copter goes to the sky like a rokcet.
i grab my RC and switch the mode from AUTO to Stab and was able to get it down without any crash.
My Gopro camera was also onboard. ;)
After i tried one more time, Set point of 100mtr .
When the copter reach 60mtr, same thing happend, it suddenly gives 100% throttle and goes like a rocket up in the sky,
Im not able to find the root couse to this problem. Please help..
The log also showing 11sat count at all times.
Can this be becouse of 4s lipo??? or is this just a coincidence?
When using 4s, i ha to change my Rate P from 0.150 to 0.110.
Regards
Ludvig
Replies
hi mate!!!!
Yes something similar happened to me. on my case it was flying nice in stabilize... also nice in alt hold.. but the moment i press loiter and started to work with satelites... the quad just started climbing like crazy. it was not a problem of satelites number or even hdop. check vibrations on z axis. in the new update you have the EKF on the main menu of the flying data. to measure the vibrations. however dont do it in the ground. it happens flying so you have to measure it flying.
regards!!
Hi Guys
I agree, the problems seems to be related to vibrations.
After i installed foam under APM board and adjusted the INS_MPU6K_FILTER to be 20, i never had this problem again.
I think i will invest in new and better motors and carbon prop.
@Bill
Im using 3g GPRS for telemetry.
https://www.youtube.com/watch?v=pV4_WlfTPq0
Is there an error path back to the GCS using Mavlink?
I'm trying to think of ways that the Aircraft could communicate a problem to the Ground Station.
Logging seems to be so port-mortem.
Can you post here all the logs of this unwanted event?
I think is not related to the number of lipo cell.
But quite a few of the many strange runaways is happening after many successful flights and with no changes.
Add fresh battery, start mission as usual, and it takes off, or crashes.
This is happening more frequently now with 2.9.1 but as yet no pattern has emerged to indicate any commonality, other than running 2.9.1
Seems like there have been many instance of a runaway climb in Auto and Loiter modes that I have read on the forums (or seen personally). Is it possible that this is being caused by not setting the new tuning values as per Randy in the V2.9 / V2.9.1 release notes?