Hello guest, if you read this it means you are not registered. Click here to register in a few simple steps, you will enjoy all features of our Forum.
This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Unable to Connect to Beta Flight
#1
I bought a BetaFPV 95X (V2 I think) with Caddx Vista (used), and I’m unable to connect to beta flight. I’m pretty sure I screwed something up when I tried to flash the firmware.

I’m 100% stuck, tried the reboot sequence with the boot button, etc. Itll occasionally connect, but then quickly disconnects. Would I be better off buying a new FC and starting over? I really hate to have wasted $$$ on this thing if I can’t get it up and running.

Really appreciate any help!!

Otherwise: If anyone’s interested in buying this thing with a naked GoPro I’m happy to sell it cheap
Reply
Login to remove this ad | Register Here
#2
Maybe a dumb observation on my part, but are you 100% sure your usb cable is not just a charging cable?
I made that mistake. Changed cables and it works like it should
My ability to remember song lyrics from the ‘60s far exceeds my my ability to remember why I walked into the kitchen just now 
Reply
#3
Try reflashing in DFU mode. You cannot really brick an FC, so you don't need to buy new FC. Hold he boot button then plug in the USB. Once you see that BF recognized that the FC is in DFU mode, you go ahead a flash again. If BF does not see the FC in DFU mode, you might need to load the Zadig driver. You can tell if you need to load the driver by booting the FC in to DFU mode. Then go to the device manager. If you see a device with an yellow ! mark, you do not have the driver. If you are on a Mac, the driver should already be there.

https://zadig.akeo.ie/
Reply
#4
Thanks for the help, I’ll try these tonight when I get home.

Does it make any sense that BF only recognizes the FC when the battery isn’t plugged in? Just the usb…
Reply
#5
(26-Sep-2023, 07:30 PM)Goforbroke001 Wrote: Thanks for the help, I’ll try these tonight when I get home.

Does it make any sense that BF only recognizes the FC when the battery isn’t plugged in? Just the usb…
If this is the case, then the diode that regulates the 5V backflow might be bad. Not allowing the 5V from the USB to power the FC. There is not need to reflash if you can connect to FC with lipo power.

You have a few choices.
1. Live with the FC. You need to power from lipo everytime you make changes.
2. Try to repair the FC if you are into microsoldering. (personally this is my choice, but is not for most people)
3. Buy a new FC (probably what most people would do)
Reply
#6
For some of the older FCs, I seem to recall it shared a UART between MSP and a peripheral. If that was the case then having the peripheral connect/powered up would prevent connecting to the FC via USB.
Reply
#7
Update: BF identifies “COM4 - Betaflight STM32F405” and also the board “OMNIBUSF4SD - version 4.4.2 - June 2023”

However, when I hit “connect” it will say “serial port successfully opened,” but then nothing happens, stays on the initial screen, then says “serial port successfully closed.” Without me doing anything, after 5-10seconds. Then it’ll say “Failed to open serial port” the next half dozen attempts to connect to BF
Reply
#8
Go to Device manager. Then plug in your FC. What shows up? Can you post what pops up?
Reply
#9
I think I’m just going to buy a new stack and start over, it should be less hassle and stress than trouble shooting this electronic communication black-hole.

Everything happens for a reason as they say, I’ve been interested from the sidelines in learning electronics soldering, so I think this is a good time for me to learn. I have some slight experience in soldering wires, but this will be next-level, so I’m excited to try.

Any advice on equipment or techniques? My current soldering equipment isn’t really meant for micro-electronics.

Any advice would be much appreciated!
Reply
#10
If you have a driver issue, then you will have the same issue with a new FC.
Reply
#11
(28-Sep-2023, 03:49 AM)voodoo614 Wrote: Go to Device manager. Then plug in your FC. What shows up? Can you post what pops up?

STMicroelectronics Virtual COM Port (COM4)
Reply
#12
(30-Sep-2023, 07:01 PM)Goforbroke001 Wrote: STMicroelectronics Virtual COM Port (COM4)

That is the correct driver. So maybe the FC is bad.
Reply
#13
(29-Sep-2023, 07:12 AM)voodoo614 Wrote: If you have a driver issue, then you will have the same issue with a new FC.

If I replace the entire stack, what would cause the driver issue? Just curious, I’m newish to all of this. Really appreciate the help!
Reply
#14
Almost all of the FC today uses the "STMicroelectronics Virtual COM Port" to connect to BFC. Your new stack should connect to BFC without issue. If you are still having problem on the new FC, then we can say something is wrong with your computer driver or the cable. Since you don't have a working FC that connects to BFC, it is hard to right out the factor that causing your current issue. If you still want to try to get your current FC working, the last thing you can try is reloading the STM driver. And make sure you have an USB cable capable of data transfer and not just a charge cable. I honestly don't think is your cable because BFC was able read the firmware target.

To reinstall the driver, go to the website below and download the driver. Run the exe file to load the firmware on your computer

https://www.st.com/en/development-tools/...32102.html

Then follow the step as I outlined below.

https://intofpv.com/t-com-port-issue-wit...#pid119646
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  low flight times on 3.5 cinewoop technoflyer97 2 129 03-May-2024, 09:16 AM
Last Post: technoflyer97
  Flight time decreased Billybobthe3 8 227 01-May-2024, 10:57 PM
Last Post: hugnosed_bat
  problems connecting and writing code for the remote (esp32) and the flight controller YarikVor 2 147 23-Apr-2024, 03:58 PM
Last Post: YarikVor
  Can I connect my DJI fpv v2 goggles to and dji fpv remote controller 2 to other drons qt179 4 264 08-Apr-2024, 10:57 AM
Last Post: roleyrev
  After 1-2 minutues of flight, drone flips over in air doublebubble 22 853 16-Feb-2024, 11:32 PM
Last Post: mstc


Login to remove this ad | Register Here