How on Earth do you know what problem I am going to have before I have them, and them fix them so I can stay flying? You sir are the most helpful person I know.
I always learn something when i view your superb chanel Mr Bardwell,thank you for giving up your time to create all of your video's (aka vlogs),as being new to the hobby 6 months ago,your chanel,and Mr Davis's chanel have been my go to for help. Living in Australia there are a few stores but the knowledge is limited. Thank you again mate.👍
Thanks for the great on point vids! I set all my quads to Pt1 and turned off the two notch filters. I have to say I have never had such performance. 3.2 is incredible. Keep me coming 👍
Joshua Bardwell yes! Not to mention getting the antigravity up at 3.5 and d and set point just where I like it. I have never had anything fly this awesome and it’s thanks to the knowledge I got from your vids. I def learned something:) thanks again!
More great info, thanks! Over the course of watching your videos I've really come to appreciate your excellent attention to detail, and technical level of explanation.
MR. BARDWELL , sir, THANK GOD people like you exist in this addicting hobby, I’m getting absolutely no help from the hobby shop that sold me this expensive, but, worth every penny stuff. Therapist are way more expensive, lol. Your right , I kept fooling with settings, following you moves of course, when BAM, it armed. Just built my first 4 in , and I think I’ve found my favorite bird. THANK YOU again bro, I owe you a six pack!
This helped me out so much! literally in minutes, I had it figured out. I changed my low and high throttle in the receivers tab of betaflight... Don't know why I did it, but there you have it. Thanks again, you're the best!
You are awesome man, I updated my firmware on my flight controller from 3.2 to 3.5 and uploaded my old setup over and then it wouldn't arm. Thanks to you it's arming. Thank you!!
Thanks ever so much for your efforts to help us navigate the hurdles of this ever expanding and more intergrated and complicated Hobby. Was watching Makers Muse Pod cast about the new Prusa 3 plus and that community is the same style of open source and The improvements that the inventor has incoporated in the latest version to help users sort out 3D printing problems is worth a look Regards from downunder
Again.... I must say. Thank you! A very helpful videos for a newbie to drones. Im use to RC Cars and boats with bind and play. What a new world I have been introduced to.
Just a heads up for everyone who wants to see the arming disabled flags in their OSD as Joshua suggested at 7:39 - in current versions of Betaflight (3.4 and later) you'll have to enable "Warnings" in the OSD elements selection on the left AND select "Arming Disabled" from the warnings selection on the right side. Also I recommend placing the warnings OSD element at the bottom of the screen, so that when you also have warnings like critical battery enabled, it won't just pop up in the center and block your view...
I went looking for this topic due to a current problem I am having, or at least was. You have been my go to foe quad info for the last year or so and I always seem to find it in your videos. I really wish I could help you out on Patreon Thank you for all you do for us.
Hey Joshua, I dont know if this is the right place to ask my question, but its kinda my last Hope: I can't arm my quad because of arming flag "Calib" - When powered by battery. When Quad is powered by USB, then calibration finishes right after getting powered on, as usual (3 beeps). I already read many articles on github etc and watch many of you videos for this topic. But all hints, like e.g. a higher term of "moron_threshold" didnt work either (Set it to 200). I also calibrated the acc multiple times (with success) But it seems the Gyro just doesnt "Start" when first powered by battery (debug_mode = Gyro -> No movements in "Sensor Tab" on Gyro or debug_3. When powered by USB, there i can see the Gyro correctly working. Additionaly, When Quad is powered by USB only, my voltage drops. Even my Transmitter warns me of that and keeps on alerting. I have to disconnect modules like VTx, to get the voltage normal (until Tx stops warning) I wonder why modules like VTx are powered when connected via USB (maybe it all sticks together?) Pleeaase, can you tell me what else I can check to finally get my Gyro calibrated for arming? Omnibus F4 AIO V5 (Not banggood), RAW-Jumper Set to 5v (VTx, Cam) Hobbywing 4in1 XRotor 40A ESC. FC is powered from ESC by using 8pin Header Connection. Both Parts are new. Thanks a lot in advance! Greetings
If anyone need the infos to what happened: It was a Bad FC - even it was brand new. I mounted another FC with exact the same wiring and components - Works perfectly 😁
Thanks for decoding the binary for those using F1 and F3 boards. Probably best for us all to shift to F4 boards like the Kakute F4. Kakute = in this way Also, here's another: Kakute = Rings made of iron or steel that were sometimes worn by the ninja, and favored by the kunoichi, having one to four metal spikes protruding from it. The spikes were sometimes dipped in poison. Kakute were usually worn on the middle finger with the spikes hidden inside the hand, and then used to attack when the enemy least expected. The spikes were also excellent for holding onto an opponent, striking across the face, choking, and sometimes climbing as well. Some kakute had a tab with a hole, that was used for hojojutsu techniques. In this sense, the hojo (rope) could not be easily pulled away from the hands of the ninja or kunoichi, since it was tied to the kakute ring on their finger.
Happened to me once, for 2 days...you get that crazy beep-beep beep-beep bee-beep. Three bee-beeps, but no arm. Problem for me was my MIN THROTTLE was set too low. Solution: SET MIN. THROTTLE about 20 - 50 points above what the receiver tab in BF detects from your receiver -when its at its lowest. Actually the problem happened on one other occasion , MUST SET MIN THROTTLE JUST ABOVE...usually always between 1000 - 1100.
Both. You want to adjust the radio outputs to be as close to 1000-2000 and 1500 center stick as possible. Once that is correct you want to set the min throttle in the configuration tab like Brian says above. ^
Thank you for the discription of your problem, I just had the same thing on my tiny KingKong Flyegg. After I adjusted the MIN THROTTLE in Betaflight just like you said, the Arming was allowed for some magicaly reason ;). I don't know how many days more it would have taken to make my quad airbourne if I hadn't seen your comment. It helped me out allot...
Also you want to make sure your in the right protocol (DSHOT, MULTISHOT Etc.) for your flight controller cause you can get a heart throttle message if your in the wrong protocol for your esc.
help me, yesterday it flew safely and I tried osd settings but there was something strange in the rx loss cli status but the rx was already on and there was a remote response but I tried it on the reciver tab there wasn't any movement
I have a RXLOSS CLI and I correctly binded my receiver. My quad will still not arm and I have the red slow blinking light. I'm not sure what to do. Could it be a problem with my board? please help thank you
Even if the "gyro_cal_on_first_arm" is enabled the initial calibration on power up still occurs. There will just be one additional before the first arming when presumably the quad is sitting still.
Hi Joshua, I have an Eachine Qx65 that I was able to flash with 4.0 betaflight. I Omnibus. It arms and everything, all the values on betaflight are ok in reciever tab. The osd displays it going from armed to disarmed. But the motors do not turn on. Nothing I do seems to work any ideas?
Tried everything short of unslodering and resoldering the crossfire nano but I still can't get rid of the RXLoss and CLI codes to arm. Everything is green (crossfire nano, crossfire unit on tx16s) but still no stick controls in Betaflight.
I just fixed it! When i unbricked my Tx and reset up a model, i didn't set the channel range in model setup to 1-8. Mine was set to 1-16 and I learned that OTX can be finicky with this.
Hi Joshua .. I was having an issue with Arming one of my Quads after uploading the new Betaflight so I watched your two video’s on Why it Won’t Arm .. I followed all of your suggestions & the CLI was still giving me a Throttle Warning ... I went into Wiki to look for causes & wasn’t successful .. One thing I didn’t check & you didn’t mention is when there is an Arming Switch Set .. I forgot to go into Special Functions on my Taranis & program a Negative Variance for that Switch to Prevent Activation of the Throttle along with What needs to happen when Activated ... After Programing the Switch in Special Functions the Quad Armed & All is Good .. I’m not sure if anybody else had mentioned this step or not but maybe it will Help somebody in the Future .. As Always Enjoy Your Video’s & Wouldn’t be in this Hobby Without your Guidance ..
Hello Joshua, I’m not sure if this could apply to my quad. I bought the arfun95 about a month ago, flashed b/f3.2 straight away. I notice sumtimes it wouldn’t arm at all. But the problem is that if it arms successfully, I can fly about, but when attempting punchouts/ flips n rolls, it seems to disarm n fall to the ground!! I’ve changed the battery connector to xt30 and use 2s bolts instead of the stock battery, and the problem actually seems worse! I’m pretty sure it’s disarming rather than suffering the famous brown outs, for this model. Also have massive drift issues, do you think I’ve bought a faulty quad? Or am I not set up in betaflight correctly? Bought from GearBest and they don’t even respond to me after at least 10 emails!! Worst £115 I ever spent so far on this hobby unfortunately....
your old vid helped me. Mine was b/c 100% cpu. I was trying to run 8k/8k with dynamic filter on f3 nano omnibus, no bueno. Also, you have to set the dshot beep tone in the cli for the motor beeper to work. thanks for your vids
To add to this. Since Im new to this hobby and Ive been struggling with the Arm Flags. Its been 1 week since Ive been eagerly trying to figure out how to remove the "No valid receiver signal detected" RX LOSS CLI MSP. Tried using a different receiver to see if my a8s got problems, changed its ufL antenna, but still not getting any remedy. One thing I forgot is to set an arm switch on my FSi6s transmitter. Problem solved. Here is my specs. Tx FlySky fsi6s Rx fs a8s Hglrc fd 413 vtx stack Im using speedybee.
Hi Joshua.I just flashed with betaflight 3.2 and dshot 600 and racerstar lites 30a escs and an issue occured.I used dshot with betaflight 3.1.7 and everything worked fine.Although i tries downgrading and the same happens now.My transmitter is a spektrum dx8 and i fly with a satellite reciever.FC Betaflight f4 from banggood.When my quad is plugged at my laptop and the battery is on i can arm it, disarm it and it works great.As soon as i unplug the usb i can arm the quad it works and after 10-15 seconds it stops, the fc blinks the satellite blinks and escs beeping strange tones.I would apreciate if you could help!Thank you in advance.(Sorry for my bad English)
no worries basher united is selling me his old futaba dlsr . fly DMV is looking out for all pilots thanks for you time and help. looking forward to meeting you with cricket FPV an botgrinder this year
Hi Mr Bardwell been head scratching for days now so its cap in hand time as we say here ! omnibus f4 v3 ? banggood, used many times in quad builds & always worked fine installing this one in 690 swallow all set up as your vid. all lights fine & esc noises sound like shes armed but not arming tried switch slider moves but not going green cli says nav cli ? in config. nav is safe is X all rest ticked gps is not turned on either ? i am going to put in a gps after i get the arming sorted not sure whats next can you help please as im going nuts ! many thanks, Kevin.
I was having problems getting my quad to arm, I've followed your guides on the two switch arming and this one. After finally getting the quad to arm my motors went crazy and no matter how I moved the gimbles could not get control over the motors. I also couldnt get it to disarm with the switches, I had to power down the transmitter. Any help on what I should do to calm the motors and disarming would be greatly appreciated.
I have "warnings" and "disarmed" selected on an F4 board and the flags show up in the OSD Josh. Not sure which one is making the flags pop up..... maybe ill try disabling one and find out which one it is so everyone will know
THROTTLE, ANGLE, and CLI are three separate codes. Each is in the table linked here. github.com/betaflight/betaflight/wiki/Arming-Sequence-&-Safety ANGLE means the quad is not level. Calibrate the accelerometer or disable this protection entirely by typing "set small_angle=180" then hit enter then type "save" then hit enter in the CLI. THROTTLE means the throttle is too high. If the throttle is all the way down, you may need to adjust your endpoints as shown here: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-PCLxyurZsD0.html
Help: My aircraft does not arm, status showed "RXLoss". By BF definition, it means "receiver is either faulty or has no link to the transmitter". But the reality is, my transmitter is well bonded to the receiver, and in BF "receiver" and "modes" pages it corresponds to all channels movements and arm/disarm switch correctly and responsively. However, once outside of BF, the aircraft has no reaction to the transmitter at all. I believe that BF "receiver" and "modes" pages showed my transmitter and receiver both working properly, at the same time it also showed (via "status") "RXLoss CLI" message. What the heck is the real problem here? Simply concluding "receiver is either faulty or has no link to the transmitter" is not convincing. Please help (BTW, both aircraft and transmitter/receiver are new) and many thanks.
If you see channels moving in the receiver tab, then I agree you should not see RXLOSS. My guess is that when you unplug from the computer, the receiver stops talking to the FC. That is pretty weird if true, but that is the only way I can think to explain it.
Pretty sure it's the "warnings" label in the OSD that gives you the reason for not arming. For some reason one of my Matek boards occassionally get "nogryroro " and t needs to be power cycled and that comes up in the place I put warnings.
It means the quad powered on with the arm switch in the "armed" position. It needs to switch to "disarmed" position then back to "armed" before the quad will arm. Most likely you need to check the Modes tab and see that the arming mode is configured correctly.
It's arming finally! But now after I hit mid throttle it starts accelerating by itself and the only way to stop it is by disarming. Throttle settings seem normal.
Thanks for the tip. I was able to see in the osd warnings “ bad Rx “. Yet it’s reading my sticks in the receiver page in Betaflight. Can’t get my new babyhawk r to arm. It makes a light beep when I try to arm, and nothing. What can this be ? Can use a little help :( thank you.
Hi Joshua, you are one of the best in this field, I am a beginner on FPV, just starting to learn a lot of information. At the same time even I use camera drones, FPV is a new way to piloting drones. To start practicing flying I bought a tinyhawk 2 bundle 3 weeks ago and I lost the drone flying outside of home , it went to the skies and never found it !!. Having the controller and googles I thought I will be easy to buy a 2nd tinyhawk 2 and use the previous bundle. But I was wrong and never flew out of the box!! Does it make sense? Do I have to use betaflight with a new drone? Should not be flying out of the box?
Dear Joshua, I have seen so much of your vids and want to thank you for suporting us as drone pilots! You are doing a great job at it also. Now I have got a problem that i couldn't solve due to your video's.... I hope you can answer me ASAP. This message i am getting when i type Status in the CLI command line: Arming disable flags: 0x820 ...... Can you tell me or help me with finding a sollution for this! I realy would like to go and flying again but i just cant get my quad to arm..... Kind regards, Dennis C.
Hi Joshua, Well I DID LEARN SOMETHING TODAY FROM YOU!!!! I am so thankfull for your answer! When i watched your vid, I didn't take the time to see the whole video, sorry for that. But the answer was there! I figured out that i could convert it to binaries and the gave me the answer and i solved it in my transmitter and it armed just fine! Man YOU ARE REALLY ONE OF THE BEST ON RU-vid! Thanks and go on doing what you are doing! Kind regards, Dennis C.
At this point is it wise to invest in a F3 controller? You said in one of your videos that the Pid Loops for Betaflight 3.2 could not go over 4k/4k in the F3 anymore (that may have been with the new Dynamic Filter on). You also said here that the code space is so "tight" on the F3 that for some error codes they output the actual error codes like "0x400, for example" rather that a string "No RX". I would like to hear your comments about this.
OK so my quad wont arm did status it says CLI MSP says wont arm cause I have betaflight connected ???? I have alway been able to arm in betaflight before what 's up with this..If I disconnect from betaflight is arms just fine
Betaflight added a safety feature where it refuses to arm when it's connected to the configurator. You can override this by going to the Motors tab and enabling the "i understand the risks props are off" option.
Hi Josua Bardwell finally fixed my arming problem thanks for the help. Although now I am wondering about something else. Whenever i reach full throttle my fatsharks picture freezes for like half a second. This also sometimes happens randomly and I don't know why. thanks for the help
+Davis Baldwin i really don't know what could cause your picture to freeze up! Wow, that's weird. Since it happens at full throttle probably it is related to vibration. So I would look at the physical wiring and plugs between the camera and vTX.
Ok so it says Rx loss. the green light says it's bound set up a model and in beta flight under receiver nothing moves and in modes it does noting when I flip the switches. Any suggestions?
The FC is not seeing the signal from the receiver. So either it's wired up wrong or its' configured wrong. ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-ZpU6-JY6fnk.html
Thank you so much... something you said in that vid made me take a second look there was a bridge pad that needed for hooking up frsky is the signal inversion. It was supposed to be set up for frsky from the factory but wasn't . Thanks again I got it up and running now
Help! I have this: Arming disable flags: THROTTLE CLI ARMSWITCH. so i'm new to all of this. i was able to fly my quad, but it's not tuned well -- very bad oscillations when i make quick stick movements (yaw, roll, and pitch) on my 450 size quad with 10" props (i need help with this really bad). i'm able to see on betaflight that all is well (i mean that my radio is communicating with my dragonlink receiver, and to the F4 AIO board), but after changing EPA on my Hitec radio, and changing it back to try to fix the problem, it won't arm anymore. Note: i see a flashing blue light on my F4 AIO board.
Joshua can you please point me to a guide on how to get a F3evo board to keep the reciever as SBUS when UART2 or UART3 is checked. I've dug all over Google and RU-vid and no luck. It's on a Fatbee 90 and same on Qx90. ice followed several videos step by step nothing works.
If you enable serial RX on the UART, then save, then go to Configuration and select serial receiver and SBUS, then save... then that's how I would do it. If it's refusing to save, I don't know why. Have you got anything else at all active on the UART? Maybe there is a conflict. Serial RX must be alone on the UART.
When I arm the motors don’t spin until I increase the throttle. I played with the numbers for the throttle putting them over and under min check. So there will either be too much throttle to arm, or so little that I have to raise the throttle stick. What should I do?
Have you enabled the "spin motors when armed" option in the Configuration tab? If you have disabled that options, the motors won't spin unti lyou raise the throttle.
Turn on the Warning OSD element in the osd tab. When you flip the arm switch see what it says. If there is an arming code it will tell you. If there is no arming code and the drone doesn't arm, it means the FC doesn't think tor Mode is going active.
I see in 3.2 release notes to do a backup of your old version then once flashed to 3.2 to paste your settings in CLI and then reset to default settings. I haven't seen anyone elaborate on this, is this a necessary step? I have 2 lux V2 FC I flashed without doing it and all is good. Diatone Fury F4 though keeps booting up in bind mode on spectrum receiver. Receiver tab is all crazy too. Could this be an example of corrupted config? Tried reflashing 3.1.7 and still same. Also I didn't do a backup. Sorry Joshua I know this is completely off topic, any help would be greatly appreciated
Yes it sounds like a corrupted config. Frankly, coming from 3.1.7 to 3.2, I would definitely back up the config for reference, but I would probably just re-build the config manually rather than pasting in the lines.
I typed status in CLI but the “Arming disabled flags” does not show up, my Betaflight version is 10.2.0 and the FC I have is Sp racing f3, can someone help me?
I think you have an older version of betaflight. 10.2.0 is the configurator verson not the firmware version. Go to the CLI and type "version" to see the firmware version.
Great video, but although RX LOSS is noted, and the response is: Receiver is faulty or not linked to transmitter, my receiver is not faulty and is bound to my transmitter. I can see my stick action movements in my taranis. I had just come back from flying and because I had noted some strange throttle action, I opened BF 3.2.1 to see if I could figure it out. The throttle would start to spike on it's own so I decided to reflash to 3.3 and that's when my receiver tab and modes tab stopped functioning. Now what? Your help is always appreciated.
Most likely when you re-flashed you erased the configuration and now betaflight doesn't know where to find your receiver or what protocol it is. In the Ports tab, you need to enable serial RX on the correct UART to which the receiver is soldered. In the Configuration tab, you need to set the receiver type to "serial" and the serial receiver provider to the correct one for your receiver (such as SBUS, SPEKTRUM, etc.)
I did all my arming and so forth. I use Futaba 8J. I cannot get the props to stop spinning at the lowest point on my throttle. I used end point and I still could not get a setting that will stop the props when the throttle is at its lowest point. Any idea
You are wanting the option "motor stop". This is in the configuration tab "stop motors when throttle low" or something like that. If air mode is enabled the motors will always spin when the quad is armed, regardless of throttle position.
Help needed, I am unable to arm. After I enter Status in CLI the last line says Arming flag throttle CLI I am still new in this hobby so any help is appreciated
Throttle must be below the stick min threshold to arm. Go to the receiver tab and adjust your transmitter channel endpoints so that the channels go to 1000 at the bottom and 2000 at the top.
Joshua Bardwell That was exactly why I couldn't arm. Big Thank You !! I can't begin to count how many of your videos I have used to crawl through this learning process. Again, thank you for all of your knowledge and effort.
I have a Bardwell f4 in two quads now. This is within a week. One of my quads came with it in and another I put in. In both cases, they won’t arm. I have done everything as far as the stock values and the they both say the same thing🤦♂️. I’m frustrated.
The CLI parameter "min_check", which is also shown in the GUI as "stick low threshold", tells the FC if the throttle is all the way down. So I am going to guess you set that parameter to 1000, which means the throttle must be less than 1000 to arm. Which won't happen. Set "stick low threshold" to 1010.
So first off, I love your F4 board. But I'm having some Sbus issues with my third one. I can't get "rxloss" to go away In my cli status or my receiver tab to respond but everything is powered and beeps are correct. And also have telemetry with my taranis. I've tried 2 different working receivers so I'm really lost here haha, any clues?
This is helpful, I’ve been having this problem for a while. My quad keeps beeping at me when I try and arm, and I end up having to disconnect and reconnect a bunch of times
I checked osd an see no warnings in the osd. radio link contacted me and said that the switch isn't issuing instructions and gave me a link for another controller an I guess referred to stick arming
i am able to test the motors out on beta flight but i am unable to see my battery voltage on beta flight . also my quad wont arm and when i type in status it shows RX LOSS CLI how do i fix either issue because you only showed how to identify them??
RX LOSS means your FC is not seeing signal from your receiver. Troubleshooting this is pretty open-ended. It depends a lot on what type of receiver you have and what FC you have. If you email me your details I will see if I can help.
First off Mr. Bardwell, I thank you for plethora of knowledge and the willingness to share it. The disable arming flags i am receiving on my 220 build, with spracing f3 fc, and frsky D4-II receiver, using a Jumper T8SG radio, and betaflight 3.3, Was 17, and 9. After calibrating my accelerometer, and checking all the tabs in betaflight and all looks well, i look at the first tab "set up" and notice theres just the 9, as a flag. Good i think to myself, only one to go now. So i look in wiki and see what that 9 code stands for. When i type "status" in the cli, the last prompt states disable arming: breachbooted or breachboot. (Sorry currently not in front of my quad) Any sugestions as to what i am doing wrong would be greatly appreciated, as is your time. By the way, whenever im asked "dude! Where'd you learn how to build these or do all this hi tech gaget stuff?" I almost always reply, "Joshua Bardwell, he's on RU-vid. Thats all i gotta say! " Hope for some resolution, for this is driving this vet crazy. Thanks again.
Hi Joshua, I got a omnibus F7 V2 board and it takes around a minute to arm. In the OSD it is indicated CALIB or sensor calibration is on going. I am running BF3.3. With ICM20608 gyro running at 16k/8k and dshot1200. I tried 8K/8K still sensor calib still takes very long time which means arming also takes a very long time other standard. I got other omnibus F7 not the V2 same configuration as my V2 board but this one runs on BF3.2.1. Is it the firmware problem?
+Romel Mendoza hard to say. I don't know if there is an issue with Betaflight or the board or what. F7 are not yet fully supported in Betaflight so a bug is possible.
Alot of newer stuff in betaflight 3.2. I just left alot of stuff OFF that wasn't talked about in your other betaflight video when I was setting up my wizard x220 and flashed it with BF 3.2, considering I dont have most of the options available anyways. Mostly was just alot of "beeper" tabs added and such..stuff was enabled by default but I turned it off in the beeper section, and some GPS stuff..
Hello, Paul here from Australia, great vids! I have a question, if anyone would know, you should.haha. My FC is locked in Cleanfight CLI mode only, Brushed 1s FC. What commands through CLI do I need to type to change arm command from right/down yaw to ch5 on AUX? Hopefully this is a good challenge for you. Many thanks Paul, n keep up the vids, awesome!!!!!!!!!
Have they changed the DFU or boot command in one of the 3.2 versions? I'm not able to use DFU on my 3.2 quad but it works fine on my 3.1 quad, I just don't remember which RC it is, will be an early one.
Thanks for the reply, it just sits there saying "rebooting" no matter how long I leave it when I use BL. What command is that? I've never seen it before.
Great info josh!¡ you are the first one providing the info on youtube at least, or let me say leaving it easy to us ;) By the way i got a question, is there any way to turn off some of the esc sounds? I got game of thrones esc beep at start, but a second after , just makes the typical beep beep beep bi ri rip, but it is too looud and when i got my fire stopper connected in between the batery and the copter just sucks all the juice and makes the bulb briiiggt... so i was thinking that maybe we got an option in the cli, for choosing when to beep the esc alone, like the options we have in the configuration tab for the normal beeper , i know the blheli comm peotocol with betaflight its not as advanced as the kiss, but maybe there is a way already ( changing the sound level of the beacon of the esc, wont help, as you know the music played from the esc's depends ond the volume that you set it and i dont want to silence it . Thanks a .milkion for your hard work !!
Joshua Bardwell its been 2 months now since i habe not been in the blheli configurator, but... isnt that the volume adjustment that will change the 'custom' song of the esc at startup?
In the betaflight configurator I have gotten my Cli to display no problems for arming (besides CLI) and it still won’t spin the motors. Do you think the problem is with my soldering connections?
In the Motors tab, raise the slider and see if the motor spins. TAKE YOUR PROPS OFF FIRST. If the motor spins from there, the ESC is fine. If it doesn't, then somewhere between your FC and your motor, there is a problem.
Joshua Bardwell OMG I am such a knuckle head!! I don’t have signal wires on my ESCs!!! Thank you so much for the help. It’s cool to be talking to you for help!
Just got my diatone gt2. Installed receiver but I get nothing when I move gimbals. Is this because I’m having an arming issue? I hadn’t thought of that, but after seeing this it makes sense. I’m going to see if I have the arm toggle engaged first and move forward from there.🍻
HYEonDEATHROW - The 'Receiver' panel on BetaFlight configurator software, showing horizontal colored lines representing your radio channels. -> It doesn't matter if your quad is armed or not, it always shows what input the flight controller is receiving from the receiver. If you see no channel moving on screen while giving stick input, then no correct receiver input reaching your flight controller. If you're sure Tx and rx bind OK, then the most common reasons are misconfiguration of uart/Rx port/protocole. Sure enough Joshua has vidéo on this ;-)
Thanks Joshua, your info helped me narrow it down a bit, I finally got the motors to arm and spin , but they seem to start up at an unsafe speed with a nasty noisy odd vibration coming from the motors, Im scared something is going to burn up if i keep arming them. Not sure what it could be, yet when i just plug in the battery to the quad and go to the motors tab and use the slider to spin them up, they are nice and smooth. what could it be ? and some FYI, in betaflight 3.4, in the setup Tab when quad is connected via USB, the Info Square on the right of the page shows the same status input you used in the CLI tab as to why the quad wont arm, shows the Beep Codes to search in the Github link you provided.
If you are using Dshot, and assuming that the idle speed is at the default of 4.5%, then the motor speed is most likely normal. If you are using oneshot or multishot, then you have to manually calibrate the ESC endpoints and set the motor idle speed. This is why I recommend you use dshot--to avoid this complication. This video may address the question of why the motors speed up: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-xBaefeQtA1c.html
Yes Im using Dshot, but the motors arent spinning up, they are at a constant speed, they just sound crunchy and alot more vibration when they start up. But I guess i will try to fly it as is then
