<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1170" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Georgie,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I won't jump on you too hard...as that's one way to
do it....</FONT><FONT face=Arial size=2></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>But the maneuver can be flown various ways with a
longer 45 and tighter loops.......You can't make a statement that this is the
way its suppose to be....because not everyone will fly it that way.
</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>BY the rules...the pilot need only maintain
constant radii, a visible 45, a visible vertical 2/2 on the upline, a visible
vertical, and center the whole maneuver.....That's it!......You can't dictate to
the pilot how to do it beyond this. This is the rule book explanation nothing
more and nothing less. In fact the rules say that the judge is not to downgrade
based on the radii size and line length is not a judging criteria unless there
are geometry issues that require same line lengths. Power of one model is not a
criteria over the lack of power in another model as long as geometry is
preserved.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Are you advocating new judging criteria that is not
in the book?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>You know I love ya Georgie!</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Troy</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=geobet@gis.net href="mailto:geobet@gis.net">george kennie</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=discussion@nsrca.org
href="mailto:discussion@nsrca.org">discussion@nsrca.org</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, May 28, 2003 11:18
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: JR "Unplugged"</DIV>
<DIV><FONT face=Arial size=2></FONT><FONT face=Arial
size=2></FONT><BR></DIV>Don, <BR>Thanks for taking the time to respond. It was
not expected, but appreciated. I have your responce printed out for reference.
<BR>I also received an additional help from another concerned individual who
sent me an article from Horizon on programming the 10-X which just happened to
be 35 pages in length, but I was unable to print it. It activates a
non-accessable dialogue box. Duh! <BR>Regarding switch assignments: E-F, MD,
LD, MX, AU, GR, SNP, STK,......I'm aware that MX refers to the mix switch, GR
the gear switch, SNP the snap switch, and STK the throttle lever, but am in
the dark regarding the rest. Could you define E-F, MD, LD, AU, .......AU
sounds like it would be an Auxilliary switch, but which one? Also, is it
possible to assign anything to the Flap Switch (not the flap lever), the one
that says "elev and land" beside it? <BR>Thanks for explaining "Normal,
Include, and Origin" . <BR>I'm using the Elev D/R switch for activation of my
flight mode which prompts me to ask, are you flying mode one or two? <BR>On
the subject of the mousse can, the one I had on my Schmooze is going on a new
airplane this season so I have gotten more longevity from it than I originally
anticipated. <BR>Oh, while I've got you, that #10 maneuver in F-03. I got
thinking about that the other nite and it occurred to me after drawing out
several variations of the maneuver that if the loop portion of the maneuver is
sized so that the bottom of the loop is at the same altitude as the entry
line, then the vertical up becomes the absolute center of the maneuver no
matter what size you make the overall maneuver. Makes it very easy to judge
the center of the maneuver, for both the pilot and the judge. Troy's probably
going to jump in here and complain about too much detail, but as a judge I
feel every maneuver needs an absolute standard to be judged against.When
there's too much subjectivity allowed everybodys personal bias gets thrown
into the mix and interpretations run wild.Draw this out at a few different
scales and you'll see what I mean. <BR>Thanks again, <BR>Georgie <BR>
<P>don szczur wrote:
<BLOCKQUOTE TYPE="CITE"> <FONT size=-1>Georgie,</FONT> <FONT
size=-1>I'm really sorry you are having difficulty with programming, I'll be
happy to show you next time we see each other. Never having done
airbrake before (if you mean both ailerons up like when landing), I just
turned it on and programmed it with the following:</FONT> <FONT
size=-1>With the airbrake coming on at low throttle like when landing, here
are the following steps (assuming you have wing type set to
flaperon):</FONT><FONT size=-1>Pick a mix (I used 51) select throttle
---> flap. Go to "ORIG". then page back and hit the offset (I
normally give it two clicks of throttle) then enter the percent mix (that
you want the ailerons to go up). Ooops, wrong direction ailerons are
going down, just hit the "turn" button. Done! Want to turn it
on/off with any switch? Just hit the page button and select one.
BTW, "ORIG" is used so that if you have to make trim changes to
throttle, it won't effect the mix, just takes the raw stick movement.
Norm, is normal stick and trim and INCL adds in everything you have tied to
it (like mixes).</FONT> <FONT size=-1>Don't want associated airbrakes
with throttle stick position? Then just do the same 51, and mix gear to
flaps (or any free channel to flap), and you're there. Bump up the %
to where you want it. Done. In fact you can assign this to most any
(gear, aux 2, aux 3, aux 4, aux 5) switch/lever by assigning therefore, and
then going to your favorite code 17, disactivating the (master mix
channel).</FONT> <FONT size=-1>Switch assignment- mixes can be assigned
to any of your switch/lever of choice (E-F, MD, LD, MX, AU, GR, SNP, and
stick position).</FONT> <FONT size=-1>Its harder to describe than to
just dive in and program with the touch screen.</FONT> <FONT
size=-1>The 5 flight modes that are available can be used for different
setups (if you want to experiment trying different combinations during a
flight for example) Its an incredibly potent radio. BTW, To get the
extra two rates, go to your favorite function 17 and select "extra" and
you'll see FM3 and FM4 appear in your Dual Rate/Expo (Code
13).</FONT> <FONT size=-1>I've set up 5 flight modes before. For
example on my TOC plane I have normal flying (F0), 4 roll circles (F1), One
roll circles (F2), 3D/ Freestyle (F3), and alternate 3D/ Freestyle
(F4). Note for the back right switch, it gives you F0, F3 and F4, so
you can always go back you your baseline F0 with just one switch
movement. Transmitter beeps if you turn it on and switch rate position
is other than F0.. Useful if you don't want to take off in 3D
mode.</FONT> <FONT size=-1>I will say, however, its up to personal
preferences. For example, on my pattern plane, I prefer just one
switch (the aileron D/R) for changing all (Ail, elev, rudder) rates from low
to high. I make the centers the same (double expo on high) so I can
switch rates during a maneuver, in fact even during a (loose) loop radius,
and it will have the same feel and not "jerk" when I change rates. If
I could get by with just one rate and no switches at all, I would.
Chip does. Some pattern plane designs are already there.</FONT> <FONT
size=-1>BTW, still have the double moose can muffler (as a spare)that I made
from your great idea in case the multi $$ ES pipe fails.</FONT> <FONT
size=-1>Don</FONT>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"><B><FONT
face=Arial><FONT size=-1>-----Original Message-----</FONT></FONT></B>
<BR><FONT face=Arial><FONT size=-1><B>From: </B>george kennie <<A
href="mailto:geobet@gis.net">geobet@gis.net</A>></FONT></FONT>
<BR><FONT face=Arial><FONT size=-1><B>To: </B><A
href="mailto:discussion@nsrca.org">discussion@nsrca.org</A> <<A
href="mailto:discussion@nsrca.org">discussion@nsrca.org</A>></FONT></FONT>
<BR><FONT face=Arial><FONT size=-1><B>Date: </B>Tuesday, May 27, 2003 1:12
PM</FONT></FONT> <BR><FONT face=Arial><FONT size=-1><B>Subject: </B>Re: JR
"Unplugged"</FONT></FONT> <BR> I feel compelled to interject at this
point that my experience with the JR 10X programming has not been
the piece of cake that others seem to find it to
be.</BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>