dont know if you oaks knew this... I have an AR500 and AR6100e receiver... I bind them separately and I can use both without binding again, while the other one is off off course... O, this is with a DX5e... its like model memory or something hidden? whats the take on this...

Odd... The DX5e only has a single model memory so I would have expected you to have to rebind every time you changed receiver (which wouldn't be a huge issue as long as your charge socket was easily accessed). If it's working for you that's fine, just make sure to range check every time you fly and I'd avoid having both receivers turned on at the same time.

I think perhaps you guys are confusing "model memory" with 'model match".

The "bind" tells the RECEIVER to listen to a particular transmitter (Identified by a GUID - Globally Unique ID), and no other transmitter. It does NOT tell the transmitter to speak only to a particular Rx.

The "Model Memory" doesn't have beans to do with which receiver is in use. It simply stores settings...trim, mixes, reverses, etc. The fact that the Dx5e has only "one model" simply means that whatever trim or other settings you've put into it will be in use for ANYTHING you fly with it. It does NOT mean that it will only speak to a certain Rx.

All that's happened is that you've told 2 Rx's to listen to a particular transmitter. nothing strange about that at all.

Now, on the radios with multiple 'model memory", there may be some sort of "model match" feature (on the Dx6i, for example). Again, there's nothing in the TRANSMITTER that says "only speak to this Rx when on this model". it's all in the receiver. As part of the bind, the Rx is told not only to only listen to Transmitter X, but only listen to it if it tells you it's on model #1.

Even in this case, you could certainly have two Rx's bound to the same model...just bind them. once again, all you have is two receivers that are told to listen to a certain radio on a certain model.

Just so I understand this, the reason my DX6i doesn't talk to more than one RX at a time is the model match feature, and NOT the bind feature? (I have 2 AR6200 RX's bound to it, on two of the model memories, and they will not work unless the correct memory channel is selected.)

Correct...sort of.

The reality is that your DXAnything will talk to any number of Rx's that feel like listening. Heck, it'd talk to 100Rx's if they were all told to listen to it.

"Bind" tells a Receiver to LISTEN to only one transmitter...it doesn't tell the TRANSMITTER a darn thing.

Consider this:

Transmitters transmit, Receivers receive. If either of them did both, they'd be Transceivers. You can see a very basic "proof" of this by asking yourself the a simple question:

1) Why, when I "bind" to a new Rx, do I have to look at he RECEIVER to know when it's bound? (The light stops flashing) how come the Transmitter doesn't stop binding when the bind is achieved?

1a) because the Rx has no way to 'transmit" the info that it's bound...and even if it did, the transmitter has no way to "receive" that information. the transmitter doesn't KNOW when a bind is achieved...only the Rx knows that. So, lacking the ability to 'tell" the transmitter, it tells YOU...by stopping blinking.

"Model Match" is what tells a RECEIVER to listen ONLY at a given time...when the right model is selected. The transmitter transmits not only ITS GUID (Hi, i am the transmitter you promised to listen to) but ALSO a packet of information saying what model it's on. ("I'm using model #2 currently")

It goes basically like this:

Say I have 2 pieces of paper, a black one and white one, one in each hand. When I first contact you, I say "Listen exclusively to me, but only if I'm holding up the black paper." You say "Ok. Got it."

Then I approach Switch_639, and say "Listen exclusively to me, but only if I'm holding up the white paper." and he says "Ok. got it."

You're BOTH "bound" to me...when you said "Ok, got it" we had successfully completed a bind. Neither of you will listen to anyone else.

But if I say "Hey, hop on one foot" while holding up the white paper, you'll happily ignore me...because you don't see the black paper. THAT'S model match.

Take the papers out of the equation, and replace our 'bind" with "Listen exclusively to me." and you have a single model DX5e

The only thing left now is "model memory"...which is nothing more than the TRANSMITTERS list of various settings for a given model. It "remembers" that, if transmitting on Model #5, the trims should be thus, so and so servo is reversed, and 5% of up elevator should be mixed in with rudder. Again, note that ALL of these are things that are TRANSMITTED to the airplane...none of them depend on which receiver is listening.

Just always remember...It's a uni-directional link. Information ALWAYS goes FROM the Tx TO the Rx, NEVER the other way. Keep that in mind, and you'll see why a whole bunch of things that we have fancy names for (fail safe, model memory, model match, etc) happen the way they do.