<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Lucida Console";
panose-1:2 11 6 9 4 5 4 2 2 4;}
@font-face
{font-family:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
/* 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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Lucida Console";
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
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]-->
</head>
<body bgcolor=white lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=blue face="Lucida Console"><span
style='font-size:10.0pt;font-family:"Lucida Console";color:blue'>As Richard
mentioned, the main drawback to this approach is that it eats up pretty large
chunks of EPIC MRB namespace since you have to have a separate switch MRB for
each position the knob can take. But, if you are namespace rich this can
work well enough if you have knobs that spin all the way around without
encountering a physical end stop. I’ve done it in a test setting
with EPL code and a 6 place knob; kind of coarse feel compared to a real
encoder but workable and cheap compared to real encoder solutions.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Lucida Console"><span
style='font-size:10.0pt;font-family:"Lucida Console";color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Lucida Console"><span
style='font-size:10.0pt;font-family:"Lucida Console";color:blue'>For what
it’s worth, we have several actual encoders mapped into our EPIC setup
using the BlueSideUp rotary encoder module. That one is a good deal
cheaper than the RnR equivalent module and seems to work pretty well. If
feel and fidelity matter to you, I can tell you from hands-on experience that
going with real encoders is much, much nicer than the
rotary-switch-as-substitute approach and the best part is that the EPL code for
encoders is trivial by comparison…we are MRB namespace rich since we use
two expansion modules (vice usual one-only setup) but we are code size
poor…the compiled EPL code is almost bursting out of the EPIC USBs
capacity already so to us, it was a code-size necessity to go with proper
encoders in the end. Just one more consideration for you to factor in I
guess.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Lucida Console"><span
style='font-size:10.0pt;font-family:"Lucida Console";color:blue'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal><font size=2 color=blue face="Lucida Console"><span
style='font-size:10.0pt;font-family:"Lucida Console";color:blue'>Cheers,</span></font><font
color=blue><span style='color:blue'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face="Times New Roman"><span
style='font-size:12.0pt;color:blue'> <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Lucida Console"><span
style='font-size:10.0pt;font-family:"Lucida Console";color:blue'>Mark.</span></font><font
color=blue><span style='color:blue'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face="Times New Roman"><span
style='font-size:12.0pt;color:blue'> </span></font><o:p></o:p></p>
</div>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> Steve Wilson
[mailto:mafsix@hotmail.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, February 05, 2004
1:25 PM<br>
<b><span style='font-weight:bold'>To:</span></b> Simulator Cockpit tech list<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [simpits-tech] rotary
encoder</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>I've seen a lot of rotary encoder stuff in the group, and
until recently, I didn't understand what the fuss was all about. With
recent dialogue, I do - as far as what key combo is sent depending on which way
the knob was turned.</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>This was something I always intended to take care of with
some sort of simple rotary switch and my EPIC. Say you have a rotary with
10 contacts. That's 10 separate connections to the EPIC, and in the EPIC
program, all one would need to do is set up some fairly straightforward logic
to analyze where the rotary is at. If the program simply stored the value
associated with the current position of the knob, and when a different contact
of the 10 was detected, it would be compared to the previously stored value,
which would determine which way the knob was being turned. This would
give EPIC enought data to send whatever the appropriate key combination was for
increment or decrement.</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Is there a flaw in this thinking?</span></font><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Steve W.</span></font><o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>