Hi Guys in my experiements with adapting the systems to existing  carbon nose 
cone and canopy style fuselage saiplanes, I ran across this  weird phenom:

IF I turn off the power the RX's with the TX on....then turn the power  back 
on, the remote RX's light flashes slowly. Even if I power the RX system off  
again multiple times, the same happens.

I didn't know what that meant or  if it when it happened would it cause a 
problem for me.
I found that to stop  that from happening, I have to also turn off the TX 
each time I power off the  RX's.

I didn't find anything in the manuals about the light flashing  slowly on the 
remote RX, which is different than during the 'binding' process,  which 
causes all the lights to blink rapidly...
 
So I asked the experts at Horizon...here's the scoop, its actually an extra  
cool feature that can help with identifying bad switches and battery wiring  
plugs.  A heavy load can cause a momentary loss of all power if the switch  is 
funky or a plug pin wallowed out (or one of the power wires is  frayed 
inside). Even though it was created for that purpose! Plenty of plane  never 
came out 
of the bucket on launch because of this.
Take a look at the info and link below...even if you haven't jumped  into 2.4 
of any brand take a look at the Link Bar called Spektrum Community sub  
categories.... good to know as much as possible about 2.4 before you  buy.

Gordy
 
That flashing is called quick-connect. It lets you know if the voltage  
momentarily goes below 3.5v. Previously when power loss/drop happened it would  
take 2 to 4 seconds for the receiver to “re-boot” and sync up with the tx 
again. 
 This would sometimes cause the loss of a plane, so we developed this new  
feature. Here is a link to more detailed info.
_http://www.spektrumrc.com/Articles/Article.aspx?ArticleID=1756_ 
(http://www.spektrumrc.com/Articles/Article.aspx?ArticleID=1756) 
 



**************It's Tax Time! Get tips, forms, and advice on AOL Money & 
Finance.      (http://money.aol.com/tax?NCID=aolprf00030000000001)

Reply via email to