<html>
<body>
At 03:49 PM 1/24/2005, you wrote:<br>
<blockquote type=cite class=cite cite="">On Mon, 24 Jan 2005 11:41:01
-0600<br>
Phoenix2000@phoenixcomm.net wrote:<br>
> >The point "can't talk to it" is definately not valid
for FlightGear.<br>
> >There are a bunch of methods to get data in and out of the
simulator.<br>
> ><br>
> >While flightgear is "monolythic" in the sense that
everything is<br>
> >compiled into the main binary, it can be used sort of
"modular".<br>
> <br>
> Not Not Realy<br><br>
<br>
> >the individual modules. This additional layer of communications
would<br>
> >slow the whole thing down.<br><br>
OK, maybe I understood you wrong... I thought you meant the whole<br>
simulator as individual modules. What you write below sounds more
like<br>
you meant to modularize the "systems simulation
only".</blockquote><br><br>
<blockquote type=cite class=cite cite="">On that I totally agree. I was
planning on writing some code for an<br>
external system simulation (for homecockpit sim use). <br>
... when I'm "done" with my hardware and interface
software.<br><br>
For the purposes of simulating aircraft systems (electrical,
pneumatic,<br>
hydraulic, and the whole logics behind them) it'd be great to run
this<br>
outside the actual flight simulator engine.<br><br>
The simulator would fill in the part of "the real world" and
its forces<br>
and stuff, like 3D inside/outside views, winds, and forces/physics
of<br>
the environment acting upon the aircraft.</blockquote><br>
No your realy DONT get it.. <br>
Every module (software) can be swaped out for hardware. there is NO
monolithic system anymore.<br>
There is no sacrificial cow its dead and we are going to cut it up. into
very easy to do subsystem.<br>
You dont like one part of it change it.. You have the API (and by the
way. I have over 30 years with <br>
UNIX, These API are going to be STANDARD. Most of them will come from
ADFX Ethernet. This is way the Boeing 777 uses, du. We are going to
use 802.3 UDP.. (been around a long time)<br><br>
By doing this and using a Standard (NOT A F*** Moving, Undocumented
target, like any of the other SIMs. <br>
This sim will be WIDE OPEN. <br>
This way you don't need special hardware like
ParamBus<font face="Tahoma">® simulation systems </font>hardware
interface or EPIC cards or Hagstrom Decoders.<br>
This way you can get ALL of the DATA, ALL of the TIME. You want to send
data into the SIM No Problem<br>
(great for Instructors station.)<br><br>
I should be able to deliver a small 6" x 6" sbc (single
board computer with) with 100baseT on board and the <br>
with drivers in firmware (maybe Memory Stick) for less than $100.00 each,
then put on a keyboard encoder,<br>
maybe USB inputs who knows.<br><br>
Cris Harrison<br>
Ok then please look at my NOTAM notice for Software under
development.<br>
<a href="http://www.phoenixcomm.net/~phnx2000/sim/notams.shtml" eudora="autourl">
www.phoenixcomm.net/~phnx2000/sim/notams.shtml<br>
</a>
<a href="http://www.phoenixcomm.net/~phnx2000/sim/software.shtml" eudora="autourl">
www.phoenixcomm.net/~phnx2000/sim/software.shtml<br><br>
</a>I need to know what's cool and what's not.<br>
><br><br>
<br><br>
<blockquote type=cite class=cite cite="">> 1. No Not At all when I
worked on the X-29, cockpit integration, we<br>
> were doing 50/60hz frame rates, and that my friend was along time
ago.<br>
> 2. Jets have been fly around by fly by wire for more than a few
years,<br>
> and have been using mil-1553 which runs at 1mb. or AIRINC-429.
etc<br>
> 3. The bus structure for the 777 etc. is AFDX Switched Ethernet.
You<br>
> just send / listen for UDP messages.<br>
> not a problem for 10baseT (thats 10x over 1553/429), you want faster
<br>
> 100baseT, or Fiber.<br>
> 4. and the advantage that you did not see is that you dont like
a<br>
> module? Take it out, replace it with software, or hardware.<br><br>
OK, so if I'm right, all you want could be written to use flighgear
as<br>
the 3D view and physics simulation, while all systems can be written
as<br>
external modules.</blockquote><br>
NO, NOPE the only thing we will use from flightgear is the Scenery
Disks!<br>
Its TOO DAM BIG. Its MONOLITHIC. SMALL is better. Just send
messages.<br><br>
Look <br>
1. Put in startup stuff into NAV Computer (LAT, LON,
TEMP, TIME etc.<br>
2.a Start engine(s) get start enginge(s) mesage(s) from engine(s)
controls.<br>
2.b Get fuel flow, temp, N1, N2, RPMs messages<br>
3. Get Clearance to Taxi<br>
4. Move Throtles (send message)<br>
5 Flight Dynamics Model says we are moving (INS tells me so)<br>
6. Get Clearance to Roll (take off) <br>
7. Move Throtles (send message)<br>
8. Get fuel flow, temp, N1, N2, RPMs messages<br>
9 Flight Dynamics Model says we are moving (INS tells me so)<br>
10. watch airspeed to 180kn. (messages from INS)<br>
11.Pull back on yoke ( and send messages to FDM)<br>
12 FDM says ok lift off (INS tells me so.)<br>
13 Gear UP sends messages to FDM<br>
14 Flaps UP sends message to FDM<br>
15 watch the ADI, HSI move as you take off in the blue......<br>
NOW at the same time all that crap was going on.........<br>
You got and sent messages via the RADIOs<br>
The OUT THE WINDOW Views changed by listing for INS messages.
(Whare am I, and my attitude) <br>
easy right?<br>
Do you get it now?<br>
ever see or play any of the FPS games that are networked. (they use UDP
with lots of players)<br><br>
<blockquote type=cite class=cite cite="">There are alot of interfaces
into flightgear, and another one can be<br>
written easily.<br><br>
Of course if things are kept somewhat indepentent, the systems<br>
simulation software modules could be plugged in to another
simulator.<br><br>
<br>
> >Writing a new sim from scratch, even with lots of stuff
already<br>
> >adaptable (fgfs scenery, simgear library, a few fdms) is still a
huge<br>
> >task and will most likely involve years of work.<br>
> <br>
> maybe but most likely I'll have the first cut, up in a few months.
(we<br>
> <br>
> write a lot of code in C/C++/FORTRAN/Perl/and a little Java), and
it<br>
> would just be the core modules, Pilot, FD, INS, NAV.<br>
> we are working on the message format right now, and message
viewer..<br><br>
What platform are you doing this on ?<br>
Unix/Linux ?<br><br>
Will it be free software/open source ?</blockquote><br>
Maybe I have to work through the messaging system first.. (the dispacter
& messaging system proberly not)<br>
but they will be wide open with the API for the messaging
system.<br><br>
<br><br>
<br>
<blockquote type=cite class=cite cite="">Regards,<br>
Manuel<br>
_______________________________________________<br>
Simpits-tech mailing list<br>
Simpits-tech@simpits.org<br>
<a href="http://www.simpits.org/mailman/listinfo/simpits-tech" eudora="autourl">
http://www.simpits.org/mailman/listinfo/simpits-tech</a><br>
To unsubscribe, please see the instructions at the bottom of the above
page. Thanks!</blockquote></body>
</html>