<html>
At 24/01/05 22:49, 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".<br><br>
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.</blockquote><br>
This can be done by using the ParamBus<font face="Tahoma">® simulation
systems<br>
</font>hardware interface. This allows you to integrate multiple
independant<br>
sub-system emulators with your flight-simulator engine. It also
nterfaces<br>
to the cockpit hardware in both directions.<br><br>
<br>
<blockquote type=cite class=cite cite>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.<br><br>
<br>
> 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.<br>
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 ?<br><br>
<br>
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></html>