#I need help binding to elrs.
145 messages · Page 1 of 1 (latest)
Do you have the ELRS or 4-in-1 version of the TX16S?
Set your Internal RF mode to CRSF
EdgeTX supports everything; it will let you set it wrong and not tell you it's wrong lol
Are you in the RF Protocol or the Mode selector? CRSF is in Mode
Hold on, googling
Go to your SYS menu
Page over to the Hardware tab
And look at the Internal RF > Type selector
Set that to CRSF, then go back into your Model settings and set the Internal RF > Mode to CRSF
Um, it has one on here.
Alright if you go in there and everything loads, then you're in working order
I think you have to do it through Betaflight Configurator
What v of Betaflight is on the quad?
4.4.2
Alright, so the Mobeetle is an SPI ELRS receiver. On Betaflight 4.4.2, you're running ELRS 3.x on the quad, so you'll need to update your radio's internal module to 3.whatever before you can bind
In the ELRS tool on your radio, go to WiFi Connectivity
And select Enable Wifi
Is your PC connected to the internet via LAN or wifi?
Alright
Here's what you gonna do
https://expresslrs.github.io/web-flasher/
Go through the selections on the ELRS Web Configurator, and when you get to the Flashing Method, select local download. It will give you a .hex file. After that, go to your wifi and select the ExpressLRS TX network, password is expresslrs. Once it's connected open a browser window to http://10.0.0.1/, and you should be able to find the box to upload that hex file
If something doesn't work, take a screenshot and come back here
are you kidding me?
You can do it by plugging the radio in I guess
EdgeTX has passthrough
I forget about that sometimes
I get so used to the wifi lol
so i plug my tx into my pc
Ah yea that'd be the easier way to go for you
So go to this website here: https://expresslrs.github.io/web-flasher/
Pick your device, then for the Flashing Method you'll use EdgeTX Passthrough
Oh, now I'm remembering
You can enter a binding phrase in here, and then use the same binding phrase in Betaflight and they will bind automatically
It's been a while since I've done the SPI receivers
You do need the website
What browser are you using?
You could always try to download+install the stand-alone Configurator tool
ok, i have evcerything input as you have it in the last pic
edge
ok
ok, im on the options screen
i will put in the binding phrase and click next
Aight
i didnt have my tx plugged in
i'll start over
heh
withg usb, am i clicking on serial?
"Failed to connect to device, restart device and try again"
hmm
Yes
it just says failed to connect over and over
should i use the usb C port on the botrtom?
its the top one that has trhe serial option
esptool.js v0.1-dev
is all that shows up
im not sure what i am doing wrong
Might be a driver problem
"elrs is so easy to setup" imma be giving some people the bird in the future 
just a bit enouigh to have me walk away for a bit and conetemplate selling it here at a loss. 
i'll come back later to this
Ok
Tbf most of these issues aren't even ELRS related
I see it's me and my TX
But I was hoping to just press button
I don't see how anyone could say this is easier than crossfire.
Frsky was easier. And I needed 3 hands 🤣
My first experience was with prerelease 1.0, and DIY hardware (incorrectly assembled at that)... And still got it working within like 10-15 minutes. It's gotten a lot better since too
It is a bit of a process, without all of the magic that Crossfire offers, but then again you do have a real chance of figuring out what actually happened if something goes wrong, with Crossfire the troubleshooting is more vague.
And it's not even remotely close to the frsky mess that is ACCST/ACCESS, LBT/FCC, firmware and protocol versions, and all of that you have to get from their website that purposely hides it away and is either slow or completely down most of the time 
I used frsky before that mess started. Was using crossfire by the time they switched to access
Had a x9d+. So no need for a physical mod as well.
I dunno. I'll sleep on this.
Troubleshooting with crossfire is hard at times.
I have a rather large grudge against Mike chin cause of that.
I won't email tbs anymore for help because of the way he (doesn't) help people.
Out of:
- not being able to select CRSF at first
- Website being a bit jumpy and going blank
- Not having the TX plugged in correctly
Only one issue is really ELRS related and it's not even with the firmware itself
Would be a shame to sell it because of just that
I always had the tx plugged in on top and selected serial option. I just asked if I should move it to the other one.
I mean...I use it for Sims too.
Anyways though, it's probably not worth putting a nano rx on it. Wake up tomorrow and try again.
@warm sierra Your "not being able to select CRSF" issue happened because of the corrupted radio configuration...
Lovely
tag me when you have time for this
I appreciate the help guys. Im just not interested in this. Can you guys help me put a nano rx on it?
Has to have an open uart.
No need to berate me.
Well, tag me when you decide to stop being stupid and want to actually get this working. @warm sierra
It obv aint easy to setup if you manage to mess it up yourself.
In my experience ELRS took a few hours to setup, even when it was just flashing the RX and TX. But I helped a few people by now who just got into using elrs and honestly it all went very smooth with them. None of them seemed to have issues and within 15-30 minutes it was all done.
The thing is.. often you don't even need to flash nowadays, as most hardware comes with v3 firmware. Sure, it's recommended, just like with Crossfire, but if the major version matches, it will work.
All I needed @warm sierra to do, was to check the firmware versions on both the transmitter and receiver, and then I'd explain the shortest possible route to getting them talking.
Because I know their issues with patience, I wanted to make it as straightforward as possible, but I guess I won't get that opportunity.
It can be made straightforward, most people make it complicated in order to get all of the latest features, which isn't strictly necessary.
3.x on the receiver (Betaflight 4.4.2), 2.4.0 on the transmitter
That isn't the simplest situation to get out of, but it's plenty easy to deal with, since the TX update process is documented to hell and back.
I was going to walk him through EdgeTX Passthrough with the web configurator
If he decides to come back to it, we can help him. If not, that's OK too
Drivers are the only tricky part to that.
Yea that's where we got stuck. He only had wifi on the laptop though, I figured it might be easier than a local hex download then swapping networks
Elrs docs have the correct drivers listed