<html><body>
<DIV>Question: Could the JR has the same problem? Please don't start a war around brands. I just want to know if the JR could eventually have the same issue.</DIV>
<DIV> </DIV>
<DIV>--<BR>Vicente "Vince" Bortone</DIV>
<DIV> </DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">-------------- Original message -------------- <BR>From: "John Pavlick" <jpavlick@idseng.com> <BR><BR>> That makes sense. The only problem is you can't assign this code yourself <BR>> even if you could see what it is and you DID find that it was re-set to <BR>> 0000. Not a good thing. Kinda defeats the whole purpose of using 2.4GHz in <BR>> the first place. Another brilliant accomplishment for "Dr. Murphy"! <BR>> <BR>> John Pavlick <BR>> http://www.idseng.com <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 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 module, and <BR>> > is I think visible 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 is where <BR>> > the problems occur as you have no way of identifying you have a default <BR>> > code. Then you re-bind your rx and now its default as 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 code by <BR>> > re-booting your tx within 5 seconds...but the fact you cannot see if a <BR>> > problem was caused is the reason for the precaution. I think anyone who <BR>> > has to re-bind a rx that has already been bound, should have a 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 someone who has <BR>> >> screwed up their FASST system Tx (re-initialized the ID to 0000) and see <BR>> >> if <BR>> >> your Tx controls their Rx too. I'm thinking that the ID that we're <BR>> >> concerned <BR>> >> about is stored in the FASST module NOT the Tx itself though. Think about <BR>> >> it. You can put a FASST module in a 9Z. When the 9Z came out, 2.4GHz was <BR>> >> only popular in car radios. It's very unlikely that the 9Z has a unique <BR>> >> ID <BR>> >> assigned to each Tx. I could be wrong but I bet the ID is embedded in the <BR>> >> module NOT the Tx itself. One way to verify this would be to take 2 <BR>> >> identical FASST systems that are working correctly (i.e. each one <BR>> >> controls <BR>> >> it's own Rx) and swap Tx modules. If they now control the "other" Rx then <BR>> >> the ID is embedded in the module. <BR>> >&
gt; <BR>> >> Unfortunately you still can't verify that your module / Tx / whatever has <BR>> >> not been re-set to ID 0000 unless you have a known "bad" system. What a <BR>> >> bummer. The ID should be completely non-volatile, not stored 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" <VANPUTTE@COX.NET><BR>> >> To: "NSRCA Mailing List" <NSRCA-DISCUSSION@LISTS.NSRCA.ORG><BR>> >> Cc: "Mel Duval" <DUVALJ@COX.NET><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 Futaba <BR>> >>> FASST system wh
en the owner turns on the transmitter and turns it off <BR>> >>> within the 5 second "boot up" period. Namely, that the transmitter's <BR>> >>> code defaults to 0000 and the owner must rebind the receiver to the <BR>> >>> new transmitter code. However, EVERYONE who does this now has a 0000 <BR>> >>> "unique" code in their FASST system and can control other airplanes <BR>> >>> with the same code. <BR>> >>> <BR>> >>> I wonder what happens to the ordinary transmitters with a new FASST <BR>> >>> system module plugged in. Do non-FASST transmitters also have this <BR>> >>> code and, if I've turned on my transmitter and turned it off within <BR>> >>> the 5 second "boot up" period, has my transmitter gone to the default <BR>> >>> code? I know I've done this with my transmitter and I'm sure I'm not <BR>> >>> the only one. For example, I decide to do
some transmitter <BR>> >>> programming and turn on my transmitter. Then I decide to go to the <BR>> >>> mode in which my transmitter's RF section is not transmitting, so I <BR>> >>> shut it off and go to the "no RF" mode, all within 5 seconds. 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 FASST <BR>> >>> systems at local hobby shops with Futaba's "FASST test station". <BR>> >>> <BR>> >>> Ron Van Putte <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>> > _______________________________________________ <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 </BLOCKQUOTE></body></html>