Just fixed my problem... a uart was stopping my boot button working. Desoldered everything and fixed What would we do without you. A Beacon of light for us all to look to when lost. I bow to you sir
This video just saved me some work A tight build Th2 Freestyle with all of the bells and whistles I spun the board to make all the mods I did work out smoothly Problem was The board wouldnt flash and my motors where all out of whack. The Driver fixer worked on the second try. The fc was flashed motors fixed and ready for testing Thank You Josh!!!
Yep, all good, exact same problem, disconnected everything and used manual bootloader button, reflashed to 4.3 and working fine, TX RC power on OSD too, yeah boi!!! Thanks
The last thing that I did that ended being what I needed first was to download the Impulse RC DFU driver. I am using axisflying 55 amp F7 FC. USB-C cable is good. Couldn't open serial port until I installed the Impulse RC DFU driver to access the bootloader.
What about FCs on F4 with integrated ELRS on UART1? I don’t understand why manufacturers use UART1 than any other UART and second if they use UART1 why they don’t give an option to turn peripheral off by a jumper. These FCs may be ‘bricked’ as DFU is messed up with ELRS
I had a problem with my first FC RUSHFPV blade F722 and i made the mistake of switching off the top port. No matter what i tried I couldn't get in DFU mode, tried the immersion driver fixer. I finally found a fix going through a program from STM Electronics & for that to work I had to get Rushfpv hex file & it fixed my problem.
Hey I was using the CLI to change motor position an when I save and reboot, now my flight controller wont connect and when I connect to my googles and controller it connects but I dont have OSD on my googles and the controller and camera are conected but i cant arm the drone. please help
I just flash INAV 6.1.1, and success. But it only connected for view minute and disconnected. I tried to reconnect, not showing any Port Com or USB modem. Except DPU mode
I had a similar problem, when I set my fc to bootloader mode, betaflight was not able to find it anymore. However it was shown as DFU in my Devicemanager. My problem was, that I used the browser Version of Betaflight. When I used the downloadable version, betaflight found the fc in bootloader mode and I was able to flash.
de soder and disconnect..... THIS IS MY FIRST FPV i bought a cinebot 30..... thats definitely last resort. seems to be in DFU mode but betaflight doesnt acknowledge that its in DFU mode...
I had the exact issue. I previously just remapped motor 5 and the led pad for my gps. As soon as I hit save in the cli after remapping immediately I was kicked into bl mode or at least what I thought was boot loader. I think im just going to remove the gps unfortunately. Im glad you made this video I would be scratching my head forever on this if you didnt. Thanks JB.
I've removed everything but mine still does it, but I have continuity between the 2 DFU enable pins somehow, even after I removed the button so idk, that might be it
@I played around a bunch more with that FC but I ended up with a new stack for different reasons. I could get it to exit DFU mode via BFC, but it would boot back into it after another reset. I did a bunch of other random shit on it and it was sometimes fixed sometimes fucked again, but in the end I think there was a short on unrelated pins that were sparking (5V and GND iirc), that was very confusing. Used that FC as sacrificial test for my conformal coating (since it registered via USB again for the time being) and it passed it tho. It was in my first build so I kept it as a trophy :3 edit: the DFU drivers fixer something that ppl mention was a great thing to keep in mind because that helped me with 2 other FCs on 2 different computers since btw
Good afternoon, please help me, I have a drone Darwin baby ape, does not connect to betaflight, I can not put it in dfu mode, and the computer does not see it. Although before it was connected. Help me to solve this problem
My f7 flight controller is only loading in Betaflight in failsafe mode and I have connected my new dji v2 goggles and my new expresslrs zorro tx but I cannot get it to show controls on the reciever tab or arm. It says the com is in FS Mode.
So I just had this issue with hakrc aio 20a with 4.4.1. That's what it came with. I tried adding motor protocol. It gave me a weird error. So I thought it was the one with the motor bug. 4.4.1 is no longer there to grab from the flasher. Now I only get a flashing yellow light and a solid red light. This is a f411D. It seems fine but sometimes won't let me flash a new firmware. But I can connect to the flight controller. And it won't show any esc in esc config. And now esc 4 won't spin
Hi Joshua, I‘ve got the so called ghost in the shell. Since feb I couldn’t connect drone to BetaFlight. The virtual com port is not listed in the device manager 🤦🏻♂️ Maybe someone has come up with a similar issue, many thnx infront & much help appreciated, thnx
Aye. Actually shorting a ground and 5v on the same sbus rail will do that. I should be good tho because it bound. Been working on this conversion all day was was bout to go nuts or to sleep.
How do I get your email I have a manta 3.6 With a Argus f7 ministack . I switched the dji 03 for a nebula and I get view through my goggles and the tango 2 connects to the receiver tbs crossfire nano pro . The problem is the flight controller has has a blinking green with a solid red . I cannot get the controller to start motors Or have any inputs . I don’t know whats wrong or what the problem is but I cannot find any information on what to do.
brand new fc no wiring straight out of the box, when plugged in most of the time betaflight detects in in dfu mode, after unplugging a few times betaflight will detect it as a com port but will put itself back into dfu mode while trying to config settings or just looking at it the wrong way, no problems with my 6 other fc's so not thinking its cable or driver related, any ideas
I just flashed the skystars F722HDpro and then it asked me that it had no motor protocol and so I went to the motors tab and set Dshot600 and clicked save and reboot and it didn't make the sound that it saved or worked and the light stays solid red. I tried impulsedRc and it updates it but then I click exit DFU and nothing changes when I unplug and plug in again, need help.
Can an electrical storm corrupt receiver & FC firmware? I had a drone where the bat voltage in the OSD would work sometimes, then lock up on a number, causing me to over-drain a battery because it was still reading 22.1 volts. I also had a different drone that flew fine for a couple years. I didnt' crash it. I flew it a lot, then stopped flying it for several months. When I went back to fly it, the receiver would not connect to my radio. I had to reflash the ELRS receiver. Then my radio locked up & I had to reflash Edge TX onto it. It's strange that several of my electronics just out of the blue decided to stop working, but reflashing firmware made them work again. All I can think of is that these things have antennas on them and an electrical storm may have went through the area.
ALSO WEIRD, the FC that had the locking up Bat voltage, when I plugged it into BF, there was no OSD tab. Several of the tabs were missing. I reflashed it from BF 4.4.2 to 4.5.0 and the tabs are all back.
can you help me , i jst got my new cinebot30 , at 1st it can connect to beta flight with version 4.3.1 . but then i update it to 4.4 because my tx elrs is 3.0 , after 5 min i cant connect my drone to beta flight anymore , while i try to connect other drone it work well . only my cinebot after update to 4.4 . and i forgot to backup the original firmware , did i jst erase all the information like drive on the FC that make it like this ?
What option that i think will work is buy a new same cinebot30 and backup the original firmware and load it via local to my 1st cinebot to restore what ever it is inside the Fc . Does it possible ?
I use impluse driver it cant find my fc , what im confuse is if i connect with other drone it work fine , only my cinebot30 happe like this after flash firmware to 4.4 . Any suggestion and advice ..
My quad connected just fine until I did the usb thing after watching a guide on how to use my fc as a dongle to use a simulator. Now, I can`t connect to betalight, and the "show all" option does nothing. There`s nothing wrong with my cable, it`s the same cable I used less than a hour ago. But now I can no longer connect to BF so I can`t get into the CLI to turn the friggin thing off. Yeah guess what, the FOJHRKUDG NIKUYRIHEUKGUKEH who made that video didn`t mention that.. Ima about to book a flight and bring guns.
Just fixed my problem... a uart was stopping my boot button working.
Desoldered everything and fixed
What would we do without you.
A Beacon of light for us all to look to when lost.
I bow to you sir
I'm having the same issue with mines. This video and comments below hopefully will help 🙏 🙂 thank you
This video just saved me some work
A tight build
Th2 Freestyle with all of the bells and whistles
I spun the board to make all the mods I did work out smoothly
Problem was
The board wouldnt flash and my motors where all out of whack.
The Driver fixer worked on the second try.
The fc was flashed motors fixed and ready for testing
Thank You Josh!!!
Thanks for your knowledge and help always with all my FPV needs. You are the real MVP!
Yep, all good, exact same problem, disconnected everything and used manual bootloader button, reflashed to 4.3 and working fine, TX RC power on OSD too, yeah boi!!! Thanks
aww shoot hope i dont have to disconnect everything to my FC board
The last thing that I did that ended being what I needed first was to download the Impulse RC DFU driver. I am using axisflying 55 amp F7 FC. USB-C cable is good. Couldn't open serial port until I installed the Impulse RC DFU driver to access the bootloader.
What about FCs on F4 with integrated ELRS on UART1? I don’t understand why manufacturers use UART1 than any other UART and second if they use UART1 why they don’t give an option to turn peripheral off by a jumper. These FCs may be ‘bricked’ as DFU is messed up with ELRS
I had the same issue. I desoldered my rx Boot it up on DFU mode. And that worked. For me 4.4 there’s a Bardwell TH-cam short that talks about this
Unsoldered ELRS receiver only and quad loaded in DFU mode. Thank you, Joshua!
Yep, same for me. Spot on!
Having this issue with my new Crux35. As a newbie im very overwhelmed by this issue
I had a problem with my first FC RUSHFPV blade F722 and i made the mistake of switching off the top port. No matter what i tried I couldn't get in DFU mode, tried the immersion driver fixer. I finally found a fix going through a program from STM Electronics & for that to work I had to get Rushfpv hex file & it fixed my problem.
I did this on the first quad i ever tried updating. Took me forever to get it back working lol
Hey I was using the CLI to change motor position an when I save and reboot, now my flight controller wont connect and when I connect to my googles and controller it connects but I dont have OSD on my googles and the controller and camera are conected but i cant arm the drone. please help
I just flash INAV 6.1.1, and success. But it only connected for view minute and disconnected. I tried to reconnect, not showing any Port Com or USB modem. Except DPU mode
I had a similar problem, when I set my fc to bootloader mode, betaflight was not able to find it anymore. However it was shown as DFU in my Devicemanager. My problem was, that I used the browser Version of Betaflight. When I used the downloadable version, betaflight found the fc in bootloader mode and I was able to flash.
de soder and disconnect..... THIS IS MY FIRST FPV i bought a cinebot 30..... thats definitely last resort. seems to be in DFU mode but betaflight doesnt acknowledge that its in DFU mode...
ImpulseRC Fixer is windows only, what do us apple Mac people do?
I had the exact issue. I previously just remapped motor 5 and the led pad for my gps. As soon as I hit save in the cli after remapping immediately I was kicked into bl mode or at least what I thought was boot loader. I think im just going to remove the gps unfortunately. Im glad you made this video I would be scratching my head forever on this if you didnt. Thanks JB.
I've removed everything but mine still does it, but I have continuity between the 2 DFU enable pins somehow, even after I removed the button so idk, that might be it
@@SwainixFPV i have the same issue, did you have a solution? 🙏🏻
@I played around a bunch more with that FC but I ended up with a new stack for different reasons. I could get it to exit DFU mode via BFC, but it would boot back into it after another reset. I did a bunch of other random shit on it and it was sometimes fixed sometimes fucked again, but in the end I think there was a short on unrelated pins that were sparking (5V and GND iirc), that was very confusing. Used that FC as sacrificial test for my conformal coating (since it registered via USB again for the time being) and it passed it tho. It was in my first build so I kept it as a trophy :3
edit: the DFU drivers fixer something that ppl mention was a great thing to keep in mind because that helped me with 2 other FCs on 2 different computers since btw
@@SwainixFPV thanks for the response! I fixed it by removing the bind button on mine
@@Jonanice :)
Good afternoon, please help me, I have a drone Darwin baby ape, does not connect to betaflight, I can not put it in dfu mode, and the computer does not see it. Although before it was connected. Help me to solve this problem
My f7 flight controller is only loading in Betaflight in failsafe mode and I have connected my new dji v2 goggles and my new expresslrs zorro tx but I cannot get it to show controls on the reciever tab or arm. It says the com is in FS Mode.
Is there any hope for the old spracing f3 controllers with the newest version of betaflight?
Thanks u saved me impulse rc worked
So I just had this issue with hakrc aio 20a with 4.4.1. That's what it came with. I tried adding motor protocol. It gave me a weird error. So I thought it was the one with the motor bug. 4.4.1 is no longer there to grab from the flasher. Now I only get a flashing yellow light and a solid red light. This is a f411D. It seems fine but sometimes won't let me flash a new firmware. But I can connect to the flight controller. And it won't show any esc in esc config. And now esc 4 won't spin
Hi Joshua, I‘ve got the so called ghost in the shell. Since feb I couldn’t connect drone to BetaFlight. The virtual com port is not listed in the device manager 🤦🏻♂️
Maybe someone has come up with a similar issue, many thnx infront & much help appreciated, thnx
Thaks have same issue
same FC I need help here please Joshua
Alls I did was wire up my 03 bound it and everything. The whole time not liking this solid red light. Where my blue flashes go?!
Aye. Actually shorting a ground and 5v on the same sbus rail will do that. I should be good tho because it bound. Been working on this conversion all day was was bout to go nuts or to sleep.
How do I get your email I have a manta 3.6 With a Argus f7 ministack . I switched the dji 03 for a nebula and I get view through my goggles and the tango 2 connects to the receiver tbs crossfire nano pro . The problem is the flight controller has has a blinking green with a solid red . I cannot get the controller to start motors Or have any inputs . I don’t know whats wrong or what the problem is but I cannot find any information on what to do.
brand new fc no wiring straight out of the box, when plugged in most of the time betaflight detects in in dfu mode, after unplugging a few times betaflight will detect it as a com port but will put itself back into dfu mode while trying to config settings or just looking at it the wrong way, no problems with my 6 other fc's so not thinking its cable or driver related, any ideas
Have you found the solution?
@@hazimhakimi1492 bad usb port on the fc is my guess, change a setting and save real quick was my fix
I just flashed the skystars F722HDpro and then it asked me that it had no motor protocol and so I went to the motors tab and set Dshot600 and clicked save and reboot and it didn't make the sound that it saved or worked and the light stays solid red. I tried impulsedRc and it updates it but then I click exit DFU and nothing changes when I unplug and plug in again, need help.
Did you find a solution?
Can an electrical storm corrupt receiver & FC firmware? I had a drone where the bat voltage in the OSD would work sometimes, then lock up on a number, causing me to over-drain a battery because it was still reading 22.1 volts. I also had a different drone that flew fine for a couple years. I didnt' crash it. I flew it a lot, then stopped flying it for several months. When I went back to fly it, the receiver would not connect to my radio. I had to reflash the ELRS receiver. Then my radio locked up & I had to reflash Edge TX onto it. It's strange that several of my electronics just out of the blue decided to stop working, but reflashing firmware made them work again. All I can think of is that these things have antennas on them and an electrical storm may have went through the area.
ALSO WEIRD, the FC that had the locking up Bat voltage, when I plugged it into BF, there was no OSD tab. Several of the tabs were missing. I reflashed it from BF 4.4.2 to 4.5.0 and the tabs are all back.
can you help me , i jst got my new cinebot30 , at 1st it can connect to beta flight with version 4.3.1 . but then i update it to 4.4 because my tx elrs is 3.0 , after 5 min i cant connect my drone to beta flight anymore , while i try to connect other drone it work well . only my cinebot after update to 4.4 . and i forgot to backup the original firmware , did i jst erase all the information like drive on the FC that make it like this ?
What option that i think will work is buy a new same cinebot30 and backup the original firmware and load it via local to my 1st cinebot to restore what ever it is inside the Fc . Does it possible ?
I use impluse driver it cant find my fc , what im confuse is if i connect with other drone it work fine , only my cinebot30 happe like this after flash firmware to 4.4 . Any suggestion and advice ..
My quad connected just fine until I did the usb thing after watching a guide on how to use my fc as a dongle to use a simulator.
Now, I can`t connect to betalight, and the "show all" option does nothing.
There`s nothing wrong with my cable, it`s the same cable I used less than a hour ago.
But now I can no longer connect to BF so I can`t get into the CLI to turn the friggin thing off.
Yeah guess what, the FOJHRKUDG NIKUYRIHEUKGUKEH who made that video didn`t mention that..
Ima about to book a flight and bring guns.
WTF, I hate things like these so much. Unsoldered UART 1 ELRS RC, now i could reflash...so stupid
❤❤❤❤