<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word"><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content=Word.Document name=ProgId>
<META content="MSHTML 5.00.2614.3500" name=GENERATOR>
<META content="Microsoft Word 10" name=Originator><LINK
href="cid:filelist.xml@01C52E56.77621930" rel=File-List><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:DoNotRelyOnCSS/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:GrammarState>Clean</w:GrammarState>
<w:DocumentKind>DocumentEmail</w:DocumentKind>
<w:EnvelopeVis/>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
</w:WordDocument>
</xml><![endif]-->
<STYLE>P.MsoNormal {
FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; mso-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; mso-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; mso-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; text-underline: single
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal-compose; mso-style-noshow: yes; mso-ansi-font-size: 10.0pt; mso-bidi-font-size: 10.0pt; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; mso-bidi-font-family: Arial
}
SPAN.SpellE {
mso-style-name: ""; mso-spl-e: yes
}
DIV.Section1 {
page: Section1
}
</STYLE>
<!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";}
</style>
<![endif]--></HEAD>
<BODY bgColor=#ffffff lang=EN-US link=blue style="tab-interval: .5in"
vLink=purple>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=860491605-22032005>Yeah, I agree with Eric. As far as I'm concerned,
the new Futaba radio (14MZ) is really nice looking, and of course I wouldn't
mind having one BUT since I don't fly the really big stuff where 14 channels is
a big help (multiple servos on each control surface), it wouldn't be much of an
improvement over my 9ZAP. It seems like the RF section is always an
after-thought. I remember when all the "new" frequencies were being discussed
(pre 1991 times). One of the ideas behind getting all the new frequencies was to
reduce the chance of someone being on your frequency. I always thought a better
approach would have been to make everything with synthesized RF decks. Since the
plan we adopted ended up making a lot of otherwise good equipment obsolete
anyway, I don't see what the problem would have been. We wouldn't need
as many channels that way either (more room for other stuff). If you can select
your frequency, rather than just increase the odds of not being on someone
else's frequency, then the real problem is solved. I seem to recall that Kraft
had synthesized RF and "narrow band" FM equipment before anyone
else. Almost every major radio manufacturer has some type of synthesized RF
deck today.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=860491605-22032005> If you add the synthesized RF deck to a digital
encoding "code hopping" transmitter and receiver you have a good solution
to our newest problem. As long as the receiver isn't swamped by a very high
output transmitter, this is safer than what we have now. A code hopping system
uses a digital encoding scheme in addition to the base frequency. The "digital
key" changes when the system powers up. You don't even know it's
happening. Even if someone is transmitting on the same frequency, if the
"keys" don't match the receiver won't respond. That's over simplifying a bit but
that's the basic idea. There's more to the link than just the RF frequency,
which as we all know is not always exclusive. Clothes pins with channel numbers
are not exactly a foolproof method of securing your frequency. This kind of
stuff is in $40.00 cordless phones and garage door openers - remember the old
garage door openers that used to open for "no reason"? How do you think
they fixed that? Why can't this technology be used in a $2000.00 radio? If we
keep building bigger and bigger airplanes and controlling them with what is
basically outdated technology, it's only a matter of time...</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=860491605-22032005>
<P><FONT size=2>John Pavlick<BR><A href="http://www.idseng.com/"
target=_blank>http://www.idseng.com</A><BR> </FONT>
</P></SPAN></FONT></DIV>
<DIV><SPAN class=860491605-22032005></SPAN><FONT face=Tahoma><FONT size=2><SPAN
class=860491605-22032005><FONT color=#0000ff
face=Arial> </FONT></SPAN></FONT></FONT></DIV>
<DIV><FONT face=Tahoma><FONT size=2><SPAN
class=860491605-22032005> </SPAN>-----Original Message-----<BR><B>From:</B>
discussion-request@nsrca.org [mailto:discussion-request@nsrca.org]<B>On Behalf
Of </B>Grow Pattern<BR><B>Sent:</B> Monday, March 21, 2005 11:48
PM<BR><B>To:</B> discussion@nsrca.org<BR><B>Subject:</B> Re: JR
10SX<BR><BR></DIV></FONT>
<BLOCKQUOTE dir=ltr
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"></FONT>
<DIV><FONT face=Arial size=2>Bill, the update to the 10SX (actually a 10SXII)
was the digital trim 10X. </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Is the 10X what you meant to
say?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>In general terms I don't intend to buy another
radio, of any brand, until they fix the weakness of our RF link to the plane.
We can all still be radio-shot-down far too easily.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Regards,</FONT></DIV>
<DIV><FONT face=Arial size=2><BR>Eric.</FONT></DIV>
<BLOCKQUOTE dir=ltr
style="BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A href="mailto:flyinbill1@bellsouth.net"
title=flyinbill1@bellsouth.net>William C. Harden</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A
href="mailto:discussion@nsrca.org"
title=discussion@nsrca.org>discussion@nsrca.org</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Monday, March 21, 2005 9:42
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> JR 10SX</DIV>
<DIV><BR></DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10pt">Now that JR has come to market
with their new 9303 radio, does JR intend to update their 10SX radio?<SPAN
style="mso-spacerun: yes"> </SPAN>If so, when will the new radio be
available???<SPAN style="mso-spacerun: yes"> </SPAN>Just
curious.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10pt">Bill
<o:p></o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>