[simpits-tech] To all - what do you guys think
Frank Riedel
simpits-tech@simpits.org
Thu, 26 Dec 2002 23:55:40 +0100
This is a multi-part message in MIME format.
------=_NextPart_000_000A_01C2AD3A.4B9883B0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Re: [simpits-tech] To all - what do you guys thinkYes Mark your are =
right, but as you say it coud be easyer to start if wiring diagrams and =
som EPLcode was
to find somewhere, but it is'nt.... a basic setup that you can work your =
way out from... you now what i mean :o)
it will the be possible to save a lot of time and newbees will not run =
there head in a wall... i'll keep up my work
to be the first in Denmark to have a "homepit of an F16" ;o)
Fly well
Frank
----- Original Message -----=20
From: Mark Doran=20
To: simpits-tech@simpits.org=20
Sent: Thursday, December 26, 2002 10:55 PM
Subject: RE: [simpits-tech] To all - what do you guys think
I would echo what Marv is saying here. A standard is a tough route to =
go - I for our project know we have almost all the panel wiring done now =
in the proto unit and I can just hear the yelling if I were to ask the =
hardware guys to change it!! J We have all the circuit diagrams, MRB =
allocation charts and wiring harness fabrication/BoM lists made up and =
it would be far too much back-tracking to pick up a new wiring scheme at =
this point.
=20
That said, I think the EPIC programming is relatively straightforward. =
It's no worse really than writing macro scripts for TM Cougar or =
F22pro/TQS controllers.
=20
In practice, I think the way the new device syntax works in EPL, the =
most interesting part is actually the logic code that makes the buttons =
and lamps and such do what they need to do. The device structures just =
assign procedural code to the particular wiring scheme (MRB =
assignments). I think you could take someone else's "logic" code and =
match it up to your wiring by changing the MRB numbering in the device =
structures pretty easily.
=20
I think that's your fastest route if you don't want to start from =
scratch with the EPL coding. The fly in that ointment is that people =
may choose to model switch/lamps etc to different levels. I know for =
example that we are modeling the interactions between the ELEC panel and =
TEST panel with respect to the functions the dash-1 describes for the =
FLCS test operations. This is all outside of scope for Falcon4 game =
code but EPIC makes it possible to program up the switches and lamps to =
work somewhat like the actual jet anyway. Others may or may not choose =
to go to the same level of detail.and their EPL code will vary =
accordingly.
=20
Cheers,
=20
Mark.
=20
=20
=20
-----Original Message-----
From: simpits-tech-admin@simpits.org =
[mailto:simpits-tech-admin@simpits.org] On Behalf Of Marv De Beque
Sent: Thursday, December 26, 2002 12:45 PM
To: simpits-tech@simpits.org
Subject: Re: [simpits-tech] To all - what do you guys think
=20
I agree. I wish you luck. =20
However, you might find programming is not so hard as you think. The =
other thing that you should consider is no matter what your pin =
assignment you can easily reconfigure the software to agree with it. It =
is not the pin assignments that are your concern, but the functionality =
for each input type.
That is, you can assign a function that handles the landing gear, =
which should be two switches. There are actually three states to the =
F-16 gear. UP, DOWN, and TRANSITIONING. You need two switches to =
capture those states. It doesn't really matter which inputs they are =
assigned to, because you can redefine them in software very easily.
Another function example is when the dogfight switch is engaged some =
buttons on the ICP console are disabled.
Lastly, every function must have some sort of output. This is where =
the keystrokes for that function are passed to the PC so they can be =
processed in the sim program. Sort of where the rubber meets the =
street.
So, developing a function for each input type would be valuable. All =
you need do is make sure that it can be easily redefined to the input(s) =
of your choice.
That would be a very worth while standard to do and my recommendation.
Marv
On 12/26/02 12:24 PM, "Frank Riedel" <frank@rezultat.dk> wrote:
You got a point there Marv, but if we/I make a wiring diagram for all =
the buttons and lamps in an F16 Block 50,
then we mabe can find someone there is hardcore on EPIC to make the =
code for it !... and then we
place the file for download "outthere" and by that way we have maked a =
"standard" for those to come !
=20
Frank
----- Original Message -----=20
From: Marv De Beque <mailto:mdebeque@woh.rr.com> =20
To: simpits-tech@simpits.org=20
Sent: Thursday, December 26, 2002 3:22 PM
Subject: Re: [simpits-tech] To all - what do you guys think
Had thought about that and actually discussed that with a few people.
The idea has merit in that everybody has the same set up and we can =
share knowledge and debugging tips.
The reality is that it would take a lot of time to come to some =
agreement as to what the standard should be. Look at the aircraft =
industry and you see what I mean. ARINC standards are a good one, but =
they take years to come to a delusion and then nobody follows them when =
they do because of unforeseen needs.
Now, I would think that we could come to an agreement faster than =
ARINC does on a standard for EPIC. However, there are a number of us =
that already have work invested in their own cockpits and the associated =
wiring. Even if we reached an agreement, chances are everyone that =
already has stuffed wired up would be violating the new standard. How =
many of those people do you believe would rebuild their systems just to =
comply with a new standard?
Personally, I think the best hope is to find one or two others that =
are at the same development point as you are and hammer out a standard =
with input from anyone else that is interested. =20
Right now I am up to my eyeballs with alligators, so I don't have the =
time to invest in that part of the project. Otherwise, I would lend a =
hand.
Marv
On 12/26/02 4:03 AM, "Frank Riedel" <frank@rezultat.dk> wrote:
Hi all !
Idea is to make a standard way to wireing the EPIC Input/Output-module
to the panels and one EPIC-file by that way we have created a complet
F16 pit - that all newbees can use, (inclued my self)
All the best
Frank
----- Original Message -----=20
From: Marv De Beque <mailto:mdebeque@woh.rr.com> =20
To: simpits-tech@simpits.org=20
Sent: Thursday, December 26, 2002 3:19 AM
Subject: Re: [simpits-tech] To all - what do you guys think
Not sure what the "idea" is that you are asking about.
On 12/25/02 7:10 PM, "Frank Riedel" <frank@rezultat.dk> wrote:
Is it a bad idea ???
Frank
----- Original Message -----=20
From: Frank Riedel <mailto:frank@rezultat.dk> =20
To: simpits-tech@simpits.org=20
Sent: Monday, December 23, 2002 10:52 AM
Subject: [simpits-tech] To all - what do you guys think
Hi Martin "Pegasus" and all other that can help !
Now that we are close to the year 2003, and we all
have make a fantastic work by collecting huge data about
simulator and by that way help one and another... include my self
I startet out collecting information and nowhow at January 2002
and came out this year and have already make all panels with backlight
and now in construction face of my "pit" by help from ALL you guys...
THANKS ALOT ALL
I just need to wireing up all the panels... but when i come to =
programing i am
a real "NewBee" and other upcomming pitters will came in same =
situation, I
was thinking off makeing a standard connection (wiering) of all the =
panels.
I can make all the diagrams look here =
http://www.rezultat.dk/f16/full-wireing.htm =
<http://www.rezultat.dk/f16/full-wireing.htm> (Not finished)
Will any of you be able to program an EPIC-file after this diagram ???
if so... i think we then will have all drawings and wiering-diagram =
complet !
and do any of you have any changes and "=B4hint" to the diagram just =
speak out ! ! !
Frank
----- Original Message -----=20
From: "F16" <f16@xflight.de <mailto:f16@xflight.de> >
To: <simpits-tech@simpits.org <mailto:simpits-tech@simpits.org> >
Sent: Sunday, December 08, 2002 12:14 PM
Subject: AW: [simpits-tech] Epic hardware
> Hi Frank,
>=20
> the 64BTN modul you can buy - I think - only in Europe by =
MicroCockpit. To=20
> the 64BTN modul you must have an ABA modul. The 64BTN modul is for =
INPUT,=20
> the 32-point output modul is for OUTPUT. Here is a short description =
for=20
> the ABA-, 64BTN- and 32-point output modul (more see on my site=20
> (http://www.xflight.de/f16/pe_sim_com_epc.htm =
<http://www.xflight.de/f16/pe_sim_com_epc.htm> ):
>=20
> ABA modul:
> The ABA module is the heart of the system. You can connect up to 4 =
64BTN=20
> modules to it, as well as power 16 analog channels. This module is=20
> connected to the first expansion module by two flat cables.
>=20
> 64BTN modul:
> Up to 64 push-buttons or switches can be connected to this module. =
EPIC can=20
> then identify each of them. As EPIC registers any change of each =
switch and=20
> processes it separately, only one cable is required to power normal=20
> switches. The ABA can receive up to 4 64 BTN modules, which give you =
up to=20
> 256 different controls to be powered.
> On one 64BTN modul you can connect and checked 64 buttons, switches =
and=20
> other digital INPUT parts.
>=20
> 32-point output modul:
> Using this module, which is connected to the First Expansion Module =
via=20
> EPIC-Bus, up to 32 digital output channels can be powered. That =
means, that=20
> you can activate lights, electric motors and other devices. Each =
channel=20
> can handle 3 to 50V. Up to 4 Output Modules can be installed, giving =
you=20
> 128 channels to be used. On one output modul you can steer up to 32 =
LED,=20
> lamps or engines. This module is for the OUTPUT.
>=20
> I hope it is helpful for you.
> Martin "Pegasus"
>=20
>=20
> _______________________________________________
> Simpits-tech mailing list
> Simpits-tech@simpits.org <mailto:Simpits-tech@simpits.org>=20
> http://www.simpits.org/mailman/listinfo/simpits-tech =
<http://www.simpits.org/mailman/listinfo/simpits-tech>=20
> To unsubscribe, please see the instructions at the bottom of the =
above page. Thanks!
>=20
=20
=20
=20
=20
=20
=20
------=_NextPart_000_000A_01C2AD3A.4B9883B0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD><TITLE>Re: [simpits-tech] =
To all - what do you guys think</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 6.00.2722.900" name=3DGENERATOR>
<META content=3D"Microsoft Word 10" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C2ACE6.79F99310" rel=3DFile-List><!--[if gte =
mso 9]><xml>
<o:OfficeDocumentSettings>
<o:DoNotRelyOnCSS/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:DocumentKind>DocumentEmail</w:DocumentKind>
<w:EnvelopeVis/>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
</w:WordDocument>
</xml><![endif]-->
<STYLE>@font-face {
font-family: Wingdings;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Lucida Console;
}
@font-face {
font-family: Verdana;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; =
mso-header-margin: .5in; mso-footer-margin: .5in; mso-paper-source: 0; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
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 {
FONT-WEIGHT: normal; COLOR: blue; FONT-STYLE: normal; FONT-FAMILY: =
"Lucida Console"; TEXT-DECORATION: none; mso-ascii-font-family: "Lucida =
Console"; mso-hansi-font-family: "Lucida Console"; text-underline: none; =
mso-style-type: personal-reply; mso-style-noshow: yes; =
mso-ansi-font-size: 10.0pt; mso-bidi-font-size: 10.0pt; =
text-line-through: none
}
DIV.Section1 {
page: Section1
}
</STYLE>
<!--[if gte mso 10]>
<style>
/* Style Definitions */=20
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 lang=3DEN-US style=3D"tab-interval: .5in" vLink=3Dpurple =
link=3Dblue=20
bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Yes Mark your are right, but as you say =
it=20
coud be easyer to start if wiring diagrams and som EPLcode =
was</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>to find somewhere, but it is'nt.... a =
basic setup=20
that you can work your way out from... you now what i mean =
:o)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>it will the be possible to save a lot =
of time and=20
newbees will not run there head in a wall... i'll keep up my =
work</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>to be the first in Denmark to have a =
"homepit of an=20
F16" ;o)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Fly well</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Frank</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A title=3Dmsdoran@attbi.com href=3D"mailto:msdoran@attbi.com">Mark =
Doran</A>=20
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dsimpits-tech@simpits.org=20
href=3D"mailto:simpits-tech@simpits.org">simpits-tech@simpits.org</A> =
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Thursday, December 26, =
2002 10:55=20
PM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: [simpits-tech] To =
all - what=20
do you guys think</DIV>
<DIV><BR></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3D"Lucida Console" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida =
Console'">I would=20
echo what Marv is saying here.<SPAN style=3D"mso-spacerun: yes"> =
</SPAN>A=20
standard is a tough route to go =96 I for our project know we have =
almost all=20
the panel wiring done now in the proto unit and I can just hear the =
yelling if=20
I were to ask the hardware guys to change it!! </SPAN></FONT><FONT=20
face=3DWingdings color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Wingdings; =
mso-ascii-font-family: 'Lucida Console'; mso-hansi-font-family: 'Lucida =
Console'; mso-char-type: symbol; mso-symbol-font-family: =
Wingdings"><SPAN=20
style=3D"mso-char-type: symbol; mso-symbol-font-family: =
Wingdings">J</SPAN></SPAN></FONT><FONT=20
face=3D"Lucida Console" color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida =
Console'"><SPAN=20
style=3D"mso-spacerun: yes"> </SPAN>We have all the circuit =
diagrams, MRB=20
allocation charts and wiring harness fabrication/BoM lists made up and =
it=20
would be far too much back-tracking to pick up a new wiring scheme at =
this=20
point.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Lucida Console" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida =
Console'"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Lucida Console" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida =
Console'">That said,=20
I think the EPIC programming is relatively straightforward.<SPAN=20
style=3D"mso-spacerun: yes"> </SPAN>It=92s no worse really than =
writing=20
macro scripts for TM Cougar or F22pro/TQS=20
controllers.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Lucida Console" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida =
Console'"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Lucida Console" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida =
Console'">In=20
practice, I think the way the new device syntax works in EPL, the most =
interesting part is actually the logic code that makes the buttons and =
lamps=20
and such do what they need to do.<SPAN style=3D"mso-spacerun: =
yes"> =20
</SPAN>The device structures just assign procedural code to the =
particular=20
wiring scheme (MRB assignments). <SPAN=20
style=3D"mso-spacerun: yes"> </SPAN>I think you could take =
someone else=92s=20
=93logic=94 code and match it up to your wiring by changing the MRB =
numbering in=20
the device structures pretty easily.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Lucida Console" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida =
Console'"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Lucida Console" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida =
Console'">I think=20
that=92s your fastest route if you don=92t want to start from scratch =
with the EPL=20
coding.<SPAN style=3D"mso-spacerun: yes"> </SPAN>The fly in that =
ointment=20
is that people may choose to model switch/lamps etc to different =
levels.<SPAN=20
style=3D"mso-spacerun: yes"> </SPAN>I know for example that we =
are=20
modeling the interactions between the ELEC panel and TEST panel with =
respect=20
to the functions the dash-1 describes for the FLCS test operations. =
<SPAN=20
style=3D"mso-spacerun: yes"> </SPAN>This is all outside of scope =
for=20
Falcon4 game code but EPIC makes it possible to program up the =
switches and=20
lamps to work somewhat like the actual jet anyway. <SPAN=20
style=3D"mso-spacerun: yes"> </SPAN>Others may or may not choose =
to go to=20
the same level of detail=85and their EPL code will vary=20
accordingly.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Lucida Console" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida =
Console'"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Lucida Console" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida =
Console'">Cheers,<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Lucida Console" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida =
Console'"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Lucida Console" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida =
Console'">Mark.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Lucida Console" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida =
Console'"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Lucida Console" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida =
Console'"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Lucida Console" color=3Dblue =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Lucida =
Console'"><o:p> </o:p></SPAN></FONT></P>
<DIV=20
style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue =
1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<P class=3DMsoNormal><FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original=20
Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B>=20
simpits-tech-admin@simpits.org [mailto:simpits-tech-admin@simpits.org] =
<B><SPAN style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Marv De=20
Beque<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> =
Thursday,=20
December 26, 2002 12:45 PM<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">To:</SPAN></B> =
simpits-tech@simpits.org<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [simpits-tech] To =
all - what=20
do you guys think</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT =
face=3DVerdana size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: Verdana">I agree. I wish =
you luck.=20
<BR><BR>However, you might find programming is not so hard as =
you think.=20
The other thing that you should consider is no matter what your =
pin=20
assignment you can easily reconfigure the software to agree with it. =
It=20
is not the pin assignments that are your concern, but the =
functionality for=20
each input type.<BR><BR>That is, you can assign a function that =
handles the=20
landing gear, which should be two switches. There are actually =
three=20
states to the F-16 gear. UP, DOWN, and TRANSITIONING. You =
need two=20
switches to capture those states. It doesn=92t really matter =
which inputs=20
they are assigned to, because you can redefine them in software very=20
easily.<BR><BR>Another function example is when the dogfight switch is =
engaged=20
some buttons on the ICP console are disabled.<BR><BR>Lastly, every =
function=20
must have some sort of output. This is where the keystrokes for =
that=20
function are passed to the PC so they can be processed in the =
sim=20
program. Sort of where the rubber meets the street.<BR><BR>So,=20
developing a function for each input type would be valuable. All =
you=20
need do is make sure that it can be easily redefined to the input(s) =
of your=20
choice.<BR><BR>That would be a very worth while standard to do and my=20
recommendation.<BR><BR>Marv<BR><BR>On 12/26/02 12:24 PM, "Frank =
Riedel"=20
<frank@rezultat.dk> wrote:</SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">You got a point there =
Marv, but if=20
we/I make a wiring diagram for all the buttons and lamps in an F16 =
Block=20
50,<BR>then we mabe can find someone there is hardcore on EPIC to make =
the=20
code for it !... and then we<BR>place the file for download "outthere" =
and by=20
that way we have maked a "standard" for those to come =
!<BR></SPAN></FONT><FONT=20
face=3DVerdana><SPAN=20
style=3D"FONT-FAMILY: Verdana"><BR> <BR></SPAN></FONT><FONT =
face=3DArial=20
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Frank</SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT =
face=3DVerdana size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: Verdana">----- Original Message =
-----=20
<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> Marv De =
Beque=20
<mailto:mdebeque@woh.rr.com> <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">To:</SPAN></B> simpits-tech@simpits.org =
<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Thursday, December 26, =
2002 3:22=20
PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re:=20
[simpits-tech] To all - what do you guys think<BR><BR>Had thought =
about that=20
and actually discussed that with a few people.<BR><BR>The idea has =
merit in=20
that everybody has the same set up and we can share knowledge and =
debugging=20
tips.<BR><BR>The reality is that it would take a lot of time to come =
to some=20
agreement as to what the standard should be. Look at the =
aircraft=20
industry and you see what I mean. ARINC standards are a good =
one, but=20
they take years to come to a delusion and then nobody follows them =
when they=20
do because of unforeseen needs.<BR><BR>Now, I would think that we =
could come=20
to an agreement faster than ARINC does on a standard for EPIC. =
However,=20
there are a number of us that already have work invested in their own =
cockpits=20
and the associated wiring. Even if we reached an agreement, =
chances are=20
everyone that already has stuffed wired up would be violating the new=20
standard. How many of those people do you believe would =
rebuild=20
their systems just to comply with a new standard?<BR><BR>Personally, I =
think=20
the best hope is to find one or two others that are at the same =
development=20
point as you are and hammer out a standard with input from anyone else =
that is=20
interested. <BR><BR>Right now I am up to my eyeballs with =
alligators, so=20
I don=92t have the time to invest in that part of the project. =
Otherwise,=20
I would lend a hand.<BR><BR>Marv<BR><BR><BR>On 12/26/02 4:03 AM, =
"Frank=20
Riedel" <frank@rezultat.dk> wrote:</SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi all =
!<BR></SPAN></FONT><FONT=20
face=3DVerdana><SPAN style=3D"FONT-FAMILY: =
Verdana"><BR></SPAN></FONT><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Idea is to=20
make a standard way to wireing the EPIC Input/Output-module<BR>to the =
panels=20
and one EPIC-file by that way we have created a complet<BR>F16 pit - =
that all=20
newbees can use, (inclued my self)<BR></SPAN></FONT><FONT =
face=3DVerdana><SPAN=20
style=3D"FONT-FAMILY: Verdana"><BR></SPAN></FONT><FONT face=3DArial =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">All the=20
best<BR>Frank</SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT =
face=3DVerdana size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: Verdana">----- Original Message =
-----=20
<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> Marv De =
Beque=20
<mailto:mdebeque@woh.rr.com> <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">To:</SPAN></B> simpits-tech@simpits.org =
<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Thursday, December 26, =
2002 3:19=20
AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re:=20
[simpits-tech] To all - what do you guys think<BR><BR>Not sure what =
the =93idea=94=20
is that you are asking about.<BR><BR>On 12/25/02 7:10 PM, "Frank =
Riedel"=20
<frank@rezultat.dk> wrote:</SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Is it a bad idea=20
???<BR></SPAN></FONT><FONT face=3DVerdana><SPAN=20
style=3D"FONT-FAMILY: Verdana"><BR></SPAN></FONT><FONT face=3DArial =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Frank<BR></SPAN></FONT><FONT=20
face=3DVerdana><SPAN style=3D"FONT-FAMILY: Verdana"><BR>----- Original =
Message=20
----- </SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><B><FONT face=3DVerdana size=3D3><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 12pt; FONT-FAMILY: =
Verdana">From:</SPAN></FONT></B><FONT=20
face=3DVerdana><SPAN style=3D"FONT-FAMILY: Verdana"> Frank Riedel=20
<mailto:frank@rezultat.dk> <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">To:</SPAN></B> simpits-tech@simpits.org =
<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Monday, December 23, 2002 =
10:52=20
AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> =
[simpits-tech] To=20
all - what do you guys think<BR><BR></SPAN></FONT><FONT face=3DArial=20
size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi Martin =
"Pegasus"=20
and all other that can help !<BR>Now that we are close to the year =
2003, and=20
we all<BR>have make a fantastic work by collecting huge data=20
about<BR>simulator and by that way help one and another... include my=20
self<BR>I startet out collecting information and nowhow at January =
2002<BR>and=20
came out this year and have already make all panels with =
backlight<BR>and now=20
in construction face of my "pit" by help from ALL you =
guys...<BR>THANKS ALOT=20
ALL<BR></SPAN></FONT><FONT face=3DVerdana><SPAN=20
style=3D"FONT-FAMILY: Verdana"><BR></SPAN></FONT><FONT face=3DArial =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I just need to wireing =
up all the=20
panels... but when i come to programing i am<BR>a real "NewBee" and =
other=20
upcomming pitters will came in same situation, I<BR>was thinking off =
makeing a=20
standard connection (wiering) of all the panels.<BR>I can make all the =
diagrams look here=20
http://www.rezultat.dk/f16/full-wireing.htm</SPAN></FONT><FONT=20
face=3DVerdana><SPAN style=3D"FONT-FAMILY: Verdana">=20
<http://www.rezultat.dk/f16/full-wireing.htm> =
</SPAN></FONT><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">(Not=20
finished)<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Will any of you be =
able to=20
program an EPIC-file after this diagram ???<BR></SPAN></B>if so... i =
think we=20
then will have all drawings and wiering-diagram complet !<BR>and do =
any of you=20
have any changes and "=B4hint" to the diagram just speak out ! !=20
!<BR></SPAN></FONT><FONT face=3DVerdana><SPAN=20
style=3D"FONT-FAMILY: Verdana"><BR></SPAN></FONT><FONT face=3DArial =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Frank<BR></SPAN></FONT><FONT=20
face=3DVerdana><SPAN style=3D"FONT-FAMILY: =
Verdana"><BR></SPAN></FONT><FONT=20
face=3DArial><SPAN style=3D"FONT-FAMILY: =
Arial"><BR></SPAN></FONT><FONT=20
face=3DVerdana><SPAN style=3D"FONT-FAMILY: =
Verdana"><BR></SPAN></FONT><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">-----=20
Original Message ----- <BR>From: "F16" =
<f16@xflight.de</SPAN></FONT><FONT=20
face=3DVerdana><SPAN style=3D"FONT-FAMILY: Verdana"> =
<mailto:f16@xflight.de>=20
</SPAN></FONT><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">><BR>To:=20
<simpits-tech@simpits.org</SPAN></FONT><FONT face=3DVerdana><SPAN=20
style=3D"FONT-FAMILY: Verdana"> =
<mailto:simpits-tech@simpits.org>=20
</SPAN></FONT><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">><BR>Sent: Sunday, =
December 08,=20
2002 12:14 PM<BR>Subject: AW: [simpits-tech] Epic=20
hardware<BR></SPAN></FONT><FONT face=3DArial><SPAN=20
style=3D"FONT-FAMILY: Arial"><BR></SPAN></FONT><FONT face=3DArial =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">> Hi Frank,<BR>> =
<BR>>=20
the 64BTN modul you can buy - I think - only in Europe by =
MicroCockpit. To=20
<BR>> the 64BTN modul you must have an ABA modul. The 64BTN modul =
is for=20
INPUT, <BR>> the 32-point output modul is for OUTPUT. Here is a =
short=20
description for <BR>> the ABA-, 64BTN- and 32-point output modul =
(more see=20
on my site <BR>>=20
(http://www.xflight.de/f16/pe_sim_com_epc.htm</SPAN></FONT><FONT=20
face=3DVerdana><SPAN style=3D"FONT-FAMILY: Verdana">=20
<http://www.xflight.de/f16/pe_sim_com_epc.htm> =
</SPAN></FONT><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">):<BR>>=20
<BR>> ABA modul:<BR>> The ABA module is the heart of the system. =
You can=20
connect up to 4 64BTN <BR>> modules to it, as well as power 16 =
analog=20
channels. This module is <BR>> connected to the first expansion =
module by=20
two flat cables.<BR>> <BR>> 64BTN modul:<BR>> Up to 64 =
push-buttons=20
or switches can be connected to this module. EPIC can <BR>> then =
identify=20
each of them. As EPIC registers any change of each switch and <BR>> =
processes it separately, only one cable is required to power normal =
<BR>>=20
switches. The ABA can receive up to 4 64 BTN modules, which give you =
up to=20
<BR>> 256 different controls to be powered.<BR>> On one 64BTN =
modul you=20
can connect and checked 64 buttons, switches and <BR>> other =
digital INPUT=20
parts.<BR>> <BR>> 32-point output modul:<BR>> Using this =
module,=20
which is connected to the First Expansion Module via <BR>> =
EPIC-Bus, up to=20
32 digital output channels can be powered. That means, that <BR>> =
you can=20
activate lights, electric motors and other devices. Each channel =
<BR>> can=20
handle 3 to 50V. Up to 4 Output Modules can be installed, giving you =
<BR>>=20
128 channels to be used. On one output modul you can steer up to 32 =
LED,=20
<BR>> lamps or engines. This module is for the OUTPUT.<BR>> =
<BR>> I=20
hope it is helpful for you.<BR>> Martin "Pegasus"<BR>> <BR>> =
<BR>>=20
_______________________________________________<BR>> Simpits-tech =
mailing=20
list<BR>> Simpits-tech@simpits.org</SPAN></FONT><FONT =
face=3DVerdana><SPAN=20
style=3D"FONT-FAMILY: Verdana"> =
<mailto:Simpits-tech@simpits.org>=20
<BR></SPAN></FONT><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">>=20
=
http://www.simpits.org/mailman/listinfo/simpits-tech</SPAN></FONT><FONT=20
face=3DVerdana><SPAN style=3D"FONT-FAMILY: Verdana">=20
<http://www.simpits.org/mailman/listinfo/simpits-tech>=20
<BR></SPAN></FONT><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">> To unsubscribe, =
please see=20
the instructions at the bottom of the above page. =
Thanks!<BR>>=20
</SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: =
12pt"><o:p> </o:p></SPAN></FONT></P></DIV></DIV></BLOCKQUOTE></BODY>=
</HTML>
------=_NextPart_000_000A_01C2AD3A.4B9883B0--