Posts: 13 Threads: 2 Likes Received: 0 in 0 posts Likes Given: 9 Joined: Nov 2022 Reputation: 0 02-Jul-2023, 12:10 AM (This post was last modified: 03-Jul-2023, 12:08 AM by Enjam.) Hello! Here is my situation..
I have a 5 inch 6s drone I just finished building myself. Went on the very first "flight" of this build and I'm having an interesting issue.
The drone will not take off.
under max throttle input, the motors do not really spin up. instead it sits on the ground and sort of shakes.
I checked my props to make sure they were the right orientation, fully charged battery, all the basic stuff.
Interestingly enough, If I "sneak up" on the quad with my throttle input and punch it very quickly, the quad jumps up in the air and seems to fly a few seconds before what feels like my throttle gets limited lower and lower to the point where the quad starts to fall back down again, no matter what i do with the throttle. While the quad is in the air my channel mapping seems to be correct and it's not twitchy or unstable, although I wouldnt call it controllable. maybe just a little wobbly and unresponsive with just enough control to keep it level in the air, before my throttle gets limited too low.
A few times when I tried hard yaw movements to spool up the motors, the FC beeped at me and disarmed the quad. almost like an overcurrent thing?
to me It feels like the pid gets too saturated to let the motors achieve any decent rpm. Although i'm no expert. this is literally my first build lol. First I flew with the betaflight defaults and then I tried a preset for my frame. Both times it refused to take off if i raised the throttle slowly
Video: https://photos.app.goo.gl/DXb6aWj2Ex1GQ5Ch9 any thoughts or input would be highly appreciate, I'm not sure where I should look to fix this issue, or what exactly is even happening ![[-]](https://intofpv.com/images/collapse.png) • Posts: 6,140 Threads: 172 Likes Received: 2,296 in 1,843 posts Likes Given: 4,746 Joined: Feb 2019 Reputation: 103 there is nothing such an overcurrent thing, it might be "runaway protection" which kicked in. it would be displayed in the osd warnings.
what fc and esc do you use?
can you remove the rotors, plug in a battery, connect to betaflight configurator - go to the cli tab and type "tasks" and post it back here?
do you maybe have a dvr or video? Posts: 13 Threads: 2 Likes Received: 0 in 0 posts Likes Given: 9 Joined: Nov 2022 Reputation: 0 (02-Jul-2023, 12:22 AM)hugnosed_bat Wrote: there is nothing such an overcurrent thing, it might be "runaway protection" which kicked in. it would be displayed in the osd warnings.
what fc and esc do you use?
can you remove the rotors, plug in a battery, connect to betaflight configurator - go to the cli tab and type "tasks" and post it back here?
do you maybe have a dvr or video? I'll update this post with a video tomorrow, the one I took didn't come out great my fc is a succex-d f722 20x20 and my esc is a foxeer reaper f4 mini # tasks Task list rate/hz max/us avg/us maxload avgload total/ms late run reqd/us 00 - ( SYSTEM) 10 8 0 0.0% 0.0% 0 0 749 5 01 - ( SYSTEM) 984 14 0 1.3% 0.0% 42 48 73344 5 02 - ( GYRO) 8000 16 2 12.8% 1.7% 1559 0 598267 0 03 - ( FILTER) 8000 32 14 25.6% 11.6% 8989 0 598267 0 04 - ( PID) 8000 95 62 76.0% 50.0% 35356 0 598267 0 05 - ( ACC) 933 18 3 1.6% 0.2% 252 30 72276 8 06 - ( ATTITUDE) 490 24 10 1.1% 0.5% 389 39 35606 18 07 - ( RX) 150 29 16 0.4% 0.2% 566 79 33624 20 08 - ( SERIAL) 100 209 2 2.0% 0.0% 74 0 6588 5 09 - ( DISPATCH) 967 16 0 1.5% 0.0% 55 41 73399 5 10 - (BATTERY_VOLTAGE) 50 15 4 0.0% 0.0% 11 5 3740 8 11 - (BATTERY_CURRENT) 50 14 4 0.0% 0.0% 11 1 3740 9 12 - ( BATTERY_ALERTS) 5 9 3 0.0% 0.0% 1 2 375 8 13 - ( BEEPER) 100 12 0 0.1% 0.0% 7 3 6588 2 20 - ( OSD) 12 732 11 0.8% 0.0% 562 5226 26720 27 22 - ( CMS) 20 11 2 0.0% 0.0% 3 1 1475 8 23 - ( VTXCTRL) 5 19 1 0.0% 0.0% 2 1 374 17 25 - ( ADCINTERNAL) 1 10 3 0.0% 0.0% 0 0 75 9 26 - ( PINIOBOX) 20 10 3 0.0% 0.0% 2 1 1471 8 27 - (SPEED_NEGOTIATION) 100 25 1 0.2% 0.0% 10 4 6573 5 RX Check Function 18 2 104 Total (excluding SERIAL) 64.2% • Posts: 6,140 Threads: 172 Likes Received: 2,296 in 1,843 posts Likes Given: 4,746 Joined: Feb 2019 Reputation: 103 the cpu load is to high, i would suggest to set it to 4khz amd dshot300. Posts: 13 Threads: 2 Likes Received: 0 in 0 posts Likes Given: 9 Joined: Nov 2022 Reputation: 0 (02-Jul-2023, 03:16 AM)hugnosed_bat Wrote: the cpu load is to high, i would suggest to set it to 4khz amd dshot300. did that, usage is about 30% now. will test tomorrow and see if there is a difference • Posts: 13 Threads: 2 Likes Received: 0 in 0 posts Likes Given: 9 Joined: Nov 2022 Reputation: 0 (02-Jul-2023, 12:22 AM)hugnosed_bat Wrote: there is nothing such an overcurrent thing, it might be "runaway protection" which kicked in. it would be displayed in the osd warnings.
what fc and esc do you use?
can you remove the rotors, plug in a battery, connect to betaflight configurator - go to the cli tab and type "tasks" and post it back here?
do you maybe have a dvr or video? https://photos.app.goo.gl/q7ftUVQEHeDj65mB9 here is a video of my quad showing the behavior on the bench. notice how my throttle input just becomes completely ignored. could it be the leds i have?? • Posts: 74 Threads: 9 Likes Received: 40 in 31 posts Likes Given: 96 Joined: May 2023 Reputation: 3 (02-Jul-2023, 04:29 PM)Enjam Wrote: https://photos.app.goo.gl/q7ftUVQEHeDj65mB9
here is a video of my quad showing the behavior on the bench. notice how my throttle input just becomes completely ignored. could it be the leds i have?? That is normal behavior with no props. The FC looks for feedback to produce lift and since it isn't getting any it thinks it needs more power • Posts: 6,140 Threads: 172 Likes Received: 2,296 in 1,843 posts Likes Given: 4,746 Joined: Feb 2019 Reputation: 103 02-Jul-2023, 08:26 PM (This post was last modified: 02-Jul-2023, 08:27 PM by hugnosed_bat.)
disable airmode permanently in the configurations tab, throttle should response than. if not, it might be a part of your issue • Posts: 13 Threads: 2 Likes Received: 0 in 0 posts Likes Given: 9 Joined: Nov 2022 Reputation: 0 (02-Jul-2023, 06:08 PM)skamtastik Wrote: That is normal behavior with no props. The FC looks for feedback to produce lift and since it isn't getting any it thinks it needs more power https://photos.app.goo.gl/DXb6aWj2Ex1GQ5Ch9 Here is a video of the same behavior but with props on, throttle just dies off. I record my sticks during the flight towards the end of the video • Posts: 13 Threads: 2 Likes Received: 0 in 0 posts Likes Given: 9 Joined: Nov 2022 Reputation: 0 02-Jul-2023, 08:35 PM (This post was last modified: 02-Jul-2023, 08:35 PM by Enjam.) (02-Jul-2023, 08:26 PM)hugnosed_bat Wrote:
disable airmode permanently in the configurations tab, throttle should response than. if not, it might be a part of your issue https://photos.app.goo.gl/DXb6aWj2Ex1GQ5Ch9 Here is a video of what I'm talking about. I did 2 flights, second one I recorded my sticks. If that's helpful at all • Posts: 74 Threads: 9 Likes Received: 40 in 31 posts Likes Given: 96 Joined: May 2023 Reputation: 3 02-Jul-2023, 08:51 PM (This post was last modified: 02-Jul-2023, 08:51 PM by skamtastik.) Maybe check the Reciever tab in Betaflight.. your stick threshold should look similar to this, I think most are set between 1000-2000. ![[Image: JKJOdVml.png]](https://i.imgur.com/JKJOdVml.png) • |
