<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Atwood, Mark wrote:
<blockquote
cite="mid:99B8EFCA36A5724F87FF3C71B431D872183386A82D@PEVM01.paragon-inc.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="Section1">
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">Figures
I’d end up with a more complicated one to learn on.
I have an Escape as my first F3J plane and it’s a 6 servo
wing. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">At
the end of the day I’d be curious to know if anyone can
really “feel” the difference that is being discussed here on any of
the radio systems. Slow latency is one thing, but this channel
group delay is extremely small…hard for me to believe it’s
noticeable for 99.9999% of uses, and of the remaining 1 in a million
use cases,
how many people have the skill to detect it?<o:p></o:p></span></p>
</div>
</blockquote>
<br>
<br>
On the Escape you want to get the two ailerons on each wing half
working close together. The flaps are less of an issue as far as
"synching" with the aileron. If using aileron to flap mixing
(flaperons) you are not going to have as much flaperon throw as aileron
in the first place so any mismatches are irrelevant. On a 14MZ I would
put all 4 aileron servos in one group, both flap servos in a second
group along with rudder and elevator. But even then it would not make
much of a difference.<br>
<br>
The only time I worry about the grouping is if I am going to have two
or more servos attached to the same surface, or on surface that really
need to act in unison like split elevators. If you notice any trim
issues due to the grouping or even system latency on a F3J/TD plane
then you are a pretty special guy. I hnag around some of the better
soaring pilots in the US and the world and this is not a common topic
of discussion.<br>
</body>
</html>