So what if upu have no arm disable warranty but it still will not arm? Endpoints setup, not gps rescue as you need gps lock before taking off, switch arming is on and working,throttle down don't work. Tx in binded with rx and is showing in bf, done is level and collaborated. Just refuses to spin motors with tx but in bf with sliders they spin
I have Many qwads now that i have bound (BetaFPV TX module and HM EP2 RX's) and BF gives RXloss in cli tab, and still do not arm. what else could be holding ALL my qwads from arming? I only have one qwad, using ELRS that is bound, able to get into BF and running great. My other 8 get nowhere.
The one thing you forgot, was if a pilot does an incorrect CLI dump, and is actually able to save and execute the dump, then the quad will load up, show that you have telemetry, and even lose telemetry when you unplug the quad. But not arm. And you notice in the modes tab, that when you go to arm, the little ChickLit moves into the slider range, but arm is not highlighted. Nor are some or all of the different things like air mode, horizon, crash flip, etc.. So the solution obviously is to find the correct CLI dump. It happened to me, I found this video, and then later was lucky enough to grab the correct CLI dump for a GEPRC phantom analog. Hit me up if you need it.
@@midge9740 my first thought says check your channel mapping. And also go back to the receiver tab and make sure that the arm switch (and all others in correct order) is actually popping up when you engage it. If it isn’t/they aren’t popping up in the right order…then check your channel mapping on the radio versus Betaflight. Off memory, that’s my best idea.
And i located the problem.. Some sabotour have played around with the firmware, on V2 mobula 2024.. So now when i turn left, with the right stick, the throttle decrease, when i turn right the the throttle increase. And the left stick work as the right should do.. I would guess sombody working for betaflight would do this. Or a christian religius fanatic...
$M>âtARM;FAILSAFE;BEEPER;OSD DISABLE SW;BLACKBOX;AIR MODE;FPV ANGLE MIX;BLACKBOX ERASE (>30s);CAMERA CONTROL 1;CAMERA CONTROL 2;CAMERA CONTROL 3;FLIP OVER AFTER CRASH;PREARM;VTX PIT MODE;PARALYZE;DISABLE VTX CONTROL;LAUNCH CONTROL;¬$M> ¼$M> ng Entering CLI Mode, type 'exit' to return, or 'help' help me plase
12 NEW things you should know about Betaflight ruclips.net/video/h91qRWENBhA/видео.html
Fantastic, Pawel! Thanks a lot for the video! 😃
Stay safe there with your family! 🖖😊
Awesome it will help a lot being new. much love from Sth Aussie outback, God bless n thank you for the video!
Glad it was helpful!
Great video! There one more I can think of . Crash flip !! If the arm switch is the same as the flip over crash the quad won’t arm
Most probably a great video!
for the throttle issue.. you didn't explain how to get it between 1000 and 2000, could you please elaborate on that? thanks
So what if upu have no arm disable warranty but it still will not arm? Endpoints setup, not gps rescue as you need gps lock before taking off, switch arming is on and working,throttle down don't work. Tx in binded with rx and is showing in bf, done is level and collaborated. Just refuses to spin motors with tx but in bf with sliders they spin
Excellent explaination. Many thanks.
Glad it was helpful!
Amazing work ..thank you !!!!
I'm very happy you liked it!
Excellent roundup! I will send a lot of noobs to you from reddit ;-)
Thank you very much 😁
Lol first line, look at the effing info box, it was my newly installed gps, thanks! bardwell didnt say that on his vid.
Glad to help
I love you , and here I did not even know it tells you ! I’m an such a noob …
Can you do a video for inav?
I did like 3 years ago
I have Many qwads now that i have bound (BetaFPV TX module and HM EP2 RX's) and BF gives RXloss in cli tab, and still do not arm. what else could be holding ALL my qwads from arming? I only have one qwad, using ELRS that is bound, able to get into BF and running great. My other 8 get nowhere.
BF gives you precise reason why it not armed. Just see which flag is set
The one thing you forgot, was if a pilot does an incorrect CLI dump, and is actually able to save and execute the dump, then the quad will load up, show that you have telemetry, and even lose telemetry when you unplug the quad. But not arm.
And you notice in the modes tab, that when you go to arm, the little ChickLit moves into the slider range, but arm is not highlighted. Nor are some or all of the different things like air mode, horizon, crash flip, etc..
So the solution obviously is to find the correct CLI dump. It happened to me, I found this video, and then later was lucky enough to grab the correct CLI dump for a GEPRC phantom analog. Hit me up if you need it.
my arm tab doesn’t highlight, but the other modes like air etc do. thoughts?
@@midge9740 my first thought says check your channel mapping. And also go back to the receiver tab and make sure that the arm switch (and all others in correct order) is actually popping up when you engage it. If it isn’t/they aren’t popping up in the right order…then check your channel mapping on the radio versus Betaflight.
Off memory, that’s my best idea.
And now, the fist 126 reasons why inav won't arm. nav_extra_extra_safety_arming = ON allowed values ON, very ON, EXTREME ON.
Wont arm have a load msp message....
Thanks sooooo much !!!
You're welcome!
In my googles i se throttle every time i try to arm
@hjvanderlinden Why dont you come to donbass.
And i located the problem..
Some sabotour have played around with the firmware, on V2 mobula 2024..
So now when i turn left, with the right stick, the throttle decrease, when i turn right the the throttle increase.
And the left stick work as the right should do..
I would guess sombody working for betaflight would do this.
Or a christian religius fanatic...
@hjvanderlinden Это не игрушка, там 14+ на коробке написано.
Игрушка 13+.
@@hjvanderlinden Эта вещь лечит все болезни.
По этому зайцам они (мини выпы) не нравятся.
R.I.P FPV
Help me. ARM disabled 😭
be patiencnt, youll get it, we all go through this stage in our quad lifes :) you will get it bubba !
Schwis
$M>âtARM;FAILSAFE;BEEPER;OSD DISABLE SW;BLACKBOX;AIR MODE;FPV ANGLE MIX;BLACKBOX ERASE (>30s);CAMERA CONTROL 1;CAMERA CONTROL 2;CAMERA CONTROL 3;FLIP OVER AFTER CRASH;PREARM;VTX PIT MODE;PARALYZE;DISABLE VTX CONTROL;LAUNCH CONTROL;¬$M> ¼$M> ng
Entering CLI Mode, type 'exit' to return, or 'help' help me plase
Thank you solved my problem with GPS rescue 🛟
My pleasure