View Full Version : Spektrum connection speed
billcarstairs
11-16-2007, 11:17 AM
Hi
I have just received a Module for my Futaba FF9, I am using it with the new AR6100e rx fitted to a T-rex 450. After binding how long should it generaly take for the TX and RX to connect (orange light on rx to come on) mine can come on instantly or up to a minute. should the receiver or TX be turned on first (Tx is turned on last for binding) once connected everything is working perfectly.
I am also having problems with my Gaui EP100 I have fitted a AR6100e rx everything works OK until I apply throttle the as the revs increase the motor hunts and then the rx goes into failsafe. this was working ok with the Futaba R146IP.
Thanks
frebou
11-16-2007, 02:27 PM
I'm not using a module, but I don't think it should be different so here is my experience : it takes between 1 and 3 seconds. Pretty much what the manual says. sometime it is nearly instantaneous, other times it takes at max 3 seconds. alwasy fast.
fogger
11-16-2007, 02:53 PM
Tx is always turned on first. Give it a few seconds to scan and pick it's frequencies, then turn on the Rx. Should not take more than a few seconds for the Rx to sync up. If it does, shut it all down (Rx first, then Tx) and start over. I have found that firing up the Tx under a metal canopy at my field sometimes causes the sync process to take longer too, so I always turn on out in the open now.
-Fog
Things to watch out for when you experience extended sync time are how close you have the tx to the rx and what the tx and heli are setting on. If you have the tx too close, it may take longer or not sync at all. If you have the tx laying on a metal table, tail gate, tx case, etc., it may take longer or not sync.
- John
Finless
11-17-2007, 01:20 AM
This can be a common issue with DX systems. YES you are right sometimes it can take way too long to "connect" with the RX. This can actually cause a gyro init problem too... If the gyro initializes BEFORE the RX does then the gyro will not be in LOCK mode. BAD!!!
Yes I see this about 20% of the time and the only way i have solved it is by turning off the TX and back on. This usually fixes the slow RX connect time.
SO BE CAREFUL FOLKS! Understand that sometimes the DX RX may take longer than the gyro allows to initialize....
Bob
vetterick
11-17-2007, 09:52 AM
This must be caused by interference, I've never had this happen with the DX6 or DX7, allways connects within 1 second, but I fly in a sparsely populated area.
I tried to use an onboard 2.4g camera once, it took maybe 5 seconds to connect, but the range test was about 5' wthout pushing the bind button!
fxrider
11-17-2007, 10:40 AM
The DX7 has always taken a second or two to begin operating. The 9c Futaba Fasst module seems to boot faster but does hesitate on initialization as well.
Occasionally, the DX7 will not link at all until I turn the rx off and back on again. Others I have talked to have experienced the same. However, I never have encountered a problem in nearly a year.
Mike
> This can actually cause a gyro init problem too... If the gyro initializes BEFORE the RX
> does then the gyro will not be in LOCK mode. BAD!!!
During boot up the rx will put out the pulse widths learned during binding on all channels except the throttle channel (no pulses). Thus, if you bind the rx with the correct setting for gyro gain and rudder centered, the gyro should initialize just fine.
- John
Finless
11-17-2007, 12:32 PM
John, I did bind that way and for some reason if the gyro inits before the RX the 401 LED is blinking after the RX inits. I have rebound several times after getting setup and same thing.
now interesting... The AR7000 does work this way and the gyro will init. It's only the 6100 that does this????
and oh BTW I have never had a delay in RX connect with a AR7000. The problem is with the AR6100's I have.
Bob
My AR6200 connects faster then my AR7000 every time (1 sec. against 1.5-2 seconds).
And when I forget to turn tx first it does send learned signals to gyro and gyro inits ok.
AR7000 has got some strange feature. When I switch tx off, rx goes into safe mode and hold servos positions but when I turn tx on again, 1 out of 5 times rx would jitter servos momentarily and then back into positions. AR6200 does not do it.
Well, that might be the reason. AR6100 does not send learned signals all the time but jitter it at wrong time and 401 gets it wrong.
billcarstairs
11-19-2007, 09:19 AM
Hi all
Thanks for all of the suggestions, I have found if the connection is not within 3 secs, re-starting the TX seems to cure the problem. I have had no problems with the gyro, it seems to set ok even if the rx has not connected.I have had a couple of flights with my T-rex with the AR6100e and I am very pleased once the system has connected it feels very locked in and slightly faster responce.
fogger
11-19-2007, 03:45 PM
My ar7000 / DX7 has this issue on occasion. I have had times where it -never- connects, and requires several TX reboots to get straightened out. Have to assume this is due to interference and/or the Tx is picking noisy channels for some reason, or the Tx is just not transmitting right for some other reason. Hard to know for sure. This has happened at several different fields also. I've just learned to listen to the system and make sure it's behaving ok before flying...
-Fog
Pinecone
11-19-2007, 06:09 PM
Or it is possible no channels are low enough noise and the Tx isn't transmitting.