[simpits-tech] To all - what do you guys think
Chris Crowley
simpits-tech@simpits.org
Thu, 26 Dec 2002 20:04:35 -0500
This is a multi-part message in MIME format.
------=_NextPart_000_0000_01C2AD1A.036375C0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Re: [simpits-tech] To all - what do you guys thinkWhy not try it. There are
a number of us who have not started working the electronics yet. It would be
a big help to give one ideas when they reach that point.
Chris Crowley
21st Century Infidel
-----Original Message-----
From: simpits-tech-admin@simpits.org
[mailto:simpits-tech-admin@simpits.org]On Behalf Of Frank Riedel
Sent: Thursday, December 26, 2002 5:56 PM
To: simpits-tech@simpits.org
Subject: Re: [simpits-tech] To all - what do you guys think
Yes 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 -----
From: Mark Doran
To: simpits-tech@simpits.org
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.
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.
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.
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.
Cheers,
Mark.
-----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
I agree. I wish you luck.
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 !
Frank
----- Original Message -----
From: Marv De Beque <mailto:mdebeque@woh.rr.com>
To: simpits-tech@simpits.org
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.
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 -----
From: Marv De Beque <mailto:mdebeque@woh.rr.com>
To: simpits-tech@simpits.org
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 -----
From: Frank Riedel <mailto:frank@rezultat.dk>
To: simpits-tech@simpits.org
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 "´hint" to the diagram just speak
out ! ! !
Frank
----- Original Message -----
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,
>
> the 64BTN modul you can buy - I think - only in Europe by
MicroCockpit. To
> the 64BTN modul you must have an ABA modul. The 64BTN modul is for
INPUT,
> the 32-point output modul is for OUTPUT. Here is a short description
for
> the ABA-, 64BTN- and 32-point output modul (more see on my site
> (http://www.xflight.de/f16/pe_sim_com_epc.htm
<http://www.xflight.de/f16/pe_sim_com_epc.htm> ):
>
> ABA modul:
> The ABA module is the heart of the system. You can connect up to 4
64BTN
> modules to it, as well as power 16 analog channels. This module is
> connected to the first expansion module by two flat cables.
>
> 64BTN modul:
> Up to 64 push-buttons or switches can be connected to this module.
EPIC can
> then identify each of them. As EPIC registers any change of each
switch and
> processes it separately, only one cable is required to power normal
> switches. The ABA can receive up to 4 64 BTN modules, which give you
up to
> 256 different controls to be powered.
> On one 64BTN modul you can connect and checked 64 buttons, switches
and
> other digital INPUT parts.
>
> 32-point output modul:
> Using this module, which is connected to the First Expansion Module
via
> EPIC-Bus, up to 32 digital output channels can be powered. That means,
that
> you can activate lights, electric motors and other devices. Each
channel
> can handle 3 to 50V. Up to 4 Output Modules can be installed, giving
you
> 128 channels to be used. On one output modul you can steer up to 32
LED,
> lamps or engines. This module is for the OUTPUT.
>
> I hope it is helpful for you.
> Martin "Pegasus"
>
>
> _______________________________________________
> Simpits-tech mailing list
> Simpits-tech@simpits.org <mailto:Simpits-tech@simpits.org>
> http://www.simpits.org/mailman/listinfo/simpits-tech
<http://www.simpits.org/mailman/listinfo/simpits-tech>
> To unsubscribe, please see the instructions at the bottom of the above
page. Thanks!
>
------=_NextPart_000_0000_01C2AD1A.036375C0
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 5.50.4922.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><SPAN class=3D130180301-27122002><FONT face=3DArial color=3D#0000ff =
size=3D2>Why=20
not try it. There are a number of us who have not started working the=20
electronics yet. It would be a big help to give one ideas when they =
reach that=20
point. </FONT></SPAN></DIV>
<DIV> </DIV>
<P><FONT size=3D2>Chris Crowley<BR>21st Century Infidel</FONT></P>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B>=20
simpits-tech-admin@simpits.org =
[mailto:simpits-tech-admin@simpits.org]<B>On=20
Behalf Of </B>Frank Riedel<BR><B>Sent:</B> Thursday, December 26, 2002 =
5:56=20
PM<BR><B>To:</B> simpits-tech@simpits.org<BR><B>Subject:</B> Re:=20
[simpits-tech] To all - what do you guys think<BR><BR></FONT></DIV>
<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=20
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=20
an 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 -=20
what 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"> =20
</SPAN>A standard is a tough route to go =96 I for our project know =
we have=20
almost all the panel wiring done now in the proto unit and I can =
just hear=20
the yelling if I were to ask the hardware guys to change it!!=20
</SPAN></FONT><FONT 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,=20
MRB allocation charts and wiring harness fabrication/BoM lists made =
up and=20
it would be far too much back-tracking to pick up a new wiring =
scheme at=20
this 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=20
said, 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=20
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=20
EPL coding.<SPAN style=3D"mso-spacerun: yes"> </SPAN>The fly =
in that=20
ointment is that people may choose to model switch/lamps etc to =
different=20
levels.<SPAN style=3D"mso-spacerun: yes"> </SPAN>I know for =
example that=20
we are modeling the interactions between the ELEC panel and TEST =
panel with=20
respect to the functions the dash-1 describes for the FLCS test =
operations.=20
<SPAN style=3D"mso-spacerun: yes"> </SPAN>This is all outside =
of scope=20
for Falcon4 game code but EPIC makes it possible to program up the =
switches=20
and 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]=20
<B><SPAN style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Marv De =
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>=20
simpits-tech@simpits.org<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [simpits-tech] =
To all -=20
what 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=20
size=3D3><SPAN style=3D"FONT-SIZE: 12pt; FONT-FAMILY: Verdana">I =
agree. I=20
wish you luck. <BR><BR>However, you might find programming is =
not so=20
hard as you think. The other thing that you should consider is =
no=20
matter what your pin assignment you can easily reconfigure the =
software to=20
agree with it. It is not the pin assignments that are your =
concern,=20
but the functionality for each input type.<BR><BR>That is, you can =
assign a=20
function that handles the landing gear, which should be two =
switches.=20
There are actually three states to the F-16 gear. UP, =
DOWN, and=20
TRANSITIONING. You need two switches to capture those states. =
It=20
doesn=92t really matter which inputs they are assigned to, because =
you can=20
redefine them in software very easily.<BR><BR>Another function =
example is=20
when the dogfight switch is engaged some buttons on the ICP console =
are=20
disabled.<BR><BR>Lastly, every function must have some sort of =
output.=20
This is where the keystrokes for that function are passed to =
the PC so=20
they can be processed in the sim program. Sort of where =
the=20
rubber meets the street.<BR><BR>So, developing a function for each =
input=20
type would be valuable. All you need do is make sure that it =
can be=20
easily redefined to the input(s) of your choice.<BR><BR>That would =
be a very=20
worth while standard to do and my =
recommendation.<BR><BR>Marv<BR><BR>On=20
12/26/02 12:24 PM, "Frank Riedel" <frank@rezultat.dk>=20
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=20
if 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=20
by that way we have maked a "standard" for those to come=20
!<BR></SPAN></FONT><FONT 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=20
size=3D3><SPAN style=3D"FONT-SIZE: 12pt; FONT-FAMILY: Verdana">----- =
Original=20
Message ----- <BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">From:</SPAN></B> Marv=20
De Beque <mailto:mdebeque@woh.rr.com> <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">To:</SPAN></B> simpits-tech@simpits.org=20
<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Thursday, =
December=20
26, 2002 3:22 PM<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Subject:</SPAN></B>=20
Re: [simpits-tech] To all - what do you guys think<BR><BR>Had =
thought about=20
that and actually discussed that with a few people.<BR><BR>The idea =
has=20
merit in that everybody has the same set up and we can share =
knowledge and=20
debugging tips.<BR><BR>The reality is that it would take a lot of =
time to=20
come to some agreement as to what the standard should be. Look =
at the=20
aircraft industry and you see what I mean. ARINC standards are =
a good=20
one, but they take years to come to a delusion and then nobody =
follows them=20
when they do because of unforeseen needs.<BR><BR>Now, I would think =
that we=20
could come to an agreement faster than ARINC does on a standard for =
EPIC.=20
However, there are a number of us that already have work =
invested in=20
their own cockpits and the associated wiring. Even if we =
reached an=20
agreement, chances are everyone that already has stuffed wired up =
would be=20
violating the new standard. How many of those people do =
you=20
believe would rebuild their systems just to comply with a new=20
standard?<BR><BR>Personally, I think the best hope is to find one or =
two=20
others that are at the same development point as you are and hammer =
out a=20
standard with input from anyone else that is interested. =
<BR><BR>Right=20
now I am up to my eyeballs with alligators, so I don=92t have the =
time to=20
invest in that part of the project. Otherwise, I would lend a=20
hand.<BR><BR>Marv<BR><BR><BR>On 12/26/02 4:03 AM, "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">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=20
to make a standard way to wireing the EPIC Input/Output-module<BR>to =
the=20
panels and one EPIC-file by that way we have created a =
complet<BR>F16 pit -=20
that all newbees can use, (inclued my self)<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">All the=20
best<BR>Frank</SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT =
face=3DVerdana=20
size=3D3><SPAN style=3D"FONT-SIZE: 12pt; FONT-FAMILY: Verdana">----- =
Original=20
Message ----- <BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">From:</SPAN></B> Marv=20
De Beque <mailto:mdebeque@woh.rr.com> <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">To:</SPAN></B> simpits-tech@simpits.org=20
<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Thursday, =
December=20
26, 2002 3:19 AM<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Subject:</SPAN></B>=20
Re: [simpits-tech] To all - what do you guys think<BR><BR>Not sure =
what the=20
=93idea=94 is that you are asking about.<BR><BR>On 12/25/02 =
7:10 PM,=20
"Frank 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">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=20
<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Monday, =
December 23,=20
2002 10:52 AM<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Subject:</SPAN></B>=20
[simpits-tech] To all - what do you guys =
think<BR><BR></SPAN></FONT><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Hi=20
Martin "Pegasus" and all other that can help !<BR>Now that we are =
close to=20
the year 2003, and we all<BR>have make a fantastic work by =
collecting huge=20
data 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=20
2002<BR>and came out this year and have already make all panels with =
backlight<BR>and now in construction face of my "pit" by help from =
ALL you=20
guys...<BR>THANKS ALOT 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=20
the panels... but when i come to programing i am<BR>a real "NewBee" =
and=20
other upcomming pitters will came in same situation, I<BR>was =
thinking off=20
makeing a standard connection (wiering) of all the panels.<BR>I can =
make all=20
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=20
we then will have all drawings and wiering-diagram complet !<BR>and =
do any=20
of you 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">=20
<mailto:f16@xflight.de> </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 =
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=20
08, 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=20
see 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=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">):<BR>> <BR>> =
ABA=20
modul:<BR>> The ABA module is the heart of the system. You can =
connect up=20
to 4 64BTN <BR>> modules to it, as well as power 16 analog =
channels. This=20
module is <BR>> connected to the first expansion module by two =
flat=20
cables.<BR>> <BR>> 64BTN modul:<BR>> Up to 64 push-buttons =
or=20
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>>=20
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=20
you can connect and checked 64 buttons, switches and <BR>> other =
digital=20
INPUT parts.<BR>> <BR>> 32-point output modul:<BR>> Using =
this=20
module, which is connected to the First Expansion Module via =
<BR>>=20
EPIC-Bus, up to 32 digital output channels can be powered. That =
means, that=20
<BR>> you can activate lights, electric motors and other devices. =
Each=20
channel <BR>> can handle 3 to 50V. Up to 4 Output Modules can be=20
installed, giving you <BR>> 128 channels to be used. On one =
output modul=20
you can steer up to 32 LED, <BR>> lamps or engines. This module =
is for=20
the OUTPUT.<BR>> <BR>> I hope it is helpful for you.<BR>> =
Martin=20
"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></BLOCK=
QUOTE></BODY></HTML>
------=_NextPart_000_0000_01C2AD1A.036375C0--