Hi, I have a quad and the motors maxing out in flight. Not in the takeoff or landing phases, just in the normal flight in altitude hold mode. The copter gives max throttle to the motors and the vehicle altitude increase without any control, with ignoring my rc commands.
Any suggestion about it?
Post a link to a.bin flight log file and describe the components on the craft, it’s battery power and the take-off weight.
The weight is 1.5kg, has the 4S battery. The flight in altitude hold mode.
In the flight, when the battery voltage decreases 14.0 V, the motors maxing out and altitude increase with full throttle. Then I get a “potential thrust loss (1)” error. When the vehicle rises, the battery voltage decrease to nearly zero. When I disarmed the vehicle, the battery voltage increase again the 14.0 volt level.
But I’m not sure about the battery voltage level is the reason or it is the result for uncontrolled altitude
increase with full throttle.
Unfortunately I’m not have a .bin log, can you make a suggestion according to these informations? If I get the log file I also share it but I’m not reach the vehicle now :).
14V is the default value for BATT_CRT_VOLT for a typical 4S LiPo, which in turn should trigger a failsafe, defined in BATT_FS_CRT_ACT. The drone increasing altitude at battery critical failsafe sound like it’s attempting to RTL. If this is the case, the drone tries to increase altitude with the speed defined in WPNAV_SPEED_UP until it reaches the height defined in RTL_ALT.
Check the paramters I mentioned to see how close my guess was. Or post a .param file with your parameters so we can have look and don’t have to guess anymore.
That the voltage decreases rapidly is expected behavior, because the battery is basically empty at this point and increasing altitude at high speeds needs a lot of power. The “potential thrust loss” messages comes, because the drone doesn’t climb as fast as it would expect, based on esc pwm.
Be aware that since your battery was below 3V/cell it can be permanently damaged now. Charging and using it again may be a serious fire hazard.
…
Motors, props?
Thanks for all, the flight in altitude hold mode and there no defined failsafe setting or a rtl mode. I will share the param file when I get the vehicle
Velox V2306 motors with 3 blades props
What size 3 blade props? These are simple questions. We can easily determine if there is sufficient thrust/weight if you give complete answers.
sorry, with these props: T5147 2Pairs/Bag_Propellers_FPV Model_T-MOTOR Official Store - UAV Power System, Robot Power System, Model Power System
You are missing a lot of critical calibration and configuration.
Have a look at the How to methodically tune (almost) any multicopter using ArduCopter 4.4.x guide and do all the steps youd didn’t do so far. Download the .zip folder with the param files from the guide, edit each file to suit your copter and upload them one by one as you read along. The guide tells you what to do and which file is needed at any given time. Do not skip any steps! Anything that might seem like a shortcut will result in a worse tuned copter in the end.
Do this and report back if the problem persists.
Those motors come in 3 different kV ratings. Really spinning the wheels here.
I’ll try this, thanks for all
Hello again, I had the same problem again, unfortunately I did’nt provide a log file but this time I have a log. Can you help me?
00000042.BIN (522.1 KB)
You don’t have the same problem again, you still have the same problem.
From your log I can tell that you didn’t follow the methodic tuning guide. You are still missing IMU temp cal and MOT_THR_MIX_MAN, PSC_ACCZ_I and PSC_ACCZ_P are default. I didn’t look further after that to find more errors.
Do you want a drone that flies (aka is capable of lift-off) or do you want a drone that flies great?
If you want a drone that’s capable of lift-off, congratulations you are done.
If you want a drone that flies great, there is no way around the methodic tuning guide. I really meant it when I said “Do not skip any steps!” (hint: that’s why it’s bold).
I am not willing to put in the effort and try to help you if you aren’t willing to put in the effort and do what we tell you.
Of course, but I have not yet performed a tuning according to the guide you shared, the log file I shared is not a log taken after tuning, I tried to get a log file by flying to explain the situation better. So, this log was taken to better explain the situation to you (because the previous time I cant share a log with you), not to show the tuning result, I apologize if I misunderstood.
The next weekend flight I follow the tuning guide and I hope I can share the better results after it
Actually, what I want to draw your attention to is that the “desired alt” in the CTUN section goes negative and I am experiencing such a problem in some flights in altitude hold mode. However, in the flights I made without any problems, the desired alt value is not negative, but a similar curve with alt and baro alt. Could my problem be related to this?
That’s another log file, when vehicle flies, the CTUN Desired Altitude jumps according to graph and in the flight, drone jumps up.
https://drive.google.com/file/d/1USnzdvxkFXAHN72Z7Gcxb_cTUd_A7RWJ/view?usp=sharing
Apologies if I was harsh, we see a lot of people who expect to get their drones fixed without them doing anything. Indeed, the log gives a better insight to what is happening with your drone.
And that is not good, you have a severe vibration problem:
Fix this before you try to fix anything else. It is not possible to build a well flying drone with these vibrations.
You are right, the desired altitude (DAlt) jumps but the drone is ascending before that, at the jump DAlt and Alt just catch up to the barometric altitude (BAlt). What I think is even more concerning than the jump of DAlt is that Alt matches DAlt and not BAlt, which I would again attribute to the vibrations.
Also (as a sidenote) why are you on 4.5-dev? At the time you created this topic Copter 4.5 was already on beta4. And now you can even update to 4.5 stable when you start tuning the drone on the weekend.
Thanks for all, you explain as the documentation’s “vibration failsafe”, but I didn’t see a warning like “vibration failsafe on” as the mentioned as the doc’s page ?
I think I triggered vibration failsafe according to the page
