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
Help getting DarwinFPV 129 erls to bind
#16
Oh I’m not really upset with Darwin per se because of the receiver. There were no instructions as to which target to flash. Like I said originally, on the webpage that opens when activating the WiFi on the receiver, it initially said to flash a BetFPV target. Then after that it said to use a DYI target. It was after I tried that target that the LED went solid and I haven’t been able to do anything with it since. When I try BF passthrough it says “Could not open com port 3, the port doesn’t exist” I have tried manually telling it to use that port and I’ve tried it without naming a port to use and it gives me the same error each time. When I try to use the FTDI adapter the error message says, “Please specify upload port or choose global”. I have no clue what that means. And I do have telemetry off in Betaflight.

What I meant about being upset with Darwin is that I didn’t get a battery that I ordered. It does seem that this receiver is harder than other to bind. I tried bridging the two pads identified earlier and nothing happens. I know they won’t do anything about the receiver. I wasn’t expecting them to. I think it would be really helpful if they simply sent which target to use with the receiver. I don’t know why that 10.0.0.1 address originally told me to use a BetaFPV target then later it said to use a DYI one. 

Shouldn’t the receiver still put itself into WiFi mode after being powered on and not binding with a transmitter within 60 seconds or so? I’m new to this hobby, especially ELRS so I’m just trying to understand how I could have avoided this problem and to prevent it in the future.
Reply
Login to remove this ad | Register Here
#17
When I’ve accidentally flashed the wrong firmware to a receiver, or had an interrupted flash, it no longer goes into WiFi mode no matter how long I wait.

Those errors both make me think you might have a conflict or configuration issue on your computer, or that you don’t have the right drivers installed- but I wouldn’t know where to tell you to start to fix that, my computer knowledge is a couple decades out of date.

I’d still suggest jumping on the discord, but if you post a screenshot of the ELRS configurator with it set up as you had it trying to flash via ftdi adapter, maybe v22 or I can tell you if you need to change something.

Edit- when you’re connecting your ftdi adapter to the receiver, you are remembering to connect rx to tx and tx to rx, yeah?
Dangerous operations.

Disclaimer: I don’t know wtf I’m talking about.
I wish I could get the smell of burnt electronics out of my nose.
Reply
#18
V22 was very helpful. We tried all sorts of things with no luck. I’d be happy to send the receiver to someone to see if he can flash. I did load new drivers on my computer because I thought that it could be causing the problems. I had the right connections, Tx to Rx and Rx to Tx.

My new Happymodel Rx showed up and it flashed great and I even flew the quad around briefly. The Discord is a pretty cool thing. The people on there are great and were always willing to help out. Thanks again for the link and invite!!
[-] The following 2 users Like sharptailhunter's post:
  • Lemonyleprosy, V-22
Reply
#19
This did seem to be a hardware issue with the receiver. Even attempting to flash directly with a FTDI was failing due to too much noise on the serial UART. There have been several people on the ELRS Discord having trouble with these as well.

It's really disappointing to see DarwinFPV ship such poor quality knockoff-of-a-knockoff receivers, especially when the ELRS devs provide free assistance to manufacturers with hardware design and configuration. I don't understand why more manufacturers don't take advantage of it, as it would save them a ton of support requests and save their users many headaches.

I'm glad things are working well with the new HappyModel RX though. Happy flying!
[-] The following 1 user Likes V-22's post:
  • Lemonyleprosy
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  CLI dump for DarwinFPV FoldApe Oscar 1 366 22-Apr-2024, 11:27 AM
Last Post: bar1
  CLI Dump for DarwinFPV Cineape35 (original) Oscar 0 413 01-Feb-2024, 09:28 PM
Last Post: Oscar
  Help with GPS on DarwinFPV 129 sharptailhunter 5 664 02-Apr-2023, 10:21 PM
Last Post: Mugen_G
  Trashcan DSMX won't bind eintim 17 5,326 01-Mar-2022, 01:45 PM
Last Post: Jef
  Not able to bind - BetaFPV LiteRadio2 SE & Tinyhawk 2 Freestyle Elcid_888 7 2,580 21-Jan-2021, 11:38 PM
Last Post: Jphernandez0925


Login to remove this ad | Register Here