<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
Correction: Those systems would damage themselves by leaving them on for longer than 5 minutes :)<BR>
<BR>
Ed<BR><BR>> From: mjfrederick@cox.net<BR>> To: nsrca-discussion@lists.nsrca.org<BR>> Date: Sun, 27 Jan 2008 20:36:57 -0600<BR>> Subject: Re: [NSRCA-discussion] Futaba FASST System<BR>> <BR>> By that rationale everyone who bought a computer with windows 95, 98, or Me <BR>> should have returned it immediately.<BR>> <BR>> I just realized that although my intent was sarcasm, that statement was <BR>> pretty much right-on.<BR>> <BR>> Matt<BR>> ----- Original Message ----- <BR>> From: "John Ferrell" <johnferrell@earthlink.net><BR>> To: "NSRCA Mailing List" <nsrca-discussion@lists.nsrca.org><BR>> Sent: Sunday, January 27, 2008 8:23 PM<BR>> Subject: Re: [NSRCA-discussion] Futaba FASST System<BR>> <BR>> <BR>> >I feel that any device that can be damaged by turning it off too quickly<BR>> > after turning it on is defective as shipped.<BR>> > We, the customers and the users are entitled to a product that works as<BR>> > advertised.<BR>> > I still love my 9Z after all these years but how Futaba handles this<BR>> > disaster will determine my future choice of equipment.<BR>> ><BR>> > I feel betrayed that they let it happen to begin with.<BR>> ><BR>> > John Ferrell W8CCW<BR>> > "Life is easier if you learn to plow<BR>> > around the stumps"<BR>> > http://DixieNC.US<BR>> ><BR>> > ----- Original Message ----- <BR>> > From: "Chad Northeast" <chad@f3acanada.org><BR>> > To: "NSRCA Mailing List" <nsrca-discussion@lists.nsrca.org><BR>> > Sent: Sunday, January 27, 2008 12:32 PM<BR>> > Subject: Re: [NSRCA-discussion] Futaba FASST System<BR>> ><BR>> ><BR>> >>I think the possibility exists to reset the code in the module if you<BR>> >> cycle power too fast. If you lose the code the binding is gone. The<BR>> >> problem is if your module resets to 00000000, and you re-bind your rx,<BR>> >> now your rx will see any 00000000 module around it, and can be shot down<BR>> >> until its re-bound to a unique code.<BR>> >><BR>> >> This is why you are being told not to re-bind the rx, and send in your<BR>> >> module (in the case of a TM-7) or your radio to be checked.<BR>> >><BR>> >> Chad<BR>> >><BR>> >> Jay Marshall wrote:<BR>> >>><BR>> >>> Reading the Futaba FASST advisory, it is not clear to me what are the<BR>> >>> results of turning the TX on and off quickly. Does it loose its code,<BR>> >>> or just the binding which would have to be repeated?<BR>> >>><BR>> >>> http://2.4gigahertz.com/techsupport/service-advisory-tm7-7c-6ex.html<BR>> >>><BR>> >>> */Jay /**/Marshall/*<BR>> >>><BR>> >>> -----Original Message-----<BR>> >>> *From:* nsrca-discussion-bounces@lists.nsrca.org<BR>> >>> [mailto:nsrca-discussion-bounces@lists.nsrca.org] *On Behalf Of<BR>> >>> *vicenterc@comcast.net<BR>> >>> *Sent:* Sunday, January 27, 2008 11:39 AM<BR>> >>> *To:* NSRCA Mailing List; NSRCA Mailing List<BR>> >>> *Subject:* Re: [NSRCA-discussion] Futaba FASST System<BR>> >>><BR>> >>><BR>> >>><BR>> >>> Question: Could the JR has the same problem? Please don't start a<BR>> >>> war around brands. I just want to know if the JR could eventually<BR>> >>> have the same issue.<BR>> >>><BR>> >>><BR>> >>><BR>> >>> --<BR>> >>> Vicente "Vince" Bortone<BR>> >>><BR>> >>><BR>> >>><BR>> >>> -------------- Original message --------------<BR>> >>> From: "John Pavlick" <jpavlick@idseng.com><BR>> >>><BR>> >>> > That makes sense. The only problem is you can't assign this code<BR>> >>> yourself<BR>> >>> > even if you could see what it is and you DID find that it was<BR>> >>> re-set to<BR>> >>> > 0000. Not a good thing. Kinda defeats the whole purpose of using<BR>> >>> 2.4GHz in<BR>> >>> > the first place. Another brilliant accomplishment for "Dr. <BR>> >>> Murphy"!<BR>> >>> ><BR>> >>> > John Pavlick<BR>> >>> > http://www.idseng.com<BR>> >>> ><BR>> >>> > ----- Original Message -----<BR>> >>> > From: "Chad Northeast"<BR>> >>> > To: "NSRCA Mailing List"<BR>> >>> > Sent: Sunday, January 27, 2008 11:11 AM<BR>> >>> > Subject: Re: [NSRCA-discussion] Futaba FASST System<BR>> >>> ><BR>> >>> ><BR>> >>> > > On the 14 (and I think the 12) the code is in the TX not the<BR>> >>> module, and<BR>> >>> > > is I think vis! ible to the user, but I am not sure where.<BR>> >>> > ><BR>> >>> > > On the TM-7 (and probably TM-8) the code is in the module which<BR>> >>> is where<BR>> >>> > > the problems occur as you have no way of identifying you have a<BR>> >>> default<BR>> >>> > > code. Then you re-bind your rx and now its default as<BR>> >>> well....so anyone<BR>> >>> > > that has a default code can now shoot you down.<BR>> >>> > ><BR>> >>> > > I don't believe there is a guarantee that you will reset the<BR>> >>> code by<BR>> >>> > > re-booting your tx within 5 seconds...but the fact you cannot<BR>> >>> see if a<BR>> >>> > > problem was caused is the reason for the precaution. I think<BR>> >>> anyone who<BR>> >>> > > has to re-bind a rx that has already been bound, should have a<BR>> >>> few ??<BR>> >>> > > dancing through their head and send the system in to ensure its<BR>> >>> > > operating properly.<BR>> >>> > ><BR>> >>> > > Chad<BR>> >>> > ><BR>> >>> > > John Pavlick wrote:<BR>> >>> > >> Ron,<BR>> >>> > >> Great question. One way to find ! out wou ld be to find<BR>> >>> someone who has<BR>> >>> > >> screwed up their FASST system Tx (re-initialized the ID to<BR>> >>> 0000) and see<BR>> >>> > >> if<BR>> >>> > >> your Tx controls their Rx too. I'm thinking that the ID that<BR>> >>> we're<BR>> >>> > >> concerned<BR>> >>> > >> about is stored in the FASST module NOT the Tx itself though.<BR>> >>> Think about<BR>> >>> > >> it. You can put a FASST module in a 9Z. When the 9Z came out,<BR>> >>> 2.4GHz was<BR>> >>> > >> only popular in car radios. It's very unlikely that the 9Z has<BR>> >>> a unique<BR>> >>> > >> ID<BR>> >>> > >> assigned to each Tx. I could be wrong but I bet the ID is<BR>> >>> embedded in the<BR>> >>> > >> module NOT the Tx itself. One way to verify this would be to<BR>> >>> take 2<BR>> >>> > >> identical FASST systems that are working correctly (i.e. each<BR>> >>> one<BR>> >>> > >> controls<BR>> >>> > >> it's own Rx) and swap Tx modules. If they now control the<BR>> >>> "other" Rx then<BR>> >>> > >> the ID is embedded in the module.<BR>> >>> >! ; >& gt;<BR>> >>> > >> Unfortunately you still can't verify that your module / Tx /<BR>> >>> whatever has<BR>> >>> > >> not been re-set to ID 0000 unless you have a known "bad"<BR>> >>> system. What a<BR>> >>> > >> bummer. The ID should be completely non-volatile, not stored<BR>> >>> in EEPROM or<BR>> >>> > >> Flash. I guess Futaba doesn't use Maxim / Dallas ID chips.<BR>> >>> > >><BR>> >>> > >> John Pavlick<BR>> >>> > >> http://www.idseng.com<BR>> >>> > >><BR>> >>> > >> ----- Original Message -----<BR>> >>> > >> From: "Ron Van Putte"<BR>> >>> > >> To: "NSRCA Mailing List"<BR>> >>> > >> Cc: "Mel Duval"<BR>> >>> > >> Sent: Sunday, January 27, 2008 10:29 AM<BR>> >>> > >> Subject: [NSRCA-discussion] Futaba FASST System<BR>> >>> > >><BR>> >>> > >><BR>> >>> > >><BR>> >>> > >>> I've been thinking about the problem that occurs with the<BR>> >>> Futaba<BR>> >>> > >>> FASST sy! stem wh en the owner turns on the transmitter and<BR>> >>> turns it off<BR>> >>> > >>> within the 5 second "boot up" period. Namely, that the<BR>> >>> transmitter's<BR>> >>> > >>> code defaults to 0000 and the owner must rebind the receiver<BR>> >>> to the<BR>> >>> > >>> new transmitter code. However, EVERYONE who does this now has<BR>> >>> a 0000<BR>> >>> > >>> "unique" code in their FASST system and can control other<BR>> >>> airplanes<BR>> >>> > >>> with the same code.<BR>> >>> > >>><BR>> >>> > >>> I wonder what happens to the ordinary transmitters with a new<BR>> >>> FASST<BR>> >>> > >>> system module plugged in. Do non-FASST transmitters also have<BR>> >>> this<BR>> >>> > >>> code and, if I've turned on my transmitter and turned it off<BR>> >>> within<BR>> >>> > >>> the 5 second "boot up" period, has my transmitter gone to the<BR>> >>> default<BR>> >>> > >>> code? I know I've done this with my transmitter and I'm sure<BR>> >>> I'm not<BR>> >>> > >>> the only one. For example, I decid! e to do some transmitter<BR>> >>> > >>> programming and turn on my transmitter. Then I decide to go<BR>> >>> to the<BR>> >>> > >>> mode in which my transmitter's RF section is not<BR>> >>> transmitting, so I<BR>> >>> > >>> shut it off and go to the "no RF" mode, all within 5 seconds.<BR>> >>> Did I<BR>> >>> > >>> just make my transmitter's code default to 0000?<BR>> >>> > >>><BR>> >>> > >>> This could be really bad if the situation I described is true.<BR>> >>> > >>> Please tell me it isn't like this.<BR>> >>> > >>><BR>> >>> > >>> BTW, check out this url: http://www.rcgroups.com/forums/<BR>> >>> > >>> showthread.php?t=807785#post9017413<BR>> >>> > >>> The thread involves modeler's experiences of testing their<BR>> >>> FASST<BR>> >>> > >>> systems at local hobby shops with Futaba's "FASST test<BR>> >>> station".<BR>> >>> > >>><BR>> >>> > >>> Ron Van Putte<BR>> >>> > >>> _______________________________________________<BR>> >>> &g! t; > >> NSRCA-discussion mailing list<BR>> >>> > >>> NSRCA-discussion@lists.nsrca.org<BR>> >>> > >>> http://lists.nsrca.org/mailman/listinfo/nsrca-discussion<BR>> >>> > >>><BR>> >>> > >><BR>> >>> > >> _______________________________________________<BR>> >>> > >> NSRCA-discussion mailing list<BR>> >>> > >> NSRCA-discussion@lists.nsrca.org<BR>> >>> > >> http://lists.nsrca.org/mailman/listinfo/nsrca-discussion<BR>> >>> > >><BR>> >>> > >><BR>> >>> > > _______________________________________________<BR>> >>> > > NSRCA-discussion mailing list<BR>> >>> > > NSRCA-discussion@lists.nsrca.org<BR>> >>> > > http://lists.nsrca.org/mailman/listinfo/nsrca-discussion<BR>> >>> ><BR>> >>> > _______________________________________________<BR>> >>> > NSRCA-discussion mailing list<BR>> >>> > NSRCA-discussion@lists.nsrca.org<BR>> >>> > http://lists.nsrca.org/mailman/listinfo/nsrca-discussion<BR>> >>><BR>> >>> ------------------------------------------------------------------------<BR>> >>><BR>> >>> _______________________________________________<BR>> >>> NSRCA-discussion mailing list<BR>> >>> NSRCA-discussion@lists.nsrca.org<BR>> >>> http://lists.nsrca.org/mailman/listinfo/nsrca-discussion<BR>> >> _______________________________________________<BR>> >> NSRCA-discussion mailing list<BR>> >> NSRCA-discussion@lists.nsrca.org<BR>> >> http://lists.nsrca.org/mailman/listinfo/nsrca-discussion<BR>> >><BR>> ><BR>> ><BR>> > _______________________________________________<BR>> > NSRCA-discussion mailing list<BR>> > NSRCA-discussion@lists.nsrca.org<BR>> > http://lists.nsrca.org/mailman/listinfo/nsrca-discussion <BR>> <BR>> _______________________________________________<BR>> NSRCA-discussion mailing list<BR>> NSRCA-discussion@lists.nsrca.org<BR>> http://lists.nsrca.org/mailman/listinfo/nsrca-discussion<BR><BR><br /><hr />Helping your favorite cause is as easy as instant messaging. You IM, we give. <a href='http://im.live.com/Messenger/IM/Home/?source=text_hotmail_join' target='_new'>Learn more.</a></body>
</html>