I'm fairly certain you can enable the "Motor Diagnostics" OSD element and, using only bidirectional dshot, display for each motor the level commanded or an "S" if stalled. It won't pop up all cool like that warning but it's always there and helpful if you know how to use it.
I tried it last night and it works! Simply check the Motor Diagnostics box in the OSD and you get a box with "SSSS" indicating which motor is stalled. In normal operation it shows "- - - - "
I just took a quick look in the code and the value is the RPM threshold below which the warning will be shown. I also noticed that the warning is supposed to work both with ESC telemetry or bidirectional DSHOT, so not sure what is going on there. I don't want to post the link here because youtube tends to hide comments that post links, but the relevant code is in src/main/osd/osd_warnings.c#L285 (for ESC telemetry) and src/main/osd/osd_warnings.c#L340-L342 (for bidirectional DSHOT) Great video as always Joshua
Happened to me today. Was on the 3rd flight of an Apex 3" build, was flying beautifully and smooth with an JHEMCU AIO 45A, Ant motors 1408/3800kv, 4s, and clipped a tree branch. No problem as I pretty much knew where it went down. Spent 15 mins looking for it and couldn't see it. I knew I was close so I armed and disarmed quickly twice to hear a spin, but heard a 'popping' sound. Turned around and saw the thing on fire on the flat grass where I missed it ......FML. Definitely lost 2 motors and the AIO. Last time I use one of those AIO for anything except tiny whoop motors. I've done this repeatedly for the last 6 years to find quads with separate FC/ESC boards and never popped an ESC. It's not like it was all tangled up so I think maybe some other issue. Oh well.....Fly it, Break it, Fix it.
Ya, I have never had luck with AIOs. Well, the 533 kit one was good, but ya lose All-at-once when it does go bad. I had 2 from Iflight and both lit in flames when I plugged in the USB to my PC. Nether had been touched yet, nothing attached to them and flames in my hand. Other than that, I love Iflight products, but have switched to speedybee f7 v3 stack.
Would be amazing if it could detect the stuck motor and disable just that motor until you flip a switch back so the other motors can still help you get unstuck
I have a drone that struggles to spin up its motors and when it cant do it for like 10 seconds, it makes a specific long beep sound AND, I THINK it stops trying to activate that motor because ive never gotten it to spin after ive heard that wbeep So it might be a thing on some escs or their firmware...?
Oh, it could help a lot! Thanks, Joshua!!! 😃 The 1000 would be the signal I believe... 1000 to 2000, in which 1000 would be zero RPM? I don't know. Anyway, stay safe there with your family! 🖖😊
JB not knowing it all? We've been lied to, tricked and bamboozled this whole time! Really though, this is an amazing feature for when the inevitable happens in a tree. Thanks for covering this!
03:51 # get osd_esc_rpm_alarm osd_esc_rpm_alarm = -1 Allowed range: -1 - 32767 so one would guess.... I've set it 999 RPM below my lowest motor idle value... Cheers for the Tip Yancy/JB Edit: now set to 60...if it's not spinning once a second.. sounds like a decent setting..at least for turtle 🧠 Edit: can't get this to RELIABLY trigger at any RPM unless above idle value... I don't want wont trust this at all...but better than nothing.. even if not reliable? 🤔
Sounds crazy but i've never burnt a motor or fet from a tree branch, normally i manage to cut through the foliage with my props before they explode 😂 or im lucky and it falls out from all the jiggling 🤣 nice video mate 👌🛸🛸
I'm surprised that trying to turtle while stuck is the most common. I've never burned a motor due to it being stuck, and I've definitely pushed my luck there tons of times. I've only ever burned out motors while flying with a catastrophically damaged prop that creates overly excessive vibrations.
According (to my understanding of) the code of BetaFlight, since 4.4.0 it is enough to have 1) "osd_esc_rpm_alarm", "osd_esc_current_alarm" & "osd_esc_temp_alarm" set to not 0 value and 2) OSD warning "ESC_FAIL" enabled to get warnings about low RPM, high current and high temperature based on info coming through DSHOT protocol. Can't check it on the drone right now though :( PS: this warning appears only when quad is in ARMED state
Should be some form of high RPM protection too, running motors prop-less by accident at max is a good way to burn them up as they don't have sufficient cooling.
Thanks for the info. Anyone know if it's normal to need to goto 54 throttle on mobula7 HD to take off. I tend to bounce up and down alot. On my channel I have a video if you want to see the throttle details in a video
@@rippfpv it is set to whatever default is. I looked in reciever tab and it is set to spi rx. if thats what you mean. in ports i see blackbox logging set to 2470000 and blackbox tab i see serial port then 1/8 250Hz Gyro_scaled.
@@aphixe so turn on your radio and plug in the mob7 in to beta flight go to the receiver tab and move your sticks the default is usually like 988 on the low and and like 2008 on the high end it should be 1000ish to 2000
How to turn this off? On my SpeedyBee F405v3, telemetry on ESC does not want to work, but now I keep getting the "ERROR" message in the warnings. 😪 after I set osd_esc_rpm_alarm = 1000 😁
RPM alarm requires ESC telemetry. It doesn't work with bidirectional DSHOT even though bidirectional DSHOT reports RPM. So if you don't have ESC telemetry working, you can't use this function. I advise turning off the alarm.
Not yet since it only works with ESC's with telemetry, basically 32bit esc's, ie 32bit Blheli esc vs 16bit Blheli_S esc. The Mobula 6 is running Blheli_S escs that do not provide telemetry data, but with Bluejay flashed to the ESC we do get RPM data. But like Joshua stated, nowadays we have bidirectional DSHOT on Blheli_S escs with Bluejay installed on them, so we are getting RPM information that way. Lets hope that the Betaflight devs change the code so we can use it on tiny whoops that are running Bluejay.
I thought that this was going to be good for IGOW and diagnosing why my whoop that's crashed the other side of the field won't take off and let me fly back. But I don't think any of my whoops have esc telemetry
Hey man! I was thinking the exact same thing for IGOW, then I realized that you can just turn on the "motor diagnostics" element in the OSD, and it will present an "S" for whichever motor is "stalled". I just tried it on my happymodel x 12 AIO in my Mobula 8, and it works great! No more wondering if I have one of my girlfriends thicc-ass Indigenous hairs caught in my Tiny Whoop prop.. 😅
@@robinmoore3649 what I understand it achieves the same. I could be wrong, and there might be some other use case but it seems like what baby is showing in the video is kind of like a workaround for what this element. I'm no betaflight October though I could be mistaken. But I did try it out and if you stall a motor and ask pops up which is all I need as far as functionality.
This might actually be handy for tiny whoops, there are times when I'm not sure if my motor is spinning up fully, because I've got one of my girlfriends thick ass hairs caught in the prop.. 😅
Yeah, lets hope that the Betaflight devs catch wind of this and add it as a feature for quads using Bluejay for bidirectional DSHOT. It would definitely save us all a bunch of money.
Not sure. I bought the early AliExpress ones but they still put pressure on my nose. Then I saw the Iflight wide and narrow versions and tried the narrow as it seems to push the goggles away from your face under your eyes which relieved the pressure on my nose. Therefore haven’t needed to try the newer DJI ones as the iFlight ones are pretty comfy
I made a drone recently and whenever it touches the ground or a object it reactants strongly by accelerating the motors. This makes it really hard to land as the drone just starts to bounce. Is there a setting in beta flight I can configure to fix this?
You can disable AirMode in the configuration tab. But it will behave poorly when lowering throttle in flight. You can activate it and deactivate it with a switch, there are plenty of videos about that. “Airmode on a switch” Or just learn to disarm low to the ground 😅
I'm pretty sure that's just how Air Mode is. If you hit anything it will react strongly. You can set Air Mode on a switch. If you don't assign a mode it will be plain Acro Mode. I'm not 100% sure but in Acro, if you put your throttle to zero the motors will stop completely and bad things will happen. But in Acro you won't get that strong reaction. The guys that try to grind their kwads use Acro instead of Air for that exact reason.
The number is a binary encoded X/Y coordinate for the position on the OSD. If it's zero, the element is hidden. Setting it to 1000 will simply display the element in a default position.
For anyone searching for the CLI:
set osd_esc_rpm_alarm = 1000
save
I'm fairly certain you can enable the "Motor Diagnostics" OSD element and, using only bidirectional dshot, display for each motor the level commanded or an "S" if stalled. It won't pop up all cool like that warning but it's always there and helpful if you know how to use it.
mine NEVER in all my years worked. all my quads are filtered with bidirectional (bluejay)
That's slick! I'm going to try it!
You're the man, Baked Beaner. 👊🏻
It even works on my HM X12 AIO on my 85mm Whoop. 👌🏻
This is what I have on my race kwads. Helps let me know that I'm caught up in a flag or a gate and a motor is not spinning.
I tried it last night and it works! Simply check the Motor Diagnostics box in the OSD and you get a box with "SSSS" indicating which motor is stalled. In normal operation it shows "- - - - "
The value of 1000 is the RPM threshold. If the motor's RPM falls below this value, it will show the error.
could also be a bit signal with 8 different toggle settings. what for i don't know. so it could be = 1011
JB has never seen the motors tab?
Birdman to the rescue! Excellent song my man, damn impressive!
I just took a quick look in the code and the value is the RPM threshold below which the warning will be shown. I also noticed that the warning is supposed to work both with ESC telemetry or bidirectional DSHOT, so not sure what is going on there.
I don't want to post the link here because youtube tends to hide comments that post links, but the relevant code is in
src/main/osd/osd_warnings.c#L285 (for ESC telemetry) and
src/main/osd/osd_warnings.c#L340-L342 (for bidirectional DSHOT)
Great video as always Joshua
I couldn't get it working with Dshot RPM, but maybe the code was changed recently?
Super cool feature. If I had this setup it would be blinking like a mad man!
Happened to me today. Was on the 3rd flight of an Apex 3" build, was flying beautifully and smooth with an JHEMCU AIO 45A, Ant motors 1408/3800kv, 4s, and clipped a tree branch. No problem as I pretty much knew where it went down. Spent 15 mins looking for it and couldn't see it. I knew I was close so I armed and disarmed quickly twice to hear a spin, but heard a 'popping' sound. Turned around and saw the thing on fire on the flat grass where I missed it ......FML. Definitely lost 2 motors and the AIO. Last time I use one of those AIO for anything except tiny whoop motors. I've done this repeatedly for the last 6 years to find quads with separate FC/ESC boards and never popped an ESC. It's not like it was all tangled up so I think maybe some other issue. Oh well.....Fly it, Break it, Fix it.
Ya, I have never had luck with AIOs. Well, the 533 kit one was good, but ya lose All-at-once when it does go bad. I had 2 from Iflight and both lit in flames when I plugged in the USB to my PC. Nether had been touched yet, nothing attached to them and flames in my hand. Other than that, I love Iflight products, but have switched to speedybee f7 v3 stack.
Would be amazing if it could detect the stuck motor and disable just that motor until you flip a switch back so the other motors can still help you get unstuck
that would be good
I have a drone that struggles to spin up its motors and when it cant do it for like 10 seconds, it makes a specific long beep sound
AND, I THINK it stops trying to activate that motor because ive never gotten it to spin after ive heard that wbeep
So it might be a thing on some escs or their firmware...?
Really cool feature and presentation was great 🤟
What a nice option 4 our goggles - I just love this channel
JB can you bring back your old series about learning to fly FPV in Freerider? My dad could really use it
Oh, it could help a lot! Thanks, Joshua!!! 😃
The 1000 would be the signal I believe... 1000 to 2000, in which 1000 would be zero RPM? I don't know.
Anyway, stay safe there with your family! 🖖😊
Excellent information as always
1000 is probably the RPM speed. At Idle you were just over 1000 and if its blocked it would be lower.
JB not knowing it all? We've been lied to, tricked and bamboozled this whole time!
Really though, this is an amazing feature for when the inevitable happens in a tree. Thanks for covering this!
03:51
# get osd_esc_rpm_alarm
osd_esc_rpm_alarm = -1
Allowed range: -1 - 32767
so one would guess.... I've set it 999 RPM below my lowest motor idle value... Cheers for the Tip Yancy/JB
Edit: now set to 60...if it's not spinning once a second.. sounds like a decent setting..at least for turtle 🧠
Edit: can't get this to RELIABLY trigger at any RPM unless above idle value... I don't want wont trust this at all...but better than nothing.. even if not reliable? 🤔
Sounds crazy but i've never burnt a motor or fet from a tree branch, normally i manage to cut through the foliage with my props before they explode 😂 or im lucky and it falls out from all the jiggling 🤣 nice video mate 👌🛸🛸
Love the shirt..
Thx bud www FlyHighFPV com, check the Swag Section
@@Fly_High_FPV yeah I'm about to order a red one. Dope shirt 🔥🤖 🖕 Metallica
@shanescordamaglia8433 The shirt idea spawned from Metallica sueing me for $500,000 back in the Napster Days. They can suck my FairUse 🤣
Amazing feature = thanks for tutorial
AM32 has the stuck motor protection feature. Not sure if Blheli32 has that as well already.
Living in the south and having Spanish Moss everywhere.. your 99% sure ALL your motors won’t spin if stuck in it..😂
I'm surprised that trying to turtle while stuck is the most common. I've never burned a motor due to it being stuck, and I've definitely pushed my luck there tons of times. I've only ever burned out motors while flying with a catastrophically damaged prop that creates overly excessive vibrations.
According (to my understanding of) the code of BetaFlight, since 4.4.0 it is enough to have 1) "osd_esc_rpm_alarm", "osd_esc_current_alarm" & "osd_esc_temp_alarm" set to not 0 value and 2) OSD warning "ESC_FAIL" enabled to get warnings about low RPM, high current and high temperature based on info coming through DSHOT protocol. Can't check it on the drone right now though :(
PS: this warning appears only when quad is in ARMED state
My thoughts.... The OSD warning needs to display longer. It flashed so fast, I would never notice it. I barely see my battery voltage....
IF the motor is blocked, it will stay on screen and not flash just because someone slowed the motor down shortly.
Ist that alsp good to Notice a bennt bell
Should be some form of high RPM protection too, running motors prop-less by accident at max is a good way to burn them up as they don't have sufficient cooling.
What about the stuck rotor detection feature in Blheli?
Thanks for the info. Anyone know if it's normal to need to goto 54 throttle on mobula7 HD to take off. I tend to bounce up and down alot. On my channel I have a video if you want to see the throttle details in a video
Sounds normal to me
Did you set the Rx range on for your receiver in beta flight?
@@rippfpv it is set to whatever default is. I looked in reciever tab and it is set to spi rx. if thats what you mean. in ports i see blackbox logging set to 2470000 and blackbox tab i see serial port then 1/8 250Hz Gyro_scaled.
@@aphixe so turn on your radio and plug in the mob7 in to beta flight go to the receiver tab and move your sticks the default is usually like 988 on the low and and like 2008 on the high end it should be 1000ish to 2000
@@rippfpv on the low end of throttle it is 989 and on highest it is 2009
How to turn this off? On my SpeedyBee F405v3, telemetry on ESC does not want to work, but now I keep getting the "ERROR" message in the warnings. 😪 after I set osd_esc_rpm_alarm = 1000 😁
RPM alarm requires ESC telemetry. It doesn't work with bidirectional DSHOT even though bidirectional DSHOT reports RPM. So if you don't have ESC telemetry working, you can't use this function. I advise turning off the alarm.
How should I know which port to select to get telemetry from ESC?
You have to look at your FC wiring diagram.
I can't get a blinking RSSI dbm warning out of my OSD, using O3 Air Unit, Goggles V2. Why is that? Had to set an entirely new FC up
Set your dBm threshold correctly and/or disable the warning entirely: ruclips.net/video/LnWdIssBk-c/видео.html&ab_channel=JoshuaBardwell
Hey bro is there a way to make my radio failsafe trigger show in OSD ?
Thank you... will this work on a tiny whoop like mobula 6.
Not yet since it only works with ESC's with telemetry, basically 32bit esc's, ie 32bit Blheli esc vs 16bit Blheli_S esc. The Mobula 6 is running Blheli_S escs that do not provide telemetry data, but with Bluejay flashed to the ESC we do get RPM data. But like Joshua stated, nowadays we have bidirectional DSHOT on Blheli_S escs with Bluejay installed on them, so we are getting RPM information that way. Lets hope that the Betaflight devs change the code so we can use it on tiny whoops that are running Bluejay.
The real question now is
Can we use both bidirectional DShot and esc telemetry together on a quad?
Coz losing bidirectional DShot is a big deal.
Yes you can use them both. I'm doing exactly that in this video.
I thought that this was going to be good for IGOW and diagnosing why my whoop that's crashed the other side of the field won't take off and let me fly back. But I don't think any of my whoops have esc telemetry
Hey man! I was thinking the exact same thing for IGOW, then I realized that you can just turn on the "motor diagnostics" element in the OSD, and it will present an "S" for whichever motor is "stalled". I just tried it on my happymodel x 12 AIO in my Mobula 8, and it works great!
No more wondering if I have one of my girlfriends thicc-ass Indigenous hairs caught in my Tiny Whoop prop.. 😅
@@willpowerfpv3246 I have one set up on a whoop that shows 4 lines that I think represent the motors, is that the same one or something else?
@@robinmoore3649 what I understand it achieves the same. I could be wrong, and there might be some other use case but it seems like what baby is showing in the video is kind of like a workaround for what this element. I'm no betaflight October though I could be mistaken. But I did try it out and if you stall a motor and ask pops up which is all I need as far as functionality.
@brandonbeans has made another post confirming what we're both thinking
I would like the opposite, I want to know when one motor is running faster on average than the others, then I know I’ve got a slipping or damaged prop
This might actually be handy for tiny whoops, there are times when I'm not sure if my motor is spinning up fully, because I've got one of my girlfriends thick ass hairs caught in the prop.. 😅
Yeah, lets hope that the Betaflight devs catch wind of this and add it as a feature for quads using Bluejay for bidirectional DSHOT. It would definitely save us all a bunch of money.
Hello there
Hey, Joshua, what kind of foam are you using on goggles 2, i badly need a new foam for them?
Iflight narrow version is good if you have pressure on your nose with current foam
@@thomasbrian7097 is there any good reviews comparing new dji soft fit foam with iflight ones ?
Not sure. I bought the early AliExpress ones but they still put pressure on my nose. Then I saw the Iflight wide and narrow versions and tried the narrow as it seems to push the goggles away from your face under your eyes which relieved the pressure on my nose. Therefore haven’t needed to try the newer DJI ones as the iFlight ones are pretty comfy
Heya!
"Know it all" is a moniker for guys JUST like you.
I made a drone recently and whenever it touches the ground or a object it reactants strongly by accelerating the motors. This makes it really hard to land as the drone just starts to bounce. Is there a setting in beta flight I can configure to fix this?
You can disable AirMode in the configuration tab. But it will behave poorly when lowering throttle in flight.
You can activate it and deactivate it with a switch, there are plenty of videos about that. “Airmode on a switch”
Or just learn to disarm low to the ground 😅
I'm pretty sure that's just how Air Mode is. If you hit anything it will react strongly. You can set Air Mode on a switch. If you don't assign a mode it will be plain Acro Mode. I'm not 100% sure but in Acro, if you put your throttle to zero the motors will stop completely and bad things will happen. But in Acro you won't get that strong reaction. The guys that try to grind their kwads use Acro instead of Air for that exact reason.
when it will be most useful is if you bend a prop and its stuck on the arm, or your in some grass and try to take off
well, Bard
The number is a binary encoded X/Y coordinate for the position on the OSD. If it's zero, the element is hidden. Setting it to 1000 will simply display the element in a default position.
no
Definitely not. The RPM warning appears in the position of the Warning OSD element.
Kiss ultra just solves this….
NEVER HAPPENED TO ME knowital
First!