Originally, when I started with this undertaking, I made first of several statements, and they are worth repeating.http://www.phoenixcomm.net/~phnx2000/sim/software.shtml
- No KeyBoard encoders.
- Must use standard equipment protocols. AIRINC-429, ARINC-410, etc.
- Must be able to support x-number of crew stations. ie. P51, 747, L1011, B-52, Starship Enterprise, or naval craft's: CICS bridge, etc.
If you wish to read my diatribe, please go here: to my first website for my aircraft Phoenix2000. BTW 2000 was the year I was going to start ground testing and the name Phoenix is not taken from mythology, but an omage to the film with Jimmy Stuart "Flight of the Phoenix". The re-make was terrible! That plane was real N93082 piloted by Paul Mantz who died when the aircraft crashed.
Well that it for now.
Stay Tuned In,
|Box / Name||Functionality||Communication Bus||Notes|
Runs 100 frames/sec, Calculates Velocities, Acceleration, Distance, Time, Knows where we are. tells everybody.
Master Frame, once/sec
Sub Frames broadcasts Velocities, Acceleration, Distance, Time, Lat, Lon, Alt, Speed, et
Runs: HSI, VSI, RMI; Monitors all Radios. Controls Radio Audio and mixing as well.
Generates Slant-Range info for Radios, DME, etc.
Generates Mose Code for localizers, Handels FAAdb.
Runs as the master for EADIN Lite network (code from NASA tech-brief.)
|3. NAV-IOP||Runs: HSI, VSI, RMI;|
|4. Gen-IOP||Runs other panels, switches, etc. Also handles Flight Controls, Throttles, Fule Burn Rates|
|5. GE-Master||Worldviews etc are will be generated via Google Liquid Earth.|
|x. GE-Slaves||takes in information via GE-Master and then projects it.|