652
edits
OpenRadarGuide: Difference between revisions
Jump to navigation
Jump to search
m
→OpenRadar-Welcome - Settings: Update FGCom settings + add FlightPlan Server
m (→Operating: Replacing OR-total picture with an uptodate version) |
m (→OpenRadar-Welcome - Settings: Update FGCom settings + add FlightPlan Server) |
||
| Line 62: | Line 62: | ||
=== OpenRadar-Welcome - Settings === | === OpenRadar-Welcome - Settings === | ||
These settings are grouped into 3 parts: | These settings are grouped into 3 parts: | ||
===='''1) | ===='''1) FGCom (Radio/Voice Communication)'''==== | ||
:OpenRadar can support up to 4 instances of FGcom in 2 ways: | :OpenRadar can support up to 4 instances of FGcom in 2 ways: | ||
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window) | :#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window) | ||
| Line 69: | Line 69: | ||
:You select these modes of operation by the “'''FgComMode'''” selection: | :You select these modes of operation by the “'''FgComMode'''” selection: | ||
<br /> | <br /> | ||
:''' | :'''1a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar | ||
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used: | ::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used: | ||
::'''Path:''' Here you define where your FGcom is installed. | ::'''Path:''' Here you define where your FGcom is installed. | ||
| Line 86: | Line 86: | ||
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*) | |on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*) | ||
|} | |} | ||
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar''' | ::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar, see 1b''' | ||
</small> | </small> | ||
::'''Executable:''' Here you define the program-name that shall be started | ::'''Executable:''' Here you define the program-name that shall be started | ||
:::*For Windows: "fgcom.exe" or "anyName.bat" | :::*For Windows: "fgcom.exe" or "anyName.bat" | ||
:::*for Linux: "fgcom" or "anyName.sh" | :::*for Linux: "fgcom" or "anyName.sh" | ||
:::*OSX: ''again for OSX this | :::*OSX: ''again for OSX this does not apply, see 1b'' | ||
::'''Server:''' | :::Do not forgett to mark "FGCom3" if you are using the new FGCom versions (e.g. with FGFS ver.3.0) | ||
:: | ::'''Server:''' As of today there is only one FGCom-server available that also supports FGFS ver.3.0: fgcom.flightgear.org | ||
:::''You still may be using fgcom01.flightgear.org in a group in that all users can uses this server'' | |||
::'''Client:''' must always be “localhost” | ::'''Client:''' must always be “localhost” | ||
::'''FGcom Ports:''' The here defined values are crucial for the operation because: | ::'''FGcom Ports:''' The here defined values are crucial for the operation because: | ||
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !! | ::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !! | ||
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar | ::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar | ||
::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle! | :::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle! | ||
:::::e.g. 16661,16662 | :::::e.g. 16661,16662 | ||
<br /> | <br /> | ||
:''' | :'''1b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port. | ||
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.: | ::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.: | ||
::*'''Client:''' localhost | ::*'''Client:''' localhost | ||
| Line 109: | Line 109: | ||
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)'' | ::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)'' | ||
<br /> | <br /> | ||
:''' | :'''1c) OFF:''' No FGcom support (e.g. using MUMBLE or similar) | ||
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the fields | ::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the FGCOM-fields. | ||
===='''2) | ===='''2) Multiplayer Chat'''==== | ||
:Here you find the server and connection port of FlightGears multiplayer server. It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change. | :Here you find the server and connection port of FlightGears multiplayer server. It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change. | ||
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http:// | :In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpserver15.flightgear.org/mpserverstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals". | ||
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''. | :'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''. | ||
===='''3) METAR'''==== | ===='''3) Flightplan exchange'''==== | ||
You must define the Server for the FlightPlan data. So activate "enable flightplan exchange" and insert the server address: | |||
<br>http://h2281805.stratoserver.net/FgFpServer/ | |||
===='''4) METAR'''==== | |||
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts. | :OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts. | ||
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source! | :If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source! | ||