It was suggested I repost this here....sorry for the sloppy formatting
of this message....
*_Summary of this project_*......
For students in air cadets....too young for actual flight training, just
trying to get them interested.
Trying to build a 172 cockpit , having 'out the window' view handled by
at least one system, just the panel handled by another...
In essence, a network of systems, one segment handling view, another the
gauges, and a third for an instructor to monitor the entire process.
Eventually, on a simple motion base.
Was trying to use opengc for this, but discovered that opengc and FG
.9.9 dont talk so well under windows (not at all, apparently opengc
becoming dormant in that area)
Moved to linux boxes, and into a whole new set of issues with getting
opengc to compile, etc.
Is there a way to do this without using opengc? (or wiring 'actual'
gauges...doable, but too expensive right now..._zero_ budget would be a
good description...this is all volenteer)
I'm not sure the 'glass cockpit' approach is what this project needs
anyway for this simpler cockpit (I'd rather have them be able to scan
the 'big 6' than glance at a PFD or HUD)
Any advice or links to advice would be GREATLY appreciated.
Bruce B
(btw...I'll try and open source any software we come up with for the
motion base...still a long way down the road, but any help here would
also be appreciated)
below I've attached some of the conversation I've had with John W.
regarding this...it's kinda messy 'cause I just copied and pasted
it...sorry!!!
Actually, just thinking of the 172 for right now... a basic generic
cockpit for now....(might do a glider as well...air cadets offers a
gliding program...)
Is there a way to do this without opengc? (I have a tendency to look
for the complicated solutions first.....then kick myself later.) Just
want to have the panel on a seperate screen(computer)...might expand the
"view" to 3 screens if I have the time..even just the 'big 6' gauges on
a seperate screen...
You're right on the money with the virtual desktop solution for the
Instructor....I suppose I could just use VNC as well, that might just
allow the instructor to "point out" things.
btw....FG running on a Fedora Core 4 box, fresh install. Can't get
opengc to compile (with or without cmake), but I've heard theres more
than one source? (kingmont/sourceforge?) I'm also having issues with
cvs on this box....but thats another story (my old mandrake box was so
nice to me...FC4 hates me....)
The box I sacrificed is an Athlon xp 2000, Nvidia 5200, 512 MB ram, so
not the highest amount of power out there.
Thats why I want to divide this up amoungst a few older machines.
I've been REALLY busy lately and haven't been able to do much research
into this, but I'm hoping to get more involved over the holidays. I'm
not the best coder out there either(self tought there...I'm a hardware
guy since the late 70's)
Sorry to keep buggin' you......
Bruce Benneke
John Wojnaroski wrote:
Bruce Benneke wrote:
Great info... thanks...
I'm going to bump the whole project over to linux boxes over the
weekend and see what happens.
1 running FG, another running opengc and atlas. (maybe mirror it all
to an instructors station if I can figure out how)
We're also hoping to build a motion base for this sucker as well...any
sage advice/warnings?
Consider using the "export DISPLAY=machine_name:0.0" command to set up X
on a remote host? If you're running fvwm2 under X you can setup several
virtual desktops on the instructors station.
Are you trying to model any specific aircraft or just a generic
cockpit? OpenGC is glass, others may have added the more conventional
"steam gauges" but my contributions were only for modern glass displays.
With OpenGC going dormant, the interface is most likely very stale. I
suspect that will be one of the problems you face; however all is not
lost :-) . If FG is transmitting, you should be able to look at the
network traffic with a packet sniffer tool. If you have the OpenGC
code, look in the DataSources directory for a file called
openegc_data.hxx. That should match up with the FG packet of the same
name in the Network directory. Its quite possible the version numbers
and data structues DO NOT match. Get those in sync and you should be
able to receive FG data packets.
(BTW...this project is being built for our local air-cadet
squadron..it's a lot cheaper than renting actual aircraft, and I lost
my medical a long time ago....)
Hi Bruce,
Contacting you via your private email, hope you don't mind..
The OpenGC/Flightgear interface is designed for Unix/Linux and Cygwin
platforms. There is no provisions for connecting on MS Windows
machines. You'll probably need to use FSUIPC on the OpenGC side, and
write your own .dll library on the FG side.
Two other comments, mostly the data packet in FG-0.9.9 is not in-sync
with the OpenGC code. That has been dormant for almost two years now.
begin:vcard
fn:Bruce Benneke
n:Benneke;Bruce
org:Benneke Computers
email;internet:[EMAIL PROTECTED]
tel;work:1 (306) 542-2891
version:2.1
end:vcard
_______________________________________________
Flightgear-devel mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
