[simpits-tech] Servo Driven Gauges and MFD/HUD data

Sat, 8 Jun 2002 08:11:01 -0500

This is a multi-part message in MIME format.

------=_NextPart_000_0008_01C20EC4.0A354F80
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Why is this feature so complicated? The MFDs show up in the Black boxes
that are located in the "virtual cockpits". If you have ever looked at
the virtual cockpit graphics, all of the gauges are blacked out so the
software can generate the flight info in the black areas. Somehow a
function places them in a position that is "cut out" for them. It varies
from virtual cockpit to virtual cockpit, or even from view to view.

Now if they are adding multiple monitor capability, why not have a view
that is just the LEFT and one that is just the right MFD? This would be
simpler than pulling the raw data out of the code.

This is a question, I am sure its more complicated than that.

Chris Crowley

Chris, I agree with you totally, it shouldn't be that complicated.  This
is my thought.  If there will be multiple monitor option available, it
shouldn't be that difficult to bring up MFD/HUD data into a monitor of
its own.  Now, there are plenty of LCD's out there that are about the
size of MFD's and these use pretty standard NTSC (TV) inputs.  There are
plenty of video cards and even video to TV signal converters out there
that you could set up the buttons as an independent output device to the
EPIC card and have your LCD mounted in the MFD space with the output of
a different monitor via a signal converter (Computer video to NTSC) to
display that data on the LCD screen.  Bingo, a functional MFD.  Sure, it
would take some savvy programming of the EPIC to keep up with the
cycling of different MFD modes and different options for the different
buttons, but I don't think that would be impossible, just a challenge.

Joseph (Jay)

------=_NextPart_000_0008_01C20EC4.0A354F80
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">

<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* 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
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

Why is this feature =
so
complicated?
The MFDs show up in the Black boxes that are located
in the &quot;virtual cockpits&quot;. If you have ever looked at the =
virtual
cockpit graphics, all of the gauges are blacked out so the software can
generate the flight info in the black areas. Somehow a function places =
them in
a position that is &quot;cut out&quot; for them. It varies from virtual =
cockpit
to virtual cockpit, or even from view to view.

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span></font></p>

Now if they are =
adding
multiple monitor capability, why not have a view that is just the LEFT =
and one
that is just the right MFD? This would be simpler than pulling the raw =
data out
of the code.

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>This is a question, =
I am
sure its more compli</span></font><font size=3D2 face=3D"Courier =
New"><span
 style=3D'font-size:10.0pt;font-family:"Courier =
New"'>cat</span></font><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>ed
than that.</span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>Chris =
Crowley</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>Chris, I agree with you totally, it =
shouldn&#8217;t
be that compli</span></font><font size=3D2 face=3D"Courier New"><span
 style=3D'font-size:10.0pt;font-family:"Courier =
New"'>cat</span></font><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>ed.&nbsp;
This is my thought.&nbsp; If there will be multiple monitor option =
available,
it shouldn&#8217;t be that difficult to bring up MFD/HUD data into a =
monitor of
its own.&nbsp; Now, there are plenty of LCD&#8217;s out there that are =
about
the size of MFD&#8217;s and these use pretty standard NTSC (TV) =
inputs.&nbsp;
There are plenty of video cards and even video to TV signal converters =
out
there that you could set up the buttons as an independent output device =
to the
EPIC card and have your LCD mounted in the MFD space with the output of =
a different
monitor via a signal converter (Computer video to NTSC) to display that =
data on
the LCD screen.&nbsp; Bingo, a functional MFD.&nbsp; Sure, it would take =
some savvy
programming of the EPIC to keep up with the cycling of different MFD =
modes and
different options for the different buttons, but I don&#8217;t think =
that would
be impossible, just a challenge.</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>Joseph (Jay)</span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0008_01C20EC4.0A354F80--