Infact this was my first attempt to make a quad copter. unless if i hadn't seen this CLI MSP VIDEO i would have given up this drone project and iwas planning to buy another flight controller board. Thanks a lot and a big salute to you.
As usual, your videos are the best and always help to solve my problems. Plus they are enjoyable to watch and I learn so much from each one. Thanks a million!
You are so awesome I’ve been fighting this for months thinking my rx s are shot or messed up turns out you just explained what I needed to know an good thing I didn’t throw any over my recivers away
I wasnt sure which of your videos to post this on because I've used so many in setting up my first drone. somehow it came despite the build going so smoothly and the only thing I ever resoldered was my receiver. Yet somehow I had every issue possible in setting it up in betaflight it seemed like. my throttle and pitch were reversed which is where my first arming disabled flag came from and after two days of working with my transmitter got that straighter out, to the realize I set up a failsafe mode instead of a gps take over mode. (I have the tyro 119 so it came with a gps). but thank you and god bless you and you're seemingly infinite knowledge of drones.
Wow... you save my life..... thanks for your best explanation... you solve 2 problems with this video and another one that I watched from you channel. You are the best.
So I’ve done all this in the video, I can get the receiver tab to respond properly and can get the motors to power up while connected to Betaflight. I disconnect the cord and plug a battery up and get nothing. Is there a setting I’m missing?
Hi Joshua! My spektrum satelite receiver now works (yellow light solid) only when the usb cable is connected to betaflight. If I disconnect it (drone battery is plugged, so there is energy in the STM32F411 board) the receiver light goes off. It was working fine previously... Do you have any clue why? Can it be a board malfunctioning, or you think this is programming? Thanks!!!!
I'm new to this whole quadcopter thing and mine wouldn't arm at all. This is my first one and I was so confused and I didn't know why it wouldn't fly. Keep in mind I know absolutely nothing about this. I thought it would be fun because I fly just normal story ready drones. So, I thought I'd take it up a level. Little did I know that level would be a huge one. I spent my first 3 days with this quadcopter not knowing how to even get it off the ground. Although it's kinda hard to break my spirit if I like something so I kept searching the web and well...you're the only person who actually fixed my problem. And you made it seem so simple. Thank you a ton. I can actually fly now😂
JB, once I select (I understand the risk...) in the motors tab, how do I save it? I checked it, then switched over to Modes tab and it still doesn't arm because of MSP. went back into the motors tab and it was I selected again.
I have 4 quads that are "armless" after flying well, then going to Beta 4.02. I followed your instructions and typed in set runaway_takeoff_prevention = off and it said it was off- then would not arm . Same warning showed in motors tab. I guess that "I did'y learn something today".Thanks in advance for a response!!
@@jmbauer68 thanks for replying! If by any chance you still have everything for the quad my problem was the newer updates do not allow you to arm your quad while connected to betaflight. So when you flip the switch to arm it will display as "disabled" on betaflight. I resolved this by just leaving my switch in the unarmed position, unplug the quad and turn off the transmitter. Then started off by turning on transmitter first then plugging in quad. Waited 5- 10 seconds after the startup beeps and then flipped my switch to arm. The quads motors started spinning at the 3% idle i had set it to
Hey josh I have the iflight succex f4 Mini . have my xm+ binded no stick inputs. Binded to a model that already setup. Do I have to change something In cli. I watched all your videos related to this. Any help is appreciated. Crossfire will be here in two days otherwise lol
Thanks for the videos I bought a Chameleon off offer up being my first drone period ended up having everything in beta flight messed up motors hooked up backwards a bad esc transmitter end point where way way off I got it all working from your videos thanks I appreciate it
Joshua, When you first plug in it says "Arming disabled". WHen you pwer up and try to arm it says "runaway takeoff prevention temporarily disabled". Will not hit through Beta or transmitter. Thanks again, Joshua.
In your intro vid you had one long beep and 3 short beeps, exactly my issue in 4.2.9. Not found a solution though. Surely you can run the motors up in the motors tab with MSP overridden. My motors (props off) still wont run up.
Could you help! Cant work it out been on it for days. My beta75x HD wont arm because the arming status flag is saying PARALYZE and i cant find anything about getting rid of it
Joshua, I typed in as before, CLI said OFF, I hit all save buttons I could find- "save to file", typed in Saved in CLI box, it said "Saved"-- nada. Back to motors (Runaway_takeoff_prevention diabled. The engines will not run on Beta or arm without it. This is despararate. I have 50 quads and more than 20 are diasabled. They flew fine before Beta 4,02. How far back can I go to reload old Betaflght configuartor programs? Thanks for your response if you have an idea!!
What is the arming status code that is preventing you from arming. That is, ultimately, the answer to why it won't arm. What does the Warning OSD element say when you try to arm?
I guess I do not understand- those are the only warnings I see. Is the OSD a separate warning-- One that I am stupid and missing? If so, clue me in oh great flight brother!!?? Your attention to this problem is SO much appreciated.
I have the exact opposite problem here.. Can't disarm the quad, at lowest throttle, bt I set stick low threshold to 1100,min command esc to 1000,min throttle to 1100,all channels mid point set to 1500-1502 with a dead and, any help thanks
Hello, again Joshua, wondering if you can help me I'm stumped again, i have an CL Racing F4 FC Stack, the problem is that on the receiver tab On BF when i move the roll to the right the bar on BF goes left same with Yaw. Second is the green light flashes when plugged into the pc, and when i plug in the battery and try to arm it is blinks 4 time fast then 3 with a pause and then 1 pause then 3 more blinks what is the problem? Info on BF says Arming disable flags: MSP. that is cause its plugged in ?
Dude@ I have a diatone f405 mk2 stack.. I flashed the latest firmware, connected the motors to the ESC, and connected the R9 MM receiver.. The receiver is connecting to the remote but no movements are detected by betaflight, know that i tried all 3 channel maps to no avail. Then i wanted to test the motors using betaflight.. No go, they dont even try.. I also only hear 3 prime beeps when plugging the battery on. I cant figure it out, its a new stack.
First, check that the R9MM is definitely bound to the controller. Solid green LED when controller is on will confirm this. Blinking red LED when controller is on means it's not bound. Once the receiver is bound, check for moving channels in the receiver tab of betaflight. If not, then check Ports tab and see which UART has "serial rX" enabled. Make sure it is the correct UART. Also check that the receiver protocol is correct in the Configuration tab (it should be SBUS by default for that receiver). Check your wiring. The SBUS OUT wire on the R9MM must go to the SBUS pad on the F405. The missing last-3 tones of the ESC startup mean the ESC is not seeing any motor signal from the FC. This is unrelated to your receiver.
@@JoshuaBardwell Thank you.. Everything checks out.. I think i might have a bad stack.. Because the ES is also not seeing the motors. The FC LED is also Red.. So IDK.. What do you think?
Diego Ruiz I might be too late.. But, I downloaded the stack firmware from Diatones website.. After the download, I loaded the files using Betaflight and flashed the firmware.. It worked very well.. I've had no issues with it.. Flashing the firmware using the available firmware file versions on betaflight seems to not work with this stacks. It does work when downloading the firmware files from Diatones website.
I've jumped from toy drones to Hoby and now my head is shot to bits.. Bought a betafpv hx100se(dsmx) Cant bind it to my jumper (far to advanced) drone just sits flashing a red led.. Im not a real beginner but this is a bit harder to understand.. Jumper set to dsmx but bind it will not.. 🤔.. Your videos are great but I think I've bitten off more than I can chew with this lot.. Thanks, bk (UK)
Hi Joshua i have been looking at a lot of your videos and they have been really helpful. I have my quad setup for the most part but i am encountering and failsafe that is caused by loss of voltage after arming and advancing the throttles. I have an armattan marmotte, connected to BF i see the 6s pack with the correct voltage. As soon as I arm it the mototrs start the voltage goes to 5v but when i advance the throttles the voltage drops rapidly and i see a failsafe in the setup - Armng disable flag line. Hoping you might be a able to offer some ideas. this is my first quad build and I am running a hobbywing F4 G3 stack inc 60amp ESC, jeti ex bus radio. rush tank vtx I re soldered the wires for the radio and same issue. Once again i am hoping you might be able to help. Simon
Hi Joshua! I've just started to build another new quad. And I have troubles with receiver. Flashed today 3.5.1 on OmnibusF4 Receiver R9Mini is binded in 1-8 channel TEL. mode. Port uart1 is selected for Serial-RX. Receiver setup - Serial-based, SBUS is selected. Betaflight Serial status - linked. Receiver is green. Battery is connected. But on Receiver tab all values are frozen! Nothing is moving Tried to bind in 9-16 ch mode - the same story I have same Omnibus F4 on other quad and same R9Mini - everything works fine on betaflight 3.3.x Do you have an idea?
Joshua, Thanks for all of your videos. Unfortunately, none of them have helped. I am new (never gotten my drone off the ground) to the sport and am within a hairs breadth if throwing the whole mess - batteries and all in the nearest trash can. The problem I am having is that I am able to bind my receiver(s) to my transmitter, but I cannot get any response on the receiver tab in beta flight. I have tried two different receivers, Frsky D4R-II and Frsky V8R4-II with my Taranis-Plus. I can get both to bind in both modes, but I am unable to get any response on the transmitter tab. I have a Speedy Bee flight controller which is using: # version # Betaflight / SPEEDYBEEF4 (SBF4) 3.5.7 Mar 15 2019 / 22:20:51 (e9130527c) MSP API: 1.40 Any help will be greatly appreciated.
Under the "Mode" section, the "Arm" shows red and disabled. the arm switch is actually controling the flight mode...I have the tinyhawk drone and remote. How should I correct it? Thanks.
is there a reason my sensors never calibrate on initial setup? everything else works except it won't calibrate and says its still calibrating sensors. not to be confused with this issue. but kinda similar
I get the same message but when I press arm on the control it does not move to arm in betaflight nor does it recognize my control, but when I press turn off on the control it tells me that it is connected to the Drone but in betaflight it does not recognize my control
Runaway takeoff prevention disabled, Josh, I am dying -- all those hours building-- they all have the same message. I tried to go back and download 3.4 Beta-- was not there. I was able to turn the Prevention from ON to OFF-- but it did not hold to arm. Thanks for your attention- I know you are busy!
This fixed my arming problem but when my throttle is all the way down and I arm, the motors start pulsing like I’m slightly moving the throttle. Any help?
hi from indonesia here,i tried it on mobula 7 hd but still got the arming disable flags: msp and then all of my setting is gone in the betaflight and disconnected from the radio,oh and i put nick burn pid for the mobula 7 hd, any advice would be great Master Bardwell :) ,need to do this for the lockdown time here :) ,Thx
My throttle joystick is slowly raised, but the throttle continues to increase. I checked betaflight, it indicates in arming status flags "THROTTLE MSP". What should I do?
I think the speedybee app will allow arming while connected to MSP over OTG cable in all configuration tabs (not just motors tab. Props off of course ;-)
Betaflight should absolutely prevent arming when anything is connected via MSP. I'm not sure how the app could override this... maybe by disconnecting after loading the screen? It's possible... but dumb if true.
i just received my receiver and got er bound and guess which status codes i had cli and msp so i got the arm switch working no gps yet but thank you joshua man all your vids and messages helped so much how ever now when i arm the props start spinning so need to get that sorted lol thx
hello JB, i am not able to arm it even after doing what you have said, i am trying to arm when it showed CLI MSP, then i did what you said to do, but still it wont arm, and when i connect battery the motors start to spin, without recieving any signal, can you please help me to solve the issue Thank you
Hallo joshua..I have the same problem like this I'm checking the cli the status CLI is ( Arming disable flags: CLI) on osd warning I see his battery flashing So What am I supposed to do?
The FC is restarting every couple of seconds but only when the camera is plugged in with 7 beeps(with a smoke stopper). When the camera is not plugged in, it is ready to fly. I pulled another camera from one of my other quads that I know works and it resulted in the same thing, so it shouldn't be the camera. I looked over the wiring and everything looks ok visually. I also checked with a multimeter and the camera is getting the right power. Arming disable flags: RXLOSS CLI MSP. I followed the video and I'm still having difficulty, what am I missing?
This is a very tough one. If the FC reboots when the camera is plugged in, but the camera is not at fault, it's a real mystery what else it could be. My next guess is that the voltage regulator on the FC is damaged and the camera is drawing enough current to overload it. Replacing the FC would be the fix. If the camera is powered from vBat then I'm truly at a loss.
Hi Joshua. I have noted that if I connect the FC to the USB and launch the BF configurator, then feed up the ESCs with a LiPo (may be to test the motors) and then I unplug the USB cable, the quad won't arm. I think that it happens because the LiPo is keeping the FC alive with the MSP flag still active. In fact, if I detach the LiPo and reattach it again, the quad will arm with no problems at all. Can it be a kinda of bug in the BF configurator?
Hey Josh I'm having problems with my quad it's saying calib is the arming flag but it arms whilst I'm in th configurator but the minute I unplug a the usb it does not arm and it's not arming on just my new lipos for some reason as it works absolutely fine on my old ones
i have a msp arming disable flag. ıt doesn't work by unplugging the usb. every time I disarm then i need to connect to the Betaflight and check the box I understand the risk under motors tab then it arms. but I don't want to do it every time i disarm. ıs there any fix for that. thanks
Thank you for pointing me this video, I followed his instructions (MSP) lost, but everything remains the same as the old motor test still does not spin and info (Arming Deaktivert aufgrund). I turn on the AUX1 switch, then the motor has 3 music (Te te ti) but the motor does not spin. I want to reiterate my chip is the MAMBA F405 Mk2 4in1 ESC Konfiguration 4.1.4, very expecting him indications.
I have an issue, trying to set up a tricopter and my motors run continuously when not armed, about half throttle. Also, ESCs wont initialize when not plugged into USB. And the servo is backward, but that's another issue.
Your expertise is second to none and your videos are very appreciated. My problem. I've got a Meteor 65. Using BF 3.5.7. Xmitter is a Taranis X-Lite. Set-up aux 1 for arming/disarming. I never use the CLI command until now. Problem, quad won't arm. In the CLI I get the "CLI MSP" message. I've done all you've explained in the video to no avail? In BF I activated the motors and get all the results you've covered. In 'MODES' when I arm them box on the left says ARM (Disabled) and turns RED. Disconnected from BF connect the batt and can't ARM. Any ideas..........I'm completely lost.
In the OSD tab turn on the Warnings OSD element. On 4.0 and newer it's on by default. On 3.5 I think it exists but it's not on by default. When you go to arm it will give whatever status code is preventing arming. Something must be coming up after you disconnect from USB.
@@JoshuaBardwell Here's the dirt. IT's WORKING!! Here's what I did: - OSD tab was already checked? Reviewed OSD checks & made some minor changes as to what I wanted to see. - Adjusted ALL Recvr travels to min 1000 and max 2000, not just throttle. - In CLI got new message 'throttle CLI'. Thr in recvr was 1010, readjusted to min 996 couldn't go to 990. - CLI now states 'CLI MSP'. hmmmmmm - Did the motor thing as you suggested then in the CLI it displayed 'cli'..hmmmmmm - Unplugged USB, turned on the TX, plugged in the battery, armed & motors spun up?? - Plugged USB, went back to BF Config screen & activated 'Motor Stop' and saved. - Reviewed all the different tabs leaving defaults as is ensured DShot 300 was still selected, Rec'r set to SPI RX support - FRSKY_X. - Made a back-up of everything. - Unplugged USB, turned on Tx, put batt on, and low & behold she behaves as a quad should. Made an observation though. Connect the 65 in BF and just leave it on the 'setup' screen. Look at the model, after a few seconds it gives a little 'twitch' & continues doing it every few seconds?? Could that be related to what Nick Burns was taking about? Anyway, gotta fly this sucker. Couldn't have done it without you. Thank you ever so much Joshua. You dedication to the hobby, effort in producing, time uploading all the videos, and especially sharing all the interesting and entertaining videos is very much appreciated by, and I'm sure I'm speaking for all of us enthusiasts, me. Very best holidays, prosperity in the New Year and best of health.
Tonight I noticed I could arm whilst connected to usb, I thought I was going crazy with arming flags and of course your useful series pointing to the BF flashing codes was really useful. But how can I arm the quad with usb and BF connected, I don't have motors connected so haven't been near the motor overide option shown in this video? I checked using CLI 'status' and noticed no MSP flag, just CLI listed ...bug?
Hi my Serial Link Icon in the Configurator is sometimes blinking, sometimes not. I use a Multiplex Reciever. What does the blinking icon says. No arming flags in the status only msp and cli. Sometimes i cant arm, i'm confused With Jeti Reciever no problem at all...
Well definitely have to have a look at the rest of the series as I was having issues with that on my Mantis 85 and when I went to find out why, got the notification with status that it was the CLI. Is there a way to know what all the warning flags are? Perhaps that's one of your video's but I know one I can ignore now, thanks again.
I would think the use of MSP telemetry or RX would not prevent arming since those functions are intended for use in flight. Only MSP configuration would prevent arming. But I've never used MSP telemetry or RX to be honest, and I don't know of any FC or receiver that uses them.
Spent all night trying to get my new tinyhawkfreestyle 2 to arm, Iwas getting rxloss cli so I check out your playlist and give myself a headache lol. In my case it was my taranis playing up pitch roll raw throttle was all missed up, I don't understand what is going on with my taranis but when I try to create a new model I get a message saying id used on a different model witch means I can't choose plane multi ect . I have got round this but I have to go to the mixer page and edit because I can see pitch engine or something next to Ail Ele Thr Rud. Does any one know what's going on here sd card in the taranis maybe, thanks
NOGYRO typically means that the FC is toast. It could also mean you flashed the wrong firmware to the FC but you would know if you had flashed it recently.
@@JoshuaBardwell Yeah, just recently flashed 3.5 on the board. No chance to reinstall? I found that if I went into CLI, did a get gyro and then reboot, it would arm again. The only oddity was that the CPU was at 2% while it wasn't responding
So let me get this straight.The simple flip of a switch starts the motors??or am I missing something?.If this is true i see many people getting hurt..Bring back the throttle bottom left arm...
If you are concerned about flipping the switch use the prearm mode, which requires two simultaneous switch flips to arm. Using the sticks to arm and disarm doesn't work for freestyle and racing drones where you need to use yaw at the same time that you are at zero throttle. With the stick disarm method, I can't do an inverted yaw spin without disarming. And switch disarming is faster and more certain than stick disarming. With racing and freestyle drones, you often need to disarm immediately to avoid damage to the quad or to property. Having to input a stick command is slower.
@@JoshuaBardwell Makes sense in the race acro environment.would be nice to have a simple option/toggle or something like that to use throttle stick like years ago. I think you still can setup throttle arm on aux switches?
Hi Joshua, I've got the MSP warning still coming up even when the quad is completely disconnected from the usb cable. this has only started happening since I flashed from 3.4.0 to 3.5.4 earlier today. Im not sure if it is related (as I'm also running from a new laptop) but BF is having loads of trouble connecting to the quad when it is plugged in - i have to keep unplugging and replugging in the cable, and maybe 1 in 10 tries, it will connect. FC is a Matek F405-OSD. Im really hoping its not an FC issue. Is there any way to disable the MSP flag so i can at least fly? cheers
just following on from my last post - I tried downgrading back to 3.4.1 but the problem persists. Also, when i said BF was having trouble connecting - its a bit stranger than that - it seems to connect, and the configurator reads that it is a matek FC and what BF version is on it, but then times out waiting for the config to read. I'm thinking more and more that its got to be the FC hardware itself is the issue.
As a newbie and just getting into betaflight, your videos have been a great help.
I agree he definitely can be a huge help when you first start out.
After hours of research and trying to get our copters airborne for the first time, you have now told us the important information we needed.
Thanks
You deserve 1 million subs josh ! Because the information you give is second to none.
Thank you Mr. Bardwell for all you do for this hobby. You probably have kept so many flyers in the hobby.
Infact this was my first attempt to make a quad copter. unless if i hadn't seen this CLI MSP VIDEO i would have given up this drone project and iwas planning to buy another flight controller board. Thanks a lot and a big salute to you.
Glad to hear the video helped you fix your problem!
spend 40 mins to figure out that problem , finally came across this video .
Thanks Joshua.
Once again Joshua Bardwell saves the day !!! Thanks Josh 👍
Thank you JB! Once again, you had the answer to a problem I've been having. Your content has been a goldmine for me building my 1st DIY quad!
As usual, your videos are the best and always help to solve my problems. Plus they are enjoyable to watch and I learn so much from each one. Thanks a million!
You are so awesome I’ve been fighting this for months thinking my rx s are shot or messed up turns out you just explained what I needed to know an good thing I didn’t throw any over my recivers away
The wonderful thing about your vids is the instruction clarity. TY JB
That voice… like melting butter on a pile of warm flapjacks. Amen.
I wasnt sure which of your videos to post this on because I've used so many in setting up my first drone. somehow it came despite the build going so smoothly and the only thing I ever resoldered was my receiver. Yet somehow I had every issue possible in setting it up in betaflight it seemed like. my throttle and pitch were reversed which is where my first arming disabled flag came from and after two days of working with my transmitter got that straighter out, to the realize I set up a failsafe mode instead of a gps take over mode. (I have the tyro 119 so it came with a gps). but thank you and god bless you and you're seemingly infinite knowledge of drones.
Wow... you save my life..... thanks for your best explanation... you solve 2 problems with this video and another one that I watched from you channel. You are the best.
mine still doesn't want arm, it said cli msp but when i unplug it still won't arm, help me..😭
I absolutely love your videos, without you I won't be able do anything on my quads. Love you.
Like usual , thank you soo much mr bardwell ❤ you save my day
So I’ve done all this in the video, I can get the receiver tab to respond properly and can get the motors to power up while connected to Betaflight. I disconnect the cord and plug a battery up and get nothing. Is there a setting I’m missing?
thank you joshua, i learned something today
I learn something everyday. I appreciate JB also :)
Every time I search RUclips and try to solve and issue with my drone one of your videos comes up! Thanks again......
Hi Joshua! My spektrum satelite receiver now works (yellow light solid) only when the usb cable is connected to betaflight. If I disconnect it (drone battery is plugged, so there is energy in the STM32F411 board) the receiver light goes off. It was working fine previously... Do you have any clue why? Can it be a board malfunctioning, or you think this is programming? Thanks!!!!
My Quad still doesnt work i also had in status exactly the same issues
Thanks again for saving my frustrations and launching my quad/controller/goggles into a wall. 🙏🏻
OMG thanks dude, That helped so much and was easy to follow, great vid thanks!
I'm new to this whole quadcopter thing and mine wouldn't arm at all. This is my first one and I was so confused and I didn't know why it wouldn't fly. Keep in mind I know absolutely nothing about this. I thought it would be fun because I fly just normal story ready drones. So, I thought I'd take it up a level. Little did I know that level would be a huge one. I spent my first 3 days with this quadcopter not knowing how to even get it off the ground. Although it's kinda hard to break my spirit if I like something so I kept searching the web and well...you're the only person who actually fixed my problem. And you made it seem so simple. Thank you a ton. I can actually fly now😂
JB, once I select (I understand the risk...) in the motors tab, how do I save it? I checked it, then switched over to Modes tab and it still doesn't arm because of MSP. went back into the motors tab and it was I selected again.
Well this video seems to have cleared up my arming problem, at least I finally got my mobula 7 to take off and hit the ceiling on 2s :-) Thanks Joshua
I have 4 quads that are "armless" after flying well, then going to Beta 4.02. I followed your instructions and typed in set runaway_takeoff_prevention = off and it said it was off- then would not arm . Same warning showed in motors tab. I guess that "I did'y learn something today".Thanks in advance for a response!!
Did you type "save" after you turned off the feature?
My arm mode turns red and says disabled when the switch goes in the range. Any ideas?
did you ever figure out the problem?
Third this
@@joshuarodriguez5988 nope. Paperweight.
@@jmbauer68 thanks for replying! If by any chance you still have everything for the quad my problem was the newer updates do not allow you to arm your quad while connected to betaflight. So when you flip the switch to arm it will display as "disabled" on betaflight. I resolved this by just leaving my switch in the unarmed position, unplug the quad and turn off the transmitter. Then started off by turning on transmitter first then plugging in quad. Waited 5- 10 seconds after the startup beeps and then flipped my switch to arm. The quads motors started spinning at the 3% idle i had set it to
@@joshuarodriguez5988 Thanks for the insight. I will give this a try.
Did it for me. I was baffled. Thank you.
Hey josh I have the iflight succex f4 Mini . have my xm+ binded no stick inputs. Binded to a model that already setup. Do I have to change something In cli. I watched all your videos related to this. Any help is appreciated. Crossfire will be here in two days otherwise lol
Thanks for the videos I bought a Chameleon off offer up being my first drone period ended up having everything in beta flight messed up motors hooked up backwards a bad esc transmitter end point where way way off I got it all working from your videos thanks I appreciate it
That's really awesome to hear, Shawn!!!
Ok... just had to restart my quad completely after I disconnected it... that was it.... thanks Joshua xD
by the way this is like the 100st time I set up a quad xD
The Goggles that come with the new dgi FPV Drone can u use that in other drones that have dgi unit in them
Hey Joshua. Thanks for sharing your wisdom. - but didn't you forget to mention to disconnect the batteri and reconnect? - That's needed to.
Thank you for this really helpful series of videos! you rock!
Joshua, When you first plug in it says "Arming disabled". WHen you pwer up and try to arm it says "runaway takeoff prevention temporarily disabled". Will not hit through Beta or transmitter. Thanks again, Joshua.
In your intro vid you had one long beep and 3 short beeps, exactly my issue in 4.2.9. Not found a solution though. Surely you can run the motors up in the motors tab with MSP overridden. My motors (props off) still wont run up.
Hello Pilots
Would be easy for me, how you wrote the comando name? ceiling on 2s? not work on my desk. Thanks for help.
Could you help! Cant work it out been on it for days. My beta75x HD wont arm because the arming status flag is saying PARALYZE and i cant find anything about getting rid of it
Joshua, I typed in as before, CLI said OFF, I hit all save buttons I could find- "save to file", typed in Saved in CLI box, it said "Saved"-- nada. Back to motors (Runaway_takeoff_prevention diabled. The engines will not run on Beta or arm without it. This is despararate. I have 50 quads and more than 20 are diasabled. They flew fine before Beta 4,02. How far back can I go to reload old Betaflght configuartor programs? Thanks for your response if you have an idea!!
What is the arming status code that is preventing you from arming. That is, ultimately, the answer to why it won't arm. What does the Warning OSD element say when you try to arm?
I guess I do not understand- those are the only warnings I see. Is the OSD a separate warning-- One that I am stupid and missing? If so, clue me in oh great flight brother!!?? Your attention to this problem is SO much appreciated.
Great video, I'm getting throttle msp?
Joshua Bardwell HI.you are an angel genius .what we do without you.thanks for all.
I have the exact opposite problem here.. Can't disarm the quad, at lowest throttle, bt I set stick low threshold to 1100,min command esc to 1000,min throttle to 1100,all channels mid point set to 1500-1502 with a dead and, any help thanks
I love you lol JB YOU THE MAN!!!! Thanks for saving the day!!!!
Wow seriously amazing man...you are doing great job...this tutorial helped me a lot!! Thank you soo much
Hello, again Joshua, wondering if you can help me I'm stumped again, i have an CL Racing F4 FC Stack, the problem is that on the receiver tab On BF when i move the roll to the right the bar on BF goes left same with Yaw. Second is the green light flashes when plugged into the pc, and when i plug in the battery and try to arm it is blinks 4 time fast then 3 with a pause and then 1 pause then 3 more blinks what is the problem? Info on BF says Arming disable flags: MSP. that is cause its plugged in ?
Dude@ I have a diatone f405 mk2 stack.. I flashed the latest firmware, connected the motors to the ESC, and connected the R9 MM receiver.. The receiver is connecting to the remote but no movements are detected by betaflight, know that i tried all 3 channel maps to no avail. Then i wanted to test the motors using betaflight.. No go, they dont even try.. I also only hear 3 prime beeps when plugging the battery on. I cant figure it out, its a new stack.
First, check that the R9MM is definitely bound to the controller. Solid green LED when controller is on will confirm this. Blinking red LED when controller is on means it's not bound.
Once the receiver is bound, check for moving channels in the receiver tab of betaflight. If not, then check Ports tab and see which UART has "serial rX" enabled. Make sure it is the correct UART. Also check that the receiver protocol is correct in the Configuration tab (it should be SBUS by default for that receiver).
Check your wiring. The SBUS OUT wire on the R9MM must go to the SBUS pad on the F405.
The missing last-3 tones of the ESC startup mean the ESC is not seeing any motor signal from the FC. This is unrelated to your receiver.
@@JoshuaBardwell Thank you.. Everything checks out.. I think i might have a bad stack.. Because the ES is also not seeing the motors. The FC LED is also Red.. So IDK.. What do you think?
@@Ivar1231 I have the same problem, how did you resolve it?
Diego Ruiz I might be too late.. But, I downloaded the stack firmware from Diatones website.. After the download, I loaded the files using Betaflight and flashed the firmware.. It worked very well.. I've had no issues with it.. Flashing the firmware using the available firmware file versions on betaflight seems to not work with this stacks. It does work when downloading the firmware files from Diatones website.
bonjour merci beaucoup pour ton tuto sa ma aide pour l'armements de mon quad
I've jumped from toy drones to Hoby and now my head is shot to bits.. Bought a betafpv hx100se(dsmx) Cant bind it to my jumper (far to advanced) drone just sits flashing a red led.. Im not a real beginner but this is a bit harder to understand.. Jumper set to dsmx but bind it will not.. 🤔.. Your videos are great but I think I've bitten off more than I can chew with this lot.. Thanks, bk (UK)
Change from 22 ms to 11 ms sub-protocol see if that works.
you are awesome. Thank you for sharing your knowledge!
Hi Joshua i have been looking at a lot of your videos and they have been really helpful. I have my quad setup for the most part but i am encountering and failsafe that is caused by loss of voltage after arming and advancing the throttles. I have an armattan marmotte, connected to BF i see the 6s pack with the correct voltage. As soon as I arm it the mototrs start the voltage goes to 5v but when i advance the throttles the voltage drops rapidly and i see a failsafe in the setup - Armng disable flag line. Hoping you might be a able to offer some ideas.
this is my first quad build and I am running a hobbywing F4 G3 stack inc 60amp ESC, jeti ex bus radio. rush tank vtx I re soldered the wires for the radio and same issue.
Once again i am hoping you might be able to help. Simon
Hi Joshua!
I've just started to build another new quad. And I have troubles with receiver.
Flashed today 3.5.1 on OmnibusF4
Receiver R9Mini is binded in 1-8 channel TEL. mode.
Port uart1 is selected for Serial-RX.
Receiver setup - Serial-based, SBUS is selected.
Betaflight Serial status - linked. Receiver is green.
Battery is connected.
But on Receiver tab all values are frozen! Nothing is moving
Tried to bind in 9-16 ch mode - the same story
I have same Omnibus F4 on other quad and same R9Mini - everything works fine on betaflight 3.3.x
Do you have an idea?
Something must be different in the wiring or configuration because nothing I csn think of changed in the different BF versions.
Joshua,
Thanks for all of your videos. Unfortunately, none of them have helped. I am new (never gotten my drone off the ground) to the sport and am within a hairs breadth if throwing the whole mess - batteries and all in the nearest trash can. The problem I am having is that I am able to bind my receiver(s) to my transmitter, but I cannot get any response on the receiver tab in beta flight. I have tried two different receivers, Frsky D4R-II and Frsky V8R4-II with my Taranis-Plus. I can get both to bind in both modes, but I am unable to get any response on the transmitter tab. I have a Speedy Bee flight controller which is using:
# version
# Betaflight / SPEEDYBEEF4 (SBF4) 3.5.7 Mar 15 2019 / 22:20:51 (e9130527c) MSP API: 1.40
Any help will be greatly appreciated.
Under the "Mode" section, the "Arm" shows red and disabled. the arm switch is actually controling the flight mode...I have the tinyhawk drone and remote. How should I correct it? Thanks.
is there a reason my sensors never calibrate on initial setup? everything else works except it won't calibrate and says its still calibrating sensors. not to be confused with this issue. but kinda similar
ruclips.net/video/47rNFd7q618/видео.html
I get the same message but when I press arm on the control it does not move to arm in betaflight nor does it recognize my control, but when I press turn off on the control it tells me that it is connected to the Drone but in betaflight it does not recognize my control
thank you so much i got same problem yet and fixed by wacthing your video
Runaway takeoff prevention disabled, Josh, I am dying -- all those hours building-- they all have the same message. I tried to go back and download 3.4 Beta-- was not there. I was able to turn the Prevention from ON to OFF-- but it did not hold to arm. Thanks for your attention- I know you are busy!
Hi, Bud. Same as I said in your last comment: if betaflight won't arm, then what message is the Warning OSD element showing when you try to arm?
Hi Buddy, thanks for the video. It fixed my problem. My drone can arm and fly now.
I was wondering what your favorite strain is? (see this asked to Bot quite often but no idea what they mean!!)
Grandaddy Purp
This fixed my arming problem but when my throttle is all the way down and I arm, the motors start pulsing like I’m slightly moving the throttle. Any help?
JB, is a "high idle trim" on the transmitter enough to keep your quad from arming?
It can be, if you have it active, and the throttle is above your min check value
Yes. THROTTLE flag.
hi from indonesia here,i tried it on mobula 7 hd but still got the arming disable flags: msp and then all of my setting is gone in the betaflight and disconnected from the radio,oh and i put nick burn pid for the mobula 7 hd, any advice would be great Master Bardwell :) ,need to do this for the lockdown time here :) ,Thx
MSP will go away if you go to the Motors tab and enable the "I understand the risks" option. MSP should not appear when you don't plug in USB.
@@JoshuaBardwell thank u for the fast respon tried it again and it works :D
My throttle joystick is slowly raised, but the throttle continues to increase. I checked betaflight, it indicates in arming status flags "THROTTLE MSP". What should I do?
Thanks man. You're the best.
can you tell me why i get cli msp bad rx loss ? my drone wont arm in the arm section on modes it turn red instead of yellow any ideas ?
If you've unplugged from BETAFlight and are sill getting MSP, plug back in and hit disconnect. I just spent 30 minutes diagnosing this.
I think the speedybee app will allow arming while connected to MSP over OTG cable in all configuration tabs (not just motors tab. Props off of course ;-)
Betaflight should absolutely prevent arming when anything is connected via MSP. I'm not sure how the app could override this... maybe by disconnecting after loading the screen? It's possible... but dumb if true.
What about mwosd? It uses msp too.
i just received my receiver and got er bound and guess which status codes i had cli and msp so i got the arm switch working no gps yet but thank you joshua man all your vids and messages helped so much how ever now when i arm the props start spinning so need to get that sorted lol thx
hello JB, i am not able to arm it even after doing what you have said, i am trying to arm when it showed CLI MSP, then i did what you said to do, but still it wont arm, and when i connect battery the motors start to spin, without recieving any signal, can you please help me to solve the issue
Thank you
Hallo joshua..I have the same problem like this I'm checking the cli the status CLI is
( Arming disable flags: CLI)
on osd warning I see his battery flashing
So What am I supposed to do?
The FC is restarting every couple of seconds but only when the camera is plugged in with 7 beeps(with a smoke stopper). When the camera is not plugged in, it is ready to fly. I pulled another camera from one of my other quads that I know works and it resulted in the same thing, so it shouldn't be the camera. I looked over the wiring and everything looks ok visually. I also checked with a multimeter and the camera is getting the right power.
Arming disable flags: RXLOSS CLI MSP. I followed the video and I'm still having difficulty, what am I missing?
This is a very tough one. If the FC reboots when the camera is plugged in, but the camera is not at fault, it's a real mystery what else it could be. My next guess is that the voltage regulator on the FC is damaged and the camera is drawing enough current to overload it. Replacing the FC would be the fix.
If the camera is powered from vBat then I'm truly at a loss.
@@JoshuaBardwell I was hoping that wasn't the case, but looks like I'm in for another FC, I appreciate the reply to help confirm my suspicion.
Hi Joshua.
I have noted that if I connect the FC to the USB and launch the BF configurator, then feed up the ESCs with a LiPo (may be to test the motors) and then I unplug the USB cable, the quad won't arm.
I think that it happens because the LiPo is keeping the FC alive with the MSP flag still active. In fact, if I detach the LiPo and reattach it again, the quad will arm with no problems at all.
Can it be a kinda of bug in the BF configurator?
Turn on the Warning OSD element and look and see what flag is active. That is the best way to answer.
Hey Josh I'm having problems with my quad it's saying calib is the arming flag but it arms whilst I'm in th configurator but the minute I unplug a the usb it does not arm and it's not arming on just my new lipos for some reason as it works absolutely fine on my old ones
Fantastic, JB! Thanks a lot! 😃
i have a msp arming disable flag. ıt doesn't work by unplugging the usb. every time I disarm then i need to connect to the Betaflight and check the box I understand the risk under motors tab then it arms. but I don't want to do it every time i disarm. ıs there any fix for that. thanks
Thank you for pointing me this video, I followed his instructions (MSP) lost, but everything remains the same as the old motor test still does not spin and info (Arming Deaktivert aufgrund). I turn on the AUX1 switch, then the motor has 3 music (Te te ti) but the motor does not spin.
I want to reiterate my chip is the MAMBA F405 Mk2 4in1 ESC Konfiguration 4.1.4, very expecting him indications.
Did you find any solutions?
I have an issue, trying to set up a tricopter and my motors run continuously when not armed, about half throttle. Also, ESCs wont initialize when not plugged into USB. And the servo is backward, but that's another issue.
Wow it was so easy! You helped me out a lot.....Thanks!
Great video. Love the shirt!
Your expertise is second to none and your videos are very appreciated. My problem. I've got a Meteor 65. Using BF 3.5.7. Xmitter is a Taranis X-Lite. Set-up aux 1 for arming/disarming. I never use the CLI command until now. Problem, quad won't arm. In the CLI I get the "CLI MSP" message. I've done all you've explained in the video to no avail? In BF I activated the motors and get all the results you've covered. In 'MODES' when I arm them box on the left says ARM (Disabled) and turns RED. Disconnected from BF connect the batt and can't ARM. Any ideas..........I'm completely lost.
In the OSD tab turn on the Warnings OSD element. On 4.0 and newer it's on by default. On 3.5 I think it exists but it's not on by default. When you go to arm it will give whatever status code is preventing arming. Something must be coming up after you disconnect from USB.
@@JoshuaBardwell Here's the dirt. IT's WORKING!! Here's what I did:
- OSD tab was already checked? Reviewed OSD checks & made some minor changes as to what I wanted to see.
- Adjusted ALL Recvr travels to min 1000 and max 2000, not just throttle.
- In CLI got new message 'throttle CLI'. Thr in recvr was 1010, readjusted to min 996 couldn't go to 990.
- CLI now states 'CLI MSP'. hmmmmmm
- Did the motor thing as you suggested then in the CLI it displayed 'cli'..hmmmmmm
- Unplugged USB, turned on the TX, plugged in the battery, armed & motors spun up??
- Plugged USB, went back to BF Config screen & activated 'Motor Stop' and saved.
- Reviewed all the different tabs leaving defaults as is ensured DShot 300 was still selected, Rec'r set to SPI RX support - FRSKY_X.
- Made a back-up of everything.
- Unplugged USB, turned on Tx, put batt on, and low & behold she behaves as a quad should.
Made an observation though. Connect the 65 in BF and just leave it on the 'setup' screen. Look at the model, after a few seconds it gives a little 'twitch' & continues doing it every few seconds?? Could that be related to what Nick Burns was taking about?
Anyway, gotta fly this sucker. Couldn't have done it without you. Thank you ever so much Joshua. You dedication to the hobby, effort in producing, time uploading all the videos, and especially sharing all the interesting and entertaining videos is very much appreciated by, and I'm sure I'm speaking for all of us enthusiasts, me.
Very best holidays, prosperity in the New Year and best of health.
@@JoshuaBardwell Just supported you on Patreon as a 'thanks'. Wish you well in your new endeavors. Pierre
you are awesome bro ... you helped me lot, thanks a lot (love from india)
Tonight I noticed I could arm whilst connected to usb, I thought I was going crazy with arming flags and of course your useful series pointing to the BF flashing codes was really useful. But how can I arm the quad with usb and BF connected, I don't have motors connected so haven't been near the motor overide option shown in this video?
I checked using CLI 'status' and noticed no MSP flag, just CLI listed ...bug?
You are probably on an older version of betaflight before they implemented teh MSP flag.
Checked across multiple versions of BF from 3.5.1 down to 3.2.0, MSP flag isn't always present and FC WILL arm if USB is connected.
My drone is just flying the went to change the battery turned it on and suddenly my fc is blinking red it says arm but motors not spinning.
Hi my Serial Link Icon in the Configurator is sometimes blinking, sometimes not. I use a Multiplex Reciever. What does the blinking icon says. No arming flags in the status only msp and cli. Sometimes i cant arm, i'm confused
With Jeti Reciever no problem at all...
Well definitely have to have a look at the rest of the series as I was having issues with that on my Mantis 85 and when I went to find out why, got the notification with status that it was the CLI. Is there a way to know what all the warning flags are? Perhaps that's one of your video's but I know one I can ignore now, thanks again.
LOL go watch the intro video like I said :-)
I spent like 15 minutes one day trying to figure out what MSP meant. Guess now I know.
I definitely learned something today!
I have problem CMs_MENU any idea? I am new
Hi. What about the situation when you want to have MSP telemetry or/and the model is controlled through MSP (RX_MSP) ?
I would think the use of MSP telemetry or RX would not prevent arming since those functions are intended for use in flight. Only MSP configuration would prevent arming. But I've never used MSP telemetry or RX to be honest, and I don't know of any FC or receiver that uses them.
Much appreciated, sir!
Spent all night trying to get my new tinyhawkfreestyle 2 to arm, Iwas getting rxloss cli so I check out your playlist and give myself a headache lol. In my case it was my taranis playing up pitch roll raw throttle was all missed up, I don't understand what is going on with my taranis but when I try to create a new model I get a message saying id used on a different model witch means I can't choose plane multi ect . I have got round this but I have to go to the mixer page and edit because I can see pitch engine or something next to Ail Ele Thr Rud. Does any one know what's going on here sd card in the taranis maybe, thanks
my tinyhawk canot arming and with this status in BF ...
I2C Errors: 0
Arming disable flags: RXLOSS CALIB CLI MSP
how to fixed?
I am currently dealing with a nogyro warning on an AIO from board from a QX 105 Bat
NOGYRO typically means that the FC is toast. It could also mean you flashed the wrong firmware to the FC but you would know if you had flashed it recently.
@@JoshuaBardwell Yeah, just recently flashed 3.5 on the board. No chance to reinstall? I found that if I went into CLI, did a get gyro and then reboot, it would arm again. The only oddity was that the CPU was at 2% while it wasn't responding
So let me get this straight.The simple flip of a switch starts the motors??or am I missing something?.If this is true i see many people getting hurt..Bring back the throttle bottom left arm...
If you are concerned about flipping the switch use the prearm mode, which requires two simultaneous switch flips to arm. Using the sticks to arm and disarm doesn't work for freestyle and racing drones where you need to use yaw at the same time that you are at zero throttle. With the stick disarm method, I can't do an inverted yaw spin without disarming. And switch disarming is faster and more certain than stick disarming. With racing and freestyle drones, you often need to disarm immediately to avoid damage to the quad or to property. Having to input a stick command is slower.
@@JoshuaBardwell Makes sense in the race acro environment.would be nice to have a simple option/toggle or something like that to use throttle stick like years ago.
I think you still can setup throttle arm on aux switches?
Hi Joshua, I've got the MSP warning still coming up even when the quad is completely disconnected from the usb cable. this has only started happening since I flashed from 3.4.0 to 3.5.4 earlier today. Im not sure if it is related (as I'm also running from a new laptop) but BF is having loads of trouble connecting to the quad when it is plugged in - i have to keep unplugging and replugging in the cable, and maybe 1 in 10 tries, it will connect. FC is a Matek F405-OSD. Im really hoping its not an FC issue. Is there any way to disable the MSP flag so i can at least fly? cheers
just following on from my last post - I tried downgrading back to 3.4.1 but the problem persists. Also, when i said BF was having trouble connecting - its a bit stranger than that - it seems to connect, and the configurator reads that it is a matek FC and what BF version is on it, but then times out waiting for the config to read. I'm thinking more and more that its got to be the FC hardware itself is the issue.
Sounds like your USB cable is damaged. Try different USB cables to at least rule it out.
@@bangthumper1195 have tried a bunch of different cables. but that wouldnt explain why the quad thinks its connected when its not even plugged in
Ben D you’re right it wouldn’t. You may have already tried it but do a clean install. Reinstall firmware. Good luck!
that helped me a lot great video :)
Always good content!