|
|
| Line 1: |
Line 1: |
| − | ==ProSim737 System== | + | == ProSim737 System== |
| | + | |
| | ===Introduction=== | | ===Introduction=== |
| − | In the cockpit, pilots interact with an aircraft in various ways. There are switches, dials and levers to interact with the aircraft and there are indicators and gauges to read back states. All of these elements are represented in ProSim737 System. For the software to operate correctly, ProSim737 System needs to know exactly how these elements relate to your specific cockpit hardware.
| |
| − |
| |
| − | Configuring ProSim737 System is the process of assigning each of these elements to the physical switches, indicators, levers and dials that you have in your cockpit.
| |
| − |
| |
| − | Foremost, ProSim737 System is the multifunctional module that performs the following tasks:
| |
| − | *Performs as a central hub for all ProSim737 Suite modules.
| |
| − | *Manages the simulation of aircraft systems.
| |
| − | *Features a webserver for the Instructor Operating Station (IOS).
| |
| − | *Distributes audio and navigational data to relevant modules.
| |
| − | *Interacts with the image generator.
| |
| − | *Validation of the user license key for the ProSim737 Suite.
| |
| − | *Manages geographical databases.
| |
| − | *Connectivity of cockpit hardware.
| |
| − | *Performs ProSim737 Suite version update.
| |
| − | *Automates ProSim737 Suite updates.
| |
| − | *Provides debugging tools for connected hardware.
| |
| − | *Extensive hardware and software debugging tools provided.<br>
| |
| − | ===Module instances and directory names===
| |
| − | * Only one instance of ProSim737 System is allowed in the simulator setup.
| |
| − | * ProSim737 Systems needs direct access to simulator platform and therefore must run on the primary computer.
| |
| − |
| |
| − | ===ProSim737 General===
| |
| − | ====First start====
| |
| − | # Double click the file Prosim737.exe from the ProSim737 directory on the primary computer for the ProSim737 System module to start.
| |
| − | # During initial startup of ProSim737 System, firewall warnings might be displayed. ProSim737 System starts a built in web server and connects to the online ProSim-AR servers for license validation, so this is a normal procedure.
| |
| − | # If no license key has been entered previously ProSim737 System will display a license key input screen on startup. Enter a valid license key or select 30 minutes free trial and press OK to continue. Internet connection is required for this step.
| |
| − | # Read Terms and Conditions as displayed. Agree to continue or abandon use.
| |
| − | # First the splash screen appears for a couple of seconds after which the ProSim737 System Interface is displayed
| |
| − |
| |
| − | ====ProSim737 System window====
| |
| − | * The ProSim737 System Interface always displays a horizontal top navigation with the items “File”, “Config” and “Help”.
| |
| − | * Below is a horizontal navigation bar dividing the screen in tabs. The '''Main''' tab displays an overview of connected cockpit hardware and software, the other tabs display the current state of cockpit switches, indicators, gauges, gates, etc. These tabs are not used for making configuration changes, they are only used to display the current state of elements or to change the value of a switch in the software if no hardware switch for that particular function is connected.
| |
| − | * While running your simulator software, verify that the ‘Simulator Connection’ on the main tab states "Connected". If not check FSUIPC installation.
| |
| − |
| |
| − | ====Config->Configuration->Main====
| |
| − |
| |
| − | Used for general configuration settings. Recommended after initial setup.
| |
| − |
| |
| − | ====Config->Configuration->Drivers====
| |
| − |
| |
| − | Used to enable and configure drivers for cockpit hardware.
| |
| − |
| |
| − | ====Config->Configuration->Combined config====
| |
| − |
| |
| − | Used to assign hardware indicators, gauges and switches to software functions.
| |
| − |
| |
| − | ====Config->Database====
| |
| − | * In the Navigraph database section - verify that the Navigraph database is loaded (installation described in the [[Installation]] chapter of this manual) - if not, reinstall.
| |
| − | * In the Terrain data section - verify that the terrain database is available - if not, reinstall.
| |
| − | * In the Scenery database section - select the path to the installation directory from your back-end simulator (Lockheed Martin Prepar3D® or FSX) and click on "Build database". Remember to repeat this step after making changes to your installed scenery.
| |
| − |
| |
| − | ====Help > Updates====
| |
| − |
| |
| − | Opens the ProSim737 version manager, which displays the current installed version number and the expiry date of the update subscription and contains 3 tabs:
| |
| − | * '''Releases''' - Used to download and install regular ProSim737 updates
| |
| − | * '''Add ons''' - Used to download ProSim737 Flight Model updates and other add-ons
| |
| − | * '''Pre-releases''' - Used to download and install ProSim737 beta releases
| |
| − |
| |
| − | ProSim737 System will notify when new releases become available (depends on the setting in Config->Configuration->Main/Updates). In order to install a new version, click on install next to the desired version in the ProSim737 version manager. Update will be automatically downloaded and distributed to all the connected ProSim737 modules.
| |
| − |
| |
| − | In between releases, the ProSim-AR team constantly creates beta releases for testing purposes. Beta releases may be installed however can contain untested functionality. To receive notifications for new beta releases check the box ‘Monitor beta releases’ in the Config->Configuration->Main
| |
| − |
| |
| − | ===Hardware Configuration===
| |
| − | Cockpit hardware can be divided into two groups:
| |
| − |
| |
| − | ====Specific hardware====
| |
| − | Specific hardware are modules that can tell ProSim737 exactly what the state of specific switches / function is. These are usually plug and play panels like radios and MCPs. This hardware requires little configuration.
| |
| − | Examples are all SimWorld, CPFlight, Cockpitsonic components as well as some FDS cockpit modules.
| |
| − |
| |
| − | ====Generic hardware====
| |
| − | Generic hardware are parts that provide a set of input and output signals which don’t have a specific function. These boards are usually generic I/O boards. With this hardware, ProSim737 needs to be configured in detail.
| |
| − | Examples are FDS SYS boards, Phidgets boards, OpenCockpits hardware and joystick cards.
| |
| − |
| |
| − | ===Supported hardware (click on link for instructions)===
| |
| − |
| |
| − | ====[[CPflight Hardware|CPFlight]]====
| |
| − |
| |
| − | ====[[FDS Hardware|Flightdeck Solution]]====
| |
| − |
| |
| − | ====[[OpenCockpits Hardware (SIOC)|OpenCockpits]]====
| |
| − |
| |
| − | ====[[SimWorld Hardware|SimWorld]]====
| |
| − |
| |
| − | ====[[CockpitSonic Hardware|CockpitSonic]]====
| |
| − |
| |
| − | ====[[Sismo Hardware|Sismo]]====
| |
| − |
| |
| − | ====[[Flight Illusion|Flight Illusion]]====
| |
| − |
| |
| − | ====[[DirectInput devices (Game Controllers)|DirectInput devices (Game Controllers)]]====
| |
| − |
| |
| − | ====[[Phidgets|Phidgets]]====
| |
| − |
| |
| − | ====[[PoKeys|Pokeys]]====
| |
| − |
| |
| − | Flight Simulator Center / Poldragonet
| |
| − |
| |
| − | GoFlight
| |
| − |
| |
| − | Pololu
| |
| − |
| |
| − | FlyEngravity
| |
| − |
| |
| − | Matrix Orbital
| |
| − |
| |
| − | === Notes ===
| |
| − | ====8.33Khz====
| |
| − | As of 2.07b8, ProSim737 supports 8.33Khz voice spacing channels.
| |
| | | | |
| − | Note the following:
| + | ProSim737 System is the main server module of the ProSim737 suite. All other modules connect to this application in order to communicate with one another. |
| − | # Requires FSUIPC 5.132b or later.
| + | The main use of this application, besides being a central hub for the suite, is to configure ProSim as well as checking the status of hardware and connected modules. |
| − | # Will only work with P3D V4 if using MSFS
| |
| − | # You need to enable this option on IOS -> Cockpit Setup -> Options
| |
| − | # Not all hardware will support it (thus the option to use it). Any hardware handling the frequency internally will not work unless 833 is supported by the hardware. Script based radios may not work either.
| |
| − | And NO we cannot do anything about the not supported hardware. Contact your hardware supplier.
| |
| | | | |
| − | This new functionality will handle the frequency in hz, instead of the old BCD format.
| + | IMAGE OF MAIN INTERFACE |
| | | | |
| | + | ===File=== |
| | + | ====License==== |
| | | | |
| − | ====Active Sky==== | + | ===Config=== |
| − | ProSim supports Active Sky as weather engine.
| + | Under this tab you will find the different configuration settings. |
| − | To have AS weather radar depicted on ProSim Display you need to add the following line to your FSUIPC.ini file ([General] section):
| |
| | | | |
| − | ASNwxRadarPath = <YOUR_PATH_TO_PROSIM_SYSTEM_FOLDER>/radar.bin
| + | ====Configuration==== |
| | + | blablabla |
| | | | |
| − | It is also important to configure detailed clouds in FSX/P3D
| + | ====Import configuration==== |
| | + | blablabla |
| | | | |
| − | P3D:
| + | ====Database==== |
| | + | blablabla |
| | | | |
| − | [[file:Detailed_clouds_p3d.png]]
| + | ====Audio addons==== |
| | + | blablabla |
| | | | |
| − | FSX:
| + | ====Company routes==== |
| | + | blablabla |
| | | | |
| − | [[file:Detailed_clouds_fsx.png]]
| + | ====Import from V2==== |
| − | [[Category:ProSim737 Manual]]
| + | blablabla |
ProSim737 System is the main server module of the ProSim737 suite. All other modules connect to this application in order to communicate with one another.
The main use of this application, besides being a central hub for the suite, is to configure ProSim as well as checking the status of hardware and connected modules.
Under this tab you will find the different configuration settings.
