#Does anyone know how to use a SD card with a tx16s correctly?
255 messages · Page 1 of 1 (latest)
Does anyone know how to use a SD card with a tx16s correctly?
Bump
@dusky tapir show the backed up sd contents
Ok, lemme plug it in.
Also, why sorry for the thread, that's what this place is for
Well, because the it's like 1 question.
If the convo in a different channel died a while ago, it's fine
Potato cam pics.
the root folders, and most files inside them.
These are the old files?
I have never updated my TX besides the crossfire Lua updates
Not what I mean,,..
Those are the files on my new 32gb Sim card copied directly from sd card in tx16
So old files
so new files
you put it in the radio
and turned it on
so these files are of no interest to me
I wanted to see if the files from the old SD card are messed up somehow
Oh
causing the radio to just discard them
most importantly, I want the radio.yml
since you have a new radio.yml, post both
The old one works. The new one won't let it boot up.
If you can get files from both the working and non-working SD
then I need the radio.yml from both of them
from the RADIO folder
I need the file not pics of it 😂
Oh
You want both files?
here is the one from the new 32gb card that wont even boot up the trx
i will send the fil from the original SD card now
was there a second radio.something.yml file?
Curious.
?
Maybe it's a newer version feature..
I've seen edgetx rename a corrupted radio.yml
and generate a new one
hmmmm
edgetx version is irrelevant to radio communication
you're thinking of ELRS there
why the heck would the radio go into emergency mode..
It only did it once. Then i turned it off, back on. and it has no models, settings, etc. but boots up
after that happened is when the old sd card started working again.
i emailed radiomaster
And at least it still works for now.
@dusky tapir honestly, after this I'd be flashing latest EdgeTX xD
hmm
you may have hit a bug in 2.7.1 or whatever
they changed the UI on large screen radios tho
just sayin
i don't wanna rebind a dozen rx. lol
how is that in any way related to edgeTX?
well, i remember after upgrading my x9d+ i had to re-do all models
that was also a loing time ago
models and binding are separate issues
um, ok
lemme explain
can you help me here then?
a transmitter has a "name", in ELRS terms a "UID".
a receiver learns that name through binding (or in ELRS, through setting the binding phrase which in turn sets UID)
for FRSKY, that "name" is hardware-based and set in the factory.
The only thing you can adjust about it is the RXNum
A FRSKY radio identifies itself, to the receivers, as "name"+rxnum
um, ok then \
So even if you flash the OS of the radio, the transmitter module is still the same
and it still has the same "name"
in ELRS terms, it's very similar
it's also stored in the transmitter module itself
flashing the radio's OS doesn't change ELRS
just like it doesn't change the FRSKY's transmitter
i think i miss understood. i thouight when you upgraded software on your TX you had to go back and re-set a lot of things that are back to default
binding phase was one of them. Gues im wrong
isnt it part of every rx?
ive yet to see a rx that didnt need to be binded
Binding is the process in which a receiver learns the UID of the transmitter
in ELRS, you can set that UID on both the transmitter and receiver in advance
you said binding phrase was part of el;rs. I thought all rx's needed to be binded
ugh..
The context switching is a bit difficult here xD
You need to think of two pieces of hardware separately.
yea, im just super confused. possibly my wentire understanding of how a reciever works is not quite right.
The radio (TX16S, Boxer, etc)
the transmitter (FRSKY: XJT, IRSM, ELRS: whatever, lots, etc)
this makes me regreat gfetting a elrs whoop
?
elrs works exactly the same as frsky in regards to binding, except that it's about 10x easier..
Let's start from the basics, because you missed one very important info about radios
a radio is 2 things in one package
yea, im neaSUS AT THIS POint trying to keep up. I'm juat goiung to delete this tyhread
I appreciate your help
???
dude...
If you let me explain it to you, I will
but you completely missed one critical info about radios, which is leaving you extremely confused right now
I'd like to solve that so we can move on from that
what might have been the critical issue here?
Okay
i wonder how i made it this far not fully nderstanding how a transmitter works in both receiving and transmitting
this is the ELRS transmitter inside of your radio
Or a similar one, RM uses 2 or 3 different kinds for internal ones
ok
Just like an external transmitter (like your Crossfire unit), it lives an independent life from the "Radio"
The "radio" being the controller portion
The binding information is stored within this module, just like for Crossfire, it is stored within the crossfire module
for FRSKY, it is stored within the specific FRSKY module (internal XJT, IRSM, etc)
The transmitter module has its own UID.
For Crossfire and FRSKY, it is constant. It's set at the factory to be unique and unchangeable.
For ELRS, it is configurable.
When a receiver binds to a transmitter, it learns the transmitter's UID.
i think i was not understanding edge tx right
EdgeTX is the Radio's OS. It can direct the Transmitter module about some things (like extra binding info - RXNum), but the binding is still fundamentally the Transmitter's thing.
ok, i know that edge trx is an os. I come from freedom OS and open tx before that.
Ok cool
For ELRS, you can adjust the UID on the transmitter and receiver to match without having to do any binding shenanigans
no receiver button pressing
As long as the firmware is the same major version (v2 to v2, v3 to v3, etc), all you have to do for a standard ELRS receiver, is to wait for it to go into WiFi mode, connect to its wifi, and set the binding info there (to match the transmitter's, which you can do via its wifi network)
Normally, since people suck at remembering UID numbers, a text phrase is used. A binding phrase.
Now, EdgeTX being the OS of your radio, can be upgraded with no fear about losing binding, HOWEVER, you may lose models.
You shouldn't lose models/radio config/etc.
But you should make a backup.
whoa
EdgeTX will do its best to upgrade them.
that ulberly more complicated than pressing a bind putton
eh?
it's the simplest thing ever
i press one button wityh my rx's right now. then it just works. NO need to wait for wifi
okay, so just power up the receiver 3x in quick succession to get it into binding mode.. (assuming it has no binding phrase set)
ELRS has a traditional binding mode, for masochists..
power up the whoop 3 times in quick succession? then go into lua and bind?
setup internal module?
There's a bit of a mistake that happened a long time ago that is impossible to remedy now, we just have to live with it.
That mistake is called SPI receivers.
It's actually easier for you lol
we just live with it??
well, we can't just discard half a million whoops and tell their users to f* off?
😄
no. But, what happened here?
There is a cost-reduced variant of ELRS, where Betaflight takes over the role of ELRS receiver's brain.
One chip less.
The radio chip is directly connected to the FC.
i see that being NOT NEEDED
this is the "SPI" receiver
in that case, ELRS version depends on the BF version
and binding is done in BF
you can either input the binding prhase or use a bind button (in BFC)
idk which kind of receiver you've got
my tx has multiple elrs luas'
why?
you just need the correct LUA for your ELRS version
I see
what ELRS version is in your TX?
the ELRS one is the old one iirc
can you open up the ExpressLRS one, scroll down to the bottom, and tell me the ver?
Oh, I'm going to have to make a new model. I forgot. All my crsf ones are on a single one.
But yea, set to internal module.
Then go bind.
I like super duper appreciate your help here.
If your drone has a SPI ELRS receiver, then you need to match up the BF version with ELRS version.
BF 4.3.x - ELRS 2.*
BF 4.4.x - ELRS 3.*
quick note: SPI ELRS is broken in 4.3.2 because of fixes to SPI FRSKY 😂
If your drone has a Serial ELRS receiver, then you'll deal with it as with any standard ELRS receiver. It will go into wifi mode after 60 seconds, after which you can set the same binding phrase in there as you have on your TX.
iI ordererd the whoop 10 daYS AGO. gET FPV HATES ME. god damn caps
As for ELRS versions -
2.x.x rx will work with any 2.y.y tx
3.x.x rx will work with any 3.y.y tx
ok, the EXPRES lrs lua seems to look at what module is in the device
yeah it asks the TX module for a printout of its internal menu
for ELRS modules, you can see the firmware version at the very bottom
well, you have helped me, saved me time and taught me much
For that i am in debt to you. I will name lmy first born MAniack
As for the model issue with your radio.. keep an up-to-date backup, in case it happens again xD
pls don't, there's enough children with stupid names out there already 😂
oh, as for updating EdgeTX...
i dont even have the edge trx software on my computer. I'll downlkoad today and backup
i will also need to update my tx16s EVENTUALLY because i also have a ghost module.
thx for the link. I will read it over and apply
If you're on a MAC, Flash via USB should work.
If you're on a PC, windows f*s up the USB drivers, so you'll need to run ImpulseRC Driver Fixer before flashing
Flashing via USB is done by plugging in the data usb while the radio is turned OFF.
You can also flash it from SD card, from a bootloader mode, but considering your SD issues..
Well, I'll describe it anyway...
To access the bootloader mode:
Turn the radio off
Push and hold the horizontal trims (for yaw, roll) inwards/towards each other
Turn the radio on
that will land you in a bootloader menu
in which you can flash a file from SD card
a firmware file which you can get from the edgetx buddy I linked above
USB flashing is nice when you have a known working USB cable and know how to beat Windows over the head with a stick.
SD flashing relies on a working SD card, but can be a bit less of a pain.
I will start here.
Much appreciative of info on getting back into bootloader.
if thats not a success i will go the micro sd route
i see why you are a helper and mod now 🙂
Just to make sure nothing got mixed up:
USB flashing:
Turn radio off
Plug USB into data port
Fix windows using ImpulseRC Driver Fixer
Flash using edgetx buddy's Flash via USB button in a chrome-based browser
Ignore the SD update thing that edgetx buddy offers
Flashing from SD via bootloader:
Get firmware file from edgetx buddy using the download .bin button
Put firmware file on SD card into FIRMWARE folder
Turn the radio off
Push and hold the horizontal trims (for yaw, roll) inwards/towards each other
Turn the radio on
Navigate the bootloader menu to your firmware file
Screenshot taken. When ever my Mobettle 6 arrives I'll update it. Started flying my other whoop again now until then.

Honestly, this shouldn't affect the Mobeetle
this is just for the "omg my models are gone"
in case your issue is caused by an EdgeTX bug that got resolved in a later version
yea, I over reacted a 🤏
As for the Mobeetle 6:
I'm a bit too tired to go digging about which receiver it uses.
If it uses a SPI ELRS receiver: **
ELRS version depends on BF version.
BF 4.3 => ELRS 2.
BF 4.4 => ELRS 3.
Binding is done in BF Receiver tab.
You either enter the same binding phrase as you already entered on your TX and save,
or you press Bind in the ExpressLRS LUA and then Bind in Receiver tab.
**If it uses a Serial(UART) ELRS receiver: **
**Normal ELRS style binding: **
Power it up so that the receiver powers up (USB may be enough)
and wait for 1 minute.
You should see an ExpressLRS RX wifi network appear.
Connect to it (password: expresslrs)
In a browser, go to http://10.0.0.1
There, you can set a binding phrase.
Set the same binding phrase as you set on your TX, save.
"Traditional" binding (only works if there was no binding phrase set on the rx):
Power up the receiver 3x in very quick succession.
It should go into binding mode.
Press bind in the ExpressLRS LUA.
Notes:
In ExpressLRS LUA, you can see if the receiver is connected. It will show a "C" in the top right corner.
SPI ELRS receivers have a major limitation - they don't support Packet Rates that start with F or D.
You can se the packet rate in ExpressLRS LUA. 250Hz is recommended for SPI stuff.
Serial ELRS receivers have a status LED.
Explanation of LED:
https://www.expresslrs.org/quick-start/led-status/#receiver-led-status
You can get the transmitter module into WiFi mode from the LUA.
If a receiver is bound and connected to the transmitter module,
you can also get it into WiFi mode from the LUA.
Updating ELRS firmware for Transmitter modules or Serial receivers (not SPI) can be done via WiFi or USB (EdgeTX or Betaflight will act as a passthrough)
Don't flash or reset Betaflight without having made a backup. Make a backup of the configuration that the drone lands with from the factory.
Whoa, thank you for that information. If this goes well I will probably put elrs on all my whoops.
ELRS's slightly different process for updating/binding might seem daunting at first, but it's made to be a lot more.. modern
Well, you explained it in layman's. So I got most of it.