<html>
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 10 (filtered)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Brush Script MT";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p
{margin-right:0in;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle17
{font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:.2in .25in 33.1pt .25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Reading the Futaba FASST advisory, it is
not clear to me what are the results of turning the TX on and off quickly. Does
it loose its code, or just the binding which would have to be repeated?</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>http://2.4gigahertz.com/tech</span></font><font
size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'>support</span></font><font size=2 color=navy face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:navy'>/service-advisory-tm7-7c-6ex.html</span></font></p>
<div>
<p><b><i><font size=4 color=navy face="Brush Script MT"><span style='font-size:
13.5pt;font-family:"Brush Script MT";color:navy;font-weight:bold;font-style:
italic'>Jay </span></font></i></b><b><i><font size=4 color=navy
face="Brush Script MT"><span style='font-size:13.5pt;font-family:"Brush Script MT";
color:navy;font-weight:bold;font-style:italic'>Marshall</span></font></i></b><font
color=navy><span style='color:navy'> </span></font></p>
</div>
<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'>-----Original Message-----<br>
<b><span style='font-weight:bold'>From:</span></b> </span></font><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>nsrca-discussion-bounces@lists.nsrca.org</span></font><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> [mailto:</span></font><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>nsrca-discussion-bounces@lists.nsrca.org</span></font><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>] <b><span
style='font-weight:bold'>On Behalf Of </span></b>vicenterc@comcast.net<br>
<b><span style='font-weight:bold'>Sent:</span></b> Sunday, January 27, 2008
11:39 AM<br>
<b><span style='font-weight:bold'>To:</span></b> </span></font><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>NSRCA Mailing
List</span></font><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma'>; </span></font><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'>NSRCA Mailing List</span></font><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'><br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [NSRCA-discussion]
Futaba FASST System</span></font></p>
<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'> </span></font></p>
<div>
<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>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.</span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'> </span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>--<br>
Vicente "Vince" Bortone</span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'> </span></font></p>
</div>
<blockquote style='border:none;border-left:solid #1010FF 1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-bottom:5.0pt'>
<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>-------------- 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" <br>
<CHAD@F3ACANADA.ORG>> To: "NSRCA Mailing List" <br>
<NSRCA-DISCUSSION@LISTS.NSRCA.ORG>> 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 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 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" <br>
<VANPUTTE@COX.NET>> >> To: "NSRCA Mailing List" <br>
<NSRCA-DISCUSSION@LISTS.NSRCA.ORG>> >> Cc: "Mel Duval" <br>
<DUVALJ@COX.NET>> >> 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 sy! stem 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 decid! e 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>
&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 </span></font></p>
</blockquote>
</div>
</body>
</html>