AR7000 lost binding with DX7 after 14 days

[psindrup]

After spending 14 days on the shelf due to bad weather I took my T-rex 500 to the local club evening event to show it to my club mates.

On of my friends wanted to see how the swash plate operates, and with the motor wires securely disconnected, I plugged in the battery - but it would not initialize. I double checked that I had the right model selected on the transmitter, that I was in throttle hold and the throttle stick was at it lowest position.

I have not yet had a chance to do a new bind, primarily because my receiver is "tucked away" behind tons of wires, and I can not connect the bind plug without taking a lot of my wiring apart.

Has anyone else experienced that a AR7000 looses its binding to/with the DX7 transmitter?

Peter

[Airboss]

you should check the remote Rx and wires. also locate your Tx in a different location during power up. when you did fist bind did you rebind as per instructions?

[TheBum]

Has anyone else experienced that a AR7000 loses its binding to/with the DX7 transmitter?
Only once, and I suspect it was due to the button on the back accidentally being pressed down when I powered up the transmitter. Is it possible you did the same thing?

[psindrup]

Thanks for your feedbacks

you should check the remote Rx and wires. also locate your Tx in a different location during power up. when you did fist bind did you rebind as per instructions?

I have only performed the bind process once, but I have had 20 successfully flights before this happened. I have tried different transmitter positions but to no avail.

Only once, and I suspect it was due to the button on the back accidentally being pressed down when I powered up the transmitter. Is it possible you did the same thing?

No, I have not done that.


Peter

[psindrup]

I forgot to mention that the lights is blinking rapidly on the main receiver and is steady on on the satellite.

Peter

[Laurens]

Its also a good idea to rebind after every small thing you've changed in the programming.

[psindrup]

Its also a good idea to rebind after every small thing you've changed in the programming.

Thanks, but why?

Peter

[joehelicopter]

Thanks, but why?

Peter
Because the Tx sees a lot of large programming changes as a Different model-you will need to re bind once in a while .

[psindrup]

OK - what do you guys do?

Do you connect a "servo extension wire" to the battery plug, and then place it on the outside of the frame, or do you just take the transmitter out if its "cage" to install the bind plug?

Peter

[JimLerch]

Anecdotal information at best, but

On my DX6i, if I copy a model from one "memory" location to another, this will require a rebind. Not saying that you did, but that is how I've experienced the need to re-bind


Also, if a model has a high difficulty in getting to the receiver, perhaps you should consider a bind switch?

(Newbie alert / question!!) There is no reason that one could not run a wire from the ground thru a switch to the top terminal on the rx power input. Turning the switch on would enable a re-bind w/o having to pull skins and wires... You would want some kind of safety switch (or better, a set of serial wired switches such that a binary address has to be entered to activated the bind process, I actually did that on a '72 Chevy Nova where the ignition switch failed. You had to know the appropriate pattern for 10 switches before it would power up the ignition :YeaBaby:)

[JC]

I forgot to mention that the lights is blinking rapidly on the main receiver and is steady on on the satellite.

Peter:thinking That's not what it should be doing. Rapid blinking happens when it's sitting ready to be bound correct?
Refreshing my memory as I type - Insert bind plug, power up Rx (both main and satellite Rx blink fast), hold bind button on Tx and power up Tx. Rapid flash changes to slow flash, then goes solid once bound.
Someone correct me if that's wrong please.

[cbflys]

Someone correct me if that's wrong please.

That is correct.

[JKos]

> Because the Tx sees a lot of large programming changes as a Different model-you will
> need to re bind once in a while .

This is simply not true! Changing the model number or name will require a rebind, but not simply changing the programming.

- John

[psindrup]

> Because the Tx sees a lot of large programming changes as a Different model-you will
> need to re bind once in a while .

This is simply not true! Changing the model number or name will require a rebind, but not simply changing the programming.

- John

That was what I thought too.

Any idea why my receiver has started to behave the way it does?

Peter

[Pinecone]

Tx only knows which model memory. You can change from heli to airplane on that model memory and the Rx will still work (no rebind needed).

Theonly ways for the Rx to become unbound are, AFAIK:

1) Defective Rx (which is what this sounds like).

2) If using DSM2 Rx, turning the Tx on with the bind button pushed. The reason for this is DSM2 Rxes do transmit a low power signal in bind mode to tell the Tx that a DSM2 Rx is out there looking to bind. If the Tx doesn't hear this signal, then it switches to DSM mode and hopes all goes well. So if yo have a DSM2 Rx bound and hit the power switch with the bind button pushed (can happen due to the Tx laying on something or other accidental pushing), the Tx will switch to DSm and the DSM2 Rx will not work.

[joehelicopter]

That was what I thought too.

Any idea why my receiver has started to behave the way it does?

Peter

Look at the bottom of page 19 of the manual and see if this is the problem assuming an electric chopper-I have been flying the DX7 for a year-you will need to rebind occaisionally-believe what you like.

[psindrup]

Look at the bottom of page 19 of the manual and see if this is the problem assuming an electric chopper-I have been flying the DX7 for a year-you will need to rebind occaisionally

Thanks. You are right. Especially regarding low throttle and neutral settings.
Quote from the manual:
"After you’ve programmed your model, it’s important to rebind the system so the true low throttle and neutral control surface positions are programmed."

-believe what you like.

Easy now :YeaBaby:

I wasn't trying to be a "non-believer" I just wanted to understand what goes on with my heli. :)

I will re-bind during the weekend, and rapport back.

Peter

PS: Joe, how does your receiver behave when it needs to be rebound?

[JKos]

> you will need to rebind occaisionally-believe what you like.

Yes, rebinding after programming is recommended and a very smart thing to do; pretty much required you could say. However, it does NOT stop working just because you make programming changes, period. The system will still connect and work.

You can do whatever you want to the programming and the system will connect and work. You can even change the model type and it will still work.

> how does your receiver behave when it needs to be rebound?

A receiver which needs rebound will usually have no LED indication. You may see a quick flash of the LEDs when the rx is powerd up, but then they will not come on after that.

- John

[Stallion]

I would like to chime in here!

I have the same binding problem. If it binds correctly then i can usually fly without problems for several flights. But once and a while the secondary Rx will not initialise the main Rx goes solid an the secondary keeps flashing but very weak.

Ok than usually i start to rebind. As per manual instructed. Right now the secondary Rx won't bind. it starts flashing whenn i turn on the power to both Rx and then it keeps flashing very weak an very slow. the Main Rx stays in bind mode and goes solid after a while.

I realy starting to hate that thing. It is the first sunny day in over 2 weeks and now i can not fly my bird because of that crappy Rx :-(

Any one any ideas?

[dennis22g]

I have a 6100 question. Most times when I turn on the receiver has a continuous led. OK.
However occassionally, mostly after a quick battery change, the receiver has a slow flash.
Not like the flash when binding. When binding there are two speeds, first rapid, then medium. The flash speed I experience is about .5 sec on then .5 sec off continuously. The heli flys ok but I think its a bit risky. To stop the flash, I have to disconnect the battery for about 60 seconds or so.
Does anyone know what it is? Maybe a bad receiver?

[Pinecone]

v1.6 firmware.

See my reply to your other post of the same question.