dx7 keeps locking me out!

[mak24seven]

installed my new dx7 in the trex with the 6000 (dx6) receiver and no probs but today i've fitted the night3d out with the proper 2 part receiver system and its not working correct, i'm only bench setting it up and on several occasions ive turned the model on only to find its not responding to the tx, then another time its fine until its turned off and on again, when the models not responding the little light on the small receiver flashes slowly but the big receiver is lit as normal, there's only 1 niggle i've got and that's the way i've bound the system, i've not got a charging plug to plug the bind plug into from the off on switch as i'm using a regulated system so i powered up the receiver by plugging the battery lead from the switch into a servo channel and plugged the bind plug into the batt on the receiver could this be where my problem lies although like i say i have bound it successfully that way.

[ChrisB]

That is the correct way to bind in your case,i have seen this exact same problem on a fellow fliers model and re binding seemed to cure it with no problems to my knowledge since

[mak24seven]

Cheers mate at least i no its not the way i've installed the bind setup, i've just tried it again and it works, flicked it on and off 3 times all working then the 4th nothing, its still bind-ed to the tx because i left it for 5 minutes and turned it back on and it works, forget the orange light comment in my 1st post though because its also locked out with it on constant, once working its not actually lost its signal it only seems to be when its switched on and off, i've also re bound the system while its been locked out only to find it will rebind but still wont work, do u think it may be a faulty receiver?

[jamiem]

ive found that if my transmitter is within an inch or 2 of the rx('s) then they lose connection. This isnt the case here is it (being that you are setting up on the bench)?

[moyesboy]

Sometimes my Rx doesn't find the Tx immediately. sometimes I switch the rx off and back on to make it work. today i discovered that it did find the Tx after about 10 -25 seconds without switching off and on.
So far i have never had a problem flying the model (touch wood). This delayed model match happens from time to time on both raptor (AR7000) and trex (AR6200).
Unusually for us here is the back of beyond we had a lot of models in the air today. We had two heli flight points on the go and the planks on the normal patch, and four in the air on 2.4G at the same time (with others on 35Mhz), one futaba and the rest DX7.

[mak24seven]

O! seems like this is common place then, looks like i'll just have to play hit and miss with it, i've also been making sure i'm not to close to the receiver with the tx (jamiem) i'm a little dissapointed though because my old dx6 and recently my futaba 2.4ghz where faultless in every way, it must be the dx7 receiver because it fires up the dx6 receiver 100% in the trex.

[Rod]

I believe the startup process is for the transmitter to test and find two "quiet" channels in the eighty available. It then starts broadcasting the model number on both channels. When the receiver is powered up it starts listening for the model number bound to it on all eighty channels. Remember there are two receivers on an AR7000 so it has to take a little time for them both to find the pair of channels they are wrking on. I find that it is better to give the tranny a moment or two before you power up the receiver. However if it does not link straight away leave it for a few seconds and it seems to sort itself out.

I have found that you can be too close to bind a receiver, a step or two away is enough, but it may also be more about the tranny finding free channels.

In any event once bound and linked I have never ever had one single glitch or fade or any hint of radio problem.