Group Actions
Engagement
  • Author Author: phoenixcomm
  • Date Created: Date Created
  • Views 348 views
  • Likes 0 likes
  • Comments 4 comments
Related
Recommended

NexGen: System Overview

phoenixcomm

Ok Now Lets all take a deep breath in an I will begin...image


Ok I have been dissatisfied my the state of flight simulation. It really bugged me that most planes have on than one seat, ie.. pilot, copilot, reo, nave, weapons, etc. Then I remembered a game called Star Trek that we played on the TCNJ, a computer network in NJ. each team had a captain, weapons, helm, engineering, science, transporters, and a few others that my old brain can't recall. BTW all this was played on a PCxt and the big 360.... I have more power in one desktop than all that put together. And then of course now add in Microsoft Flight Simulator, and X-Plane, and a few others.. nah, all.

So here where my design objectives came from.

  1. The system should handle multi-seats with out problems.
  2. The above entails that you system must also handle multiple radios, instruments, etc. (so if you can write it for one (1) make it handle a few or more.
  3. Radios are a big part of a sim.. so we need all types.. and the faa frequency, and lat/long for all the towers, runways, etc. (oh, no)
    1. this needs a database
    2. Morse Code Simulator
    3. drive for some indicators such as RMI, HSI, VSI, and others. Plus all the flags
    4. a little math so while you are on the ramp at LAX you cant hear the tower at lets say JFK.
  4. The system should use mostly IP for our data.
  5. Instructors Console and Data Recorder.
  6. The simulation model should be on one (1) computer.
  7. The other parts of the system will be IOPs that is Input/Output Processors.
  8. All of the Hardware (Aircraft Parts) will talk with there perspective IOP ie RSS_IOP, NAV_IOP, DISPLAY_IOP, etc. via embedded microprocessors via USB.
  9. On Hardware (Aircraft Parts) rule 1. DO NO HARM. Before you work on a unit find manuals,  pin-outs, etc. GUTTING IS THE LAST RESORT!


And Just Remember This is Just a Start.


One of the things that help me with working on a new unit..  Write you own manual.. Personally I  have several

  • NexGenRegistered 1252 CDU, Computer Display Unit
  • NexGenRegistered Nav_IOP,  Navigation Input Output Processor
  • NexGenRegistered RSS_IOP,   Radio Sub System Input Output Processor
  • NexGenRegistered Protocols 


image  Keep Tuned In More To Come

Cris

  • in reply to DAB

    Just occasionally...LOL I hope you went to the old site and read my RANT. Its a good read but most of friends still a playing with the "Fist Person Shooters" ie pilot only...

  • in reply to phoenixcomm

    Hi Chris,

     

    Did not intend to indicate a change, but just welcome the clarification.

    You do have to admit, setting up virtual seats enable you to go global with the number of seats that can go interactive.

    Even the Captain had to check with Star Fleet occasionally.

     

    Meanwhile keep up the good work, it reminds me of some of my past projects.

    DAB

  • in reply to DAB

    DAB

    This is NOT a change in direction.

    Please Note this manifesto has been my guide since day #1. Here is a link the old web site with my first RANT!
    item #1. let me explain what a seat is: A seat is simply a user so very easily we can go from a single seat / single screen to a F14 with both pilot and reo; a B52 Pilot, Copilot, Radar Navigator (Bombardier), Navigator and Electronic Warfare Officer; or the star ship Enterprise Captain, Science Officer, Chief Dr., Engineer, Communications, Helm, Navigator, Weapons, Nurse, Transporter Control
    Tower no, Interactions between yes

  • Hi Chris,

     

    Nice update.  I agree that having each function broken out opens your design considerably.

    Are you planning to enable multiple concurrent players?  Ala flight team interaction?

    You might also consider a tower control seat to enhance the real time environment of the simulator.

     

    Lots of option with this change.

     

    DAB