Magic QX7?

[Andy7]

One of the nice things about having a FLEET of quads is that you can mix it up a little while out flying. I was alternating between my Marmotte which has enough heft to carry my RC3 and the Airo 4" for the spicy suff, if you dont mind goggle recordings.
It was only when I was a few packs in that I realised that I hadn't changed the model on my QX7 between the two quads.
I thought that each time you bound an RX (xm+ micro in my case) that it was assigned a unique code so that this kind of thing wouldn't happen - now, I'm not compaining TOO much cos it's one less thing to have to do to swap models, but what if it interfers with someone else?

What gives?
 

[Bad Raven]

You are talking about two completely different things.

When you bind a FrSky receiver a model memory number is allocated. This is separate from the bind.
Depending on the age and type of FrSky Transmitter, the model number may increment up to the max models allowed, or may not, leaving you to set it. It is shown in the Tx bind area.

Each receiver bind however uses far more and so is pretty much unique.

Each Model Memory number will not be, but its only used to separate the models on YOUR Transmitter.

[badger1]

Each Model Memory number will not be, but its only used to separate the models on YOUR Transmitter.

ah, but when you bind, you can optionally set an Rx ID to stop you accidentally controlling the wrong model with the wrong Tx model profile.

I presume that every Tx has a globally unique identifier (somewhat like an ethernet MAC address) & that when you bind an Rx to the Tx, it binds to TxID+RxID (where RxID is probably 0 by default).

but regardless, as you say, once bound an Rx will only listen to the TxID(+RxID) that it's bound to.

@Andy7 - don't accidentally have two quads powered on at once or you might have a bit of a surprise when you take off   

[Andy7]

Thanks for the replies.
SO... Whatever happens, only MY TX will (normally) ever talk to the RX that I bound to it, and the model number doesn't necessarily matter.
It's still a single unique bind code, that will be the same with whatever RX I bind to it and the MODELS are just for various configurations according to whatever is unique about the model you're flying?

That kind of makes sense. Nope, I'm never going to have more than one of my quads powered at any one time - but now I'll know to make sure I'll NEVER do that.

Cheers, learned something today! 

[badger1]

It's still a single unique bind code, that will be the same with whatever RX I bind to it and the MODELS are just for various configurations according to whatever is unique about the model you're flying?

it's not such a big deal with quads as the inputs are pretty well standardized, but with planes which have many variations of physical linkages, it's very possible that roll/pitch/yaw may be reversed from one model to the next, which can be disastrous if you take off with the wrong model selected.

[Bad Raven]

ah, but when you bind, you can optionally set an Rx ID to stop you accidentally controlling the wrong model with the wrong Tx model profile.

That is what I said, almost.......... The point is that the model memory number is set and recorded regardless of user action, its not optional yes or no as could be read from above. The Tx will always allocate a model memory number, which you may or may not influence.

SOME FrSky Tx incremented the number each time, but that does not help once you reach max or when you want to replace a model. During Horus X12S Beta we tried a range of ways of semi-automating the number order, but all have traps.

Many years ago Futaba came unstuck when they issued some 2.4GHz 6EX with a common default bind ident. (I had one briefly!!) If two or more of those appeared at the same field, and it did happen, one Tx could jam/control the others receivers.  They had to actually REPLACE the Tx's as the fault was not locally alterable!!   That of course left the possibility of an owner missing the "recall", and two faulty Tx appearing months or years later. STILL a possibility!

Spektrum was the first mainstream manufacturer to add model memories to their ident system. Futaba were quite slow in doing so.  My top end (then) 10CG does not!

The only real way to ensure no model clash/duplication occurs on your Tx is to keep a list of what numbers are used. I have spreadsheets for each Tx type.

There are people who group model types, and quads are a type that generally have FC set individuality so one memory for many is sometimes used.

[badger1]

I think we're maybe talking at cross-purposes here.

this is what I mean by model # - which is just the number of the profile stored on the Tx:



& the Rx # which causes a model to bind uniquely to that Tx & Rx #:



although you could still (I think) use the same Rx # on multiple profiles.

I tend to use Rx # 0 for all my models.  I have been known to take a plane out to fly with the wrong profile selected on my Tx, check all the control directions, which just happen to be right by chance, & then take off & wonder it's wildly out of trim.      

[daich]

i used to have a model for each craft.
Nowadays I have one model for each protocol - D16, D8, Crossfire, Bayang, etc...
This only works if I keep the betaflight set ups in the mode tab the exact same for all the models.

i've only had to add models for exceptional set ups like kiss.