Binding 2 RX as same time...

[coolrunner]

Sorry if this question was already post here but I got a little problem.
I got a second rx and I use a spectrum module tx system so do I have to bind the 2 rx same time to make it work or should I have to bind any time I change the heli??
tom

[fogger]

Bind each one seperately. Not sure if your TX spektrum module has the "model match" feature like the DX7 and X9303, but you should set the TX to control the model who's RX you are binding, -before doing the binding sequence- just in case.

-Fog

[coolrunner]

Yeah but I didn't know if the module system has this possibility to bind each model?
Sorry I posted it two times did you know how to take one out??
tom

[fogger]

you only have to bind each receiver once. Just make sure your controller is set to control the correct model before binding. The model match uses a different GUID for each model so you can't accidentally fly one model with the wrong one selected in the controller... Not sure how else I can explain it, but you do not have to d anything to your original RX if it is already set up and working properly.

-Fog

[Pinecone]

Actually you need to bind more than once.

But, the binding has to do with the Rx only, so you can bind any number of Rxes to one Tx. The modules do not have model match, so you COULD bind an Rx to one model and fly it set to another one. I tried that last week. :)

OK, why bind more than once. You need to bind the Rx to start so you can setup. Once you get the heli setup, you need to bind again, to make sure the Rx remembers the proper settings.

The Rx outputs the stick positions, as you had them when you last did the binding, for the period between power up and linking to the Tx. Except for the throttle, which gets no signal.

The Rx uses the throttle position at binding for Fail Safe when the Rx loses the signal.

So you need to bind at least twice. Not a bad idea to bind after getting the throttle/ESC setup to set the fail safe early.

And no, you do not have to bind the Rxes at the same time. The bit with pushing the bind button on the Tx is to send info on a channel for any Rx in range inbind mode to pick up to do the binding.

[Pinecone]

Answered in your other thread.

[Gino CP]

"so you COULD bind an Rx to one model and fly it set to another one" <---can you tell us what you mean by this?

[Pinecone]

You could bind your Rx to your Tx (module setup ) with model number 1 selected. But then change to model number 2 on your Tx and try to fly. Of course the setup would be wrong and with a heli it will not be pretty. Same as you could with 72MHz. You need a dedicated Tx like the DX7 or X9303 to have model match.

With model match the Rx will only resond if the Tx has the same model selected as the Rx was bound to. It sort of makes it work like each model memory is a separate Tx and the Rx will only respond to that one.

[fogger]

At least with the ar6000 and ar7000's that I use the only thing binding sets is the default servo positions (what it drives them to while waiting to link to the TX) and the failsafe throttle position. If your TX is set up approximately right before binding, maybe with the exception of a few clicks of sub-trim to get the servos perfectly level at center stick, you technically only need to bind once. As long as you remember to have the tx in either TH or zero throttle during the first bind, you are good to go. It doesn't need to have perfect servo positions on startup... Failsafe on these RX's maintains last known good servo position and goes to the throttle position set at binding.

-Fog

[Pinecone]

How about the tail? :)

[fogger]

still working like a champ, thanks for asking ;)

[Pinecone]

No, I mean making sure the bind position for the tail channel and the gain is proper.

[fogger]

Just messin with ya Terry...

It's moot I'm sure; you would never initialize your heli without the TX on, so why does the gain setting at binding matter? And rudder, like all the other channels besides throttle, goes to "last known good" on failsafe. Am I missing something in the question?

Anyway bind as often as ya like, it only takes a minute. Just be sure your throttle is zero when you do, and you're on the right model if you have model match.

-Fog

[Danal Estes]

It's moot I'm sure; you would never initialize your heli without the TX on, so why does the gain setting at binding matter?

Because, even with the TX powered up first, the RX takes a few seconds to 'find' and 'link to' the TX. During those few seconds, the Gyro has already begun to initialize... depending on time to full link, the gyro may even fully init prior to RX/TX linkup.

As you mentioned, the RX outputs "memorized at bind" positions during this time, from power on until linkup. Therefore, it is essential for most gyros (and specifically for the GY401), that the rudder channel center be correct, and the gain channel be somewhere in the HH area, at bind time.

[fogger]

If your rx is taking that long to link up then you have a problem and you should investigate it, not rely on the binding state of the channels to help you out.

-Fog

[Pinecone]

Some 6100s have been taking 3 - 5 seconds to link.

A lot depends on what channels the Tx picks. The Rx has to scan for the Tx.

[fogger]

if my 7000 takes more than 3 seconds, I shut everything down and start over. It may take a few tries but often I get it to sync in under a second. 5 is way too long and you are going to risk interference / lockouts IMO. If everything is happy, and the channels are clean, it just should not take that long.

-Fog

[Pinecone]

The 6100s are different.

But even so, you want the gyro to see a steady signal during initialization.

[Danal Estes]

So fog, if you get a link in 1 second... you'd be OK with the GY401 'seeing' one set of signals for rudder neutral and gain for 1 full second, then a different set (from the TX) during second number 2, while the gyro finished init?

Getting a gyro to init properly (and avoiding a linkage jam on servos) is the whole reason Spektrum designed the system to output "memorized at bind" from the instant of power up. Whether its 1 second, or 2 or 3, the Gyro needs the same signal it's going to later get from the TX.


And, your statement about a longer linkup having higher risk of lockout... on what do you base that statement?

[th3tick]

Actually, Danal, what you're saying makes perfect sense to me. When I first set up my 450, which uses a 6100, it would frequently do the slow-bind, and end up with my GY401 blinking. Given its location under the boom, I often wouldn't notice this until I was off the ground.

Later on, the 6100 lost its binding for some reason, so I re-bound it. Since then, I've never had the issue with it coming up seeing rate mode, even though, presumably, the late binding is still happening sometimes.

So, re-binding "fixed" my tail issues. I just never knew why until now!

John

[Pinecone]

Not having the proper rudder stick position set at bind measn the gyro may see differing positions, like wiggling the stick while initializing.

[WillJames]

I have seen in the last couple weeks that an AR7000 was taking long enough to link/bind or whatever that a 401 would not go into heading hold and everything had to be cut off and then turned back on a few times to get the gyro ti init properly in HH. It was discovered by the pilot that if he placed his X9303 closer to the model, it would bind/link or whatever faster and the 401 would get the solid red led the first time most times.

If the TX was more than a few feet from the model, 401 would init in flashing led (Normal Mode) mode about 3 out of 5 turn-ons. I found it to be interesting.

[fogger]

The futaba gyros do not init as soon as they get power, rather there is a noticeable delay. Esp my 611, sometimes it doesn't init for several sec after the rx does. Set it up how you want, I'm just saying in my exp it's not as critical as some would lead you to believe, and frankly it's more important that your rx links up fast and sees your real tx settings.

My experiencce with long sync times has shown me that the model often behaves less than "dialed in" after a long sync startup. I have had times where it literally felt like there was added delay in the control, as though there were missing packets of data or something. This tells me that the link between the tx and rx was not as solid as it should have been. Eventually I connected the dots and realized what had been happening and now I listen to the system more carefully when starting up. When it sync's fast, the heli feels almost telepathic in control speed.

Take it fwiw, that's just my experience over the last year and a half and probably about a thousand flights on spektrum...

-Fog

[Pinecone]

The 401 is undergoing init for that entire tire. Just like you tell people to not move the heli or the rudder stick during that time, having different rudder settings at bind versus what you end up with is like moving the stick.

But the slow sync can be a sign of link problems. ALthough I have seen reports of slow synch with the Tx too close, or if under a metal canopy. Or it could be that the picked channels are as noise free as we would like.

I wonder if the Tx actually scans all the channels and picks the best two, or if it picks the first two that are reasonable?

[fogger]

good?. In my estimation, if it "listened" carefully to every channel before picking the best two, rather than just picking two that it diesn't see another spektrum signal on, there would be less probability of it picking "dirty" channels. It seems to me, picking bad (interference laiden) channels would be the most likely reason for long sync times and poor rf link performance. That's obviously speculation on my part...

-Fog